HP Insight Control Virtual Machine Management 6.3 User Guide

Configuring the polling frequency for virtual machine status checks
Insight Control virtual machine management provides a configurable parameter, VMConfigRefreshRate. This
parameter controls the frequency with which virtual machine management checks for changes in virtual
machine configuration, such as number of NICs on the virtual machine, size of the hard disk, and so on.
Configuration changes on the virtual machines are updated by virtual machine management. The default
polling frequency is 5 seconds.
Add the following configurable parameter in the hpvmm.conf file found in the CMS location <Insight Control
virtual machine management installation directory on CMS>/bin:
VMConfigRefreshRate=<< value in milli seconds >>
For example, VMConfigRefreshRate = 5000
The value of the parameter can be between 5 seconds and 5 minutes. Any values entered outside this range
are automatically adjusted to the max/min value of the range.
Because increasing the polling frequency also reduces the ability of virtual machine management to identify
the changes in virtual machine status.
Failed host recovery
VMware ESX Server
For VMware ESX virtual machines, use the failed host recovery feature if you do not use the VMware vCenter
High Availability (HA) solution.
IMPORTANT: In a setup where both the failed host recovery feature and VMware vCenter HA or VMware
Distributed Resource Scheduler (DRS) are configured, the results might be unpredictable because both
management tools try to control the same resource.
IMPORTANT: Do not configure both the failed host recovery feature and the VMware HA or VMware DRS
solution for the same VMware ESX hosts.
IMPORTANT: Do not configure both the failed host recovery feature and the VMware HA or VMware DRS
solution for the same VMware ESX hosts.
If the virtual machine being moved is part of the vCenter cluster, then a warning message appears.
When a failed host recovery process is being performed for virtual machines failing over to the alternate
hosts, the moved virtual machines might appear as Orphaned in the vCenter. If this occurs, delete the
orphaned nodes from vCenter.
In the failed host recovery procedure, the running virtual machine guest will be recovered as powered off
state in the target host. This is an expected behavior.
Microsoft Hyper-V
The failed host recovery feature enables you to recover a failed virtualchines of Hyper-V R2 server and
leverage the ability of Systems Insight Manager SIM to detect hardware failures. For Microsoft Hyper-V R2
Server, virtual machines on failed hosts must meet the following requirements to be recovered on alternate
hosts:
• The virtual machine must not be highly enabled.
• The virtual machine configuration and disk files must be on cluster shared volumes.
• The virtual machine must not have passed through disk(RDM) disk attached to it.
Configuring the polling frequency for virtual machine status checks 21