HCX Migration Types
1 / S.Mesh
1 / S.Mesh
250 / Mgr
Replication Assisted migration.
200 / Mgr
OS Assisted Migration
50 disks / S.Mesh
In private to public cloud deployment, activation keys come from public cloud providers.
HCX for VMware Cloud on AWS
Compute profile captures the following information
Compute profile on Cloud HCX
On activating HCX on VMC, a compute profile is created automatically.
We can login to HCX on the VMC side with firstname.lastname@example.org user account and check the compute profile
Uplink Network profiles on Cloud HCX
Uplink network profiles define how the migration traffic and network extension traffic flows between HCX appliances Onprem and VMC.
HCX Interconnect and network extension appliances communicate over the internet or directconnect. These appliances create their own ipsec tunnels; they do not use the VPNs created in the VMC console .
However, HCX managers can communicate over the VPN tunnels.
On the VMC side, the following network profiles are created by default
Configure HCX to use Direct Connect
( enterprise edition
Solves hairpinning or tromboning effect for migrated VMs i.e. Avoids a long round trip network path via on-prem gateway
The network path of routed traffic for migrated VMs
( enterprise edition
Reference: vmw-blog vmw-bp-doc license-doc vmw-blog
What is a Proxy Host?
It is a two-way vmotion proxy.
- When a vMotion is initiated to a remote host, the local ESXi host migrates that VM to the local proxy ESXi host.
- HCX-IX appliance transfers the VM data to remote HCX-IX appliance.
- Target proxy ESXi host migrates the VM to target ESXi host
How to deploy the Proxy host?
When a service mesh is created with “vMotion Migration Service” selected, a proxy host gets automatically deployed on vCenter. It’s purpose is
- It looks like nested ESXi, but it isn’t. It is a dedicated mobility platform.
- The processor, memory, storage and networking resources displayed on this object does not represent actual consumption on the physical hypervisor hosting the IX appliance.
1. Replication based migration
2. vMotion based migration
3. Deploys Mobility Agent service that appears as a host object in the vCenter server.
1. Applies WAN optimization techniques like the data de-duplication and line conditioning.
2. It accelerates on-boarding to the destination site using Internet connections, without waiting for Direct Connect/MPLS circuits.
Network Extension (HCX-NE)
Layer 2 Extension
Connects and forwards source workloads to destination
( In OS assisted migrations )
Sentinel Data Receiver
Receive, manage, and monitor data replication operations at the destination environment ( In OS assisted migrations )
HCX Traffic Types
HCX appliances use the network to communicate with HCX Manager, vCenter Server, NTP, DNS.
Local HCX appliances use the network to connect with remote HCX appliances and vice versa.
HCX appliances use the network to communicate with the vMotion interface of ESXi hosts.
HCX appliances use the network to communicate with the vSphere replication interface of ESXi hosts.
To reach the vSphere replication interface of ESXi hosts.
HCX Guest Network
To connect to the Sentinel agents.
HCX Installation Flow
Deploy HCX on VMC
Download HCX OVA for On-Prem
Activate and Register HCX
Register NSX (optional)
Create network profiles
Create compute profile
Create Service Mesh