[prev in list] [next in list] [prev in thread] [next in thread] 

List:       linux-ha-dev
Subject:    Re: [Linux-ha-dev] non broadcast heartbeats (again)
From:       Chris Wright <chris () wirex ! com>
Date:       2001-11-27 18:55:55
[Download RAW message or body]

* Tony Willoughby (tonyw@pobox.com) wrote:
> 
> Hello,
> 
> On November 14th, Jean-Yves asked:
> 
> http://marc.theaimsgroup.com/?l=linux-ha&m=100575753204976&w=2
> 
> > how can i do to restrict udp heartbeats emission between my 2 cluster
> > nodes only ?
> > I don't want broadcast.
> > Is it possible?
> > Thanks,
> 
> I didn't see an answer to this and was wondering if there is one.
> 
> In a more general sense:  Has anyone had success running Heartbeat over a 
> routed network?  Should it be expected to work (if one gets past the 
> broadcast issue)?

as horms and lars pointed out, there is multicast support.  this allows
you to define a group of hosts that will receive the heartbeats.
multicast is routable, but you have to have mrouted capable routers
along the way.  also, make sure to use a routable multicast address, and
choose the right ttl.  if you have control of the interim routers, you
may want to consider using a multicast address in the 'administratively
scoped' range (239.0.0.0 - 239.255.255.255).  this is roughly akin to
10.0.0.0 private range, which is why you have to be able to direct the
administrative domain at each mrouted point.

for a decent overview see:
http://www.linuxdoc.org/HOWTO/Multicast-HOWTO.html

rfc 1112 is the basic multicast rfc
rfc 1700 will show you which multicast addresses are already reserved
(and no, heartbeat.mcast.net is not what you want to use ;-)

cheers,
-chris
_______________________________________________________
Linux-HA-Dev: Linux-HA-Dev@lists.community.tummy.com
http://lists.community.tummy.com/mailman/listinfo/linux-ha-dev
Home Page: http://linux-ha.org/

[prev in list] [next in list] [prev in thread] [next in thread]