In this article I am showing how to deploy, install and test HCX on-premises. More about HCX can be found here: https://cloud.vmware.com/vmware-hcx
Before jumping into the, hopefully easy to follow, deployment and configuration of HCX, let me give you a few gotchas.
- HCX requires NSX in the Destination Site
- NSX is optional in the Source site
- You require an NSX Datacenter Enterprise Plus license to active HCX
- An active internet connection is required in both source and destination site in order to activate and upgrade NSX
- HCX will be deployed in the Destination site FIRST
- HCX will be upgraded as part of the deployment.
- HCX will be deployed in the Source site once HCX has been configured and upgraded in the destination site. HCX will provide an OVA that has to be used in order to deploy HCX in the source site.
- The HCX Cloud Manager is the HCX Manager in the Destination Site
- The HCX Enterprise Manager is the HCX Manager in the Source Site
- The vCenter Plugin is only deployed in the Source site but the use is optional. With the recent version HCX provides also a standalone client that can be accessed through the Hybridity of each HCX appliance.
- The Admin interface can be accessed via :9443
- The Hybridity interface can be access via :443
- Custom Certificates are not applied on the admin interface (:9443) but only for the Hybridity interface (:443)
- Bulk Migration has currently a limit of 100 concurrent migrations / vCenter
- vMotion has currently a limit of 1 migration / vCenter
Let’s get started though .. There’s probably more, so I suggest looking through the official documentation that can be found here: https://docs.vmware.com/en/VMware-HCX/index.html
Here you can see I have two sites. Cunningly called Source and Destination.
The destination has NSX deployed and enabled.
The deployment isn’t much different from any other VMware-based appliance.
Deploy the OVA downloaded from my.vmware.com in the Destination site first
Once the OVA has been deployed and powered on, browse to the admin interface on port :9443
Please Note: It can take quite a while for the interface to come up. In my nested environment it took around ten minutes for the admin interface to come up.
Once you clicked Continue you will be asked to enter a license key
As mentioned, one of the first steps is to activate but also upgrade the HCX appliance. It is unlikely that you will find the most up to date OVA on my.vmware.com.
Once the upgrade is completed, it will simply forward to the main admin login screen.
If you browse to the page too quickly, you might get a browser error. In my case it took nearly ten minutes for the interface to come up again.
You can tail the logs to see if there is any activity.
[[email protected] ~]$ tailf /common/logs/admin/app-startup.log
So once that has calmed down, login to the admin interface again.
In order to get the OVA for the Source Site you will need to login to the Hybridity Interface (:443) – but before that becomes available, you need to configure the vCenter connection.
Once you logged in you will first have to configure the physical location of the datacenter. This has no implication with the setup and is merely cosmetic
Next we need to configure the System Name, here I just leave the FQDN
Here I am using my on-premises vSphere clusters
Enter both vCenter and NSX details. As mentioned before, NSX is mandatory for destinations.
Next your identity source
Enter the public URL. In my case I am not using any NAT etc., so my public URL is the actual FQDN of the appliance
Let it restart and get a drink or five.
Once again you can follow the reboot in the logs
Once rebooted the appliance will login automatically
Jump to the appliance summary and make sure the services are started
Here you can see the Web Service is still Starting.
Next we need to configure the role mapping. Here I am leaving the SSO Admin but it should obviously be an AD Group.
Note: The Enterprise Administrator is not relevant in on-premises deployments, only VMC.
What I have noticed is that if you are using embedded PSC and use a different SSO domain, you may need to add the vCenter that holds the PSC to the HCX vCenters
Next, login to the Hybridity interface (https://fqdn:443)
You should see the dashboard now.
Click Download VMware HCX Client
Click Request Download Link
Now VMware HCX
This will now download the OVA for the SOURCE Site – the HCX Enterprise Manager
Deploy this OVA just like the Cloud Manager OVA into every Source site you would like to migrate VMs from. You will need to do the same configuration as you have done for the Destination site. As the steps are identical just follow the same article 😉
Next I will talk about Site Pairings