Having thousands of switches, routers, firewalls etc, all with unique descriptions on each port, makes informative alarms an absolute must.
I've solved it by modifying the trigger prototype in SNMP Interface discovery.
Or make a new trigger:
Name:
{HOST.HOST}: {#SNMPVALUE}, {ITEM.VALUE1} = {ITEM.VALUE2}
Expression:
{Template SNMP Interfaces:ifAlias[{#SNMPVALUE}].str(nointerfacehasthisdescription)}=0 & {Template SNMP Interfaces:ifOperStatus[{#SNMPVALUE}].diff(0)}=1
Description:
Your choice
Severity:
Your choice
What I'm doing, is making two checks, using AND, so both have to be true for the trigger to fire.
1) Check for a text string in the ifAlias item for this particular interface. We define a string we know does NOT exist on any ports on any device in your network.
2) Check that the latest value of IfOperStatus does not match the previous. (hence triggering an alarm on Link up OR down.
Make sure IfAlias and IfOperStatus is supported by your device, and this should work.
I've solved it by modifying the trigger prototype in SNMP Interface discovery.
Or make a new trigger:
Name:
{HOST.HOST}: {#SNMPVALUE}, {ITEM.VALUE1} = {ITEM.VALUE2}
Expression:
{Template SNMP Interfaces:ifAlias[{#SNMPVALUE}].str(nointerfacehasthisdescription)}=0 & {Template SNMP Interfaces:ifOperStatus[{#SNMPVALUE}].diff(0)}=1
Description:
Your choice
Severity:
Your choice
What I'm doing, is making two checks, using AND, so both have to be true for the trigger to fire.
1) Check for a text string in the ifAlias item for this particular interface. We define a string we know does NOT exist on any ports on any device in your network.
2) Check that the latest value of IfOperStatus does not match the previous. (hence triggering an alarm on Link up OR down.
Make sure IfAlias and IfOperStatus is supported by your device, and this should work.
Comment