Warning alert isn't working

[Leonardo Bacha Abrantes]

Hi Trond,

Thank you so much! it worked very well.


On Fri, Apr 13, 2012 at 20:37, Trond Hasle Amundsen <
t.h.amundsen at usit.uio.no> wrote:

> Leonardo Bacha Abrantes <leonardo at lbasolutions.com> writes:
>
> > Hi everybody!
> >
> > I'm using check_openmanage plugin in nagios to monitoring the
> temperature of my
> > dell servers.
> > It's working, however, the warning and critical alerts that I configure
> are not
> > working.
> >
> > [root at monitor:/etc/openmanage]#
> /usr/lib/nagios/plugins/check_openmanage -w 25
> > -c 30 -H 10.11.12.1 -C Test--only temp
> > TEMPERATURES OK - 1 temperature probes checked:<BR>Temperature Probe 0
> [System
> > Board Ambient Temp] reads 30 C (min=8/3, max=42/47)
> >
> > The temperature is 30 and the check should appear WARNING because I used
> -w 25.
>
> Hello Leonardo,
>
> The syntax you're using with the '-w' and '-c' options is wrong. From
> the manual page:
>
>       -w, --warning STRING or FILE
>           Override the machine-default temperature warning
>           thresholds. Syntax is "id1=max[/min],id2=max[/min],...". The
>           following example sets warning limits to max 50C for probe 0,
>           and max 45C and min 10C for probe 1:
>
>           check_openmanage -w 0=50,1=45/10
>
>           The minimum limit can be omitted, if desired. Most often, you
>           are only interested in setting the maximum thresholds.
>
>           This parameter can be either a string with the limits, or a
>           file containing the limits string. The option can be
>           specified multiple times.
>
>           NOTE: This option should only be used to narrow the field of
>           OK temperatures wrt. the OMSA defaults. To expand the field
>           of OK temperatures, increase the OMSA thresholds. See the
>           plugin web page for more information.
>
>       -c, --critical STRING or FILE
>           Override the machine-default temperature critical
>           thresholds. Syntax and behaviour is the same as for warning
>           thresholds described above.
>
> The reason that you need to specify the ID of the temperature probes is
> that there may be more than one, each with its own thresholds. In your
> case there is only one probe and its ID is 0, so replace your command
> above with:
>
>  check_openmanage -w 0=25 -c 0=30 -H 10.11.12.1 -C Test --only temp
>
> That should do the trick.
>
> Regards,
> --
> Trond H. Amundsen <t.h.amundsen at usit.uio.no>
> Center for Information Technology Services, University of Oslo
>
>
> ------------------------------------------------------------------------------
> For Developers, A Lot Can Happen In A Second.
> Boundary is the first to Know...and Tell You.
> Monitor Your Applications in Ultra-Fine Resolution. Try it FREE!
> http://p.sf.net/sfu/Boundary-d2dvs2
> _______________________________________________
> 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
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.monitoring-lists.org/archive/users/attachments/20120416/6e63430d/attachment.html>
-------------- next part --------------
------------------------------------------------------------------------------
For Developers, A Lot Can Happen In A Second.
Boundary is the first to Know...and Tell You.
Monitor Your Applications in Ultra-Fine Resolution. Try it FREE!
http://p.sf.net/sfu/Boundary-d2dvs2
-------------- next part --------------
_______________________________________________
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