Stale Transport Node alarms for decommissioned hosts in NSX

search cancel

Stale Transport Node alarms for decommissioned hosts in NSX

book

Article ID: 447383

calendar_today

Updated On:

Products

VMware NSX

Issue/Introduction

In the NSX UI, multiple alarms appear in the Alarms section. These alarms refer to transport nodes that no longer exist or have been removed from the environment.

Symptoms:

"Control Channel To Transport Node Down Long" alarm is active.
"Management Channel to Transport Node Down Long" alarm is active.
The referenced host or cluster was removed from vCenter.
Universal search for the Transport Node name shows the node, but clicking it results in "No clusters available."
System > Fabric > Hosts shows no associated hosts in the Other Nodes or Standalone tabs.

Environment

VMware NSX 3.2.x
VMware NSX 4.x

Cause

Stale entries remain in the Corfu database for ESXi hosts that were deleted or decommissioned without first uninstalling NSX. NSX recognizes these entries as active configurations and triggers alarms due to the lack of connectivity.

Resolution

Resolution Steps via GUI:

1. SSH into all three NSX Manager nodes as admin.

2. Run the command:

start search resync all

3. Log out and log back into the NSX UI.

4. Navigate to System > Fabric > Hosts and check the Other Nodes or Standalone tabs. Stale transport nodes should now appear.

5. For each stale host, select the host and choose Delete NSX > Force Delete.

6. After deletion, run this command again on all manager nodes.

start search resync all

7. Confirm the hosts are no longer listed. Alarms should clear automatically.

Resolution Steps via API: If the hosts do not appear in the UI after a resync, use the following API steps:

1. Verify the node state:

GET https://<NSX-Manager-IP>/api/v1/transport-nodes/<Transport-Node-ID>/state

2. If the state is found, execute the deletion:

DELETE https://<NSX-MGR-IP>/api/v1/transport-nodes/<UUID>?force=true&unprepare_host=false

3. Confirm the GET call returns "Object Not Found."

NSX API Guide

Additional Information

If alarms persist, check for stale NSX VIBs on remaining hosts:

esxcli software vib list | grep nsx

Refer to Uninstall NSX from a vSphere Cluster for standard decommissioning procedures.