Loading

×Sorry to interrupt
CSS Error

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

Skip to main content

My Subscriptions

Loading

Knowledge Base

Implications of enabling or disabling VMware HA strict admission control when using DRS and VMware DPM (1007006)

Last Updated: 11/7/2016Categories: InformationalTotal Views: 58612Language:
Chinese (Simplified)JapaneseEnglish

1 like this article

Subscribe to get an email
newsletter with new updates

1 people found this helpful Please provide article feedback:

Details

The behavior described in this article applies to VirtualCenter 2.5 Update 3 and later.

VMware HA (High Availability) 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 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 VMwareDistributedPowerManagement (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

Solution

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.

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.

A minimum of two hosts must be powered on in any HA-enabled cluster.

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:

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, 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.

Additional Information
For translated versions of this article, see:

日本語: DRS および VMware DPM の使用時に VMware HA の厳密なアドミッション コントロールを有効または無効にする場合の影響 (2081795)

简体中文: 使用 DRS 和 VMware DPM 时启用或禁用 VMware HA 严格接入控制的影响 (2087024)

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)JapaneseEnglish

Attachments

Additional Resources

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

KB
•
Preguntas frecuentes sobre vSphere Client (HTML5) y vSphere Web Client 6,5 (2147929)

KB
•
vSphere Client (HTML5) 和 vSphere Web Client 6.5 常见问题 (2147929)

KB
•
Verificando a integridade dos arquivos da máquina virtual do ESX/ESXi (1003743)

Results 1-4 of 4

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vSphere ESXi

VMware VirtualCenter

VMware vCenter Update Manager

VMware vCenter Server

VMware ESX Server

Related Versions:

VMware vSphere ESXi 6.0

VMware vSphere ESXi 5.1

VMware vSphere ESXi 5.0

VMware VirtualCenter 2.5.x

VMware vCenter Server 6.0.x

VMware vCenter Server 5.1.x

VMware vCenter Server 5.0.x

VMware vCenter Server 4.1.x

VMware vCenter Server 4.0.x

VMware ESXi 4.1.x Installable

VMware ESXi 4.0.x Installable

VMware ESXi 4.0.x Embedded

VMware ESXi 3.5.x Installable

VMware ESXi 3.5.x Embedded

VMware ESX Server 3.5.x

VMware ESX 4.1.x

VMware ESX 4.0.x

view all

Take Our Survey

Was this article helpful?

YES

NO

Copyright © 2005-2024 Broadcom. All Rights Reserved. The term “Broadcom” refers to Broadcom Inc. and/or its subsidiaries.

Terms of Use

Your California Privacy Rights

Privacy

Accessibility

Cookie Settings

Support Assistant