6.7
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
- How Fault Tolerance Works
- Fault Tolerance Use Cases
- Fault Tolerance Requirements, Limits, and Licensing
- Fault Tolerance Interoperability
- Preparing Your Cluster and Hosts for Fault Tolerance
- Using Fault Tolerance
- Best Practices for Fault Tolerance
- Legacy Fault Tolerance
- Troubleshooting Fault Tolerant Virtual Machines
- Hardware Virtualization Not Enabled
- Compatible Hosts Not Available for Secondary VM
- Secondary VM on Overcommitted Host Degrades Performance of Primary VM
- Increased Network Latency Observed in FT Virtual Machines
- Some Hosts Are Overloaded with FT Virtual Machines
- Losing Access to FT Metadata Datastore
- Turning On vSphere FT for Powered-On VM Fails
- FT Virtual Machines not Placed or Evacuated by vSphere DRS
- Fault Tolerant Virtual Machine Failovers
- 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
3 After the first clone has been created, clone the Active node again for the Witness node.
Option Value
New Virtual Machine Name Name of the Witness node. For example, use vcsa-witness.
Select Compute Resource
Select Storage
Use a different target host and datastore than for the Active and Passive nodes if
possible.
Clone Options Select the Customize the operating system and Power on virtual machine after
creation check boxes and click the New Customization Spec icon on the next
page.
In the New Customization Spec wizard that appears specify the following.
a Use the host name of your choice.
b Ensure the timezone is consistent with the Active node. Keep the same
AreaCode/Location with UTC as the Active node. If you have not specified
AreaCode/Location with UTC while configuring the Active node, keep London
in AreaCode/Location during cloning. London has 0.00 offset, so it keeps the
clock to UTC without any offset.
c On the Configure Network page, specify the IP settings for NIC2, which maps
to the vCenter HA interface. Leave the NIC2 Default Gateway blank.
4 Ensure that the clone process completes and the virtual machines are powered on.
What to do next
Return to the vCenter HA wizard on the Active node to complete the setup. See Complete the vCenter
HA Advanced Configuration.
Complete the vCenter HA Advanced Configuration
After you create the Passive and Witness nodes, return to the configuration wizard on the Active node to
complete the configuration.
Prerequisites
Complete the process of cloning the Active node to a Passive node and a Witness node.
Procedure
1 Return to the configuration wizard and click Finish.
2 Wait for vCenter HA setup to complete.
Manage the vCenter HA Configuration
After you configure your vCenter HA cluster, you can perform management tasks. These tasks include
certificate replacement, replacement of SSH keys, and SNMP setup. You can also edit the cluster
configuration to disable or enable vCenter HA, enter maintenance mode, and remove the cluster
configuration.
n
Set Up SNMP Traps
You can set up Simple Network Management Protocol (SNMP) traps to receive SNMP notifications
for your vCenter HA cluster.
vSphere Availability
VMware, Inc. 81