In this post we will continue covering the objective from the blueprint and now its time for Configure Advanced vSphere HA Features.
The following are objectives from the blueprint:
- Configure a network for use with HA heartbeats
- Apply an admission control policy for HA
- Enable/disable advanced vSphere HA settings
- Configure different heartbeat datastores for an HA cluster
- Apply virtual machine monitoring for a cluster
- Configure Virtual Machine Component Protection (VMCP) settings
- Implement vSphere HA on a Virtual SAN cluster
- Modify vSphere HA advanced cluster settings
Configure a network for use with HA heartbeats:
You will need to have a cluster to enable HA , in my home lab i setup only two ESXi host in cluster configuration with very basic configuration, On the switch you will need to enable management traffic on the VMkernel . in real production envioremnt you want to setup NIC teaming and multiple switches.
Enable/disable vSphere HA:
Click on the Cluster >>Manage>>Settings>> vSphere HA >> Edit and click the check box to turn it on.
Configure Virtual Machine Component Protection (VMCP) settings:
When enabled vSphere HA the ESXi hosts will be able to monitor additional failures that do not cause the vm’s to stop working.(for example loss access to a storage)
You an control these failure events via the following settings:
Apply virtual machine monitoring for a cluster:
When enabled VM monitoring will restart VM’s if the VM’s VMWare tools does not respond to heartbeat , you have two options for VM only and also for VM and applications(if your application support it).
You can control VM monitoring sensitivity settings:
Apply an admission control policy for HA:
Admission control ensure that sufficient resources are available in a cluster to provide failover protection by setting aside some resource just in case we have a failover and all resource as busy (all other host in the cluster are maxed out)
You can set static number of hosts aside this means that the capacity of one host is reserved from all hosts in the cluster you can setup fix amount of reserved or percentage of the reserved. in VMware availability guide there are some good examples.
Configure different heartbeat datastores for an HA cluster:
This is a backup for cases that host get isolated in the management network , so instead setting the heartbeat only on the management network you can configure the heartbeat to work also via the storage side.
Implement vSphere HA on a Virtual SAN cluster:
- If you have a vSAN enabled on the cluster HA traffic will flow over the storage network and not the management network
- you will have to disable HA to install vSAN after the install of the vSAN you can enable HA back.
Modify vSphere HA advanced cluster settings:
Below are screenshots from VMware vSphere Availability document (not sure if we need to remember this for the exam)