NSX UI Shows Default Transport Zones Down for vlan and overlay transport zones

Products

• VMware NSX

Issue/Introduction

An Edge Transport Node that is in degraded state will trigger the coresponding Transport Zone status to be degraded.  However the affected Edge Node may still function normally with data plane services.

In System->Fabric->Transport Zones, one or more transport zones has a Status of Down.

Clicking on the transport zone's Down Status provides a status dialog.  A listed Edge node will also have a Down state

Selecting System->Fabric->Nodes->Edge Transport Nodes, the same listed Edge from the affected transport zone will have a Node Status of Down

 

Environment

VMware NSX

Cause

NSX components running on the Manager and transport nodes can become unresponsive, causing incorrect status reporting in the UI.

Resolution

Recommended Actions:

Restart the proton service on NSX Managers: A known issue in some older NSX-T versions was a race condition that could be resolved by restarting the proton service on all NSX Managers to force an update of the node status.

• SSH to one NSX Manager as root.
• Run the following command   /etc/init.d/proton restart
• Wait for the cluster to stabilize by running nsxcli -c get cluster status
• Repeat on the other managers.

Restart the nsx-proxy service on transport nodes: A race condition can also cause management connection issues on a transport node.

• Log in as root to the transport node (ESXi host or Edge).
• Run /etc/init.d/nsx-proxy restart  

Note:   Performing a reboot of the NSX Managers and/or the affected Edge Node will also resolve this issue.