[Xen-users] bonding combined with network-bridge fails heartbeat cluster on dom0

["Tijl Van den Broeck" <subspawn@xxxxxxxxx>]

When setting up heartbeat for several dom0's for usage of EVMS on
SLES10 I've hit a problem. Bonding with network-bridge was solved with
a custom network script from someone of the list:

bond-network-script:
#!/bin/sh
dir=$(dirname "$0")
"$dir/network-bridge" "$@" vifnum=0 netdev=bond0

As such, domU's networking and bond0 were operational.
Whenever the networking for Xen is launched, the EVMS-HA cluster dies.
It looses connectivity over multicast. tcpdump sees the packages
coming and going. On the "bad"-side  it sees the other node going
away. On the "healthy"-side (not yet started networking for Xen)
heartbeat logs the following:

Dec 19 15:50:06 xendev heartbeat: [6676]: ERROR: Message hist queue is
filling up (200 messages in queue)
Dec 19 15:50:06 xendev heartbeat: [6676]: debug: hist->ackseq =2459
Dec 19 15:50:06 xendev heartbeat: [6676]: debug: hist->lowseq =2633,
hist->hiseq=2833
Dec 19 15:50:06 xendev heartbeat: [6676]: debug: expecting from xendev2
Dec 19 15:50:06 xendev heartbeat: [6676]: debug: it's ackseq=2459

As soon as I go /etc/xen/scripts/bond-networking-script stop all
trouble is over.

Is this a specific multicast issue with the combination
bonding+heartbeat+network-bridge? Has anyone got a config like this
tested or running?

greetings

Tijl Van den Broeck

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