On Wed, Jun 03, 2009 at 01:46:29PM +0200, Michael Schwartzkopff wrote: > Am Mittwoch, 3. Juni 2009 13:43:03 schrieb Dejan Muhamedagic: > > On Wed, Jun 03, 2009 at 01:06:02PM +0200, Michael Schwartzkopff wrote: > > > 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> > > > > Adding > > > > > ucast eth1 <ip address of node1 on eth0> > > > ucast eth1 <ip address of node2 on eth0> > > > > in both ha.cf works as well. That way ha.cf remains equal on all > > nodes. > > > > > But anyway, using the resources net for heartbeat communication is not > > > the best idea. > > > > Why not? Because of noise? There's not much traffic with > > heartbeat. Of course, in this case it is preferable to use > > unicast. > > - Using tcpdump on an other node in that net I have to add "not port 694".
Just like for any other traffic you don't want to see. Really, how could this be an argument? > - If the other traffic blocks the net, you get delayed heartbeats. Unless the switch is really saturated this shouldn't be the case. Besides, that's why there are redundant communication paths. The nodes could also be in different rooms. > - Having multiple clusters on the same net you have to use other ports than > 694 with broadcasts. There's always an option to use unicast. At any rate, as well as with the first argument, I don't see why this should be an issue. It's regular sysadmin business. Thanks, Dejan > > -- > 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 _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
