- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - Linux
- >
- RedHat Cluster Suite
Operating System - Linux
1754016
Members
7897
Online
108811
Solutions
Forums
Categories
Company
Local Language
юдл
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
юдл
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-08-2005 11:48 PM
тАО12-08-2005 11:48 PM
RedHat Cluster Suite
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.
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.
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-10-2005 11:10 PM
тАО12-10-2005 11:10 PM
Re: RedHat Cluster Suite
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.
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-15-2005 05:55 AM
тАО12-15-2005 05:55 AM
Re: RedHat Cluster Suite
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.
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.
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP