> -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf > Of [EMAIL PROTECTED] > Sent: Wednesday, July 05, 2006 7:49 PM > To: [email protected] > Subject: [Nagios-users] Really dumb question - how do folks > distinguishunreachable from over threshold ? > > Dear Folks, > > Is it possible to use the standard plugin distro check_ping > to distinguish a reachability failure brought about by > sluggish transport and one caused by a routing failure. > > What occurs to me at the moment is to either > > 1 don't use check_ping in cases of volatile routing (examine > routing with SNMP or CLI) > > 2 have a service event handler that reacts to 'plugin time > out' (by ultimately generating a HOST_DOWN passive service > check result if the routing has failed).
The default behavior of check_ping allows you to set separate thresholds for response time and packet loss. Try check_ping -h. Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Nagios-users mailing list [email protected] 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
