Hi, On Mon, Mar 10, 2008 at 09:34:49PM +0100, Johan Hoeke wrote: > Hi all, > > Am testing a 2-node 2.1.3 crm enabled cluster. > > Pulled the heartbeat crosslink cable on eth1, to test that the heartbeat > would continue to be received on eth0 as configured. > > from ha.cf: > bcast eth0 eth1 # Linux > > on both nodes: > [EMAIL PROTECTED] ~]# ps -ef | grep bcast > root 9377 9374 0 16:44 ? 00:00:00 heartbeat: write: bcast eth0 > root 9378 9374 0 16:44 ? 00:00:00 heartbeat: read: bcast eth0 > root 9379 9374 0 16:44 ? 00:00:00 heartbeat: write: bcast eth1 > root 9380 9374 0 16:44 ? 00:00:00 heartbeat: read: bcast eth1 > > Nevertheless, the nodes declare each other dead when the crosslink is > pulled: > Mar 10 16:57:21 koch heartbeat: [4648]: WARN: node julia.uvt.nl: is dead > Mar 10 16:57:21 julia heartbeat: [9374]: WARN: node koch.uvt.nl: is dead > > Why is the heartbeat link on eth0 not preventing this?
No idea. There's nothing in the logs which would indicate where is the problem. This should work. Did you check with tcpdump if heartbeats are reaching the other side? Though there are no error messages about eth0. At least this should be easy to debug: run the cluster with only bcast eth0 and see if that works. You can also try with unicast and see how that behaves. If the problem is definitely with heartbeat, you should open a bugzilla. Thanks, Dejan > [hb_report included] > > tia, > Johan > _______________________________________________ > Linux-HA mailing list > [email protected] > http://lists.linux-ha.org/mailman/listinfo/linux-ha > See also: http://linux-ha.org/ReportingProblems _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
