Discussion thread for official Zabbix Templates for Cisco

[AlexL]

This thread is designed to provide grounds for discussion of the official Zabbix Template for Cisco.
The template and details of the template will soon be available in GIT repository.


Zabbix is always looking for ways to improve our services and to make our users happier.
We pride ourselves on doing our best each and every day, but we know that there is always something more to learn.

[smlvalk]

Good day,

I'm pretty new in Zabbix and sorry for my english.
I have a question regarding Cisco UCS Manager SNMP template. How can I edit macros {$TEMP.MAX.CRIT:"Ambient"} from 35 to 45?
When I trying to save it and refresh page value goes back to 35.

Thanks.

[stu_net]

Hi,

Thanks for the great template. I added the following Marcos:
{$TEMP_CRIT:regex:"Homewood"} - 110
{$TEMP_WARN:regex:"Homewood"} - 90

[povtux]

Hi all,

I tested the 'Cisco Nexus 9000 Series by SNMP' on Nexus 9000 & 7000 successfully, maybe the template could be renamed 'Cisco Nexus by SNMP'

Then, for temperature discovery, I propose to add minor & major thresholds from the SNMP values instead of using constants:
Major:
snmp_oid: '1.3.6.1.4.1.9.9.91.1.2.1.1.4.{#SNMPINDEX}.2'
key: 'sensor.temp.MajorThresh[{#SNMPINDEX}]'

Minor:
snmp_oid: 'get[SNMPv2-SMI::enterprises.9.9.91.1.2.1.1.4.{#SNMPINDEX}.1]'
key: 'sensor.temp.MinorThres[{#SNMPINDEX}]'

and use the values in trigger protos instead of constants:

name: '{#SNMPVALUE}: Temperature is above critical threshold'
expression: 'avg(/Cisco Nexus 9000 Series by SNMP/sensor.temp.value[{#SNMPINDEX}],5m)>last(/Cisco Nexus 9000 Series by SNMP/sensor.temp.MajorThresh[{#SNMPINDEX}])'
recovery_expression: 'max(/Cisco Nexus 9000 Series by SNMP/sensor.temp.value[{#SNMPINDEX}],5m)<last(/Cisco Nexus 9000 Series by SNMP/sensor.temp.MajorThresh[{#SNMPINDEX}])-3'
event_name: '{#SNMPVALUE}: Temperature is above critical threshold: >last(/Cisco Nexus 9000 Series by SNMP/sensor.temp.MajorThresh[{#SNMPINDEX}])°C'

name: '{#SNMPVALUE}: Temperature is above warning threshold'
expression: 'avg(/Cisco Nexus 9000 Series by SNMP/sensor.temp.value[{#SNMPINDEX}],5m)>last(/Cisco Nexus 9000 Series by SNMP/sensor.temp.MinorThres[{#SNMPINDEX}])'
recovery_expression: 'max(/Cisco Nexus 9000 Series by SNMP/sensor.temp.value[{#SNMPINDEX}],5m)<last(/Cisco Nexus 9000 Series by SNMP/sensor.temp.MinorThres[{#SNMPINDEX}])-3'
event_name: '{#SNMPVALUE}: Temperature is above warning threshold: >last(/Cisco Nexus 9000 Series by SNMP/sensor.temp.MinorThres[{#SNMPINDEX}])°C"}'


this avoids having temperature alerts due to constants that does not match the thresholds of each module of each device type.

[mcbrineellis]

Maybe I have misunderstood something, but there is an issue with the trigger expression for "Interface {#IFNAME}({#IFALIAS}): Link down", specifically the change() part of the trigger expression.

expression: |
{$IFCONTROL:"{#IFNAME}"}=1
and last(/Cisco Nexus 9000 Series by SNMP/net.if.status[{#SNMPINDEX}])=2
and change(/Cisco Nexus 9000 Series by SNMP/net.if.status[{#SNMPINDEX}])

The description says the following:

change(//net.if.status[{#IFNAME}]) - condition prevents firing of trigger if status did not change. It helps in cases, when interfaces were initially down.
BEWARE, manual close will ceasefire until at least two status changes happens again!

When an interface goes from UP to DOWN, the trigger will fire. However the alert immediately clears (making it seem like the issue is resolved) because next time the interface status net.if.status is collected, the trigger expression no longer evaluates as a problem since there was no change to the status (DOWN -> DOWN = no change).

I am making this adjustment to the template on my end but it seems to be a serious enough bug that I expect Zabbix should correct the issue in the template on their side too.

[KBBarbers]

Good catch! luckily it hasn't impacted our site yet

What logic did you implement to accommodate both conditions where the link was initially down, and where the link went down for 2 collections?

[KBBarbers]

Hold on, what version of zabbix did you install? I installed 7.0.6 from November

I just checked my 9000 series template and my triggers looked like:

{$IFCONTROL:"{#IFNAME}"}=1 and last(/Windows by Zabbix agent/net.if.status["{#IFGUID}"])<>2 and (last(/Windows by Zabbix agent/net.if.status["{#IFGUID}"],#1)<>last(/Windows by Zabbix agent/net.if.status["{#IFGUID}"],#2))

with recovery expression:

last(/Windows by Zabbix agent/net.if.status["{#IFGUID}"])=2 or {$IFCONTROL:"{#IFNAME}"}=0

I know that it is a design decision that if you update your server to the latest version it wont update your templates automatically so that it wont overwrite your customisations

[mcbrineellis]

The trigger expression is the exact same in version 6.0 and 7.0 (I am running Zabbix 6.0).
Looks from the trigger expression you shared, you are looking at the Windows by Zabbix Agent template, not the Cisco Nexus 9000 Series by SNMP template?

Branch release/6.0:

https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/net/cisco/cisco_nexus_9000_series_snmp/template_net_cisco_nexus_9000_series_snmp.yaml?at=refs%2Fheads%2Frelease%2F6.0#923

Branch release/7.0:

https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/net/cisco/cisco_nexus_9000_series_snmp/template_net_cisco_nexus_9000_series_snmp.yaml?at=refs%2Fheads%2Frelease%2F7.0#893

[mcbrineellis]

Is anyone from Zabbix is monitoring these forums?