Incorrect Temperature Alarms for Cisco EnvMon Devices in Smarts
Article ID: 448966
Updated On:
Products
Issue/Introduction
Temperature-related alerts trigger based on the device default threshold settings instead of custom SMARTS-configured thresholds․
SYMPTOMS:
Device reports invalid threshold values
Missing or false temperature alerts
CONTEXT: Occurs with Cisco devices monitored via CISCO-ENVMON-MIB․
IMPACT: Incorrect monitoring and false alerts․
Environment
VMware Smart Assurance
Any version prior to 25.4.11
Cause
For Cisco devices monitored via the CISCO-ENVMON-MIB, the system always used the temperature threshold value reported by the device itself via SNMP․ The legacy Cisco class ignored the UseMIBThresholds attribute entirely․
Who Is Affected?
Customers monitoring Cisco routers or switches via CISCO-ENVMON-MIB where the device does not return a valid temperature threshold, resulting in incorrect or missing temperature alarms.
Resolution
Upgrade to Smarts release 25․4․11 or higher to get the code fix.
EXPECTED: System uses the threshold configured in Smarts instead of the device-reported MIB threshold․ NOTE: No additional configuration is needed․ The existing setting now covers Cisco EnvMon devices automatically after a reconfiguration․
VERIFY SUCCESS:
Delete and rediscover the device
Verify device generates alarms based on custom configured threshold
Additional Information
DE203702 — Temperature Threshold Source Control for Cisco EnvMon Devices
What Was Fixed?
Smarts can now be configured to use either the device-reported MIB threshold or the threshold configured within Smarts itself — for all devices monitored via CISCO-ENVMON-MIB.
This is controlled by the existing UseMIBThresholds setting, which already governed this behavior for other device types (Cisco EntitySensor, Arista). It now applies to Cisco EnvMon devices as well.
How to Use It
Setting Behavior
UseMIBThresholds = TRUE Use the threshold value reported by the device
UseMIBThresholds = FALSE Use the threshold configured in Smarts
Feedback
