Destination network is not automatically detected during migration planning

Products

• VMware HCX

Issue/Introduction

• Destination network is not automatically selected during HCX migration planning.
• Network used here is part of HCX network extension.
• The stretched network between the source and destination sites is usually selected automatically while initiating the migration.

 

Environment

VMware HCX

Cause

HCX Manager retrieves compute and network details from vCenter or NSX. If its registration with these components is broken, the inventory may not load with the correct information. Similarly, if the NSX Manager registration with vCenter (Compute Manager) is broken, the same issue can occur.

Resolution

• If the destination network is an NSX segment:
• • Check the vCenter registration in the HCX Admin (9443) page.
  • Check the NSX Manager registration in the HCX Admin (9443) page.
  • Login to NSX Manager and confirm that the Compute Manager connectivity is successful.
  • If any errors or failed states are found, re-register the affected component.
• After registration please restart the HCX manager services (app and web) from admin page.

Note: If similar issue is reported during reverse migration (No NSX on the destination) please verify the vCenter registration with HCX.

 

Additional Information

How to restart HCX Manager services.

Migrating Virtual Machines with Mobility Groups