WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

Re: [Xen-users] bonding combined with network-bridge fails heartbeat clu

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-users] bonding combined with network-bridge fails heartbeat cluster on dom0
From: "Tijl Van den Broeck" <subspawn@xxxxxxxxx>
Date: Fri, 22 Dec 2006 10:36:45 +0100
Cc: ulrich.windl@xxxxxxxxxxxxxxxxxxxx
Delivery-date: Fri, 22 Dec 2006 01:36:43 -0800
Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=ZyuVnVeuilN3Df6sSEyV1DwEZtTFGZEKKI+sGwoKlCxCLFsgNrN+KfLXMrpU7e3nfptq5wG7bi5MhbrK6mCsvFAEzkYXePDjvJCqKqpqCjMnmS2Y/eV1WAcb2H37tolO9vkHYIbXYls6hFQR49Frz6MvafqOmPQW6ASTuBFZqEg=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <5a4fbd6c0612210340u58c25c62n440de1a6ac7c5ccb@xxxxxxxxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <4588F8DD.21631.5565455@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> <5a4fbd6c0612200113ga9895feqe17e411af8700bd0@xxxxxxxxxxxxxx> <45893C0A.18802.65CBCE8@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> <5a4fbd6c0612210340u58c25c62n440de1a6ac7c5ccb@xxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Issue resolved in a weird an strange manner which I'm not fond of.

Running lots of tcpdumps learned me that traffic from multicasts
reached the following interfaces (from and to):

(xendev = normal eth0 + xenbridging machine, xendev2 = bond0 +
xenbridging machine, tcpdumps taken from xendev2)

xenbr0: multicasts xendev
vif0.0: multicasts xendev
bond0: multicasts xendev, xendev2

The bridge doesn't "forward" multicasts (allthough it should, I
modified the scripts so that it should, but it doesn't).

I tried setting ha.cf to "mcast xenbr0 224.224.224.1 694 2 0" but that
didn't help either. But having resolved this all to a software bridge
multicast problem hinted me to try unicasting.
Setting the following allowed the HA cluster to come back up.
xendev:/etc/ha.d/ha.cf
"ucast eth0 xendev2"
xendev2:/etc/ha.d/ha.cf
"ucast xenbr0 xendev"

Ulrich, if you want I can mail you the entire setup so you can try to
emulate and get bonding working as well, I've read of your weird
bonding issues as well
(http://lists.xensource.com/archives/html/xen-users/2006-11/msg00504.html)
but 2 bonding interfaces could give some more problems offcourse.

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users

<Prev in Thread] Current Thread [Next in Thread>