Just a newbie here, but think this might be a legit issue rather than just a newbie mistake (feel free to correct me).
I set up a test Cisco 2901 router via SNMPv2 using the provided "Template Net Cisco IOS SNMPv2". That part went fine. Once it had fully populated the triggers, it started throwing a PROBLEM that the CPU temp was too high. The "show environment" on the router shows CPU temp as "CPU temperature: 55 Celsius, Normal", so it's within acceptable range. When digging into the triggers defined on the host, the temperature discovery trigger shows anything above 50C as warning. After digging around the templates, there appear to be a pair of macro values: {$TEMP_WARN} and a {$TEMP_WARN:"CPU"}, the latter having a higher temp (70C vs 50C). The issue appears to be that the template discovery created a trigger for the CPU using the wrong macro value. The host trigger (Configuration->Hosts->Device->Triggers) shows:
Temperature Discovery: CPU: Temperature is above warning threshold: >{$TEMP_WARN:""}
it would appear that this should be:
Temperature Discovery: CPU: Temperature is above warning threshold: >{$TEMP_WARN:"CPU"}
Of all the Cisco devices I've added, the 2901 is the only one that has a discovered CPU temperature trigger set. The other routers and switches have only chassis temperature triggers (yes my lab gear is old eBay/hand-me-downs)...
As part of learning the platform, I'm going to be fiddling with the templates and such to see if I can find a fix for this, but as this was an "out of the box" template, I thought I should pass it along.
Details on this issue:
Zabbix Server: Zabbix 4.2.3 (revision 3685611ba5).
The 2901 is IOS version 15.7(3)M3
Applied template is "Template Net Cisco IOS SNMPv2"
Template with the apparent issue: "Template Module Cisco CISCO-ENVMON-MIB SNMPv2"
Discovery Rule "Temperature Discovery"
Not sure if you can embed a macro within a macro, but it looks like that's what you'd want given they have a CPU specific temperature thresholds. Not sure if you have to create a separate discovery rule for that or not.
I set up a test Cisco 2901 router via SNMPv2 using the provided "Template Net Cisco IOS SNMPv2". That part went fine. Once it had fully populated the triggers, it started throwing a PROBLEM that the CPU temp was too high. The "show environment" on the router shows CPU temp as "CPU temperature: 55 Celsius, Normal", so it's within acceptable range. When digging into the triggers defined on the host, the temperature discovery trigger shows anything above 50C as warning. After digging around the templates, there appear to be a pair of macro values: {$TEMP_WARN} and a {$TEMP_WARN:"CPU"}, the latter having a higher temp (70C vs 50C). The issue appears to be that the template discovery created a trigger for the CPU using the wrong macro value. The host trigger (Configuration->Hosts->Device->Triggers) shows:
Temperature Discovery: CPU: Temperature is above warning threshold: >{$TEMP_WARN:""}
it would appear that this should be:
Temperature Discovery: CPU: Temperature is above warning threshold: >{$TEMP_WARN:"CPU"}
Of all the Cisco devices I've added, the 2901 is the only one that has a discovered CPU temperature trigger set. The other routers and switches have only chassis temperature triggers (yes my lab gear is old eBay/hand-me-downs)...
As part of learning the platform, I'm going to be fiddling with the templates and such to see if I can find a fix for this, but as this was an "out of the box" template, I thought I should pass it along.
Details on this issue:
Zabbix Server: Zabbix 4.2.3 (revision 3685611ba5).
The 2901 is IOS version 15.7(3)M3
Applied template is "Template Net Cisco IOS SNMPv2"
Template with the apparent issue: "Template Module Cisco CISCO-ENVMON-MIB SNMPv2"
Discovery Rule "Temperature Discovery"
Not sure if you can embed a macro within a macro, but it looks like that's what you'd want given they have a CPU specific temperature thresholds. Not sure if you have to create a separate discovery rule for that or not.
Comment