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
n
The wizard prompts you to clone the Active node. As part of the clone process, you perform
additional network conguration.
See “Congure vCenter HA With the Advanced Option,” on page 65.
Configure vCenter HA With the Basic Option
When you use the Basic option, the vCenter HA wizard creates and congures a second network adapter on
the vCenter Server Appliance, clones the Active node, and congures the vCenter HA network.
Prerequisites
n
Deploy vCenter Server Appliance that you want to use as the initial Active node.
n
The vCenter Server Appliance must have a static IP address.
n
SSH must be enabled on the vCenter Server Appliance.
n
Verify that your environment meets one of the following requirements.
n
Either the vCenter Server Appliance that will become the Active node is managing its own ESXi
host and its own virtual machine. This conguration is sometimes called a self-managed
vCenter Server.
n
Or the vCenter Server Appliance is managed by another vCenter Server (management
vCenter Server) and both appliances are in the same vCenter Single Sign-On domain. That means
they both use an external Platform Services Controller and both are running vSphere 6.5.
If your environment does not meet one of these requirements, perform an Advanced conguration. See
“Congure vCenter HA With the Advanced Option,” on page 65.
n
Set up the infrastructure for the vCenter HA network. See “Congure the Network,” on page 63.
n
Determine which static IP addresses to use for the two vCenter Server Appliance nodes that will
become the Passive node and Witness node.
Procedure
1 Log in to the Active node with the vSphere Web Client.
2 Right-click the vCenter Server object in the inventory and select vCenter HA .
3 Click .
4 Select the Basic conguration option and click Next.
This option is available only if your environment meets prerequisites for the Basic option.
5 Specify the IP address, subnet mask for the Active node and the port group to connect to the vCenter
HA network and click Next.
6 Provide the vCenter HA network IP address and subnet mask for the Passive node and the Witness
node and click Next.
The conguration wizard needs the addresses to create the vCenter HA network and to connect the
three nodes.
7 (Optional) Click Advanced if you want to override the failover management IP address for the Passive
node.
8 Review the information for the Passive and Witness nodes, click Edit to make changes, and click Next.
If you are not using a DRS cluster, select dierent hosts and datastores for the Passive and Witness
nodes if possible.
9 Click Finish.
vSphere Availability
64 VMware, Inc.