NSX Edge Transport Node Status Displays Down in UI but Up in vCenter | VMware NSX
search cancel

NSX Edge Transport Node Status Displays Down in UI but Up in vCenter | VMware NSX

book

Article ID: 447250

calendar_today

Updated On:

Products

VMware NSX

Issue/Introduction

NSX Edge Transport Node displays a Down status within the NSX Manager UI. However, the Virtual Machine (VM) appears as Up and healthy when you view it in vCenter.

Additional symptoms may include:

  • The overall status in the NSX Manager Overview tab might show as Green, while specific node views show as Down.
  • The discrepancy persists even if you attempt to refresh the UI.

Environment

VMware NSX 

Cause

Issue occurs because the Operations Agent (ops-agent) on the Edge VM is failing to report its status correctly to the Management Plane. The agent service may appear to be running on the CLI but is not communicating with the Manager.

While the VM is operationally functional in the datapath, the Management Plane reflects a Down state because it relies on periodic heartbeats from the ops-agent which are not being received. 

Resolution

To synchronize the status and restore correct reporting in the NSX Manager UI, you must restart the management services on the affected Edge node.

  1. Log in to the NSX Manager UI.
  2. Navigate to System > Fabric > Nodes > Edge Transport Nodes.
  3. Select the affected Edge node and place it into Maintenance Mode.
  4. Log in to the vCenter Server and Reboot the affected Edge VM.
  5. Once the reboot is complete and the services are initialized, take the node out of Maintenance Mode.

 

 

Additional Information

To check the agent status via API before proceeding with a reboot, run the following commands from the NSX Manager CLI (replace #### with the specific Transport Node ID): 

Check the state of the transport node 

curl -k -u admin -X GET "https://127.0.0.1/api/v1/transport-nodes/####/state"

Check the detailed status of the transport node 

curl -k -u admin -X GET "https://127.0.0.1/api/v1/transport-nodes/####/status"

If the ops_agent status in the API output is reported as down despite the node being powered on, follow the reboot steps outlined above.