Page 1 of 1

snmptt.conf mib oids and Variables

Posted: Fri May 19, 2017 7:09 am
by vijilants
System:

Nagios XI Version : 5.4.4
CentOS release 6.5 (Final)

Can anyone please assist on the following issue:

We use SNMP traps to monitor an Adtran MX2800 device. The device has 28 x T1 ports. However if two or more of theT1 ports go in to alarm, the traps come in to nagios, however on the status screen, say if two ports are in alarm, the status screen will only show one port.

I have identified this due to the fact that the OID for the alarm fo all ports in relation to the alarm in question are the same. However is it possible to get an individual trap for each port to show up on the status screen so that we see all the ports that are in alarm rather than seeing only the last one that came in to the system ?

I'm not too sure as to what is meant by Variables in the snippet below from the snmptt.conf file below which shows the OID and alarm in question and if manipulating this in any way would provide the desired effect.

Code: Select all

EVENT adMX2800xSetT1E1AISCarrier .1.3.6.1.4.1.664.1.198.0.44694 "Status Events" WARNING
FORMAT Status - Alarm: MX2800 44694: T1/E1 AIS Carrier Condition ActiveDSX Index: $1, Line ID: $2, Alarm Status, $3System Name, $4
EXEC /usr/local/bin/snmptraphandling.py "$r" "SNMP Traps" "$s" "$@" "$-*" "Status - Alarm: MX2800 44694: T1/E1 AIS Carrier Condition ActiveDSX Index: $1, Line ID: $2, Alarm Status, $3System Name, $4"
SDESC
This indicates that MX2800 enters T1/E1 AIS Carrier mode.
Variables:
  1: adMX2800StatusDSXIndex
  2: adMX2800DSXCfgLineID
  3: adMX2800SystemAlarmStatus
  4: sysName
EDESC
#

Re: snmptt.conf mib oids and Variables

Posted: Fri May 19, 2017 1:11 pm
by tgriep
The status that is displayed in Nagios will only show the last trap received for that service check and there is not a way to show the history in the GUI.
If you enabled the stalking options for that service check, you would be able to run the State History Report and see the individual Alerts as they came in to XI.
FYI, this will only show the different warning and critical alerts, it multiple OK checks came in with different status, the report will not show it.


If you want to see the Alert in the GUI, you may have to create separate service checks, one for each interface so they will not get over written by the status of the other interfaces.
I am guessing that the adMX2800DSXCfgLineID variable is the name of the T1 port, so in the EXEC line, you would replace the "SNMP Trap" option with $2 for example and that would make the TRAP unique to that port and a unique service in XI.
Try it out and see if it works for you.

Re: snmptt.conf mib oids and Variables

Posted: Tue May 23, 2017 10:54 am
by vijilants
tgriep wrote:The status that is displayed in Nagios will only show the last trap received for that service check and there is not a way to show the history in the GUI.
If you enabled the stalking options for that service check, you would be able to run the State History Report and see the individual Alerts as they came in to XI.
FYI, this will only show the different warning and critical alerts, it multiple OK checks came in with different status, the report will not show it.
If you want to see the Alert in the GUI, you may have to create separate service checks, one for each interface so they will not get over written by the status of the other interfaces.
I am guessing that the adMX2800DSXCfgLineID variable is the name of the T1 port, so in the EXEC line, you would replace the "SNMP Trap" option with $2 for example and that would make the TRAP unique to that port and a unique service in XI.
Try it out and see if it works for you.
Thank you

On the first point if i see do a state history on the device services the alarms for the individual traps are logged however, as I said before, in the live view you only see one SNMP trap alarm as the previous one appears to have been overwritten.

In relation to changing the EXEX line, can you kindly change it for me and paste it here so that I can see exactly what it should look like ?

Thanks

Re: snmptt.conf mib oids and Variables

Posted: Tue May 23, 2017 11:48 am
by tgriep
The example EXEC command that you would use.

Code: Select all

EXEC /usr/local/bin/snmptraphandling.py "$r" "$2" "$s" "$@" "$-*" "Status - Alarm: MX2800 44694: T1/E1 AIS Carrier Condition ActiveDSX Index: $1, Line ID: $2, Alarm Status, $3System Name, $4"
What this will do is setup unique check on the XI server when a new port fails. But, the first time it is received in XI, it has to be configures in the Admin > Unconfigured Objects menu.
After that, it will be automatically received.