Using SNMP LLD to discover interfaces, then filtering

[FonTim]

Hi all,

I am using Zabbix 2.0.5 and monitoring just under 100 network devices.

Currently I have the regular ifDescr LLD rule to discover and monitor interface statistics with understandable names/keys, and would very much like to know if it is possible to combine this discovery with another (specifically when ifOperStatus = 1).

It is my understanding that with 2.2 I will be able to do this by having only the ifOperStatus discovery rule, and then using the ifDescr/ifAlias value in the item name/key.

Until that point, do I have any hope of monitoring this way, or do I just need to choose between good names but uselessly monitoring disconnected ports, or efficeint monitoring of only connected ports with unreadable index names...

[fernando360]

Hi,
Do you got some solution to do this?

[netopier]

Did 2.2 solved your problem? Because I had same problem like you and I solved it by using external script to make the results as you want.

Check this:

https://www.zabbix.com/forum/showthread.php?t=25140&page=3

Only difference is, that Im searching string in ifAlias instead ifOperStatus like you want, but converting the script is simple.

[fernando360]

Template dynamic snmp filter by ifAlias

Hi,
Actually in 2.2.2 i made some workarounds to do a lld with filter by description of router interfaces.
I configure some regular expression item (Admin>General>Regular Expression) with some string to include from description, that i call Decription_IP, mentioned like @Description_IP at discovery rule´s filter. In all my routers i configure this string that i wish to monitor.

Because the ifIndex isn´t my SNMPINDEX, in this case is the interface description, i have to configure a item to check ifName and add to the interfaces trigger to match string "NEVER", that i never will use in descriptions, only to use the itemvalue at the trigger. With this value i can refer trigger names to the interface´s name (ex. Giga0/0) by using {ITEM.VALUE#} macro, {ITEM.VALUE4} in this case because is the 4th item in that trigger. This feature came alive from 2.2.0.

I hope that newer versions can handle with new macros that we can use to eliminate this addicional ifname item.

Let´s contribute!

Check my template and use as wish!

Remember to create a macro $SNMP_COMMUNITY with your snmp community and a regular expression "Description_IP" (Admin>General>Regular Expression) with strings that you wish to include, and also exclude to permit exceptions because you can add multiple conditions, use the tester to verify.

Some strings are in portuguese, and some items i check by hour due to my resources limitation.
So feel free to change and contribute with improvements.
Enjoy