- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - Linux
- >
- RedHat Linux High Availability add-on behaviour
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
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
Community
Resources
Forums
Blogs
- 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
01-24-2014 02:39 AM
01-24-2014 02:39 AM
RedHat Linux High Availability add-on behaviour
HI,
We are testing the RedHat High Availability add-on software with the Resilient storage add-on. We are having a slight issue:-
We have created a 2 node RedHat Linux cluster using virtual machines.
The cluster forms correctly, and the Global File system is fenced.
If we now reboot the one system, the system leaves the cluster correctly, but it does not rejoin the cluster on boot up.
If they reset the node and boot, it joins the cluster correctly.
If anybody can advise on why this should happen we would really appreaciate it.
Thanks
Andrew
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-29-2014 04:17 AM
01-29-2014 04:17 AM
Re: RedHat Linux High Availability add-on behaviour
Which version of RHEL? 5.x? 6.x?
What kind of virtual machines? VMware? RHEV? Other?
Which fencing method are you using?
Have you verified that multicast works between the nodes?
Here are some tools and procedures for testing:
https://access.redhat.com/site/articles/22304
With some switches (e.g. Cisco), IGMP snooping will work correctly only if there is a source of IGMP queries in the network segment/VLAN. If there is no source of IGMP queries, cluster can form if two nodes are started simultaneously, but if one node is stopped and then restarted, it will fail to rejoin the cluster because the forwarding of multicast traffic between the switches will not be restarted.
RedHat document:
https://access.redhat.com/site/node/216463/40/0
Cisco document:
http://www.cisco.com/en/US/products/hw/switches/ps708/products_tech_note09186a008059a9df.shtml