This is Part 3 of this process. If you need to review Part 2, you can do that here: Deploying vSphere 6.5 Update 2 Platform Services Controller (PSC) and vCenter in an HA configuration [Part 2]
This will walk you through deploying vCenter for HA. The deployment is actually very similar to deploying a non-HA configuration. This will use the same installer.exe that you use to deploy the PSCs.
Deploying vCenter 6.5 Update 2
- You have the Load Balancers setup for connecting to your PSCs
- You have the PSCs setup properly with certs from the VMCA (this includes the VIP FQDN)
- You have the DNS names created for any vCenter you will deploy (this includes the reverse DNS)
- If you are able to take snaps of your PSCs while they are down (this would mean you are deploying into a different vCenter that enables snapshots to be taken). If this is a greenfield, you can take a snapshot of the PSCs while running, but I do not believe this is supported.
- Launch the installer.exe
- Put a check in I accept the terms of the license agreement and then click Next
- Select vCenter Server (Requires External Platform Services Controller) and then click Next
- Type in the vCenter (or host) FQDN name that you will be deploying to and use the an administrator account (or root account if you are deploying to a host) to authenticate.
- Click Yes to accept the thumbprint
- Select the Datacenter you will deploy to and then click Next
- Select a host to deploy vCenter to and then click Next
- Type in the name of the appliance (this is the name that will show up in vCenter or on the host within it’s inventory) and the root password you want to use. Click Next
- Select the size you would like to use and then click Next
- Select the datastore and then click Next
- Set the following:
- System Name (this is the fqdn of the vCenter you are deploying)
- IP Address
- Subnet Mask
- Default Gateway
- DNS Server (you can enter just one for the time being)
- Click Next
- Validate that all the information entered is correct and then click Finish
- The deployment will start. This can take a bit of time. It may hang at around 80% while it tires to install the RPMs. This is normal. You can also watch the VM itself and see the events where it keeps trying to connect to the VM:
Eventually this will succeed:
- Once the deployment is done, click Continue
- Click Next
- Type in the FQDN of one NTP server (this should be the same NTP server you used for the PSC deployment for this site) and switch the SSH access to Enabled and then click Next
- It will now ask you to connect to a PSC. For this HA deployment, you are going to enter the FQDN of the VIP for the PSCs Load Balancers
- Once you have entered in all the information, click
- Validate all your information is correct and then click Finish
- Click OK for the warning so the process continues
- This process can take a bit of time. Generally if this is going to fail, it will fail fairly quickly (at around 6%). Cross your fingers that things start up and the bar continues to progress. When doing an HA deployment, it can be tricky to figure out what is actually wrong. Many times it’s the vCenter going back and forth between PSCs and weights are not set correctly on the Load Balancer.
- Click Close
- Now you should hit your vCenter on the https:// side of things and verify that certificate is valid. Make sure that the web site is secure and that the Certification path shows that you received a certificate from the VMCA.
If you have two sites, you should follow these steps again for the second site. This will get vCenter online for each site so we can roll into deploying vCenter HA.
Now that we have vCenter online, we will continue with Part 4 of this series. This will go through the advanced configuration of vCenter HA and why we may need to use that instead of the Basic configuration.