check_ping

[Matt Pounsett]

On Tue, 13 Jan 2004, Neil wrote:

> Hey guys, 
> 
> Me again. Question about check_ping!100.0,20%!500.0,60% 
> 
> 1. What would be the ideal or best practice way of finding the parameters 
> for the warning and critical values for check_ping? Btw, just got those 
> parameters from the sample files. 

That's really up to you, and what performance (or lack of performance) you
will tolerate from your network.  I have three different defaults I use for
host checks -- one for hosts on the same LAN as the Nagios box, which permits
only a small amount of latency and very little packet loss; and one for each
of our two remote networks, which have slightly different average RTTs.

> 2. I also would like to know how we were able to come up with 20% and 60% on 
> the command above. From the help of check_ping, it tells us that RTA and PL 
> are 2 separate values. So, I can say here that 100.0 is not dependent on the 
> 20%. Am I correct? 

Yes, you're correct.  You'd get a warning if latency is above 100ms, OR if
packet loss is above 20%..  same rules for critical, using the 500ms and 60%
loss.


-- 
Matt Pounsett                 CIRA - Canadian Internet Registration Authority
Technical Support Programmer                    350 Sparks Street, Suite 1110
matt.pounsett at cira.ca                                 Ottawa, Ontario, Canada
613.237.5335 ext. 231                                      http://www.cira.ca



-------------------------------------------------------
This SF.net email is sponsored by: Perforce Software.
Perforce is the Fast Software Configuration Management System offering
advanced branching capabilities and atomic changes on 50+ platforms.
Free Eval! http://www.perforce.com/perforce/loadprog.html
_______________________________________________
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