6.5.1
Table Of Contents
- vSphere Availability
- Contents
- About vSphere Availability
- Business Continuity and Minimizing Downtime
- Creating and Using vSphere HA Clusters
- Providing Fault Tolerance for Virtual Machines
- vCenter High Availability
- Plan the vCenter HA Deployment
- Configure the Network
- Configure vCenter HA With the Basic Option
- Configure vCenter HA With the Advanced Option
- Manage the vCenter HA Configuration
- Set Up SNMP Traps
- Set Up Your Environment to Use Custom Certificates
- Manage vCenter HA SSH Keys
- Initiate a vCenter HA Failover
- Edit the vCenter HA Cluster Configuration
- Perform Backup and Restore Operations
- Remove a vCenter HA Configuration
- Reboot All vCenter HA Nodes
- Change the Appliance Environment
- Collecting Support Bundles for a vCenter HA Node
- Troubleshoot Your vCenter HA Environment
- Patching a vCenter High Availability Environment
- Using Microsoft Clustering Service for vCenter Server on Windows High Availability
- Index
2 Wait for vCenter HA setup to complete.
Manage the vCenter HA Configuration
After you congure your vCenter HA cluster, you can perform management tasks. These tasks include
certicate replacement, replacement of SSH keys, and SNMP setup. You can also edit the cluster
conguration to disable or enable vCenter HA, enter maintenance mode, and remove the cluster
conguration.
n
Set Up SNMP Traps on page 69
You can set up Simple Network Management Protocol (SNMP) traps to receive SNMP notications for
your vCenter HA cluster.
n
Set Up Your Environment to Use Custom Certicates on page 69
The machine SSL certicate on each node is used for cluster management communication and for
encryption of replication trac. If you want to use custom certicates, you have to remove the vCenter
HA conguration, delete the Passive and Witness nodes, provision the Active node with the custom
certicate, and recongure the cluster.
n
Manage vCenter HA SSH Keys on page 70
vCenter HA uses SSH keys for password-less authentication between the Active, Passive, and Witness
nodes. The authentication is used for heartbeat exchange and le and data replication. To replace the
SSH keys in the nodes of a vCenter HA cluster, you disable the cluster, generate new SSH keys on the
Active node, transfer the keys to the passive node, and enable the cluster.
n
Initiate a vCenter HA Failover on page 70
You can manually initiate a failover and have the Passive node become the Active node.
n
Edit the vCenter HA Cluster Conguration on page 70
When you edit the vCenter HA cluster conguration, you can disable or enable the cluster, place the
cluster in maintenance mode, or remove the cluster.
n
Perform Backup and Restore Operations on page 71
For additional security, you can back up the Active node in the vCenter HA cluster. You can then
restore the node in case of catastrophic failure.
n
Remove a vCenter HA Conguration on page 72
You can remove a vCenter HA conguration from the vSphere Web Client. If you are using an
Advanced conguration, or if any of the nodes are not discoverable, you might have to perform
additional cleanup steps.
n
Reboot All vCenter HA Nodes on page 72
If you have to shut down and reboot all nodes in the cluster, you must follow a specic shutdown
order to prevent the Passive node from assuming the role of Active node.
n
Change the Appliance Environment on page 73
When you deploy a vCenter Server Appliance, you select an environment. For vCenter HA, Small,
Medium, Large, and X-Large are supported for production environments. If you need more space and
want to change the environment, you have to delete the Passive node virtual machine before you
change the conguration.
n
Collecting Support Bundles for a vCenter HA Node on page 73
Collecting a support bundle from all the nodes in a vCenter HA cluster helps with troubleshooting.
vSphere Availability
68 VMware, Inc.