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

Smarts PM Calculates very High Utilization Values with HighUtilization Event (352681)

Last Updated: 3/22/2024Categories: TroubleshootingTotal Views: 5555Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

Smarts PM Calculates very High Utilization Values with HighUtilization Event

Cause

There are several known defects in the SNMP Agents of various vendors where the high capacity (HC) 64-bit counters wrap to zero at the 32 bit mark. This is an incorrect behavior of the SNMP Agent devices.

Background
High Utilization calculations can use one of two sets of variables.  IfInOctets (OID: 1.3.6.1.2.1.2.2.1.10) and IfOutOctets  (OID: .1.3.6.1.2.2.1.16) were defined as 32-bit counters in the original MIB specifications from the IETF.  Because these counters were 32-bit, the maximum value they could hold was 2^32. As interfaces became faster, 2^32 was insufficient and network managers saw the values wrapping between polling cycles. Sometimes, the values could wrap several times between polls making these values unreliable at higher interface speeds. An extended Interface MIB was defined  to overcome the wrapping problem which included ifHCInOctets (OID .1.3.6.1.2.1.31.1.1.1.6) and ifHCOutOctets (OID: .1.3.6.1.2.1.31.1.1.1.10) as 64 bit counters.

When HC counters exist, Smarts uses them to calculate Utilization. Smarts has forumulas that handle a wrap of the counter gracefully. When any of the counter values decreases (and systemUpTime does not) Smarts regards this as a wrap and takes the difference between the max counter value and the last reading then adds the current reading and divides by the polling rate. For example, the ifInOctets formula for the wrapping of 32-bit counters is as follows:

((2^32 - LastValue) + CurrentValue)/PollTime

When HC counters exist, the ifHCInOctets formula for the wrapping of 64-bit counters is as follows:

((2^64 - Last Value) + CurrentValue)/PollTime

The problem described in this solution occurs because the 64-bit HC counters are wrapping at 32-bits.

Note: The default PollTime for Utilization variables is 240 seconds.

Resolution

As a defect in the SNMP Agent of the device, this issue cannot be resolved by EMC. Contact the device vendor for an update to the SNMP Agent. EMC Support does have a script available to assist with collection of data to confirm that the HC counters wrap at 32 bits instead of 64 bits. Contact EMC Support for more information on this script, and quote this solution ID.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

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

Result 1 of 1

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

Related Versions:

VMware Smart Assurance - SMARTS

Take Our Survey

Support Assistant