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
n
The vCenter HA network must be on a different subnet than the
management network. The three nodes can be on the same subnet or
on different subnets.
n
Network latency between the Active, Passive, and Witness nodes must
be less than 10 milliseconds.
n
You must not add a default gateway entry for the cluster network.
Prerequisites
n
The vCenter Server Appliance that later becomes the Active node, is deployed.
n
You can access and have privileges to modify that vCenter Server Appliance and the ESXi host on
which it runs.
n
During network setup, you need static IP addresses for the management network. The management
and cluster network addresses must be IPv4 or IPv6. They cannot be mixed
Procedure
1 Log in to the management vCenter Server and find the ESXi host on which the Active node is
running.
2 Add a port group to the ESXi host.
This port group can be on an existing virtual switch or, for improved network isolation, you can create
a new virtual switch. It must be on a different subnet than the management network on Eth0.
3 If your environment includes the recommended three ESXi hosts, add the port group to each of the
hosts.
What to do next
What you do next depends on the type of configuration you select.
n
With a Basic configuration, the wizard creates the vCenter HA virtual NIC on each clone and sets up
the vCenter HA network. When configuration completes, the vCenter HA network is available for
replication and heartbeat traffic.
n
With an Advanced configuration.
n
You have to first create and configure a second NIC on the Active node. See Create and
Configure a Second NIC on the vCenter Server Appliance.
n
When you perform the configuration, the wizard prompts for the IP addresses for the Passive and
Witness nodes.
n
The wizard prompts you to clone the Active node. As part of the clone process, you perform
additional network configuration.
See Configure vCenter HA With the Advanced Option.
vSphere Availability
VMware, Inc. 76