Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

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

My Subscriptions

Loading

Knowledge Base

The Total Reservation Capacity value is larger than the Cluster Total Capacity value in cluster Resource Reservation page in Web Client (76854)

Last Updated: 1/28/2020Categories: InformationalTotal Views: 5034Language:
English

5 like this article

Subscribe to get an email
newsletter with new updates

5 people found this helpful Please provide article feedback:

Symptoms

When a DRS cluster becomes resource over-committed the Total Reservation Capacity value displayed on its "Monitor->Resource Reservation" page in Web Client could be larger than the "Cluster Total Capacity" value on the same page.

A message like below will also be displayed on the cluster Summary page indicating the over-committed state.
"Insufficient capacity in cluster XXX to satisfy resource configuration in XXX"

Purpose

The purpose of this article is to explain this behavior to avoid possible confusions.

Cause

In the current design the "Total Reservation Capacity" value is simply the sum of "Used Reservation" and "Available Reservation". This is correct in normal cases.

"Used Reservation" includes the reservation configured at the direct child VMs and the child resource pools as well as resource reserved for HA Admission Control policy.

"Available Reservation" computes differently in normal cases and over-committed cases. In normal cases, it is result of the total available resource for reservation subtracting "Used Reservation" above.

When a DRS cluster becomes over-committed due to cluster member hosts number change (i.e. some hosts are moved out of cluster) the existing resource pool reservation settings is no longer valid under the new capacity(In this case, the "Insufficient capacity ..." message is displayed on the cluster Summary page for vCenter administrator to intervene and correct). In this case we would still want to allow VMs to be powered on at the cluster root node to reduce the impact from such invalid configuration. Hence the calculation of "Available Reservation" is changed to override the reservation configured on the child resource pools, which makes it a result of the total available resource for reservation subtracting reservation configured at the direct child VMs and resource reserved for HA Admission Control policy.

"Used Reservation" on the other hand remains unchanged in over-committed case. The sum of "Used Reservation" and "Available Reservation" actually counts in the resource pool reservation settings twice resulting "Total Reservation Capacity" larger than "Cluster Total Capacity".

Impact / Risks

The behavior of the displayed value is merely a cosmetic issue. The over-committed state of the DRS cluster do need administrator to correct to resume normal DRS functionality.

Resolution

vCenter administrator should take this behavior as a sign of invalid resource pool configuration and correct it by reallocating the resources under the new cluster resource capacity.

VMware is working on improving the UI to reduce the confusion in future updates.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

No results for undefined

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vCenter Server

Related Versions:

VMware vCenter Server 6.7.x

VMware vCenter Server 6.5.x

Take Our Survey

Support Assistant