Receiving traps from an APC ups..

Jaime Ventura jaimeventura at ipp.pt
Tue Feb 3 12:38:26 CET 2009


hello, I have the following problem.

I've configured a nagios service to monitor actively(to get state and
perfdata) and passively (so it can receive snmptraps via nsca-client) an
APC ups..

At the moment, the ups has one intermittent problem and one permanent
problem, which result the on sending traps, the following way:

    receive 'Problem 1' trap: critical  -> nagios notification CRITICAL
    receive 'Problem 2' trap : critical -> nagios does not send
notification, because status is the same(CRITICAL)
    receive 'Problem 1' trap : ok      -> nagios notification OK (status
changed)
    receive 'Problem 2' trap : critical -> nagios notification
CRITICAL(status changed)

So, heres's the problem, When problem 1 is solved, the UPS still has
problem 2 (and it keeps sending traps of the same problem). Receiving an
OK trap, nagios will change the service status to OK while having
another problem.
Because of that, nagios keeps sending ok notification, even thought ups
is not ok, and service is kept flapping.

Is there any way to solve this?
Can I force nagios to use the active_check command every time it
receives a trap(even if it is a ok trap).

Thanks,
    Jaime



------------------------------------------------------------------------------
Create and Deploy Rich Internet Apps outside the browser with Adobe(R)AIR(TM)
software. With Adobe AIR, Ajax developers can use existing skills and code to
build responsive, highly engaging applications that combine the power of local
resources and data with the reach of the web. Download the Adobe AIR SDK and
Ajax docs to start building applications today-http://p.sf.net/sfu/adobe-com
_______________________________________________
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





More information about the Users mailing list