Nagios & SNMP traps

[Marc Powell]

> -----Original Message-----
> From: nagios-users-bounces at lists.sourceforge.net [mailto:nagios-users-
> bounces at lists.sourceforge.net] On Behalf Of
> Aritz.Lazkano at DaimlerChrysler.com
> Sent: Friday, April 27, 2007 6:15 AM
> To: nagios-users at lists.sourceforge.net
> Subject: [Nagios-users] Nagios & SNMP traps
> 
> 
> Hi friends of Nagios!
> 
> I´m trying to monitor a service that works with snmp traps. The problem is
> that i recive the trap in my server, but nagios doesn´t do anything.
> The service  status is "pending", also when the trap arrives into our
> server  the status of the service that works with traps continues
> "pending".
> For making this work we follow a manual, we configured snmptrapd , we
> installed snmptrap translator and the simple event correlator (sec).
> Then we defined a service on Nagios to handle the traps on it. After that
> we introduced mib definition. The manual that we followed is this:
> 
> http://www.samag.com/documents/s=9559/sam0503g/
> 
> 
> Which migth be the problem?

Nagios is likely to be complaining in nagios.log. What do you see there? Possible problems --
	Nagios isn't checking external commands.
	Nagios isn't accepting passive checks.
	Your script isn't writing to the correct nagios.cmd.
	Your script doesn't have permission to write to nagios.cmd.
	The service definition isn't configured for passive checks.
	The host name/service description being submitted don't match a known host/service combination.

--
Marc

-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. 
::: Messages without supporting info will risk being sent to /dev/null