If a vCenter HA cluster is in a degraded state, alarms and events show errors.

Problem

Table 1. The following events will raise VCHA health alarm in vpxd:

Event Name

Event Description

Event Type

Category

vCenter HA cluster state is currently healthy

vCenter HA cluster state is currently healthy

com.vmware.vcha.cluster.state.healthy

info

vCenter HA cluster state is currently degraded

vCenter HA cluster state is currently degraded

com.vmware.vcha.cluster.state.degraded

warning

vCenter HA cluster state is currently isolated

vCenter HA cluster state is currently isolated

com.vmware.vcha.cluster.state.isolated

error

vCenter HA cluster is destroyed

vCenter HA cluster is destroyed

com.vmware.vcha.cluster.state.destroyed

info

Table 2. 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.health.healthy

info

PSC HA state is currently degraded

PSC HA state is currently degraded

com.vmware.vcha.psc.ha.health.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.health.unknown

info

Table 3. 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.joined

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.succeeded

info

Failover cannot proceed when cluster is in disabled mode

Failover cannot proceed when cluster is in disabled mode

com.vmware.vcha.failover.failed.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.failed.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.failed.passive.not.ready

warning

vCenter HA cluster mode changed to {clusterMode}

vCenter HA cluster mode changed

com.vmware.vcha.cluster.mode.changed

info

Node {nodename} was forcefully converted to the Active node

This node was forcefully converted to the Active node

com.vmware.vcha.force.reset.active

info

Table 4. 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.replication.state.changed

info

Table 5. File replication-related events

Event Name

Event Description

Event Type

Category

Appliance {fileProviderType} is {state}

Appliance File replication state changed

com.vmware.vcha.file.replication.state.changed

info