Implications of enabling VMware HA strict admission control
You cannot power on the virtual machine when using VMware HA strict admission control .Trying to power on the virtual machine 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.
This behavior, while providing the most secure failover protection for your cluster, might create issues in certain scenarios:
· If you 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 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 must 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 sufficient 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:
Your particular usage scenario might make disabling VMware HA strict admission control desirable. You should be aware, 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.