Implications of enabling or disabling VMware HA strict admission control when using DRS and VMware DPM (1007006)
The behavior described in this article applies to VirtualCenter 2.5 Update 3 and later.
VMware HA strict admission control is enabled by default. You can disable it in the VI Client by opening the VMware HA section of the cluster's Settings dialog box and selecting the Allow VMs to be powered on even if they violate availability constraints check box.
When VMware HA is used with Distributed Resource Scheduler (DRS) or VMware Distributed Power Management (DPM), you should be aware of the possible implications of enabling or disabling VMware HA strict admission control.
When using strict admission control, under certain conditions, you may receive the error:
Insufficient Resources for HA failover
Implications of enabling VMware HA strict admission control
In general, using VMware HA strict admission control ensures that you cannot power on a virtual machine if doing so would violate availability constraints (in other words, cause the current failover level to become less than the configured failover level). When such an attempt is made, a message informs you that the virtual machine cannot be powered on.
When VMware HA strict admission control is enabled, DRS and VMware DPM protect the availability of failover capacity at all times, and only take actions or make recommendations that are consistent with ensuring the availability of that capacity.
- DRS does not evacuate virtual machines from a host for the purpose of placing it in maintenance mode or standby mode if placing the host in this state would violate failover requirements. You can still manually evacuate virtual machines in order to place hosts in maintenance mode or standby mode. If you violate failover requirements by doing this, however, the cluster turns red.
- VMware DPM does not place hosts in standby mode if doing so would violate failover requirements.
- If necessary, VMware DPM powers on hosts (brings them out of standby mode) to maintain failover needs.
This behavior, while providing the most secure failover protection for your cluster, might create issues in certain scenarios:
· If you need to violate the failover constraints because there is a temporary, but nontrivial, time period in which there are not enough resources to support them (for example, if you are placing hosts in standby mode to test them for use with DPM).
· If any automated processes need to take actions that violate the failover constraints (for example as part of an upgrade directed by VMware Update Manager).
If you encounter such issues, you can disable strict admission control.
Implications of disabling VMware HA strict admission control
When you disable VMware HA strict admission control, virtual machines can be powered on even if there are not enough resources to ensure failover capacity. When this is done, no warnings are presented, and the cluster does not turn red.
When strict admission control is disabled, VMware HA failover resource constraints are not passed on to DRS and VMware DPM. Thus, the constraints are not enforced:
- DRS does evacuate virtual machines from hosts and place the hosts in maintenance mode or standby mode regardless of the impact this might have on failover requirements.
- VMware DPM does power off hosts (place them in standby mode) even if doing so violates failover requirements.
Your particular usage scenario might make disabling VMware HA strict admission control desirable. You should be aware, however, that doing so (when interoperating with DRS and VMware DPM or not) can lead to a reduced level of availability and failover protection for your cluster.