<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=ISO-8859-1">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<tt>Using Xymon 4.3.7<br>
OS Linux SuSE<br>
<br>
I've been struggling to understand why certain hosts are almost
always reporting the exact same ping response time. I've
determined, that xymonping isn't working, it is reporting
incorrect data for half of the hosts tested.<br>
<br>
I start by pinging 6 hosts, one at a time, everything is correct<br>
<i>[xymon@mxbscs tmp]$ /home/xymon/server/bin/xymonping X.X.X.22<br>
X.X.X.22 is alive (0.06 ms)<br>
[xymon@mxbscs tmp]$ /home/xymon/server/bin/xymonping X.X.X.70<br>
X.X.X.70 is alive (0.56 ms)<br>
[xymon@mxbscs tmp]$ /home/xymon/server/bin/xymonping X.X.X.138<br>
X.X.X.138 is alive (826 ms)<br>
[xymon@mxbscs tmp]$ /home/xymon/server/bin/xymonping X.X.X.137<br>
X.X.X.137 is alive (980 ms)<br>
[xymon@mxbscs tmp]$ /home/xymon/server/bin/xymonping X.X.X.201<br>
X.X.X.201 is alive (0.75 ms)<br>
[xymon@mxbscs tmp]$ /home/xymon/server/bin/xymonping X.X.X.202<br>
X.X.X.202 is alive (0.66 ms)<br>
</i><br>
<br>
Then, put them in the same command, the first, second, and fifth
values are wrong<br>
<i>[xymon@mxbscs tmp]$ /home/xymon/server/bin/xymonping X.X.X.70
X.X.X.22 X.X.X.138 X.X.X.137 X.X.X.201 X.X.X.202<br>
X.X.X.70 is alive (40 ms)<br>
X.X.X.22 is alive (20 ms)<br>
X.X.X.138 is alive (1307 ms)<br>
X.X.X.137 is alive (1738 ms)<br>
X.X.X.201 is alive (20 ms)<br>
X.X.X.202 is alive (0.64 ms)</i><br>
<br>
<br>
Switch the order of the pings, the first, second, and fifth value
are exactly the same as the first time, and still wrong<br>
[xymon@mxbscs tmp]$ /home/xymon/server/bin/xymonping X.X.X.201
X.X.X.202 X.X.X.137 X.X.X.138 X.X.X.70 X.X.X.22<br>
X.X.X.201 is alive (40 ms)<br>
X.X.X.202 is alive (20 ms)<br>
X.X.X.137 is alive (1598 ms)<br>
X.X.X.138 is alive (2069 ms)<br>
X.X.X.70 is alive (20 ms)<br>
X.X.X.22 is alive (0.04 ms)<br>
[xymon@mxbscs tmp]$ <br>
<br>
Switch the order again, now the third, fourth, and fifth values
are wrong.<br>
<i>[xymon@mxbscs tmp]$ /home/xymon/server/bin/xymonping X.X.X.137
X.X.X.138 X.X.X.201 X.X.X.202 X.X.X.70 X.X.X.22<br>
X.X.X.137 is alive (1537 ms)<br>
X.X.X.138 is alive (2016 ms)<br>
X.X.X.201 is alive (40 ms)<br>
X.X.X.202 is alive (20 ms)<br>
X.X.X.70 is alive (20 ms)<br>
X.X.X.22 is alive (0.06 ms)</i><br>
<br>
<br>
Another thing I have noticed is that by altering the max-pps
value, you get completely different results.<br>
[xymon@mxbscs tmp]$ /home/xymon/server/bin/xymonping X.X.X.137
X.X.X.138 X.X.X.201 X.X.X.202 X.X.X.70 X.X.X.22 --max-pps=1<br>
X.X.X.137 is alive (2000 ms)<br>
X.X.X.138 is alive (1000 ms)<br>
X.X.X.201 is alive (2000 ms)<br>
X.X.X.202 is alive (1000 ms)<br>
X.X.X.70 is alive (1000 ms)<br>
X.X.X.22 is alive (0.06 ms)<br>
<br>
[xymon@mxbscs tmp]$ /home/xymon/server/bin/xymonping X.X.X.137
X.X.X.138 X.X.X.201 X.X.X.202 X.X.X.70 X.X.X.22 --max-pps=5<br>
X.X.X.137 is alive (1500 ms)<br>
X.X.X.138 is alive (1479 ms)<br>
X.X.X.201 is alive (400 ms)<br>
X.X.X.202 is alive (200 ms)<br>
X.X.X.70 is alive (200 ms)<br>
X.X.X.22 is alive (0.06 ms)<br>
<br>
[xymon@mxbscs tmp]$ /home/xymon/server/bin/xymonping X.X.X.137
X.X.X.138 X.X.X.201 X.X.X.202 X.X.X.70 X.X.X.22 --max-pps=25<br>
X.X.X.137 is alive (765 ms)<br>
X.X.X.138 is alive (896 ms)<br>
X.X.X.201 is alive (80 ms)<br>
X.X.X.202 is alive (40 ms)<br>
X.X.X.70 is alive (40 ms)<br>
X.X.X.22 is alive (0.04 ms)<br>
<br>
<br>
</tt><tt>It doesn't appear to be a problem with my configuration. </tt><tt>I
checked the <a class="moz-txt-link-abbreviated" href="http://www.xymon.com">www.xymon.com</a> demo site, and there seems to be the
same issue there. </tt><tt>The signature of the bad data is easy
to see in the graphs as good data has and diverse line, where as
bad data is a generally flat line. </tt><br>
<tt>These hosts look good:<br>
<a class="moz-txt-link-freetext" href="http://www.xymon.com/xymon-cgi/svcstatus.sh?HOST=pto.linuxbog.dk&SERVICE=conn">http://www.xymon.com/xymon-cgi/svcstatus.sh?HOST=pto.linuxbog.dk&SERVICE=conn</a><br>
<a class="moz-txt-link-freetext" href="http://www.xymon.com/xymon-cgi/svcstatus.sh?HOST=dali.hswn.dk&SERVICE=conn">http://www.xymon.com/xymon-cgi/svcstatus.sh?HOST=dali.hswn.dk&SERVICE=conn</a><br>
<br>
These hosts look bad:<br>
<a class="moz-txt-link-freetext" href="http://www.xymon.com/xymon-cgi/svcstatus.sh?HOST=blixen.hswn.dk&SERVICE=conn">http://www.xymon.com/xymon-cgi/svcstatus.sh?HOST=blixen.hswn.dk&SERVICE=conn</a><br>
<a class="moz-txt-link-freetext" href="http://www.xymon.com/xymon-cgi/svcstatus.sh?HOST=wifi.hswn.dk&SERVICE=conn">http://www.xymon.com/xymon-cgi/svcstatus.sh?HOST=wifi.hswn.dk&SERVICE=conn</a><br>
<br>
<br>
<br>
</tt>
<pre class="moz-signature" cols="72">--
Michael Beatty
</pre>
</body>
</html>