Learning HCX-Part 2-HCX Enterprise Deployment & Configuration

By | 28/06/2018

In first post of this series, we learnt about basics of HCX and we discussed that HCX is available in 2 versions i.e HCX Enterprise (for On-Prem) and HCX Cloud (for cloud providers).

In this post we will learn how to deploy HCX Enterprise appliance in on-prem and we will touch down on basic configuration. 

Deployment of HCX Enterprise appliance is very much similar to a standard ovf deployment of any VMware product and nothing fancy is there. Below slide show walk-through steps of deploying the appliance. 

Note: Make sure to deploy appliance as ‘Thick provisioned lazy zeroed’

This slideshow requires JavaScript.

By default, HCX ENT appliance is deployed with 12 GB RAM, 4 vCPU’s and 60 GB HDD.

hcx-10

Once the appliance boots up, login to appliance by typing https://hcx-fqdn:9443 and using admin as username and password set during deployment.

hcx-11

You need to have your HCX license key handy for activating the appliance. Your appliance should be able to connect to https://connect.hcx.vmware.com in order to get activated. 

You can choose to activate the appliance later as well.

hcx-12

Select the location where your datacenter is located and hit Continue.

hcx-13

Provide a system name for the appliance and hit continue. 

hcx-14

Hit continue to proceed further with configuration.

hcx-15

Next is to connect your on-premise vCenter server and NSX manager with HCX. Provide the info and hit continue.

hcx-16

Specify IP address/fqdn of the PSC appliance for configuring SSO.

hcx-17

Once you have connected HCX to vCenter server,NSX and PSC, you need to restart the service.

hcx-18

Post restarting service, verify that SSO,NSX and vCenter connections are showing green.

hcx-19

Verify all services are running fine.

hcx-20

Next is to do vSphere role mapping which is a very important step. Basically you are configuring user/groups who can manage the HCX appliance. By default it is set to vsphere.local/Administrators.

Click on edit to modify this configuration.

hcx-21

In my environment, I am not using the default vsphere.local SSO domain and I have created my own SSO domain named ‘vstellar.local’

hcx-22.PNG

And that’s it for this post. In next post of this series, we will deploy and configure HCX cloud appliance.

I hope you enjoyed reading this post. Feel free to share this on social media if it is worth sharing. Be sociable :)