WRONG STATUS
Rob Blake
rob.blake at gmail.com
Mon Mar 26 16:56:31 CEST 2007
I' m using nagiosVersion 2.0 , on FreeBSD 6.0 , plugin version 1.4
>
>
>
> I HAVE CHANGED THE CONFIG AS REQUESTED BUT I'M STILL GETTING THE DOWN
> STATUS ON THE DEVICE.
>
> CAN I HAVE MORE DETAILS ON THE: check_command: check_ping!30.0,1%!60.0,10%
>
>
> For what I know 30 stands for the response time in milliseconds for nagios
> to deliver a warning status and 1 is the packet loss.
>
> 60ms is the critical status.
>
>
>
> define service{
>
> use generic-service ; Name of
> service template to use
>
> host_name cisco_xxxx
>
> service_description PING
>
> is_volatile 0
>
> check_period 24x7
>
> max_check_attempts 6
>
> normal_check_interval 2
>
> retry_check_interval 1
>
> contact_groups cpl
>
> notification_options w,u,c,r
>
> notification_interval 120
>
> notification_period 24x7
>
> check_command check_ping!30.0,1%!60.0,10%
>
>
>
> Thanks.
>
>
>
> Regards,
>
>
>
> Grace
>
Your command definition as it stands will return a warning status if your
host responds outside of 30ms or there is => 1% packet loss. It will return
a critical status if the host takes longer than 60ms to respond or there is
=>10% packet loss.
Rob
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.monitoring-lists.org/archive/users/attachments/20070326/0b64c824/attachment.html>
-------------- next part --------------
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
-------------- 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
More information about the Users
mailing list