Nagiosxi trap processing

This support forum board is for support questions relating to Nagios XI, our flagship commercial network monitoring solution.
kg2857
Posts: 490
Joined: Wed Apr 12, 2023 5:48 pm

Re: Nagiosxi trap processing

Post by kg2857 »

Name resolution is up to your DNS settings.
What does nslookup x.x.x.44 return?
BTW, making a new service for traps (or anything else) via a wizard, that's the same as other services is a bad thing. You should make services generic and attach multiple hosts to them. Some may disagree.
I'd suggest looking into templates, hostgroups, etc. to standardize things. For example, my hosts contain the hostname, address, and a template. I can redefine how a host is checked by changine a single template.
vretic
Posts: 9
Joined: Wed Jul 01, 2020 8:12 am

Re: Nagiosxi trap processing

Post by vretic »

kg2857 wrote: Thu Aug 01, 2024 4:21 am Name resolution is up to your DNS settings.
What does nslookup x.x.x.44 return?
BTW, making a new service for traps (or anything else) via a wizard, that's the same as other services is a bad thing. You should make services generic and attach multiple hosts to them. Some may disagree.
I'd suggest looking into templates, hostgroups, etc. to standardize things. For example, my hosts contain the hostname, address, and a template. I can redefine how a host is checked by changine a single template.
Hi,
thnx for the heads up, solved it by adding a reverse dns line to /etc/hosts....
Solved the traps, but now I have a new problem.
For each trap I can see 2 events in snmptt.log
Ups reports 3 traps when testing and they come in this sequence.
1. Ups on battery which has severity majaor and is shown in nagvis as red (all good)
2. Ups bypass frequency fail which has severity normal (this causes a trap reset and ups is shown as green)
3. Bypass AC Abnormal whit severity normal (this causes a trap reset and ups is shown as green)


I edited the processed mib file and changed severity to CRITICAL but I still read 2 lines in snmptt log first one with severity CRITICAL and second with severity NORMAL (see screenshot). Where does Nagios get the second line with severity normal. There shouldn't be any traps in english language as we translated the mib to Slovenian language?
snmptt_log_SE400.PNG
You do not have the required permissions to view the files attached to this post.
cnorell
Developer
Posts: 141
Joined: Mon Nov 27, 2017 3:08 pm

Re: Nagiosxi trap processing

Post by cnorell »

vretic,

I'm assuming you don't have access to the SNMP trap interface? This is an Enterprise level feature. If you do, this would be a good place to check to see if there are duplicitous definitions.

XI seems to pull traps from the database table xi_cmp_trapdata. Do you know how to access the database? If you do, I would check that table for duplicate definitions. If you manually edited the snmptt configuration file, the changes may not have made it into the database properly.

If you aren't comfortable poking around the database, I would recommend opening a ticket with support.

Best Regards,

Cory Norell
As of May 25th, 2018, all communications with Nagios Enterprises and its employees are covered under our new Privacy Policy.
kg2857
Posts: 490
Joined: Wed Apr 12, 2023 5:48 pm

Re: Nagiosxi trap processing

Post by kg2857 »

snmptt reads snmptt.conf and snmptt.conf.xi (I think) so look there.
cnorell
Developer
Posts: 141
Joined: Mon Nov 27, 2017 3:08 pm

Re: Nagiosxi trap processing

Post by cnorell »

I haven't touched the SNMP code in a while, but from my recollection: XI will take user input from the interface, put it in the database, then write to either snmptt.conf or snmptt.conf.nxti, depending on the method used to define the traps in the interface.
As of May 25th, 2018, all communications with Nagios Enterprises and its employees are covered under our new Privacy Policy.
Post Reply