Loading

×Sorry to interrupt
This page has an error. You might just need to refresh it.
[NoErrorObjectAvailable] Uncaught ReferenceError: addCTracking is not defined
Failing descriptor: {markup://c:KM_ArticleThemeLayout}

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 IP: 'CurrentUtilization' attribute value is not calculated for some interfaces (364417)

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

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

How is the CurrentUtilization attribute value calculated in Smarts?

Smarts CurrentUtilization attribute value is not calculated for some interfaces

Cause

All interfaces are not instrumented for performance data. If an interface is not instrumented for performance data, Smarts does not calculate the CurrentUtilization attribute value for that interface.

Resolution

If you are unsure about whether an interface should display CurrentUtilization, run an sm_snmpwalk of the device, contact EMC Support for troubleshooting assistance, and quote this solution ID. The following sections of this Fix statement explain the MIB definitions for ifSpeed and ifHighSpeed, how Smarts determines whether to calculate the CurrentUtilization attribute value, and how it calculates that value.

How Smarts determines whether to calculate the CurrentUtilization attribute value
Before the CurrentUtilization attribute value is calculated, Smarts uses the following criteria, based on the speed of the interface in question, to determine if an interface will be instrumented for performance data.

ifSpeed - 1.3.6.1.2.1.2.2.1.5.x   ( in bits per second )

0

< 20 Mb

> 20 Mb < 650 Mb

> 650 Mb

ifHighSpeed 1.3.6.1.2.1.31.1.1.1.15.x  ( in mega bits per second )

Not Exists

NI

MIB2

NI

NI

0

NI

MIB2

NI

NI

< 20 MB

NI

MIB2

NI

NI

> 20 MB - 650 MB

NI

NI

MIB2_ifMib

NI

> 650 MB

ifMib

ifMib

ifMib

ifMib

MIB definitions for ifSpeed and ifHighSpeed
The following sections contain the MIB definitions for ifSpeed and ifHighSpeed.

ifSpeed
An estimate of the interface's current bandwidth in bits per second.  For interfaces which do not vary in bandwidth or for those where no accurate estimation can be made, this object should contain the nominal bandwidth.

ifHighSpeed
An estimate of the interface's current bandwidth in units of 1,000,000 bits per second. If this object reports a value of `n' then the speed of the interface is somewhere in the range of `n-500,000' to `n+499,999'. For interfaces which do not vary in bandwidth or for those where no accurate estimation can be made, this object should contain the nominal bandwidth. For a sub-layer which has no concept of bandwidth, this object should be zero.

How Smarts calculates the CurrentUtilization attribute value
Once Smarts determines that an interface is instrumented for performance data, Smarts uses the following calculations to calculate the actual CurrentUtilization value.

CurrentUtilization = ((TrafficRate * 8) / MaxSpeed * 100;

TrafficRate = (value calculation varies for HALF DUPLEX and FULLDUPLEX Duplex Modes)

= ifInOctetsRate + ifOutOctetsRate; (if DuplexMode is HALFDUPLEX)

= max(ifInOctetsRate, ifOutOctetsRate)  (if DuplexMode is FULLDUPLEX)

ifInOctetsRate = rate(ifInOctets, PollingInterval);

ifOutOctetsRate = rate(ifOutOctets, PollingInterval);

Rate() function used in TrafficRate calculation
For the term rate(A,T) used in the calculation of the TrafficRate value, A is an attribute and T is a time interval, and the function returns the rate at which A changed during the last T seconds. Note that the time interval may be an expression that evaluates to a numeric value.

Therefore, the rate() function needs two values to compute the rate. So if there is no change in ifInOctets (1.3.6.1.2.1.2.2.1.10.x) and ifOutOctets (1.3.6.1.2.1.2.2.1.16.x) during the PollingInterval (where x is the relevant interface index), then the TrafficRate will be 0, which in turn will cause the CurrentUtilization attribute value to also be 0. In this respect, the CurrentUtilization attribute value can be considered intermittent in nature.

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:

Related Versions:

VMware Smart Assurance - SMARTS

Take Our Survey

Support Assistant