Migrating Workload Virtual Machines from an Additional On-Premises Environment with HCX

Products

• VMware HCX

Issue/Introduction

• Preparing VMware HCX to migrate workloads from Site B to the cloud when HCX is already configured on Site A, with both on-premises sites located in the same datacenter and connected at Layer 2.

Example: 

• VMware HCX for migrating workloads from VxRail to Azure VMware Solution (AVS) in an environment where HCX is already configured between Nutanix and AVS.
  
  
• HCX Connector is deployed on Nutanix(Site A)
  
  
• On-prem Site B(New site)
  
  
• Azure VMware Solution (AVS) Cloud is acting as the HCX Manager

 

•  Do not extend networks from Site B to Cloud until Site A network extensions are removed.
  
  
•  Extending both sites simultaneously will cause Layer 2 loops.
  
  

Environment

VMware HCX

Resolution

To enable migration from an additional on-premises environment to the cloud, perform the following steps :- 

1.  Deploy HCX Connector on On-Premises
   
   
   • Install the HCX Connector appliance in the on-premises environment.
     
     
   • Verify network connectivity and required firewall ports to the cloud site.
     
     
2.  Configure HCX and Perform Site Pairing
   • From the HCX Connector UI:
     
     
   • Create HCX Network Profiles.
     
     
   • Create HCX Compute Profile(s).
     
     
   • Perform HCX Site Pairing between:
     
     
3. Transition HCX Network Extensions
   
   
   • Existing network extensions from the current on-premises site must be removed before extending networks from the new on-premises site.
     
     
   • Remove Existing Network Extensions
     
     
   • Unextend networks between the existing on-premises site and the cloud.
     
     
   • Extend Networks from New On-Premises Site to cloud.
     
     
4. VLANs and subnets overlap, enable Overlapping VLANs and Subnets during NE configuration.
   
   
5. Validate Networking
   
   
   • Verify L2 connectivity for extended networks.
     
     
   • Confirm VM and application communication between on-premises and cloud.
     
     
6. Connectivity Considerations
    
   • After removing existing network extensions, L2 connectivity between the original on-premises site and the cloud is not available.
     
     
   • Remaining workloads on the original on-premises site must use L3 routing to communicate with cloud workloads.