With our sites onboarded, we can move on to configuring each site so that it can be used for HCX+ migrations.
Click the Configure Site link under the Site to be configured (Sofia in this example).
After a short time, you will see a page similar to the following:
This site only has the one cluster and datastore so there were no choices to make. Click the Next button.
Normally, you would start by clicking the Network dropdown but in this example, it defaulted to the one I wanted (Management).
Click the Add an IP Pool link in the Management Network section.
Supply a meaningful name for the pool and supply IP information that won’t overlap/conflict with any other devices on the network.
Click the Add Pool button.
Complete the rest of the Management Network form as appropriate.
Click the Save button.
Repeat the previous steps to complete the External Connectivity Network section. You’ll note that I’m using the same network information for my external network as was used for my management network. Your configuration may differ.
Select the appropriate network (Management in my example).
Click the Select button.
Complete the rest of the network information as appropriate (the same as was done for the Management network in my example).
Click the Save button.
Click the Next button.
Click Yes to configure vMotion and Replication networks. This is optional but highly recommended to help ease any potential network resource contention issues. You will want to make sure that you have separate vMotion and Replication networks configured (with appropriate VMkernel interfaces on our ESXi hosts) prior to this configuration step.
The VMotion network was selected by default so there was no need to select it. Click the Create another IP Pool link in the VMotion section.
Similar to what was done for the Sofia Mgmt IP Pool, create a pool of addresses in the appropriate range for vMotion traffic (192.168.112.0/24 in this example).
Click the Add Pool button.
Complete the rest of the form as appropriate for the vMotion network.
Click the Save button.
Click the Network dropdown in the vSphere Replication Network section.
Choose the Replication network.
Click the Select button.
Click the Create another IP Pool link.
Similar to what was done for the Sofia vMotion IP Pool, create a pool of addresses in the appropriate range for Replication traffic (192.168.113.0/24 in this example).
Click the Add Pool button.
Complete the rest of the form as appropriate for the Replication network.
Click the Save button.
This is your last chance to review. When you’re ready, click the Configure Site button.
If you click the View Connection Rules button at the top, you’ll see a precise listing of the services in use and what ports have to be open to allow for their proper functioning.
You can repeat the previous Site Configuration steps for the Cloud site (Cork in my example) at this point.
If you look at the HSM configuration, you will see that no profiles have been created yet.
In HCX+, these profiles will not be created until there is a site pairing. In traditional HCX, the profiles would be created first and then the site pairing configured.
If you find that you’ve made a mistake in the configuration of the network information for a Site, you can edit it by clicking the View Details link for the Site, then navigating to the Site Resource Profiles tab. You should see a page similar to the following:
You can click the Manage link on the tile for the network type that needs to be changed or click the network type option on the left. You should then see a page similar to the following:
From here, you can click the Edit link to make any changes.