On Mon, Nov 07, 2005 at 01:40:07PM -0500, Lon Hohberger wrote: > On Mon, 2005-11-07 at 15:17 +0000, Patrick Caulfield wrote: > > Axel Thimm wrote: > > Yes. we should register a multicast address. The default action is to use > > broadcast and there is no default multicast address. There's one mentioned in > > some example config files (which I think is the router one you mentioned) Perhaps until having a registered multicast address, the docs should use something in the range 239.x.x.x? Perhaps even 239.255.x.x, which is the "minimal enclosing local scope" implying that cluster heartbeat should not go across the whole organizational scope? Otherwise 239.192/14 is for organizational scope. > 224.0.0.0/24 is the router range, I think... Don't remember. It's been > awhile. 224.0.0/24 is for local network control, 224.0.1/24 is internetwork control including stuff like NTP syncing. There are unassigned IPs from 224.0.1.179 upwards. If they don't know what to do with you you get into 224.0.23.x upwards (currently 224.0.23.160). That's for ipv4, ipv6 is another beast. It depends on how many IPs you'd like to reserve. I'd go for at least two to have a default config for redundant intracluster networking. And cman would by default use only the first one. http://www.iana.org/cgi-bin/multicast.pl -- Axel.Thimm at ATrpms.net
Attachment:
pgpGmC66gLZpn.pgp
Description: PGP signature
-- Linux-cluster@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/linux-cluster
