[Linux-cluster] Use alternate network interfaces for heartbeat in RHCS

Christine Caulfield ccaulfie at redhat.com
Fri Aug 28 14:15:22 UTC 2009


On 28/08/09 15:10, brem belguebli wrote:
> Hi,
> I'm trying to send cluster communications thru dedicated LAN interfaces
> (out of band network) separate from the production interfaces but it
> doesn't seem to be functional.
> I have a 2 nodes cluster (RHEL 5.3) with 2 bonding interfaces each, one
> bonding for production on a given Vlan and the other on a dedicated and
> isolated LAN (out of band LAN).
> According to some cman doc (that may be outdated), the way to do so is
> to declare explicitely at each clusternode level  the multicast addr of
> the cluster and the interface on which the coms are sent.
> <clusternode name="node1.mydomain" nodeid="1" votes="1">
> <multicast addr="239.128.2.1" interface="bond1"/>
> </clusternode>
> <clusternode name="node2.mydomain" nodeid="2" votes="1">
> <multicast addr="239.128.2.1" interface="bond1"/>
> </clusternode>
> and the cman multicast addr:
> <cman expected_votes="3" two_node="0">
> <multicast addr="239.128.2.1"/>
> </cman>
> (I have a qdiskd).
> After restarting the cluster, traffic is still sent through bond0 which
> is the production interface.(tcpdump -i bond0 host 239.128.2.1)


I don't know where that document is but it's rather out of date, as you 
suspected ;-)

The wiki has a up-to-date item on how to assigned different ethernet 
interfaces for cman:

http://sources.redhat.com/cluster/wiki/FAQ/CMAN#cman_heartbeat_nic

Chrissie




More information about the Linux-cluster mailing list