Unable to install the add the host back to cluster as error says node id already exists
search cancel

Unable to install the add the host back to cluster as error says node id already exists

book

Article ID: 420783

calendar_today

Updated On:

Products

VMware NSX

Issue/Introduction

  • vMotion of a VM is blocked with error.
  • While checking transport node found Validation error as follows-  

          Validation Errors 60%: The object[X] Host TransportNode//infra/sites/default/points/default/host-transport- nodes/xxx-xxx-xxx-xxx-xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxxxxxx-xxxxxxx is already present in the system

Environment

VMware NSX

Cause

If an ESXi host is removed directly from vCenter without properly uninstalling or detaching NSX components beforehand, NSX does not receive the required cleanup signals. As a result, the host’s associated transport node records, configuration entries, and identifiers remain in the NSX Manager database. These leftover (stale) entries can later cause conflicts when attempting to re-add or re-register the same host, as NSX still believes the host exists in its inventory. 

Resolution

  1. Place the host in maintenance mode.
  2. Take the host out of cluster.
  3. From NSX UI, System > Fabric > Hosts > Other hosts and verify host is not part of NSX
  4. If the ESXi host appears in this list, select it, choose Delete NSX, and then proceed with Force Delete.
  5. Once the force delete is completed, the ESXi host can be successfully re-added to vCenter.

                      

 

Additional Information

Please refer to the following for additional reference- Installing or Upgrading NSX on an ESXi host fails reporting the node already exists