Router warning traps seen on NSTI but not in Nagios

[tgriep]

Take a look at this guide on installing SNMP Traps to be received by Nagios XI.
https://assets.nagios.com/downloads/nag ... ios_XI.pdf
Make sure you back up the configuration files in /etc/snmp before following this because it probably break NSTI.

[vijilants]

Take a look at this guide on installing SNMP Traps to be received by Nagios XI.
https://assets.nagios.com/downloads/nag ... ios_XI.pdf
Make sure you back up the configuration files in /etc/snmp before following this because it probably break NSTI.

Thank you but this is the guide that I used in the first place to set this whole thing up and this file states that you have to edit the trap severity which I did but a previous support post on page 1 of this case said that I shouldn't have to do that.

I don't think I'm getting very far with this and I will use the official support route to get this sorted out.

[tgriep]

The reason I suggested to go through the procedure again is in the config file you posted doesn't look like it is setup to have Nagios to receive traps. Below is an example of a working demo configuration.

Code: Select all

EVENT demo-trap .1.3.6.1.4.1.2021.13.990.0.17 "Status Events" Normal
FORMAT This is just a demo $*
EXEC /usr/local/bin/snmptraphandling.py "$r" "SNMP Traps" "$s" "$@" "$-*" "This is just a demo $*"
SDESC
This is just a demo
Variables:
  1: sysLocation
EDESC

The EXEC line is used to process a trap for Nagios XI.
That line is created when the MIB file is uploaded to the XI system and the Process Trap box is checked.

[vijilants]

The EXEC line is used to process a trap for Nagios XI.
That line is created when the MIB file is uploaded to the XI system and the Process Trap box is checked.

Hi,

Are you talking about the snmptt.conf file ?

Thanks

[ssax]

Yes, /etc/snmp/snmptt.conf.

[vijilants]

OK.....I have tried the process of uploading mibs via Admin, with the process trap clicked, but I get the following messages:

On one particular mib which has been provided by the manufacturer:

Total translations: 0
Successful translations: 0
MIB is added, but is does not contain any TRAP-TYPE definitions, so no traps were added, even though user input said there should be traps specified.

And on the other mib:

Failed to converted mib path to snmptt.ini. (rc: 4)

Really not sure as to what is going on here and why the mibs are nor being accepted or where to look to fix the issue

Can you please advise ?

Attached are the mibs in question....not I've renamed the mibs as .txt or else I cannot upload them

[tgriep]

Could you run the following and post the output here?

Code: Select all

 addmib /usr/share/snmp/mibs/timeprov.mib.txt

The symm-smi.mib file looks like it doesn't have any traps OID's so could you contact the vendor and see if they can provide one?

[ssax]

My recommendation is to use the command line when adding MIBs.

SSH into your Nagbios XI server.

Copy all your MIBs to /usr/share/snmp/mibs/

Code: Select all

addmib /usr/share/snmp/mibs/timeprov.mib.txt

There are no traps in the SYMM-SMI one so no need to addmib it.

[vijilants]

Thank you ....using the command line allowed the mibs to be installed......so is this a bug in the gui application ?

Coming back to the remainder of the mibs and fixing the issues of non reporting into XI, but can be seen in NSTI, here is how my setup runs:

Because I have many Cisco and other manufacturer mibs installed, in my snmptt.ini file I referenced several snmptt.conf files as per below:

Code: Select all

[TrapFiles]
# A list of snmptt.conf files (this is NOT the snmptrapd.conf file).  The COMPLETE path 
# and filename.  Ex: '/etc/snmp/snmptt.conf'
snmptt_conf_files = <<END
/etc/snmp/snmptt.conf
/etc/snmp/snmptt.conf.cisco_3
/etc/snmp/snmptt.conf.adtran
/etc/snmp/snmptt.conf.loop

I did this so that I could easily go through each individual file and edit the severity levels, or else if I used one snmptt.conf file, the file would have been huge and unmanageable.

So, according to tgriep's post on Wed 24th of June, he said....

The EXEC line is used to process a trap for Nagios XI.
That line is created when the MIB file is uploaded to the XI system and the Process Trap box is checked.

So here are the problems I am faced with and some options to make life easier would be greatly appreciated.....

1) If I delete the mibs and start over it will put everything in to one single snmptt.conf file....again a huge file.

2) It will take forever to go back and edit all the severity levels

3) I'm not sure any mores as to what were the original mibs supplied by Nagios so I may delete the wrong mibs

4) When i load mibs via the UGU, the user and group of the file is "apache" ....does that need to be changed or is that ok to lease as is ?


Your Thoughts ?

[tgriep]

How many traps are you currently monitoring now?
Do you want all of those traps to be monitored by Nagios XI?

Lets try and see if you can get Nagios XI to receive a trap.

Edit one of your snmptt.conf files and find a trap you want XI to monitor. Change the EXEC line for it to look like the example below.

Code: Select all

EXEC /usr/local/bin/snmptraphandling.py "$r" "SNMP Traps" "$s" "$@" "$-*" "The SNMP trap that is generated as a result of an event with the host $*"

Either force a trap from that device or wait for one to come in and then check the service status to see if XI received it.