Validation Error: Node with Same IP Already Exists

Products

• VMware NSX

Issue/Introduction

During VMware NSX host preparation or configuration workflows, you may encounter a validation error stating that a node with the same IP already exists. This error can prevent hosts from being prepared, removed, or reconfigured in NSX and may block cluster-level operations.

This issue is commonly observed after ESXi host lifecycle changes such as reinstallation, replacement, or recovery activities

Environment

VMware NSX

Cause

This validation error occurs due to stale NSX-T node entries remaining in the system after changes to ESXi hosts. Common scenarios include:

• ESXi hosts being reinstalled or replaced without fully removing NSX beforehand

• Host UUID changes while NSX Manager still retains old references

• Duplicate node records in NSX Manager referencing the same IP address or UUID

These stale entries cause NSX Manager to detect conflicting node identities, resulting in validation failures during host preparation or removal

Resolution

To resolve the issue, stale NSX node references must be cleared and NSX Manager must re-synchronize its internal state.

Important: Perform these steps during a maintenance window and ensure NSX Manager backups are available.

 
1. Re-synchronize NSX Search Index

On each NSX Manager node, run the following commands to re-sync policy and manager search:

start search resync policy

start search resync manager

 

Ensure the commands complete successfully on all NSX Manager nodes in the cluster.

2. Allow UI Re-Indexing to Complete

• After the resync, allow sufficient time for the NSX UI to re-index.

• Refresh the NSX UI and verify that previously greyed-out options are now accessible.

• Confirm that the affected cluster and hosts are visible and selectable.

3. Detach Policy from the Cluster

• Navigate to the affected cluster in the NSX UI.

• Detach any NSX policies associated with the cluster to unblock host-level operations.

4. Remove NSX from the Affected Host

• Use the “Remove NSX” option in the UI to fully remove NSX configuration from the host.

• This process cleans up stale configuration entries and clears duplicate node references

5. Reattempt Host Preparation

• Once cleanup is complete, proceed with normal host preparation or configuration.

• Verify that the validation error no longer occurs.

These steps remove stale node records, resolve duplicated IP/UUID references, and allow host preparation workflows to continue successfully.

Additional Information

Additional Information

Validation error: Node with same IP already exists during NSX host preparation
NSX host remains in a partially configured or stale state after ESXi host changes

Impact / Risks

If this validation error is not resolved:

• NSX host preparation and removal workflows will fail or remain blocked.

• ESXi hosts may remain partially configured in NSX, preventing further configuration.

• Cluster-level NSX policies and transport configurations cannot be modified or detached.

• Automation, upgrades, and lifecycle operations involving NSX may be disrupted.

• Inconsistent NSX Manager inventory data may lead to additional validation or configuration errors.