This error is given when VMware High Availability VM Health Monitoring does not reset the virtual machine following a failure. The error may also appear if no VM heartbeat was detected and VMware HA took no action.
When configured correctly, VMware High Availability (HA) can reduce or eliminate VMware downtime due to system failure:
- By restarting the virtual machines on other hosts with available capacity in the cluster, VMware HA responds to hardware failure. An example of hardware failure is an isolation response, which generally occurs if a node of a VMware HA cluster is isolated from the network for 15 seconds or longer. VMware HA automatically monitors the availability of physical servers. VMware HA uses admission control to ensure that capacity is always available in order to restart all virtual machines affected by host failure.
- By continuously monitoring a virtual machine's heartbeat and resetting it in when an operating system failure is detected, VMware HA also protects against operating system failure.
VMware HA may be unable to power on virtual machines on alternate hosts or, in some cases, reset a virtual machine. When this occurs, VMware AlarmVM will detect these situations and report on them.
Confio IgniteVM helps identify the impact of a VMware high availability error for sites running Oracle on VMware, SQL Server on VMware, and other virtual databases. IgniteVM helps DBAs maintain performance and availability on virtual servers. IgniteVM is the only virtualization-aware database monitoring solution.
Learn more about IgniteVM solutions for: