VMware Virtualization & Hybrid Cloud: April 2023

Configure HCX Hybrid Cloud Extension services -Site Pairing ,Compute Profile ,Network Prodile and Service Mesh.

Site Pairing:

A Site Pair establishes the connection needed for management, authentication, and orchestration of HCX services across a source and destination environment.

In HCX Connector to HCX Cloud deployments, the HCX Connector is deployed at the legacy or source vSphere environment. The HCX Connector creates a unidirectional site pairing to an HCX Cloud system. In this type of site pairing, all HCX Service Mesh connections, Migration and Network Extension operations, including reverse migrations, are always initiated from the HCX Connector at the source.

In HCX cloud-to-cloud deployments, site pairing can be unidirectional or bidirectional:

In unidirectional site pairing, the HCX Cloud containing the virtual machine inventory and networks (similar to HCX Connectors) will site pair to the destination HCX Cloud.

In bidirectional site pairing, the HCX Cloud systems are site paired with each other, share a common Service Mesh, and can initiate Migration and Network Extension operations from either HCX Cloud system.

Let us discuss about different network use by HCX service.

1.Management Network:

The HCX Interconnect appliances use this network to communicate with management systems like the HCX Manager, vCenter Server, ESXi Management, NSX Manager, DNS, NTP.

2.Uplink Network:

The HCX Interconnect appliances use this network for WAN communications, like TX/RX of transport packets.

3.vMotion Network:

The HCX Interconnect appliances use this network for the traffic exclusive to vMotion protocol operations.

4.vSphere Replication Network:

The HCX Interconnect appliances use this network for the traffic exclusive to vSphere Replication.

5.Guest Network for OS Assisted Migration

The Sentinel Gateway appliances use this vSphere network to connect with non-vSphere virtual machines.

Network Profile:

The Network Profile is an abstraction of a Distributed Port group, Standard Port group, or NSX Logical Switch, and the Layer 3 properties of that network.

We can create a different network profile based on below use case.

1.Use case 1: if customer wants to use Shared Management, Replication, and Uplink with Dedicated vMotion

2.Use case 2: If customer configured Dedicated Replication Network and want to use dedicated network profile for replication network.

3.Use case 3: If customer configured Dedicated Uplink Network and they want to use dedicated network profile for uplink.

4. Use case 4: Network profile for OS Assisted Migration Using Guest Network.

5.Use Case 5: If customer wants to use OS Assisted Migration Using Management Network

Configure Site Pairing:

1.Login to source vCenter using administrator@vsphere.local and click on Menu.

2.From the Drop-down menu click on HCX .

3.Once you will click on HCX, it will redirect on HCX dashboard, where we need to configure the rest of configuration like site pairing, network profile, service mesh and other services.

Before configuring site, pairing and network profile let discuss about the Site pairing and network profile service mesh.

4.Navigate to Site Pairing and click on connect to remote site:

5.Once you will click on Connect to Remote site, you need to provide Remote HCX Url (https://hcx_fqdn), Username (administrator@vsphere.local) and Password XXXX.

6.Once the connection will establish with remote HCX you will able to see source HCX and destination HCX are in connected state.

7.Now navigate to Interconnect from Left side bar and click on Interconnect .

8.This step in most important step where I am going to create Network profile which i explained you in with different use Case

9.Click on Network Profile and Create Network Profile in this page.

10.Once you will click on create network profile, you need to provide below details .

10.1.Select the vSwitch, vDS, or NSX network (not mandatory for HCX Connector) that you will use for this Network Profile. In this case, it is a vDS.

10.2.Add the IP Pool addresses for for the HCX Management. Uplink, vMotion and Replication. We will need one IP address per Appliance. Since we are only deploying one, then one IP Address. But you can add here a full IP Pool range. HCX will use the necessary IP addresses, and I will add two here.

10.3.In my Lab i am going to user this network profile for MGMT, vMotion and vSphere Replication and HCX uplink.

If you have dedicated network as I explained in above, use case you can create separate Network profile for HCX traffic.

Note : In deployments where ESXi servers use a dedicated Provisioning vmkernel for NFC traffic, the HCX continues to route Cold and vMotion NFC traffic through the Management interface.

11.Once First network profile if create in same manner you can create other network profile .

12.Next we are going to create a Compute Profile. From same page navigate to Compute Profile and Create Network profile.

Compute Profile :

1.Create Compute Profile, Give the Name of Compute Profile and Next.

2.In Next screen choose the HCX service which you want to use for your environment and Click continue.

3.Now we must choose the cluster where you want to use the HCX service if you want to use for all cluster the you can go with datacenter .

4.Next we must choose deployment resource like cluster datastore and folder where you want to deploy the HCX service appliance.

5.Now we must choose port group for each type of traffic. If we have MGMT port group which you are using for MGMT, vMotion, replication, uplink then choose same MGMT network profile in each type of traffic.

If you have dedicated port groups for different type of traffic, then choose separate network profile or use case for MGMT, vMotion, replication, uplink.

In my Lab environment I have only MGMT port group which we can used for vMotion and other traffic.

6.Select port for Management network profile and click continue.

7.Choose port group for uplink network, using which interconnect appliance can communicate with peer appliance.

8.Select vMotion Network profile, as I told mentioned that i am going to use MGMT network profile for all type of traffic.

9.Now select network profile for vSphere replication.

10.Review the topology for all connection and click continue.

If you are using dedicated port group for different type of traffic then make sure firewall rules are allowed to these connections.

11.Once you will review the configuration, Click on Finish to create compute profile.

You have to repeat all above steps to create network profile ,compute profile on destination or (Cloud side ).

Service Mesh:

Service Mesh initiates the deployment of HCX Interconnect virtual appliance on both sites and it will add to connected site pair that has valid compute profile created on both sites

1.Same page where we added network profile and compute profile ,Click on Service Mesh.

2. Select the source and destination sites, if you have two or more that then click on arrow to see the other sites details. Click continue.

3.Select the Compute profile in source and destination where virtual machine can use HCX services.

4.Select the service which we need to activate in your environment.

5.Select the uplink network profile to connect the HCX interconnect appliance. As we already create MGMT network profile and want to use for uplink we will select the same .

You can also change and override if wanted to change network profile for uplink network. Click continue.

6.Advacenced configuration will give you option to create a multiple transport tunnel to establish path diversity to the target.

In my Lab its is not given me option as they are not licensed with this HCX installation.