AnsweredAssumed Answered

How to identify (possible) network issues?

Question asked by oztoz01 Employee on Mar 16, 2017
Latest reply on Mar 18, 2017 by oztoz01

2017-03-16 12:51:46 WARNING 10.2.161.162 ServerReachabilityMonitor.run Server '10.2.161.161' reachability changed: 7901=open (filtered)
2017-03-16 12:51:30 WARNING 10.2.161.162 ServerReachabilityMonitor.run Server '10.2.161.161' reachability changed: 7901=filtered (open)
2017-03-16 12:24:06 WARNING 10.2.161.161 ServerReachabilityMonitor.run Server '10.2.161.162' reachability changed: 5900=open (filtered)
2017-03-16 12:23:51 WARNING 10.2.161.161 ServerReachabilityMonitor.run Server '10.2.161.162' reachability changed: 5900=filtered (open)
2017-03-16 02:56:57 WARNING 10.2.161.162 ServerReachabilityMonitor.run Server '10.2.161.161' reachability changed: 3306=open (filtered)
2017-03-16 02:56:42 WARNING 10.2.161.162 ServerReachabilityMonitor.run Server '10.2.161.161' reachability changed: 3306=filtered (open)

2 virtual appliances, on the same VLAN, no firewall policies in between. We are observing these warnings a couple of times daily. CPU, memory and disk usage is minimal on both members.

 

During previous weeks, there had been some occasions where one of the members got out of sync. Stopping and starting the cluster is needed if the member does not successfully re-sync's by itself. This problems always occurs after the warnings get more frequent.

 

For 2 days now, cluster is running OK, but occasionally we're still observing these lines.  Is this information sufficient for justifying a network quality issue, or what would be the usual suspects if there's any?

 

Thanks...

Outcomes