Edge node deployment fails with Registration Pending or Registration Timeout.

Products

• VMware NSX

Issue/Introduction

During the deployment of an NSX Edge node configured with a static management IP address, the deployment may fail with one of the following symptoms:

• The Edge remains in a Registration Pending state.
• The deployment eventually fails with Registration Timeout.
• In a multi-Edge deployment, one Edge may deploy successfully while another remains stuck in Registration Pending.
  Environment

Environment

VMware NSX

Cause

A VLAN or trunk misconfiguration prevents ARP resolution of the default gateway. Because the Edge cannot resolve the gateway's MAC address, it cannot send traffic outside its local subnet to reach the NSX Manager.

Resolution

1. Access the Edge VM console.
2. Verify the management network configuration, including:
   
   
   • IP address
   • Subnet mask
   • Default gateway
   
   
   
3. Confirm the Edge can reach its default gateway by pinging it from the console.
4. If the ping fails, verify the ARP table with this command: arp-table to confirm that the default gateway has been resolved.
5. Verify the physical network configuration, including:
   
   
   • The management VLAN exists end-to-end.
   • The ESXi host uplinks are connected to switch ports that allow the management VLAN.
   • The required VLAN is permitted on all trunk ports between the ESXi host and the physical network.
   • The port group VLAN ID matches the intended management VLAN.
6. After correcting the VLAN or trunk configuration and restoring connectivity to the default gateway, redeploy the Edge node or retry the registration process.