ESXi transport node preparation fails with validation error

search cancel

book

calendar_today

VMware NSX

ESXi transport node preparation fails with validation error
Validation Errors : 26164: Transport Node cannot be created or updated because host is not attached to every VDS specified in Transport Node Profile
You have confirmed that the ESXi host is already added to the VDS in the vCenter server and there are no issues
You recently removed the ESXi host out of the cluster and added it back
esxcli software vib list | grep nsx command confirmed there are no NSX vibs present on the host
Running GET https://NSX-Mgr-ip/api/v1/transport-nodes/<UUID>/status API confirms there are some stale entries
The error looks similar to the screenshot below

VMware NSX 4.1.2.5

The issue may arise when a stale ESXi host transport node remains in NSX.

To resolve the issue, remove the stale ESXi transport node by following these steps:

Put the ESXi host into maintenance mode and remove it from the vSphere cluster.
Run the following API to check if the ESXi host exists in NSX:
GET https://NSX-Mgr-ip/api/v1/transport-nodes/<UUID>/status
Run the following API to delete the stale ESXi transport node from NSX:
DELETE https://NSX-Mgr-ip/api/v1/transport-nodes/<UUID>?force=true
Once the host entry is cleaned from NSX, add it back to the vSphere cluster.
Confirm the host is prepared successfully in NSX.

Similar error is reported if the host is not added to VDS : NSX will not prepare a host with message "Transport Node cannot be created or updated because host is not attached to every VDS specified in Transport Node profile."

If the above steps in this KB do not resolve the issue, raise a support ticket with Broadcom support selecting NSX as the product.

Handling Log Bundles for offline review with Broadcom support.

thumb_up Yes

thumb_down No