{#SNMPINDEX} macro manipulation

[rusadm]

I don't have any unsupported elements.
I created a filter in the Discovery rule:
{#VALUE} 1.3.6.1.4.1.9.9.91.1.1.1.1.4

[kyus]

Just as an addition to rusadm answer, if {#ENTPHYSICALDESCR} exists in your JSON but has no value, you can also try this filter:

[novakm]

I finally got time to test it again

I don't have any unsupported elements.
I created a filter in the Discovery rule:
{#VALUE} 1.3.6.1.4.1.9.9.91.1.1.1.1.4

Im sorry but this works only if the device has populated the entSensorThresholdTable, for example 1.3.6.1.4.1.9.9.91.1.2.1.1.4. As soon as this table is not filled with values you will end up with lots of unsupported items (for example C9200 dont have those tables filled, I dont know why).

Maybe Im missing something trivial but I didn't find a way to prevent creating those unsupported items if the table is not popuplated.

[kyus]

That's why the filter was created, that way you only get items if the macro was populated.

You can add more filters if you need

[cbl]

There is a 3rd party template linked from the templates page here on zabbix.com that does Tx/Rx power. It has triggers for all four of the OID's (the .1-.4 after the snmp index macro)
It also takes into account the threshold and if it's a HIGH mark or LOW mark threshold.

Cisco_Sensors @ https://www.zabbix.com/integrations/cisco#3rd_party

https://github.com/zabbix/community-templates/tree/main/Network_Devices/Cisco/template_for_cisco_optical_sensors_with_autodiscovery

Note: I updated the referenced MIBs in the template to use the OID, to avoid having to load MIBs.


The issue I have with this template is that unused ports on some models still report their Tx/Rx power. Which on an unused port is out of range. This causes a false alarm even when the port is shut.