SNMP Trap reset by Nagio - OK: TRAP RESET

[MrSteve]

SNMP traps are reset by Nagios so when we have an ALARM_RAISED, we do not see the ALARM_CLEARED because Nagios resets the ALARM.

Met with Spencer at Nagios Conference and he helped isolate the issue to a particular template.

Below is a sample log of default behavior for future folks who may run into this issue. The key thing to look for is: OK: TRAP RESET

Code: Select all

2014-10-02 11:38:56	njprdhub1	SNMP Traps	Service Recovery	No	OK	diane	Nagios XI	OK: TRAP RESET	NID: 20271, COID: 283, CNID: 353, CNMID: 353
2014-10-02 11:38:56	njprdhub1	SNMP Traps	Service Recovery	No	OK	kranthi	Nagios XI	OK: TRAP RESET	NID: 20271, COID: 214, CNID: 354, CNMID: 354
2014-10-02 11:38:56	njprdhub1	SNMP Traps	Service Recovery	No	OK	yoga	Nagios XI	OK: TRAP RESET	NID: 20271, COID: 210, CNID: 355, CNMID: 355
2014-10-02 11:38:38	njprdhub1	SNMP Traps	Service Problem	No	CRITICAL	diane	Nagios XI	Min inbound sessions not reached: RAISED ALARM - Burnside Digital IN US SCB number of inbound Transceiver sessions is below minimum of 2 / enterprises.18328.1.6.18601.1 ():Burnside Digital IN US SCB enterprises.18328.1.6.18601.2 ():Transceiver enterprises	NID: 20270, COID: 283, CNID: 350, CNMID: 350
2014-10-02 11:38:38	njprdhub1	SNMP Traps	Service Problem	No	CRITICAL	kranthi	Nagios XI	Min inbound sessions not reached: RAISED ALARM - Burnside Digital IN US SCB number of inbound Transceiver sessions is below minimum of 2 / enterprises.18328.1.6.18601.1 ():Burnside Digital IN US SCB enterprises.18328.1.6.18601.2 ():Transceiver enterprises	NID: 20270, COID: 214, CNID: 351, CNMID: 351
2014-10-02 11:38:38	njprdhub1	SNMP Traps	Service Problem	No	CRITICAL	yoga	Nagios XI	Min inbound sessions not reached: RAISED ALARM - Burnside Digital IN US SCB number of inbound Transceiver sessions is below minimum of 2 / enterprises.18328.1.6.18601.1 ():Burnside Digital IN US SCB enterprises.18328.1.6.18601.2 ():Transceiver enterprises	NID: 20270, COID: 210, CNID: 352, CNMID: 352

[slansing]

Thanks for the post Steve! Yeah it's typically one of the trap/passive templates that has check_dummy set on it which gets triggered and sends a (0) "OK: Trap Reset" through to the top level service, pretty simple to change, but can cause some confusion.

[MrSteve]

I know which template is causing the problem and using check_dummy it is xiwizard_generic_service_snmptrap.

But how do I turn it off and is it safe to turn this off? Below are images of the settings:

Nagios p1.png

Nagios p2.png

Nagios p3.png

Thanks,
Steve

[sreinhardt]

I believe we went ahead and disabled it only to have nagios complain that no checks were configured for that service. Then found that enabling it in any fashion caused it to always trigger post a trap comming in. If you could, please pm me a copy of your current profile from Admin->System Profile->Download Profile. Unless of course I missed it in your first PM, which is entirely possible.

[MrSteve]

Spencer,

Through I sent a PM. Can you send me a PM and I can respond. Or send me your contact info and I can send you an email with mine.

THanks,
Steve

[abrist]

Could you resend your PM to sreinhardt with the attachment? (It was missing from your last PM)

[MrSteve]

My bad, resent with attachment.

Also see image below of "Unconfigured Objects"

Unconfig.ong.png

[sreinhardt]

Unconfigured objects are to be expected, if you have not already setup a snmp trap service, or alter the service name in snmptrapsender.py or snmptt.conf. I am taking a look at your configs now, and should have something shortly, with any luck!

[MrSteve]

Any updates?

[sreinhardt]

This post should actually be locked since you have a ticket in, I will go ahead and do that now. I responded yesterday about mid day to your ticket in with [email protected]. Briefly, I was unable to reproduce the issue in-house despite trying to replicate it several different ways. At this point I would like to do a remote and requested a time that would work for you this week. I have a couple ideas we can try during the session.