Am Mittwoch, 3. Juni 2009 12:52:14 schrieb [email protected]: > Hello all. > > > > Is there now any use to having the 2nd interface connected with HA?
Redundancy in the heartbeat path. > When previously configuring servers with HB 2.1.3, LVS and ldirectord I > had the resources listeing on eth1 and had heartbeat communicate over > eth0 on both servers to try and cut down on noise. If you do not want to have the broadcast traffic on your net, use the ucast statement in ha.cf > Is there any reason to do this and if so in what way would you set it up > using single HA resources in a 2-node HA cluster? Use: Redundancy of heartbeat path. Setup: on node1: bcast eth0 ucast eth1 <ip address of node2 on eth0> on node2: bcast eth0 ucast eth1 <ip address of node1 on eth0> But anyway, using the resources net for heartbeat communication is not the best idea. Better add a interface card to you server and user additionally eth2. By the way: When adding a new IF to the node you also could upgrade from 2.1.3 to pacemaker. Greetings, -- 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
