vCenter Server Alert
Definitions
The vCenter
adapter provides alert definitions that generate alerts on the
vCenter Server
objects in your environment.
Health/Symptom-Based
These alert definitions have
the following impact and criticality information.
- Impact
- Health
- Criticality
- Symptom-based
Alert Definition
| Symptom
| Recommendations
|
|---|---|---|
A problem occurred with a
vCenter Server
component.
| The
vCenter Server
health changed (fault symptom).
| The actions to take to resolve the
problems depend on the specific problem that caused the fault. Review the issue
details, and check the documentation.
|
Duplicate object name found in the vCenter Server . | Duplicate object name found in the
vCenter Server .
| Ensure that the virtual machines names are unique before enabling the
Name-Based Identification feature. |
The
vCenter Server
Storage data collection failed.
| The
vCenter Server
storage data collection failed.
| Ensure vCenter Management Webservice is
started and Storage Management Service is functioning.
|
VASA Provider(s) disconnected
| One or more VASA Providers disconnected
from
vCenter .
| If the VASA provider is inaccessible from the vCenter and you are
getting an invalid certificate error then, see KB article:2079087. Contact the hardware vendor for further
support. |
Certificate for VASA Provider(s) will
expire soon
| One or more VASA Providers' certificates expire soon. | Contact the hardware vendor for getting support on the CA certificates
and CRLs for VASA provider. |
Refreshing CA certificates and CRLs for
VASA Provider(s) failed
| Refreshing CA certificates and CRLs for
one or more VASA Providers failed.
| Refresh the storage provider certificate as per the following document:
Refresh Storage
Provider Certificates . Contact the hardware vendor for
further support. The Refresh
Storage Provider Certificates is in the vSphere
Storage 6.5 guide. |
Virtual machine has memory contention caused by
swap wait and high disk read latency. | Virtual Machine has a memory contention due to
swap wait and high disk read latency. | Add more memory for the virtual machine and ensure
that VMware Tools is running in the virtual machine. |
Risk/Symptom-Based
These alert definitions have the
following impact and criticality information.
- Impact
- Risk
- Criticality
- Symptom-based
Alert Definition | Symptom | Recommendations |
|---|---|---|
Virtual machine has CPU contention due to
multi-vCPU scheduling issues (co-stop) caused by too many
vCPUs. | Virtual Machine experiences a high co-stop. The
co-stop is the amount of time taken when the virtual machine is
ready to run but is experiencing delay because of the co-vCPU
scheduling contention. High co-stop occurs when too many vCPUs are
configured for the virtual machine, and not enough physical CPUs are
available to manage the co-vCPU scheduling. | Review the symptoms listed and remove the number
of vCPUs from the virtual machine as recommended. |