One of the reasons I put together the VVD 4.3 on VxRail Breadcrumb Build series was that I wanted to have a go at using VMware HCX to migrate workloads between a VxRack SDDC and a VxRail. In this series, the ultimate goal is to build a VMware HCX topology like the one shown below that will allow me to migrate virtual machine workloads between these endpoints in cold or vMotion styles using either on-demand or scheduled migrations.
HCX offers some cool features when it comes to this sort of thing. The ones that jumped out at me were these
Uncomplicated network requirements between the platforms. Really all you need open is TCP 443 and UDP 500,4500. Thats about as uncomplicated as it gets.
Ability to on-demand/schedule both bulk migration and vMotion migration types
Single source to multiple targets (could be used for redistribution from one source to multiple smaller targets)
Built in WAN optimization, and network extension
So let’s gather a few of the key data points you are going to need during the deployment. You’ll find that typically the destination system is referred to as ‘cloud’ and the source system is typically referred to as ‘enterprise’ throughout the HCX documentation (presumably to reinforce that you can migration out of your datacenter and into a cloud provider). I’m keeping that nomenclature for the parameter gathering.
VMware Enhanced vMotion Compatibility (EVC)
Before you go too far, if you intend to use the live vMotion capability of HCX, then you should check out how compatible the CPUs between enterprise/source and cloud/destination systems are. You might find that you need to turn EVC on if you haven’t already and that the levels of EVC are compatible. It can be disruptive to turn this one if there are workloads already running on the system, so get out in front of it.
Destination Name Resolution
Destination Time Synchronization
Source Name Resolution
Source Time Synchronization
Destination Load Balanced PSC or stand alone as appropriate
Source Load Balanced PSC or stand alone as appropriate