The network-bridge script does some pretty horrific things to networking while it starts. I’m not surprised if the interruption is enough to cause CMAN to fail. We avoided this by not using Xen’s network-bridge utility. Just configure your physical interfaces and bridge devices in /etc/sysconfig/network-scripts, and specify a bridge name in each /etc/xen/<domU> script. (In xend-config.sxp you can set network-script to “/bin/true”. Just remember to also turn on IP forwarding.) The advantages of doing it this way are that you get tighter control over your host networking, and starting/stopping xend won’t interrupt networking. (The main disadvantage is that the networking configuration is harder to port to a non-Red Hat OS, but if you already need clustering that probably doesn’t matter.) From: linux-cluster-bounces@xxxxxxxxxx [mailto:linux-cluster-bounces@xxxxxxxxxx] On Behalf Of Paras pradhan Hi, I have a three node red hat cluster (for xen virualization) and everything is running great until I add a 2nd interface and 2nd bridge. This is how I added the 2nd bridge http://toic.org/2008/10/06/multiple-network-interfaces-in-xen/ After reboot, cluster comes up fine and when xend comes up, cman dies. Log (from other node): -- Aug 27 15:13:23 cvtst2 openais[6343]: [TOTEM] Retransmit List: 52 53 Aug 27 15:13:23 cvtst2 last message repeated 3 times Aug 27 15:13:23 cvtst2 openais[6343]: [TOTEM] Retransmit List: 53 Aug 27 15:13:23 cvtst2 openais[6343]: [TOTEM] Retransmit List: 53 Aug 27 15:13:59 cvtst2 openais[6343]: [TOTEM] FAILED TO RECEIVE Aug 27 15:13:59 cvtst2 openais[6343]: [TOTEM] entering GATHER state from 6. Aug 27 15:13:59 cvtst2 openais[6343]: [TOTEM] FAILED TO RECEIVE Aug 27 15:13:59 cvtst2 openais[6343]: [TOTEM] entering GATHER state from 6. Aug 27 15:14:00 cvtst2 openais[6343]: [TOTEM] FAILED TO RECEIVE --- But if I execute as root (for 2nd bridge) : /etc/xen/scripts/network-bridge start vifnum=1 netdev=eth1 bridge=xenbr1, It looks like after the cman started , xend is trying to reconfigure the both bridges and cluster dies. |
-- Linux-cluster mailing list Linux-cluster@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/linux-cluster
