localhost_access_log.txt.1:2025-07-22T12:58:34.639Z - "GET /nsxapi/api/v1/transport-nodes/e3###################/status HTTP/1.1" 404 181 52 51 +nsxapi.5.log:900256:2025-07-22T23:05:39.249Z INFO L2HostConfigTaskExecutor5 DeploymentProgressServiceImpl FABRIC [nsx@6876 comp="nsx-manager" level="INFO" subcomp="manager"] Updating the DeploymentProgress from: DeploymentProgress [ deploymentType=HOST_TN, operationType=DELETE, progress=8, stateDescription=deployment.progress.tn.delete.waiting_for_host_config_reply, removeNsxFlag=false] to DeploymentProgress [ id=e36##########, deploymentType=HOST_TN, operationType=DELETE, progress=20, stateDescription=deployment.progress.tn.delete.waiting_for_host_config_reply, removeNsxFlag=false]VMware NSX 4.x
Broadcom has prepared two scripts which will detect and cleanup stale TransportNode entries, which is especially helpful for large data centers having 40 or more hosts per cluster.
If you believe these scripts are required for cleaning up stale TransportNode entries , please open a support case with Broadcom Support and refer to this KB article.
For more information, see Creating and managing Broadcom support cases.