Yes, this possible since everything running on vmware. Another point that might mtu problem involved, because vm located in two different geo locations. We tried many think so far, include lower netmtu to 1000, but it is not really helped. Corosync still unstable and right now it is only vmware left on the way.
Slava.
From: "Vladislav Bogdanov" <bubble@xxxxxxxxxxxxx>
To: discuss@xxxxxxxxxxxx
Sent: Friday, November 29, 2013 12:22:14 AM
Subject: Re: information request
26.11.2013 23:22, Slava Bendersky wrote:
> Hello Honza,
> Thank you for exact instruction how to find the trouble.
> I followed step by step. Corosync-objectctl is not reporting errors I
> was be able see data which you described earlier.
> And I see interfaces both ends are bounded to proper ip address. Also I
> see on tcpdump valid traffic which quite chatty.
>
> 10.10.10.1.5405 > 10.10.10.2.5405: [bad udp cksum 6a0!] UDP, length 107
> 14:52:09.333729 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto
> UDP (17), length 135)
This ^^^ could be a source of the issue.
Bad UDP checksumm usually means you have broken ethernet hardware or IP
stack (and main reason for this could be a broken DIMM) somewhere on the
path.
Such packets are dropped by a kernel, so corosync wont see them.
_______________________________________________
discuss mailing list
discuss@xxxxxxxxxxxx
http://lists.corosync.org/mailman/listinfo/discuss
To: discuss@xxxxxxxxxxxx
Sent: Friday, November 29, 2013 12:22:14 AM
Subject: Re: information request
> Hello Honza,
> Thank you for exact instruction how to find the trouble.
> I followed step by step. Corosync-objectctl is not reporting errors I
> was be able see data which you described earlier.
> And I see interfaces both ends are bounded to proper ip address. Also I
> see on tcpdump valid traffic which quite chatty.
>
> 10.10.10.1.5405 > 10.10.10.2.5405: [bad udp cksum 6a0!] UDP, length 107
> 14:52:09.333729 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto
> UDP (17), length 135)
Bad UDP checksumm usually means you have broken ethernet hardware or IP
stack (and main reason for this could be a broken DIMM) somewhere on the
path.
_______________________________________________
discuss mailing list
discuss@xxxxxxxxxxxx
http://lists.corosync.org/mailman/listinfo/discuss
_______________________________________________ discuss mailing list discuss@xxxxxxxxxxxx http://lists.corosync.org/mailman/listinfo/discuss
