Edge transport node may become stuck indefinitely in Maintenance Mode

Products

• VMware NSX

Issue/Introduction

During an NSX upgrade (e.g., to version 4.2.3), an Edge transport node may become stuck indefinitely in Maintenance Mode. This state prevents normal management and data plane operations. 

• NSX Edge transport node status remains in "Maintenance Mode" in the NSX Manager UI.
• CLI command get managers on the affected Edge returns: No managers configured.
• API or UI status reflects:
  • state: REGISTRATION_TIMEDOUT
  • sub_system_id: TRANSPORT_NODE_CONFIG_STATE, state: MPA_DISCONNECTED
  • • Internal files /etc/vmware/nsx/appliance.xml or mpaconfig may be empty or corrupted.

Environment

• VMware NSX 4.x
• VMware Cloud Foundation (VCF)

Cause

The management plane connectivity fails to initialize because essential configuration parameters are missing or corrupted within the local appliance.xml and mpaconfig files. Without these parameters, the management plane agent cannot resolve cluster trust anchors or address vectors needed to communicate with the NSX Manager cluster.

Resolution

Redeploy the corrupted NSX Edge transport node. This process replaces the virtual machine, regenerates the configuration files, and re-establishes the management plane binding.

1. Identify the UUID of the corrupted Edge node from System > Fabric > Nodes > Edge Transport Nodes.
2. Open a REST API client (such as Postman).
3. Configure Basic Authentication using the admin account for the NSX Manager.
4. Execute the redeploy action using the following endpoint:
   • Method: POST
   • URL: https://<nsx-manager-ip>/api/v1/transport-nodes/<transport-node-id>?action=redeploy
5. Monitor the NSX Manager UI and vCenter Tasks to verify the new VM is deployed and the status transitions to "Success."

Note for VCF Customers: Ensure the release is post-GA before referencing specific fix versions. To stay updated on the status of this issue, subscribe to this article by following the steps in