check_ping question

[Curt Shaffer]

I am having some weird issues with the check_ping command. We have 86
hosts at the present time on our wireless network. We are executing the
check_ping command to see if the AUs and SUs are alive. This seems to
work well except with one of our access units. This particular AU comes
up as critical a lot, especially during the evening hours. We have run
just a ping command from the command line at the same time and it did
not loose any packets as nagios reported that it did. When I executed
the check_ping command constantly from the command line it did loose
some. I know the problem has to be with the was the check is being run,
but it confuses me that this is the only host with the problem. Ive read
the command and I can understand what it is doing but I still don't see
why this packet loss is occurring. Regular ping times to this host and
times with the check_ping command are almost always under 12ms with the
tty of 64. It sometimes gets a little higher but only for 1 or maybe 2
pings at most then back down but nowhere near 6 times, which is what we
set the max attempts to. Can anyone shed some light on this for
me...maybe I am misunderstanding how the check_ping command works? I
realize one option is to change the check to something else for that
host but Id rather not. I would also like to know if this is just
telling me something is wrong from our POP to that host or back?? Any
help would be appreciated. Thanks!

Curt 
Wireless/Network Specialist
Chilitech Internet Solutions




-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive?  Does it
help you create better code?  SHARE THE LOVE, and help us help
YOU!  Click Here: http://sourceforge.net/donate/
_______________________________________________
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