topic RedHat Cluster Suite in Operating System - Linux

RedHat Cluster Suite

LivioTeixeiraFilho — Fri, 09 Dec 2005 07:48:38 GMT

Hi,

I have a Redhat Cluster Suite with 2 nodes, using option "Multicast HeartBeating" on clumembd, whith default IP: 225.0.0.11

The cluster member names are:

[root@rhcs1 root]# grep node /etc/hosts
192.168.100.1 node1
192.168.100.2 node2

My problem is that the Multicast IP is relating to other network addresses:

See:

[root@rhcs1 root]# ping 225.0.0.11
PING 225.0.0.11 (225.0.0.11) 56(84) bytes of data.
64 bytes from 10.20.178.241: icmp_seq=0 ttl=64 time=0.115 ms
64 bytes from 10.20.178.242: icmp_seq=0 ttl=64 time=0.353 ms (DUP!)

How to relate Multicast 225.0.0.11 to cerrect IPs (192.168.100.1 and 192.168.100.2) ?

Thanks.

Re: RedHat Cluster Suite

Vitaly Karasik_1 — Sun, 11 Dec 2005 07:10:02 GMT

Livio,

As far as I remember (you can verify this in RH Cluster Manager Manual) cluster uses for heartbeating network interface accosiated with hostname, e.g. in your case it's NIC with rhcs1 name.

Re: RedHat Cluster Suite

LivioTeixeiraFilho — Thu, 15 Dec 2005 13:55:13 GMT

Karasik,

I did this test before, and the problem was the same.
See:

[root@node1 root]# hostname
node1
[root@node1 root]# grep node1 /etc/hosts
192.168.100.1 node1
[root@node1 root]# ping 225.0.0.11
PING 225.0.0.11 (225.0.0.11) 56(84) bytes of data.
64 bytes from 10.20.178.241: icmp_seq=0 ttl=64 time=0.099 ms
64 bytes from 10.20.178.242: icmp_seq=0 ttl=64 time=0.324 ms (DUP!)

I solved the problem creating a new route to multicast address with network device:

route add 225.0.0.11 dev eth1

After that, the cluster is working well:

[root@node1 root]# route add 225.0.0.11 dev eth1
[root@node1 root]# ping 225.0.0.11
PING 225.0.0.11 (225.0.0.11) 56(84) bytes of data.
64 bytes from 192.168.100.1: icmp_seq=0 ttl=64 time=0.119 ms
64 bytes from 192.168.100.2: icmp_seq=0 ttl=64 time=0.360 ms (DUP!)

Thanks,

Livio.