NSX is Reporting TN disconnected from MPA for Orphaned Objects

Products

• VMware NSX

Issue/Introduction

• ESXi Transport Nodes without "discovered node“ (orphaned transport node objects)
  
  <HOSTNAME>_##.###.###.###
<HOSTNAME> = 2bf089b3-###-###-###-###-ccc91737345b has no fabric node ID
<HOSTNAME> = ba3acfa2-###-###-###-###-320706fa4d59 has no fabric node ID
<HOSTNAME> = 05040fbb-###-###-###-###-bd15c6c21c72 has no fabric node ID
<HOSTNAME> = 3da2ef77-###-###-###-###-8a6398af741e has no fabric node ID
<HOSTNAME> = 4f5a6160-###-###-###-###-2fc1cac6b688 has no fabric node ID
<HOSTNAME> = 8860c2d8-###-###-###-###-b5c8fc2f5f4a has no fabric node ID
<HOSTNAME> = 6f1fdba8-###-###-###-###-98f2adac06ef has no fabric node ID
<HOSTNAME> = 29f272ad-###-###-###-###-b40a7752cd53 has no fabric node ID
<HOSTNAME>_##.###.###.###
  
  

• You may see an alarm with:
  • Description
    Management channel to Transport Node <HOSTNAME> (##.###.###.###) is down for 15 minutes.
    Recommended Action
    Ensure there is network connectivity between the Manager nodes and Transport node <HOSTNAME> (##.###.###.###) and no firewalls are blocking traffic between the nodes. On Windows Transport nodes, ensure the nsx-proxy service is running on the Transport node by invoking the command `C:NSX\nsx-proxy\nsx-proxy.ps1 status` in the Windows PowerShell. If it is not running, restart it by invoking the command `C:NSX\nsx-proxy\nsx-proxy.ps1 restart`. On all other Transport nodes, ensure the nsx-proxy service is running on the Transport node by invoking the command `/etc/init.d/nsx-proxy status`. If it is not running, restart it by invoking the command `/etc/init.d/nsx-proxy restart`.
    Reported by Node
    <HOSTNAME> (##.###.###.###)

 

• TN disconnected from MPA / MPA is DOWN
<HOSTNAME>_##.###.###.###
2025-01-20T15:12:11Z: <HOSTNAME> = 4f5a6160-###-###-###-###-2fc1cac6b688 (UNKNOWN): MPA is DOWN = Client has not responded to {2} consecutive heartbeats. Port {1234} between Host to NSX Manager must be open, Please check underlay physical firewalls and host hypervisor firewalls for troubleshooting.
2025-01-20T15:15:00Z: <HOSTNAME> = 8860c2d8-###-###-###-###-b5c8fc2f5f4a (UNKNOWN): MPA is DOWN = Client has not responded to {2} consecutive heartbeats. Port {1234} between Host to NSX Manager must be open, Please check underlay physical firewalls and host hypervisor firewalls for troubleshooting.
2025-01-20T14:53:23Z: <HOSTNAME> = 6f1fdba8-###-###-###-###-98f2adac06ef (UNKNOWN): MPA is DOWN = Client has not responded to {2} consecutive heartbeats. Port {1234} between Host to NSX Manager must be open, Please check underlay physical firewalls and host hypervisor firewalls for troubleshooting.
2025-01-20T15:18:07Z: <HOSTNAME> = 29f272ad-###-###-###-###-b40a7752cd53 (UNKNOWN): MPA is DOWN = Client has not responded to {2} consecutive heartbeats. Port {1234} between Host to NSX Manager must be open, Please check underlay physical firewalls and host hypervisor firewalls for troubleshooting.
2025-07-07T13:20:32Z: <HOSTNAME> = 76515a0f-###-###-###-###-1256aa035b5b (UNKNOWN): MPA is DOWN = Client has not responded to {2} consecutive heartbeats. Port {1234} between Host to NSX Manager must be open, Please check underlay physical firewalls and host hypervisor firewalls for troubleshooting.

  
  
• Check under Fabric > Hosts > Other Nodes for orphaned hosts

Environment

VMware NSX

Cause

Host was removed from vCenter inventory before properly decommissioning the host from NSX first.

Resolution

If available in the UI, check the host and click Remove NSX > Force Delete. 

 

If force delete from the UI does not work, please follow KB below for api calls to remove the host. 

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

For further assistance please open a Broadcom Support Case and upload all 3 NSX Manager log bundles with a log age of 'ALL, so we can review and assist with removing the stale host. 

Additional Information

Best Practice for Decommissioning an NSX-Prepared ESXi Host to Avoid Stale Entries

Creating and managing Broadcom support cases