Hello,
I'm preparing my new Zabbix 5.0 to monitor replaceable linecards on Cisco switches. CISCO-ENTITY-FRU-CONTROL::cefcModuleOperStatus is exactly what I want to use. But I also want to show the operator something meaningful to identify the linecard, so I also read entPhysicalDescr (from ENTITY-MIB) -- these two OIDs use the same index. So I have:
The issue here is that entPhysicalTable contains way more than just linecards. If I used the above for item prototypes, I get hundreds of useless items. So the question is, can I tell Zabbix to throw away any discovery entry that has undefined {#MODSTATUS}? When I try to add filter expression {#MODSTATUS} does not contain ^$, then it works, but I am getting warnings "Cannot accurately apply filter: no value received for macro "{#MODSTATUS}"."
So, what can I do about this?
I'm preparing my new Zabbix 5.0 to monitor replaceable linecards on Cisco switches. CISCO-ENTITY-FRU-CONTROL::cefcModuleOperStatus is exactly what I want to use. But I also want to show the operator something meaningful to identify the linecard, so I also read entPhysicalDescr (from ENTITY-MIB) -- these two OIDs use the same index. So I have:
Code:
discovery[{#MODSTATUS},cefcModuleOperStatus,{#MODDESCR},entPhysicalDescr]
The issue here is that entPhysicalTable contains way more than just linecards. If I used the above for item prototypes, I get hundreds of useless items. So the question is, can I tell Zabbix to throw away any discovery entry that has undefined {#MODSTATUS}? When I try to add filter expression {#MODSTATUS} does not contain ^$, then it works, but I am getting warnings "Cannot accurately apply filter: no value received for macro "{#MODSTATUS}"."
So, what can I do about this?