6.5.1

Basic Configuration Workflow
Basic conguration automatically clones the Active node. You must meet one of the following requirements
to perform Basic conguration.
n
Either the vCenter Server Appliance that will become the Active node is managing its own ESXi host
and its own virtual machine. This conguration 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 vCenter Server instances 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 you meet the requirements the Basic workow is as follows.
1 The user deploys the rst vCenter Server Appliance, which will become the Active node.
2 The user adds a second network (port group) for vCenter HA trac on each ESXi host.
3 The user starts the vCenter HA conguration, selects Basic and supplies the IP addresses, the target
ESXi host or cluster, and the datastore for each clone.
4 The system clones the Active node and creates a Passive node with precisely the same seings,
including the same host name.
5 The system clones the Active node again and creates a more light-weight Witness node.
6 The system sets up the vCenter HA network on which the three nodes communicate, for example, by
exchanging heartbeats and other information.
For step-by-step instructions, see “Congure vCenter HA With the Basic Option,” on page 64.
Advanced Configuration Workflow
If you cannot select the Basic option or you want more control over your deployment, you can perform
Advanced conguration. With this option, you are responsible for cloning the Active node yourself as part
of vCenter HA setup. If you select this option and remove the vCenter HA conguration later, you are
responsible for deleting the nodes that you created.
For the Advanced option, the workow is as follows.
1 The user deploys the rst vCenter Server Appliance, which will become the Active node.
2 The user adds a second network (port group) for vCenter HA trac on each ESXi host.
3 The user adds a second network adapter (NIC) to the Active node
4 The user logs in to the vCenter Server Appliance (Active node) with the vSphere Web Client.
5 The user starts the vCenter HA conguration, selects Advanced, and supplies IP address and subnet
information for the Passive and Witness nodes. Optionally, the user can override the failover
management IP addresses.
6 The user logs in to the management vCenter Server and creates two clones of the
vCenter Server Appliance (Active node).
7 The user returns to the conguration wizard on the vCenter Server Appliance and completes the
conguration process.
8 The system sets up the vCenter HA network on which the three nodes exchange heartbeats and
replication information.
9 The vCenter Server Appliance is protected by vCenter HA.
See “Congure vCenter HA With the Advanced Option,” on page 65 for details.
vSphere Availability
62 VMware, Inc.