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 IP: How is a High Temperature threshold set in Smarts IP for Cisco and Juniper devices? (325195)

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

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

How is a High Temperature threshold set in Smarts IP for Cisco and Juniper devices?

Cisco devices in Smarts IP are not using the "High Temperature Threshold" value
The high threshold point for temperature on a Juniper and Cisco device in Smarts IP is not set using the same method

Cause

Setting the high threshold point for temperature on Juniper and Cisco devices is not completed by the same method. The High Temperature Threshold setting in Smarts IP only applies to Juniper devices (this is specified in the Smarts SAM configuration guide, that the extra High Temperature Threshold setting is available only in the Juniper devices). For Cisco devices, the HighThreshold is calculated from the "ciscoEnvMonTemperatureThreshold" (1.3.6.1.4.1.9.9.13.1.3.1.4) provided from the device and the "Relative Temperature Threshold". Please see the definition of these settings in the polling and thresholds page of the Smarts SAM configuration guide for a complete definition of these values.

Cisco device HighThreshold calculation
If the device is a Cisco device and has a ciscoEnvMonTemperatureThreshold = 105 and the RelativeTemperatureThreshold is defined as = 10.0000
This gives a HighThreshold = 94.5000 (105 - 10%).

Juniper device HighThreshold Value
On a Juniper device, this HighThreshold Value is taken as the "High Temperature Threshold" configured in polling and thresholds. Juniper devices do not provide recommended "High Threshold" recommendations in their MIBs, so the Smarts High Temperature Threshold setting was added to facilitate the equivalent functionality on these devices as is native on Cisco devices.

Resolution

The "High Temperature Threshold" setting should only be used when configuring the temperature threshold for a Juniper device. For Cisco devices, the "RelativeTemperature Threshold" setting should be used in addition to the "ciscoEnvMonTemperatureThreshold" provided on the device.

See also KB Article emc228431 for details on how TempSensor OutOfRange events are generated on Cisco 6509 devices.

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