I would start from the hardware level.

You say you are on the same network, but are you on the same network switch or segment? Is there a router in the way that is causing issues for one host and not another? Are the xymon hosts physical or virtual? If virtual, are they on the same (assuming vmware) virtual host or different? It sounds like you have an inconsistency in your network somewhere that your xymon instance is bringing to light.

-Tim James

From: Xymon <xymon-bounces at xymon.com> On Behalf Of System-Admiminstratoren Sent: Thursday, October 15, 2020 1:47 AM To: xymon at xymon.com Subject: [Xymon] Different conn Testresults after Migration to a new xymon server

--- External Email ---

Hello,

I?ve migrated my xymon Monitor to another host in the same network due to an old linux version on the old one.

The old server was Ubuntu Server 14.04 and the new one is version 20.04 LTS.

I have copied all the configuration files from the old to the new one.

Now I am really surprised, that I get different conn-test results on the two xymon server running parallel at the moment for some hosts.

On the old server the host is green (alive) on the new one the host is red (not ok), but if I run a fping or ping on both servers the tested hosts are ok and alive.

Therefore I added the trace option on the new xymon to the conn test.

Thu Oct 15 07:34:39 2020 conn NOT ok

Service conn on XXXX is not OK : Host does not respond to ping

System unreachable for 229 poll periods (67968 seconds)

[red]XXXXXX is unreachable Traceroute results: traceroute to XXXXXX , 30 hops max, 60 byte packets 1 router one 0.134 ms 0.093 ms 0.118 ms 2 XXXX.dip0.t-ipconnect.de (XXX.XXX.XXX.XXX) 1.593 ms 1.806 ms * 3 * * * 4 * * * 5 * * * 6 * * * 7 * * * 8 * XXXX.dip0.t-ipconnect.de (XXX) 64.015 ms *

I run the traceroute command on ssh-console on the new xymon for the same host at the same time

traceroute XXX traceroute to XXX (XXX), 30 hops max, 60 byte packets 1 XXX (XXX) 0.186 ms 0.126 ms 0.122 ms 2 XXX.dip0.t-ipconnect.de (80.153.230.205) 1.154 ms 1.331 ms * 3 * * * 4 * * * 5 * * * 6 * * * 7 * * * 8 * XXX.dip0.t-ipconnect.de (80.153.230.205) 59.814 ms 64.467 ms

And a ping

ping XXX PING XXX (XXXX) 56(84) bytes of data. 64 bytes from XXX: icmp_seq=1 ttl=56 time=55.7 ms 64 bytes from XXX: icmp_seq=2 ttl=56 time=55.3 ms 64 bytes from XXX: icmp_seq=3 ttl=56 time=55.0 ms 64 bytes from XXX: icmp_seq=4 ttl=56 time=55.2 ms

Even fping ?Ae on console reports the host to be alive. Why are the results so different?

What is the problem and how to fix it?

Sincerley

Steffen

This E-Mail has been scanned for viruses.

--

Diese E-Mail wurde vom Sophos Security Gateway auf gef?hrliche Inhalte gepr?ft! http://www.sophos.com