Adding host to NSX prepared cluster through SDDC manager gets stuck at "Prepare Transport Node Collection"

Products

• VMware NSX
• VMware SDDC Manager

Issue/Introduction

• This ESXi host was removed from vCenter without first removing from NSX.
  
  
• Host addition to the cluster in SDDC manager fails at below step,
  
  
  
• NSX manager UI shows the concerned host in 'validation error' state and on clicking the error we see below message which indicates on host node information already present in the system.
  

  Validation Errors
  601: The object HostTransportNode//infra/sites/default/enforcement-points/default/host-transport-nodes/###-###-###-##-########-####-####-####-############ is already present in the system.

Environment

VMware NSX 4.2.x

VMware SDDC Manager

Cause

When an ESXi host is removed directly from vCenter without first removing NSX, it can result in entries for that host to remain in the NSX database.

Resolution

Reconfigure NSX in the host from NSX UI by selecting the host (system-->fabric-->Hosts) and clicking on 'CONFIGURE NSX'.

Additional Information

If the issue still persist, please refer below KBs,

Installing or Upgrading NSX on an ESXi host fails reporting the node already exists

Add cluster failure with error "Unable to create transport node collection with profile"

Failed to add host to Cluster in SDDC Manager at "Prepare Transport Node Collection

Adding Host through SDDC fails with "Unable to create transport node collection with profile abcd on compute collection XYZ through nsxmanager"