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
Table 4‑4. The following events will raise VCHA health alarm in vpxd: (Continued)
Event Name Event Description Event Type Category
vCenter HA cluster state is
currently isolated
vCenter HA cluster state is
currently isolated
com.vmware.vcha.cluster.stat
e.isolated
error
vCenter HA cluster is
destroyed
vCenter HA cluster is
destroyed
com.vmware.vcha.cluster.stat
e.destroyed
info
Table 4‑5. The following events will raise PSC HA health alarm in vpxd:
Event Name Event Description Event Type Category
PSC HA state is currently
healthy
PSC HA state is currently
healthy
com.vmware.vcha.psc.ha.hea
lth.healthy
info
PSC HA state is currently
degraded
PSC HA state is currently
degraded
com.vmware.vcha.psc.ha.hea
lth.degraded
info
PSC HA is not monitored after
vCenter HA cluster is
destroyed
PSC HA state is not being
monitored
com.vmware.vcha.psc.ha.hea
lth.unknown
info
Table 4‑6. Cluster Status Related Events
Event Name Event Description Event Type Category
Node {nodeName} joined back
to the cluster
One node joined back to the
cluster
com.vmware.vcha.node.joine
d
info
Node {nodeName} left the
cluster
One node left the cluster com.vmware.vcha.node.left warning
Failover succeeded Failover succeeded com.vmware.vcha.failover.suc
ceeded
info
Failover cannot proceed when
cluster is in disabled mode
Failover cannot proceed
when cluster is in disabled
mode
com.vmware.vcha.failover.fail
ed.disabled.mode
warning
Failover cannot proceed when
cluster does not have all three
nodes connected
Failover cannot proceed
when cluster does not have
all three nodes connected
com.vmware.vcha.failover.fail
ed.node.lost
warning
Failover cannot proceed when
vPostgres on Passive node is
not ready to takeover
Failover cannot proceed
when Passive node is not
ready to takeover
com.vmware.vcha.failover.fail
ed.passive.not.ready
warning
vCenter HA cluster mode
changed to {clusterMode}
vCenter HA cluster mode
changed
com.vmware.vcha.cluster.mo
de.changed
info
Table 4‑7. Database replication-related events
Event Name Event Description Event Type Category
Database replication mode
changed to {newState}
Database replication state
changed: sync, async or no
replication
com.vmware.vcha.DB.replicat
ion.state.changed
info
vSphere Availability
VMware, Inc. 93