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
Change the Appliance Environment
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.
Procedure
1 Log in to the Active node with the vSphere Web Client, edit the cluster conguration, and select
Disable.
2 Delete the Passive node virtual machine.
3 Change the vCenter Server Appliance conguration for the Active node, for example, from a Small
environment to a Medium environment.
4 Recongure vCenter HA.
Collecting Support Bundles for a vCenter HA Node
Collecting a support bundle from all the nodes in a vCenter HA cluster helps with troubleshooting.
When you collect a support bundle from the Active node in a vCenter HA cluster, the system proceeds as
follows.
n
Collects support bundle information from the Active node itself.
n
Collects support bundles from Passive and Witness nodes and places them in the commands directory on
the Active node support bundle.
N The collection of support bundles from the Passive and Winess nodes is a best eort and happens if
the nodes are reachable.
Troubleshoot Your vCenter HA Environment
In case of problems you can troubleshoot your environment. The task you need to perform depends on the
failure symptoms. For additional troubleshooting information, see the VMware Knowledge Base system.
n
vCenter HA Clone Operation Fails During Deployment on page 74
If the vCenter HA conguration process does not create the clones successfully, you have to resolve
that cloning error.
n
vCenter HA Deployment Fails with an Error on page 74
Deployment failures can be caused by conguration issues, especially problems with the networking
setup.
n
Troubleshooting a Degraded vCenter HA Cluster on page 74
For a vCenter HA cluster to be healthy, each of the Active, Passive, and Witness nodes must be fully
operational and be reachable over the vCenter HA cluster network. If any of the nodes fails, the cluster
is considered to be in a degraded state.
n
Recovering from Isolated vCenter HA Nodes on page 75
If all nodes in a vCenter HA cluster cannot communicate with each other, the Active node stops
serving client requests.
n
Resolving Failover Failures on page 76
When a Passive node does not become the Active node during a failover, you can force the Passive
node to become the Active node.
Chapter 4 vCenter High Availability
VMware, Inc. 73