The vCenter adapter provides alert definitions that generate alerts on the Cluster Compute Resource objects in your environment.

Health/Symptom-Based

These alert definitions have the following impact and criticality information.

Impact

Health

Criticality

Symptom-based

Alert Definition

Symptoms

Recommendations

DRS-enabled cluster has CPU contention caused by less than half of the virtual machines.

Symptoms include all of the following:

  • DRS enabled

  • DRS fully automated

  • Cluster CPU contention at warning/immediate/critical level

  • > 0 descendant virtual machines have [ Virtual machine CPU demand at warning/ immediate/critical level ]

  • <= 50% of descendant virtual machines have [Virtual machine CPU demand at warning/ immediate/critical level ]

Use vSphere vMotion to migrate some virtual machines to a different cluster if possible.

DRS-enabled cluster has CPU contention caused by more than half of the virtual machines.

Symptoms include all of the following:

  • DRS enabled

  • DRS fully automated

  • Cluster CPU contention at warning/immediate/critical level

  • Cluster CPU workload at warning/immediate/critical level

  • > 50% of descendant virtual machines have [ Virtual machine CPU demand at warning/ immediate/critical level ]

  1. Use vSphere vMotion to migrate some virtual machines to a different cluster if possible.

  2. Add more hosts to the cluster to increase CPU capacity.

DRS-enabled cluster has CPU contention caused by overpopulation of virtual machines.

Symptoms include all of the following:

  • DRS enabled

  • DRS fully automated

  • Cluster CPU contention at warning/immediate/critical level

  • Cluster CPU workload at warning/immediate/critical level

  • == 0 descendant virtual machines have [ Virtual machine CPU demand at warning/ immediate/critical level ]

  1. Use vSphere vMotion to migrate some virtual machines to a different cluster if possible.

  2. Add more hosts to the cluster to increase CPU capacity.

DRS-enabled cluster has unexpected high CPU workload.

Symptoms include all of the following:

  • DRS enabled

  • DRS fully automated

  • Cluster CPU workload above DT

  • Cluster CPU workload at warning/immediate/critical level

  1. Check the applications running on the virtual machines in the cluster to determine whether high CPU workload is an expected behavior.

  2. Add more hosts to the cluster to increase CPU capacity.

  3. Use vSphere vMotion to migrate some virtual machines to a different cluster if possible.

DRS-enabled cluster has memory contention caused by less than half of the virtual machines.

Symptoms include all of the following:

  • DRS enabled

  • DRS fully automated

  • Cluster memory contention at warning/immediate/critical level

  • > 0 descendant virtual machines have [ Virtual machine memory workload at warning /immediate/critical level ]

  • <= 50% of descendant virtual machines have [Virtual machine memory workload at warning/ immediate/critical level ]

Use vSphere vMotion to migrate some virtual machines to a different cluster if possible.

DRS-enabled cluster has memory contention caused by more than half of the virtual machines.

Symptoms include all of the following:

  • DRS enabled

  • DRS fully automated

  • Cluster memory contention at warning/immediate/critical level

  • Cluster memory workload at warning/immediate/critical level

  • > 50% of descendant virtual machines have [ Virtual machine memory demand at warning/ immediate/critical level ]

  1. Use vSphere vMotion to migrate some virtual machines to a different cluster if possible.

  2. Add more hosts to the cluster to increase memory capacity.

DRS-enabled cluster has memory contention caused by overpopulation of virtual machines.

Symptoms include all of the following:

  • DRS enabled

  • DRS fully automated

  • Cluster memory contention at warning/immediate/critical level

  • Cluster memory workload at warning/immediate/critical level

  • == 0 descendant virtual machines have [ Virtual machine memory demand at warning /immediate/critical level ]

  1. Use vSphere vMotion to migrate some virtual machines to a different cluster if possible.

  2. Add more hosts to the cluster to increase memory capacity.

More than 5% of virtual machines in the cluster have memory contention caused by memory compression, ballooning or swapping.

  • ! Virtual machine memory limit is set AND

  • > 5% of descendant virtual machines have [ virtual machine memory contention is at warning/immediate/critical level] AND

  • > 5% of descendant virtual machines have [ Virtual machine memory is compressed OR

  • Virtual machine is using swap OR

  • Virtual machine memory ballooning is at warning/immediate/critical level]

  1. Add more hosts to the cluster to increase memory capacity.

  2. vSphere vMotion some virtual machines off the host or cluster.

DRS-enabled cluster has unexpected high memory workload and contention.

Symptoms include all of the following:

  • DRS enabled

  • DRS fully automated

  • Cluster memory contention above DT

  • Cluster memory content is at warning/immediate/critical level

  • Cluster memory workload at warning/immediate/critical level

  1. Check the applications running on the virtual machines in the cluster to determine whether high memory workload is an expected behavior.

  2. Add more hosts to the cluster to increase memory capacity.

  3. Use vSphere vMotion to migrate some virtual machines to a different cluster if possible.

vSphere HA failover resources are insufficient.

vSphere HA failover resources are insufficient (fault symptom)

  • Use similar CPU and memory reservations for all virtual machines in the cluster OR

  • Use a different vSphere HA admission control policy, such as reserving a percentage of cluster resource for failover OR

  • Use advanced options to specify a cap for the slot size.

For more information, see the vSphere Availability Guide. Hosts that have vSphere HA agent errors are not good candidates for providing failover capacity in the cluster and their resources are not considered for vSphere HA admission control purposes. If many hosts have a vSphere HA agent error, the vCenter Server generates this event leading to the fault. To resolve vSphere HA agent errors, check the event logs for the hosts to determine the cause of the errors. After you resolve any configuration problems, reconfigure vSphere HA on the affected hosts or on the cluster

vSphere HA master missing.

vCenter Server is unable to find a master vSphere HA agent (fault symptom)

Check the fault page under the Analysis tab for this object to find more objects.