In this part you add VCF Operations HCX, the component that moves workloads into your VCF 9.1 fleet. It is optional, and it is the tool you reach for when you want to migrate live virtual machines from an older vSphere or another site rather than rebuild them. It pairs well with the brownfield import path when workloads need to move rather than stay in place.

Install the HCX Manager from VCF Operations, pair it with the source site, define the network and compute profiles, then deploy the service mesh that carries the traffic. Plan the IP pools for the service mesh appliances before you start, because the mesh will not deploy without them.

Prerequisites

Step 1 create the HCX Manager DNS record

Prepare the name before you install.

1. Choose the HCX Manager FQDN.
2. Create a forward A record and a matching PTR record.
3. Confirm both resolve from the management network.

Step 2 install the HCX Manager

Start the install from VCF Operations.

1. In VCF Operations, locate the VCF Operations HCX tile.
2. Click Install.
3. On the General step, select the HCX Manager version 9.1.0.0 or later.
4. Click Next.

Step 3 set deployment settings

Give the manager its identity and credentials.

1. On the Deployment Settings screen, enter the HCX Manager FQDN.
2. Set the admin and root credentials.
3. Confirm the network settings, then click Finish.
4. Wait for the manager to reach a ready state.

Step 4 create the site pair

Connect the target and source over the control plane.

1. Open the HCX interface and go to Site Pairing.
2. Click Add a Site Pairing.
3. Enter the source HCX endpoint URL and credentials, connecting over TCP 443.
4. Click Connect and confirm the pair shows connected.

Step 5 create network and compute profiles

Define where the mesh appliances live and which addresses they use.

1. Open Interconnect, then Network Profiles, and click Create Network Profile for management, uplink, vMotion and replication.
2. Assign an IP pool to each network profile.
3. Open Compute Profiles and click Create Compute Profile.
4. Select the target cluster and attach the network profiles, then click Finish.

Step 6 deploy the service mesh

Build the data plane that carries migrations.

1. Open Interconnect, then Service Mesh, and click Create Service Mesh.
2. Select the site pair and the source and target compute profiles.
3. Select the services you need, then click Finish.
4. Wait for the Interconnect and Network Extension appliances to deploy and show green.

Step 7 verify with a test migration

Prove the path before you move production.

1. Open Migration and click Migrate.
2. Select a small test virtual machine and a migration type.
3. Start the migration and confirm it completes and the VM runs on the target.

flowchart TD
A[Create HCX Manager DNS record] --> B[Install HCX Manager from VCF Operations]
B --> C[Set FQDN and credentials]
C --> D[Create the site pair over 443]
D --> E[Create network and compute profiles]
E --> F[Deploy the service mesh]
F --> G[Run a test migration]

Verify workload mobility

Confirm the site pair shows connected and the service mesh appliances are green. Run a test migration of a small virtual machine and confirm it completes and runs on the target fleet. A clean test migration is the signal that you can plan the real moves.

Plan the service mesh networks

The service mesh will not deploy without addresses, so plan the network profiles first. HCX needs a management network for the appliances, an uplink network that carries traffic between sites, a vMotion network for live moves, and a replication network for bulk transfer. Some designs collapse these onto fewer networks, but keep management and uplink separate at minimum. Size an IP pool for each profile with room for more than one service mesh if you will pair more than one source. Confirm the uplink path has the throughput and MTU your migrations need, because that link sets the pace of every move.

Choose the right migration type

HCX offers more than one way to move a workload, and the right one depends on the workload and the downtime you can accept. Match the type to the workload before you schedule a wave, and always prove the path with a small test migration first.

Notes and best practices

Plan the network profiles before you touch the service mesh, because the mesh simply will not deploy without addresses, and a half planned profile wastes a deployment cycle. Keep the management and uplink networks separate at minimum, and size each IP pool for more than one service mesh if you will pair more than one source site. Prove the whole path with a small test migration before you schedule a wave, so you find a blocked port or a slow uplink on a throwaway VM rather than a production one. Pick the migration type per workload rather than forcing everything through one method, since a live database and a stateless web VM want different approaches. Watch the uplink MTU and throughput, because that single link sets the pace of every move, and a mismatch there turns a quick migration into an overnight one.

Common errors and fixes

Site pair will not connect.
TCP 443 is blocked between the sites or the source endpoint URL is wrong. Open 443 both ways and confirm the source HCX endpoint and credentials.

Service mesh fails to deploy.
A network profile is missing addresses. Assign IP pools to the management, uplink, vMotion and replication profiles, then redeploy the mesh.

HCX Manager install stalls.
The FQDN has no DNS record or the credentials were rejected. Create the A and PTR records, confirm the credentials, and retry the install.

Migration is slow or drops.
The uplink profile does not have enough throughput or MTU. Confirm the uplink network and MTU match the design, and place the Interconnect appliance on the right path.

Common questions

Is HCX mandatory
No. It is an optional workload mobility component, used when you want to migrate running virtual machines into the fleet.

Where do I install the HCX Manager
From the VCF Operations HCX tile, choosing version 9.1.0.0 or later.

What port does the site pair use
TCP 443 for the management control plane between the sites.

What does the service mesh deploy
The data plane appliances, the Interconnect and the Network Extension, that carry migration and stretched network traffic.

References

• VCF Blog: Workload Mobility with VCF Operations HCX 9.1, Part 1 Deployment
• VCF Blog: VCF Operations HCX 9.1, Part 2 Service Mesh
• Broadcom TechDocs: About the HCX Service Mesh

About The Author

Dr. Pranay Jha

Dr. Pranay Jha is a Cloud and AI Consultant with 18+ years of experience in hybrid cloud, virtualization, and enterprise infrastructure transformation. He specializes in VMware technologies, multi-cloud strategy, and Generative AI solutions. He holds a PhD in Computer Applications with research focused on Cloud and AI, has published multiple research papers, and has been a VMware vExpert since 2016 and a VMUG Community Leader.

See author's posts