Router warning traps seen on NSTI but not in Nagios

[vijilants]

Hi

Please do not close this as I do need to fix this and I am now in a situation where certain traps such as OPSF state change, which have been marked in the snmptt file as Critical are not showing up in Nagios but are being seen in NSTI.

Many Thanks

[tmcdonald]

Did you follow any of lgroschen's post? He had asked a few questions and I can't tell if you followed his post or not.

[cmerchant]

Also, could respond with the output from the following commands.

Code: Select all

ls -lva /usr/local/bin | grep -i 'snmp\|addmib'
ls -lva /usr/local/sbin | grep -i 'snmp\|addmib'
ls -lva /usr/sbin | grep -i 'snmp\|addmib'

grep -i 'daemon_uid\|mode =' /etc/snmp/snmptt.ini
grep -i -m 5 'exec' /etc/snmp/snmptt.conf
grep -i 'nag' /etc/group
grep -i 'snmp' /etc/group

ll /var/log/snmptt/
ll -d /var/log/snmptt/
ll /var/spool/snmptt
ll -d /var/spool/snmptt
cat /etc/snmp/snmptt.ini
cat /etc/snmp/snmptrapd.conf

[vijilants]

I haven't had the time to reload the mibs as yet but what I am finding is OSPF neighbor state changes are coming up as Critical in nsti but are not being registered in Nagios. This is getting a little desperate now and I will have to go through those steps at some stage but is there now a quicker way of identifying the problem ?

Also according to his instructions there is no mention of adjusting the trap severity level whereas your pdf "Nagios XI - How to integrate SNMP Traps with Nagios XI" states that you must adjust the trap severity level. Personally I would say that this must be done or else how do you differentiate between Warning, critical and normal traps ?

Here are the responses to the commands that you requested:

Thank you

Code: Select all

[root@]# ls -lva /usr/local/bin | grep -i 'snmp\|addmib'
-rwxr-xr-x   1 root nagios      804 Nov  7 08:44 addmib
-rwxr-xr-x   1 root root       2078 Nov  7 08:44 snmptraphandling.py
-rwxr-xr-x   1 root root      30438 Nov  7 08:44 snmpttconvertmib
[root@]# ls -lva /usr/local/sbin | grep -i 'snmp\|addmib'
[root@]# ls -lva /usr/sbin | grep -i 'snmp\|addmib'
-rwxr-xr-x   1 root root       25720 Nov 10  2010 arpsnmp
-rwxr-xr-x   1 root root       25972 Sep 30 08:37 snmpd
-rwxr-xr-x   1 root root       25992 Sep 30 08:37 snmptrapd
-rwxr-xr-x   1 root root      177466 Oct 22  2012 snmptt
-rwxr-xr-x   1 root root        6493 Oct 22  2012 snmptthandler
[root@]# grep -i 'daemon_uid\|mode =' /etc/snmp/snmptt.ini
mode = daemon
description_mode = 0
# A second (child) process will be started as the daemon_uid user so
daemon_uid = snmptt
[root@]# grep -i -m 5 'exec' /etc/snmp/snmptt.conf
EXEC /usr/local/bin/snmptraphandling.py "$r" "SNMP Traps" "$s" "$@" "$-*" "The newRoot trap indicates that the sending agent has $*"
EXEC /usr/local/bin/snmptraphandling.py "$r" "SNMP Traps" "$s" "$@" "$-*" "A topologyChange trap is sent by a bridge when any of $*"
EXEC /usr/local/bin/snmptraphandling.py "$r" "SNMP Traps" "$s" "$@" "$-*" "Notification that the trigger indicated by the object $*"
EXEC /usr/local/bin/snmptraphandling.py "$r" "SNMP Traps" "$s" "$@" "$-*" "Notification that the rising threshold was met for triggers $*"
EXEC /usr/local/bin/snmptraphandling.py "$r" "SNMP Traps" "$s" "$@" "$-*" "Notification that the falling threshold was met for triggers $*"
[root@]# grep -i 'nag' /etc/group
nagios:x:501:nagios,apache,snmptt
nagcmd:x:502:nagios,apache,snmptt
[root@]# grep -i 'snmp' /etc/group
nagios:x:501:nagios,apache,snmptt
nagcmd:x:502:nagios,apache,snmptt
snmptt:x:489:
[root@]# ll /var/log/snmptt/
total 28968
-rw-rw-r-- 1 snmptt snmptt   222424 Mar 13 04:02 snmptt.log
-rw-rw-r-- 1 snmptt snmptt   364677 Feb 15 01:51 snmptt.log-20150215
-rw-rw-r-- 1 snmptt snmptt  1510817 Feb 22 02:12 snmptt.log-20150222
-rw-rw-r-- 1 snmptt snmptt   374010 Mar  1 03:35 snmptt.log-20150301
-rw-rw-r-- 1 snmptt snmptt   302121 Mar  8 03:04 snmptt.log-20150308
-rw-rw-r-- 1 snmptt snmptt        0 Feb 28 03:11 snmpttsystem.log
-rw-rw-r-- 1 snmptt snmptt      702 Jun  2  2014 snmpttsystem.log-20140603
-rw-rw-r-- 1 snmptt snmptt     3765 Nov  7 08:44 snmpttsystem.log-20141108
-rw-rw-r-- 1 snmptt snmptt     1018 Jan 30 15:14 snmpttsystem.log-20150131
-rw-rw-r-- 1 snmptt snmptt      864 Feb 27 06:32 snmpttsystem.log-20150228
-rw-rw-r-- 1 snmptt snmptt  1563821 Mar 13 04:16 snmpttunknown.log
-rw-rw-r-- 1 snmptt snmptt   790990 Feb 15 03:26 snmpttunknown.log-20150215
-rw-rw-r-- 1 snmptt snmptt   290306 Feb 21 23:02 snmpttunknown.log-20150222
-rw-rw-r-- 1 snmptt snmptt 14105709 Mar  1 03:35 snmpttunknown.log-20150301
-rw-rw-r-- 1 snmptt snmptt  9986409 Mar  8 01:47 snmpttunknown.log-20150308
[root@]# ll -d /var/log/snmptt/
drwxrwxr-x 2 snmptt snmptt 4096 Mar  8 03:09 /var/log/snmptt/
[root@]# ll /var/spool/snmptt
total 0
[root@]# ll -d /var/spool/snmptt
drwxrwxr-x 2 snmptt snmptt 274432 Mar 13 04:16 /var/spool/snmptt
[root@]# 

