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
Configure the Network
Regardless of the deployment option and inventory hierarchy that you select, you have to set up your
network before you can start conguration. To set the foundation for the vCenter HA network, you add a
port group to each ESXi host, and add a virtual NIC to the vCenter Server Appliance that later becomes the
Active node.
After conguration is complete, the vCenter HA cluster has two networks, the management network on the
rst virtual NIC and the vCenter HA network on the second virtual NIC.
Management network
The management network serves client requests (public IP). The
management network IP addresses must be static.
vCenter HA network
The vCenter HA network connects the Active, Passive, and Witness nodes
and replicates the appliance state. It also monitors heartbeats.
n
The vCenter HA network IP addresses for the Active, Passive, and
Witness nodes must be static.
n
The vCenter HA network must be on a dierent subnet than the
management network. The three nodes can be on the same subnet or on
dierent 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 nd 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 dierent 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 conguration you select.
n
With a Basic conguration, the wizard creates the vCenter HA virtual NIC on each clone and sets up
the vCenter HA network. When conguration completes, the vCenter HA network is available for
replication and heartbeat trac.
n
With an Advanced conguration.
n
You have to rst create and congure a second NIC on the Active node. See “Create and Congure
a Second NIC on the vCenter Server Appliance,” on page 65.
n
When you perform the conguration, the wizard prompts for the IP addresses for the Passive and
Witness nodes.
Chapter 4 vCenter High Availability
VMware, Inc. 63