When I disconnect the heartbeat from one of the servers, whether through the shutdown of the NIC or by physically removing the cable, the other node senses this as a failure and immediately takes over both floating IP addresses. Strangely the node where the heartbeat was removed from also acquires both floating IP addresses and therefore causes much grief on the network. I'm at a loss here and this is causing me a lot of headache. Any ideas?
Here is node 1's ha.cf: #debugfile /var/log/ha-debug logfile /var/log/ha-log logfacility local0 keepalive 2 deadtime 30 warntime 10 initdead 60 udpport 694 ucast eth2 10.0.0.2 auto_failback on ping_group group1 10.220.3.50 10.220.3.55 apiauth client-name gid=haclient uid=hacluster apiauth ipfail gid=haclient uid=hacluster max_rexmit_delay 10000 hbgenmethod time node node1.server.com node node2.server.com Here is node 2's ha.cf: #debugfile /var/log/ha-debug logfile /var/log/ha-log logfacility local0 keepalive 2 deadtime 30 warntime 10 initdead 60 udpport 694 ucast eth2 10.0.0.1 auto_failback on ping_group group1 10.220.3.50 10.220.3.55 apiauth client-name gid=haclient uid=hacluster apiauth ipfail gid=haclient uid=hacluster max_rexmit_delay 10000 hbgenmethod time node node1.server.com node node2.server.com The IP address for the heartbeat on node1 is 10.0.0.1 and the heartbeat on node2 is 10.0.0.2. The ping_group are servers within the infrastructure that are extrememly reliable. Still, I am at a complete loss. Any help will be greatly appreciated. Best regards, Brian Klauss _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
