WRONG STATUS
Rob Blake
rob.blake at gmail.com
Mon Mar 26 17:30:08 CEST 2007
On 3/26/07, grace ingabire <ingabireg at terracom.rw> wrote:
>
> Thanks Bob.
>
>
>
> What about the DOWN STATUS that I'm receiving although the device is up.
>
>
>
>
>
> 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%
>
>
>
> nagiosVersion 2.0
>
> on FreeBSD 6.0
>
> plugin version 1.4
>
> Thanks
>
>
>
>
>
>
>
>
> ------------------------------
>
> *From:* Rob Blake [mailto:rob.blake at gmail.com]
> *Sent:* Monday, March 26, 2007 4:57 PM
> *To:* grace ingabire
> *Cc:* andy.shellam-lists at mailnetwork.co.uk;
> nagios-users at lists.sourceforge.net; cpl at terracom.rw
> *Subject:* Re: [Nagios-users] WRONG STATUS
>
>
>
> 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
>
Well from your service definition, I am assuming that the device is taking
longer than 60ms to respond or there is greater than 10% packet loss between
your Nagios Host and the router. What does running
ping <ip_address_of_router>
show you from the command line of your Nagios Host?
Rob
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.monitoring-lists.org/archive/users/attachments/20070326/009aae75/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