Awaiting too long for this!!! vCenter HA – Part 4
So this is the final part of the blog series for setting up the vCenter HA for your vCenter Server Appliance 6.5. To recap a bit, we have deployed the PSC nodes, NLB and configured the HA mode for PSC nodes. Now, we would perform the installation of vCenter (which is trivial) and also the vCenter HA (which is also quite trivial). Following steps will be taken:
- Install the vCenter Server using the Load Balancer virtual IP for the Platform Service Controller when prompted.
- Configure vCenter HA With the Basic Option
- Verify the vCenter HA function
You can read more about the vCenter HA deployment method, requirement and prerequisites from the vSphere Availability Guide. But to keep setup simple, we are using the Basic (trivial) deployment method which just require us to provide a port group and IPs for Heartbeating.
While PSC01 and PSC01 is being deployed in the Part 2 of this blog series and the HA configuration has been configured and deployed with Part 3. In this blog, we are going to configure the VC nodes. We will first deploy the VC01 first then when we are enabling the vCenter HA with basic config, the VC02 and VC Witness will be cloned out and configured directly. So let’s get started!
Install the vCenter Server using the Load Balancer virtual IP for the Platform Service Controller when prompted.
Run again the vCenter Appliance Installer and choose Install
Press Next to proceed to deployment
Accept the EULA and press Next to proceed
We are deploying a vCenter with External PSC, so please choose “External Platform Services Controller” and “vCenter Server (Requires External Platform Services Controller)”.
Choose the ESXi host you would like to deploy the vCenter Server Appliance.
Accept the certification to proceed
Provide the VM name and Root Password info. You do not need to give it the node name. I mean if you are using “vCenter” as the management hostname, you can use it directly. We do not need to make vCenter01 and vCenter02 as the node names. As the vCenter HA will cloned out the secondary node and witness node with hostname configured. In simply words, you don’t need 3 Management IP for the 3 nodes, you just need one DNS and one IP for management. While 3 heartbeat IPs would be needed for the nodes.
Choose the size of the vCenter. I use Small configuration for development and testing purpose.
Choose the proper datastore for deployment.
Input the network information, as said, we input the IP which you wants to be the final service IP. Of course FQDN as the final service FQDN too.
Press Finish to proceed
Wait for completion of the deployment in stage 1, press continue to proceed to the stage 2.
Press Next to proceed to the Stage 2 of the deployment
This is an important step, you need to enable the SSH access for the vCenter Server as the pre-requisites for the vCenter HA
Input the SSO configuration, input the NLB-ed FQDN setup in the previous steps. For my case, it’s PSC.vmware.lab.
Confirm the input and press Finish to proceed
Press OK to proceed and do not interrupt the configuration and wait for the completion of deployment.
GREAT you got the vCenter Deployed!!!
Configure vCenter HA With the Basic Option
To have the Basic Option for vCenter HA, you would have to have your vCenter Self Managed Host. i.e. You need to have your vCenter managing your ESXi which running your vCenter VM itself.
I added the hosts into the vCenter management, actually you can see my screen I have two hosts only and this is why I have failed in first time. And turn out, I added one more host into the environment to make the deployment successful
Then you need to have a separate port group for the Heartbeat taffic.
After that, we can enable the vCenter HA from the VC object. Go to the “configure” tab and go to vCenter HA and press “Configure”
Choose “Basic” Configuration for the vCenter HA deployment.
Select a Heartbeat IP for the vCenter Node 1. This is an isolated network for the VC nodes to communicate, so it can be isolated one. And choose the corresponding port group from the “Select vCenter HA network”
In the next step of the Wizard, you would have to input the Heartbeat IP for the VC Node 2 and the Witness.
After that, press Next to continue the setup
In this page, you can select separate datastores for running the different nodes in order to enhance the availability level.
You can even select thin provisioning for different nodes
So the configuration will take place. (Again, you actually need to have three hosts to make the deployment success)
On successful deployment, you can see the page changed and here you can see which node is active, passive or witness. Green lights of course mean configuration is okay. For detail you can press “vCenter HA Monitoring” under the “Edit” and “Initiate Failover” button.
You can see more detail under the Monitor > vCenter HA.
So the configuration are all DONE!!!
Verify the vCenter HA function
So before completion, definitely we need to test failover. So just click the initiate failover under the configure > vCenter HA.
Press Yes to confirm the failover.
WOW, Failover in progress. And we need wait some time to let the web client up and running
WOW, failover is done and you can see now the Active and Passive Role swapped
PERFECT!!! So all done, we deployed the vCenter HA with the NLB HA PSC configuration. You can enjoy the best protection of your vCenter Appliance now. All the nodes of the following diagram has been deployed and they are up and running and working properly. This is really a great great feature for the vSphere 6.5 and I wish the blog series could let you deploy your instance easily too.