[tgriep]

Could you search this file and see if the missing traps are in it?

Code: Select all

/var/log/snmptt/snmpttunknown.log

[vijilants]

Could you search this file and see if the missing traps are in it?

I've already tried that and no they are not there. Also the traps are showing up perfectly on NSTI but not in NagiosXI

[tgriep]

In Nagios XI, go to "Admin" > "Unconfigured Objects"
Are they in there?

[vijilants]

In Nagios XI, go to "Admin" > "Unconfigured Objects"
Are they in there?

No they are not there.

[tgriep]

Have you had the chance to reload the mib files on the XI server?

Is there a chance you can disable NSTI on the XI server, reload the SNMP traps on it and see if the XI server starts to receive the traps?

[vijilants]

How do I disable NSTI and reload the SNMP Traps ?....is there a quick process ?....If so can you please detail this.

I really need this fixed now please as NSTI is seeing all the traps correctly but these are not arriving on the NagiosXI system.

Also when I do the following I get a blank screen after I tick "Process Trap" and Upload MIB"

Then you can upload each MIB file, but check the Process trap checkbox, then upload the MIB file. If the upload failed there will be a warning and this will tell you if the MIB is good and readable, if it isn't just download a new copy. If it succeeded you'll see a blue box saying as much. When you upload a MIB this way they are written to snmptt.conf and will include an EXEC line and proper OK, Warning, and Critical lines. It's more than possible that a few typos from manually editing this file could be the reason you are only receiving parts of the picture.

Also I am getting Critical alarms in NSTI but they do not appear in Nagios even though SNMP traps are enabled for the device in Nagios...the alarm below appeared in NSTI but never appeared in Nagios under SNMP traps for the device.

Wed Jun 24 06:52:26 2015 .1.3.6.1.4.1.664.1.198.0.44692 SomAdtran01 Status Events CRITICAL Status - Alarm: MX2800 44692: T1/E1 AIS Loop Condition Active