Hi, I found the cause of that error:
> [...] > Now heartbeat says that only BRIDGE2 is up - whereas before > eth0, eth1 and eth5 were up. The xen 3.2.0 used in conjunction with SLES 10 SP2 now issues "ifup BRIDGE" after moving the physical network device to the bridge. Thus I supplied the scripts /etc/sysconfig/network/ifcfg-BRIDGE with "STARTMODE=manual". Fatal: I copied those scripts with the local IPADDR-field from node1 to node2. The result was a bridge-device on node2 that looked like it were right, but answered both IPs - that of node1 and that of node2. That additional ip was not visiblue when using "ifconfig" on the bridge-device... So - no heartbeat bug here. I was just confused by xen's new way of setting up network-bridges. Greetings, Nils _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
