Fix cisco temperature limit (#9985)

* The SNMP value ciscoEnvMonTemperatureThreshold is now stored as high limit (and no more as high warning limit)

* Updating misc/notifications.rss to make the user aware of the behavioral change

* Addition of missing </description> in the misc/notifications.rss
This commit is contained in:
Yann Gauteron
2019-03-19 08:12:54 -05:00
committed by Tony Murray
parent 05186d4b50
commit bafc195ae3
2 changed files with 6 additions and 1 deletions
@@ -16,7 +16,7 @@ if (is_array($temp)) {
foreach ($temp as $index => $entry) {
if ($temp[$index]['ciscoEnvMonTemperatureState'] != 'notPresent' && !empty($temp[$index]['ciscoEnvMonTemperatureStatusDescr'])) {
$descr = ucwords($temp[$index]['ciscoEnvMonTemperatureStatusDescr']);
discover_sensor($valid['sensor'], 'temperature', $device, $cur_oid.$index, $index, 'cisco', $descr, '1', '1', null, null, $temp[$index]['ciscoEnvMonTemperatureThreshold'], null, $temp[$index]['ciscoEnvMonTemperatureStatusValue'], 'snmp', $index);
discover_sensor($valid['sensor'], 'temperature', $device, $cur_oid . $index, $index, 'cisco', $descr, '1', '1', null, null, null, $temp[$index]['ciscoEnvMonTemperatureThreshold'], $temp[$index]['ciscoEnvMonTemperatureStatusValue'], 'snmp', $index);
}
}
}
+5
View File
@@ -53,5 +53,10 @@
<description>As described previously, Legacy Alert Templates and Transports have been removed. You can find more info here: https://community.librenms.org/t/deprecation-notice-alerting-legacy-transports-and-templates/5915</description>
<pubDate>Fri, 15 Feb 2017 23:00:00 +0000</pubDate>
</item>
<item>
<title>Cisco Temperature Sensor Threshold Values Stored as High Limits</title>
<description>During discovery, some temperature sensors discovered on Cisco devices had their highest temperature value stored as warning high limit. For new discovered devices, this value is now stored as high limit.</description>
<pubDate>Sun, 17 Mar 2019 21:00:00 +0100</pubDate>
</item>
</channel>
</rss>