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 If you cannot resolve the connectivity problem, you have to log in to Active node's console directly.
a Power o and delete the Passive node and the Witness node virtual machines.
b Log in to the Active node by using SSH or through the Virtual Machine Console.
c To enable the Bash shell, enter shell at the appliancesh prompt.
d Run the following command to remove the vCenter HA conguration.
destroy-vcha -f
e Reboot the Active node.
The Active node is now a standalone vCenter Server Appliance.
f Perform vCenter HA cluster conguration again.
Resolving Failover Failures
When a Passive node does not become the Active node during a failover, you can force the Passive node to
become the Active node.
Problem
The Passive node fails while trying to assume the role of the Active node.
Cause
A vCenter HA failover might not succeed for these reasons.
n
The Witness node becomes unavailable while the Passive node is trying to assume the role of the Active
node.
n
An appliance state synchronization issue between the nodes exists.
Solution
You recover from this issue as follows.
1 If the Active node recovers from the failure, it becomes the Active node again.
2 If the Witness node recovers from the failure, follow these steps.
a Log in to the Passive node through the Virtual Machine Console.
b To enable the Bash shell, enter shell at the appliancesh prompt.
c Run the following command.
vcha-reset-primary
d Reboot the Passive node.
3 If both Active node and Witness node cannot recover, you can force the Passive node to become a
standalone vCenter Server Appliance.
a Delete the Active node and Witness node virtual machines.
b Log in to the Passive node through the Virtual Machine Console.
c To enable the Bash shell, enter shell at the appliancesh prompt.
d Run the following command.
destroy-vcha
e Reboot the Passive node.
vSphere Availability
76 VMware, Inc.