Standby Edge on Degraded state post a Failover

Products

• VMware NSX

Issue/Introduction

• After performing failover of the active edge node, the associated Tier-1 router shows "No Standby" for its Edge Node configuration in the NSX UI (manager plane). Navigate to system>fabric>node
  
• 
• When attempting to retrieve the Load Balancer status via CLI, using the following error is returned:

  get load-balancer <lb-uuid> status
  
  24304: Internal Error : Query LB engine failed.

• Upon running the diagnostic command  on the affected Edge Node, it is observed that the Load Balancer processes are not running.

  get loadbalancer <lb-uuid> diagnosis

Environment

VMware NSX

Cause

 The primary cause of the LB Docker container failure to start is the presence of stale containers or residual state from previous Load Balancer instance on the affected Edge Node.

Resolution

 To resolve the issue and bring the LB Docker container online on the standby Edge, follow these steps:

1. Toggle Maintenance Mode:
   • Place the impacted Edge Node into Maintenance Mode.
   • After a brief period (e.g., 30-60 seconds), take the Edge Node out of Maintenance Mode. 
2. Reboot Edge Node (If Issue Persists):
   • If toggling Maintenance Mode does not resolve the problem and the LB Docker container still fails to start, perform a full reboot of the affected Edge Node. A reboot provides a clean slate for all services and Docker containers.