Unable to get traps working. MIB import errors.

[dflick]

I had 1 MIB that I had converted and it was kind of oddball so I deleted the file from the snmp directory. I now get the following error while restarting snmptt:

[root@BMCAPMON01 mibs]# service snmptt restart
Stopping snmptt: [ OK ]
Starting snmptt: Could not open configuration file: /usr/share/snmp/mibs/processed_mibs/CISCO-EIGRP-MIB.txt (No such file or directory) at /usr/sbin/snmptt line 2723.
[ OK ]

I guess I did not delete it properly. Is there some config file I need to look for to clean up the mess I made?

[sreinhardt]

Ah, yes there is, you need to remove the line importing this from /etc/snmp/snmptt.conf. Restart again and it should clear the issue for you.

[dflick]

Figured that one out! LOL. I did not see my post went to page 2!

Any idea on why the traps are still showing as unknown?

[dflick]

Do you have any other things I can try so I can fix the SNMP Traps not being recognized by Nagios?

[lmiltchev]

Can you upload all of the MIBs that you added and some of the OIDs that you are having problems with?

[dflick]

This one should be EIGRP neighbor down

Thu Jan 23 01:56:10 2014: Unknown trap (.1.3.6.1.4.1.9.9.449.0.3) received from 10.255.204.1 at:
Value 0: 10.255.204.1
Value 1: 10.255.204.1
Value 2: 41:0:42:04.02
Value 3: .1.3.6.1.4.1.9.9.449.0.3
Value 4: 10.255.204.1
Value 5:
Value 6:
Value 7:
Value 8:
Value 9:
Value 10:
Ent Value 0: .1.3.6.1.4.1.9.9.449.1.4.1.1.3.0.2604.17=10.252.0.31
Ent Value 1: .1.3.6.1.4.1.9.9.449.1.4.1.1.2.0.2604.17=1

[dflick]

I just noticed that I got a trap for a config write! The EIGRP that I sent is still showing as unknown so it must be something silly. Can you point me to any document that can explain how you can find the problem with just the OID and MIB that I posted? I would like to get a better grip on this.

Also, the config write came across like this:
Notification of a configuration management event as 1 2 3 / enterprises.9.9.43.1.1.6.1.3.357 ():1 enterprises.9.9.43.1.1.6.1.4.357 ():2 enterprises.9.9.43.1.1.6.1.5.357 ():3
Is there a way to make this more readable?

Finally, is there a way to list all of the traps received? NSTI was listed but when I install it, Nagios becomes un-useable. It seems like it is causing problems with the Nagios database in mysql. Once I install NSTI, the database is unable to start. I troubleshot it for hours with no progress. Really all I am looking for is the "proper" way to list the traps received.

[sreinhardt]

Well thats great!(the config write trap) As for the eigrp one, I do not see that oid listed, I see some similar oids after tracing through the mib but it doesn't specifically seem to have anything for 449.0.3. We might need, yet another mib to resolve this, but I will try and do some more digging before I officially say that.

What do you mean by the second section, is that what was displayed in XI?

NSTI is a finicky one, but should be compatible with XI. Which version were you attempting to work with?

[dflick]

How did you check the MIB for that OID? Did you have to run from the top to the bottom?

I cut and pasted the alert I got from XI. Here is the display:

"Notification of a configuration management event as 1 2 3 / enterprises.9.9.43.1.1.6.1.3.357 ():1 enterprises.9.9.43.1.1.6.1.4.357 ():2 enterprises.9.9.43.1.1.6.1.5.357 ():3"

Is there any way to clean that up a bit?

I see that NSTI 2.0 is out (beta) so I will try that one.

How would I go about switching from TRAP to INFORM for SNMP? Would that be more of an SMTPTT question?

[scottwilkerson]

can you run the following to see if this OID is in the snmptt.conf

Code: Select all

grep "1.3.6.1.4.1.9.9.43.2.0.1" /etc/snmp/snmptt.conf