Am Montag, 2. Februar 2009 18:27:32 schrieb Arndt Roth: > Here is my ha.cf (identical on all nodes - own interfaces are dropped > anyway): ------------------------------------------ > logfacility local0 > keepalive 1 > deadtime 30 > warntime 10 > udpport 694 > > ucast eth1 10.1.1.194 > ucast eth1 10.1.1.195 > ucast eth1 10.1.1.196 > > ucast eth2 10.1.2.244 > ucast eth2 10.1.2.245 > ucast eth2 10.1.2.246 > > auto_failback on > node server1 server2 server3 > deadping 3 > crm on > ------------------------------------------- > > server1 has two interfaces 10.1.1.194 and 10.1.2.244 > server2 has two interfaces and so on... > > I can see heartbeat ucasting on both eth1 and eth2 - that's fine. > > But my question was, if server1 is considerer "active" if only eth1 fails > and eth2 is still ok? If I bind resources (IPaddr) to eth1 they won't be > migrated to another node, right?
I would not make it dependend on the state (up/down) of the interface but of the "pingability" of a pingnode. This could be be i.e. the default router in that net 10.1.1.1. In that case you you no only take case of the network interface state but of all switches, cables and other network stuff in between that can break. See: www.linux-ha.org/pingd -- Dr. Michael Schwartzkopff MultiNET Services GmbH Addresse: Bretonischer Ring 7; 85630 Grasbrunn; Germany Tel: +49 - 89 - 45 69 11 0 Fax: +49 - 89 - 45 69 11 21 mob: +49 - 174 - 343 28 75 mail: [email protected] web: www.multinet.de Sitz der Gesellschaft: 85630 Grasbrunn Registergericht: Amtsgericht München HRB 114375 Geschäftsführer: Günter Jurgeneit, Hubert Martens --- PGP Fingerprint: F919 3919 FF12 ED5A 2801 DEA6 AA77 57A4 EDD8 979B Skype: misch42 _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
