NSX Edge upgrade from 4.0.0.1 to 4.2.2.1 is failing due to VM not receiving IP address in vCenter.

Products

• VMware NSX

Issue/Introduction

• NSX Edge upgrade from 4.0.0.1 to 4.2.2.1 fails with below error as seen from NSX UI.
  
  

  Upgrade Agent on Edge node 9b4#####-81##-41##-aa##-30d######c78 is unreachable. Restart the Upgrade agent service and check network connectivity.
  Management plane connection status of the edge transport node 9b4#####-81##-41##-aa##-30d######c78 is DOWN.
  
  Cannot upgrade edge node 9b4#####-81##-41##-aa##-30d######c78 , has errors Errors = [{"moduleName":"upgrade-coordinator","errorCode":30249,"errorMessage":"Upgrade Agent on Edge node 9b4#####-81##-41##-aa##-30d######c78 is unreachable. Restart the Upgrade agent service and check network connectivity."}, {"moduleName":"upgrade-coordinator","errorCode":30205,"errorMessage":"Management plane connection status of the edge transport node 9b4#####-81##-41##-aa##-30d######c78 is DOWN."}, ] .

• Edge VM is Powered On and there are no IP assigned in vCenter.
  
  
• Powering off the Edge VM is taking time and stuck at 0%.

Environment

VMware NSX 4.x

Resolution

Migrate the Edge VM to a different ESX host and resume the Edge upgrade.

Note : Ensure VLAN/MTU config on TORs where the Edge may be vMotioned is consistent. Define the DRS vm/host rules such that the underlying hosts for the edge VM are on the same L2 domain and that the BGP/OSPF neighbors or static route next hops defined on Tier0 are reachable from all the hosts where the Edge may be vMotioned.

Additional Information

If the above steps in this KB do not resolve the issue, raise a support ticket with Broadcom support selecting NSX as the product. 

Handling Log Bundles for offline review with Broadcom support.

• Collect Support Bundles for Troubleshooting VMware NSX
• Uploading files to cases on the Broadcom Support Portal
• Creating and managing Broadcom support cases