Transport Nodes Status in the NSX-T UI displays "Not Available"
search cancel

Transport Nodes Status in the NSX-T UI displays "Not Available"

book

Article ID: 324398

calendar_today

Updated On:

Products

VMware NSX Networking

Issue/Introduction

Symptoms:
  • Transport Nodes Status in the NSX-T UI displays "Not Available" 
  • Rebooting the Transport Node doesn't resolve the issue.
  • The Transport Node connections the NSX Manager and NSX Controller are "Up".
  • The REST API to retrieve the status of the Transport Node display error similar to:
GET api/v1/transport-nodes/{TRANSPORT_NODE_ID}/status'
{
  "httpStatus" : "NOT_FOUND",
  "error_code" : 600,
  "module_name" : "common-services",
  "error_message" : "The requested object : TransportNodeStatus/XXXXXXXXX-XXXX-XXXX-XXXX-XXXX could not be found. Object identifiers are case sensitive."
}
  • There is no impact and everything is working as expected on the Transport Node.
  • In case of an Upgrade, NSX-T precheck will report errors on the affected Edge Transport Nodes:
Edge transport node status information not found from MP data for edge node <Edge TN ID>


Environment

VMware NSX-T Data Center
VMware NSX-T
VMware NSX-T Data Center 2.x

Cause

The issue is caused by a race condition that may occur when the Transport Node is created or modified.
When a Transport Node is created or modified, a notification is sent to the NSX Manager which in turn queries the status of the Transport Node via API. Under some circumstances, the notification doesn't reach the NSX Manager and the status of the Transport Node is not queried and this result in this TN status displaying "Not Available".

Resolution

This issue is resolved in:

VMware NSX-T Data Center 2.5, available at VMware Downloads .
VMware NSX-T Data Center 3.0, available at VMware Downloads .


Workaround:
To workaround this issue, restart the proton service on all 3 NSX Managers to force the status of the Transport Nodes to be queried again:
1.  Connect to the one NSX Manager in root mode.
2.  Run the following command to restart proton: 
 #/etc/init.d/proton restart
3.  Wait for the cluster to stabilize
 #nsxcli -c get cluster status
4.  Once the cluster is stable repeat from step 1. for the next NSX Manager.