Duplicate or Phantom Transport Nodes appear in NSX Manager UI
search cancel

Duplicate or Phantom Transport Nodes appear in NSX Manager UI

book

Article ID: 408798

calendar_today

Updated On:

Products

VMware NSX

Issue/Introduction

The NSX Manager user interface (UI) displays duplicate entries for a Transport Node (TN) or a "phantom" node where one entry contains incorrect IP addresses belonging to another host.

  • One host entry shows correct IPs but displays "Validation Error".

  • Options in the host's "hamburger" (context) menu may be greyed out.

  • A duplicate entry appears with the name of Host A but the IP address of Host B.

  • Running get transport-nodes status in the NSX CLI returns the correct, non-duplicated information.

Environment

VMware NSX 4.x

VMware Cloud Foundation (VCF)

Cause

  • A defect in the synchronization between the Compute Manager (vCenter) and NSX Manager can cause orphaned or duplicate Transport Node objects to persist in the NSX database. 

Resolution

There are two methods to resolve this inconsistency.

Method 1: UI-Based Cleanup (Recommended)

    1. Place the impacted ESXi hosts in Maintenance Mode in vSphere.

    2. Drag the hosts out of the cluster to the Datacenter level. This triggers NSX to un-prepare the hosts.

    3. In the NSX Manager UI, navigate to System > Fabric > Nodes > Host Transport Nodes.

    4. Identify any leftover or "phantom" entries for the hosts. Use the Delete or Force Delete option to remove these objects.

    5. In the NSX UI, verify the Compute Manager connectivity status is "Up".

    6. Drag the hosts back into the cluster in vSphere.

    7. Monitor the NSX UI to ensure the hosts successfully transition to a "Success" state.

Method 2: REST API Update If the UI method does not clear the entries, use the NSX API to manually correct the ip_address and display_name fields:

    1. Retrieve the TN configuration: GET https://<NSX-Manager-IP>/policy/api/v1/infra/sites/default/enforcement-points/default/host-transport-nodes/<TN-ID>

    2. Copy the JSON payload to a text editor and correct the ip_address and display_name.

    3. Update the TN: PUT https://<NSX-Manager-IP>/policy/api/v1/infra/sites/default/enforcement-points/default/host-transport-nodes/<TN-ID>

Note: For VCF environments, subscribe to this article to receive updates on fix status. Refer to How to subscribe to Knowledge Articles.

Additional Information

Powered by Wolken Software