Too many warnings and critical in Connectivity service(check_ping)

[angel cuevas rumin]

Hi everybody,

I installed nagios on a Linux Mandriva 2006 monitroting a LAN.

I have many warnings and critical alerts in the connectivity service which
is a command based on check_ping sending 5 packets. The parameters
configured for these alerts are:

        ------ Warning: rtt>300ms, loss>25%(our intention is to receive a
warning with more than 1 packet lost)
        ------ Crticial: time>500 ms, loss=100%

Everytime we receive an alert, within the following minute the system is
recovered from this alert. And those elements which are showing these alerts
are working perfectly. Therefore we don't understand why Nagios is showing
these alerts.
Also we cheked with ethereal these alert events and the information given by
ethereal doesn't match  with the information given by Nagios.

We would appreciate if someone who has had the same problem or if someone
who knows sometihng about this problem could help us.

P.D: Another problem we found using check_fping (instead check_ping) is that
this command doesn't add the sequence number onto the icmp packet which are
sent.


Thank you very much in advance.

Kind Regards
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.monitoring-lists.org/archive/users/attachments/20060830/a0a5e6ec/attachment.html>
-------------- next part --------------
-------------------------------------------------------------------------
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
-------------- 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