Operational Defect Database
BugZero updated this defect 38 days ago.
Data sources
All data on this page is proprietary to BugZero® or gathered from public sources
VMware | 91906
Installing NSX on an ESXi host fails reporting the node already exists in NSX
Last update date:
4/11/2024
Affected products:
NSX-T
Affected releases:
No affected releases provided.
Fixed releases:
No fixed releases provided.
Description:
Symptoms
While preparing an ESXi host as a Transport Node the following error is seen Node <node-name> with same ip xxx.xxx.xxx.xxx already exists During host upgrade the following error is observed Failed to get Host status for upgrade unit xxxxxxxx-25d7-4ff4-ba26-xxxxxxxxxxxx due to error Transport node xxxxxxxx-25d7-4ff4-ba26-xxxxxxxxxxx not found An ESXi host was removed from vCenter without first removing it from NSX.The Host is not visible under the Host and Cluster section of the UI.Validate the host is not present under the Standalone hosts tab.An reinstallation of a host fails because IP or name already exists in NSX.An upgrade pre-check may fail and can cause the upgrade process to pause.
Cause
When an ESXi host is removed directly from vCenter without first removing NSX, it can result in entries for that host remaining on NSX.The correct procedure to remove NSX-T from a single host:https://docs.vmware.com/en/VMware-NSX-T-Data-Center/3.2/installation/GUID-52FA28CD-CB47-46C6-9D7B-F006916E3C87.htmlIf the cluster is a security only cluster, is prepared using vLCM or has service insertion installed, it is not possible to detach the transport node profile, in such circumstances, either un-prepare the whole cluster or move the single host out of from the NSX-T prepared cluster to an unprepared cluster in vCenter to remove NSX-T VIBs.
Resolution
This is a known issue impacting VMware NSX.
Workaround
As environments may have reached this problem state by following different steps, there a number of possible workaround options.Scenario 1If a host has been removed from vCenter without removing it from NSX the following steps should be taken before re-adding the host to vCenter1) On the NSX UI, navigate to System -> Fabric -> Hosts -> Standalone2) If the ESX shows present here, select it and click Delete NSX and select Force Delete3) The ESX host can now be re-added to vCenterScenario 2The host does not appear in the Standalone tab of the UI but can be removed via APIGET https://<NSX Mgr IP>/api/v1/transport-nodesDELETE "https://<NSX Mgr IP>/api/v1/transport-nodes/<UUID>?force=true&unprepare_host=false"cURL syntax for 4.x and above:curl -k -H "Content-Type:application/json" -u admin -X DELETE https://<nsx-mgr>/policy/api/v1/infra/sites/<site-id>/enforcement-points/<enforcementpoint-id>/host-transport-nodes/<tn-uuid>?force=true&unprepare_host=falseScenario 3The host does not appear on the UI due to an indexing failure.To correct the search and display the failed node, run the following indexing resync commands on all 3 managers: start search resync policystart search resync manager Then wait for some time, this depends on the size of the environment, allow at least 10 minutes.Then check for the orphaned host again under: System > Fabric > Hosts > ClusterSystem > Fabric > Hosts > Other hostsSystem > Fabric > Hosts > Standalone If the ESXi host is now visible on the UI, it can be safely deleted.Select REMOVE NSX and then the FORCE DELETE option.If none of these methods has resolved the issue, please open a Support Request for further investigation.
