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
2147038 Conguring F5 BIG-IP Load Balancer for use with vSphere Platform Services Controller (PSC)
6.5
n
2147046 Conguring NSX Edge Load Balancer for use with vSphere Platform Services Controller (PSC)
6.5
The environment setup is as follows.
Figure 4‑3. vCenter HA with External Platform Services Controller
Platform Services
Controller
Load Balancer
vCenter (Active)
HA Interface
vCenter (Passive)
Witness
vCenter HA
Network
HA Interface
Mgmt Interface
Platform Services
Controller
1 The user sets up at least two external Platform Services Controller instances. These instances replicate
vCenter Single Sign-On information and other Platform Services Controller information, for example,
licensing.
2 During provisioning of the vCenter Server Appliance, the user selects an external
Platform Services Controller.
3 The user sets up the vCenter Server Appliance to point to a load balancer that provides high availability
for Platform Services Controller.
4 The user or the Basic conguration clones the rst vCenter Server Appliance to create the Passive node
and Witness node.
5 As part of the clone process, the information about the external Platform Services Controller and the
load balancer is cloned as well.
6 When conguration is complete, the vCenter Server Appliance is protected by vCenter HA.
7 If the Platform Services Controller instance becomes unavailable, the load balancer redirects requests
for authentication or other services to the second Platform Services Controller instance.
Configuration Workflow Overview
You can select a Basic or Advanced conguration option. The Basic option automatically creates the Passive
and Witness nodes as part of vCenter HA conguration. With the Advanced option, you are responsible for
manually cloning the Active node to create the Passive and Witness nodes.
The conguration option that you select depends on your environment. The Basic conguration
requirements are stricter, but more of the conguration is automated. The Advanced conguration is
possible if your environment meets hardware and software requirements, and it oers more exibility.
However, Advanced conguration requires that you create and congure the clones of the Active node.
Chapter 4 vCenter High Availability
VMware, Inc. 61