Preparation of NSX on host fails with validation error 26211

Products

• VMware NSX

Issue/Introduction

When attempting to prepare or configure VMware NSX on a host, the task fails with a validation error. The user interface displays a specific error indicating that a node with the assigned IP address is in a pending cleanup state.

Environment

VMware NSX-T

Cause

The NSX Manager database contains a stale entry for a previously deleted Transport Node that occupied the same IP address. The management plane's internal index has not completed the cleanup or synchronization, leading to a false positive validation block during the registration of the new node.

Resolution

Follow these steps to synchronize the NSX Manager database and clear the stale validation state:

1. Perform Search Re-indexing:

   • Log in to the NSX Manager CLI as admin.

   • Execute the re-index command for both the manager and policy directories:

     • start search resync manager

     • start search resync policy

   • Wait approximately 15–20 minutes for the re-indexing process to complete across all cluster nodes.

2. Verify Cleanup Status:

   • Navigate to System > Fabric > Nodes > Host Transport Nodes in the NSX UI.

   • Ensure that any stale entries or "Orphaned" nodes associated with the target IP address are no longer visible.

3. Rolling Reboot of NSX Manager Cluster:

   • If re-indexing does not clear the 26211 error, a rolling reboot of the NSX Manager cluster is required to refresh internal cache and services.

   • Reboot the managers one at a time via the UI or CLI (reboot command).

   • CRITICAL: Wait for each manager node to become fully "Healthy" and for all services to be "Up" (typically 7–10 minutes) before proceeding to the next node.

   • Start with the non-leader nodes and finish with the cluster leader.

4. Retry Host Preparation:

   • Once the cluster is stable, navigate back to the Host Transport Node configuration.

   • Attempt to "Reconfigure" or "Install" NSX on the impacted host.

Additional Information

 

• If connectivity to the UI is interrupted during reboots, use https://<Manager_IP>/login.jsp?local=true to access the local authentication page.

• Refer to Broadcom KB 317145 for Edge and Host transport node best practices.