On Fri, 21 Jul 2006, sun sadm wrote:
> Date: Fri, 21 Jul 2006 11:25:02 +0200
> From: sun sadm <sunsadm@xxxxxxxxx>
> Reply-To: linux clustering <linux-cluster@xxxxxxxxxx>
> To: linux-cluster@xxxxxxxxxx
> Subject: dedicated heartbeat LAN and documentation
>
> Hello colleague
>
> How to configure a dedicated LAN (for example eth3) as heartbeat? We
> don't wish heartbeat over public LAN.
>
> Second: the official documentation (Red Hat Cluster Suite Configuring
> and Managing a Cluster) is very bad. Are there additional documents?
Here is an example of what I did in a two-node cluster:
Both nodes have a public interface on interface eth0. You can also set
up bonding using eth1 if you want to.
eth2 on both are assigned a private address (xxx.xx.xx.xxx and
yyy.yy.yy.yyy respectively) and are directly physically connected to
each other with one patch cable.
The cluster is configured to listen to these two ip addresses on the
two nodes.
Run on node1:
/sbin/ifconfig eth2 xxx.xx.xx.xxx pointopoint yyy.yy.yy.yyy multicast netmask 255.255.255.0 up
/sbin/route add -net yyy.yy.yy.0 netmask 255.255.255.0 dev eth0 # I need this for fencing the other
node via its service processor that is on the same subnet of yyy.yy.yy.0
/sbin/route add -host yyy.yy.yy.yyy gw xxx.xx.xx.xxx
/sbin/route add -net 224.0.0.0 netmask 240.0.0.0 dev eth2 # I use multicast.
and run on node2:
/sbin/ifconfig eth2 yyy.yy.yy.yyy pointopoint xxx.xx.xx.xxx multicast netmask 255.255.255.0 up
/sbin/route add -net xxx.xx.xx.0 netmask 255.255.255.0 dev eth0
/sbin/route add -host xxx.xx.xx.xxx gw yyy.yy.yy.yyy
/sbin/route add -net 224.0.0.0 netmask 240.0.0.0 dev eth2
You need to have these commands in a startup script and run right after eth0
is set up.
That's roughly the idea.
Regards,
Jie
--
Linux-cluster@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/linux-cluster
