Information Technology Reference
In-Depth Information
the assumption that the guest OS has failed. To help with troubleshooting, vSphere also takes
a screen shot of the VM's console right before vSphere HA restarts the VM. This might help
capture any sort of diagnostic information, such as a kernel dump or blue-screen STOP error for
Windows-based systems.
Figure 7.23
You can confi gure
vSphere HA to
monitor for guest
OS and application
heartbeats and
restart a VM when a
failure occurs.
vSphere HA also has application monitoring. This functionality requires third-party soft-
ware to take advantage of APIs built into VMware Tools to provide application-specii c heart-
beats to vSphere HA. By leveraging these APIs, third-party software developers can further
extend the functionality of vSphere HA to protect against the failure of specii c applications. To
enable VM or application monitoring, simply select the desired level of protection from the VM
Monitoring Status drop-down list shown in Figure 7.23.
If you have enabled VM or application monitoring, you can then adjust the monitoring
sensitivity. This slider bar controls how often vSphere HA will restart a VM based on a loss of
VMware Tools heartbeats and a lack of disk and network I/O trafi c. The slider bar also controls
the failure window before which vSphere HA will restart a VM again after a maximum number
of failures. Table 7.2 shows the values set by each position on the slider.
Table 7.2:
VM monitoring sensitivity settings
Monitoring
Sensitivity
Setting
Failure
Interval
Minimum
Uptime
Maximum
Failures
Failure Window
Low
2 minutes
8 minutes
3
7 days
Medium
1 minute
4 minutes
3
24 hours
High
30 seconds
2 minutes
3
1 hour
Search WWH ::




Custom Search