- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Heartbeat Best Practices
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
07-07-2009 04:31 AM
07-07-2009 04:31 AM
Heartbeat Best Practices
Are there any bestpractices as far as configuring heartbeat interfaces?
How many heartbeats are recommended for a two node cluster?
What kind of configuration is recommended, crossover cable from node to node?
Please advice!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-07-2009 04:53 AM
07-07-2009 04:53 AM
Re: Heartbeat Best Practices
- A crossover cable is very nice for heartbeats: there is very little that can go wrong with it. Unfortunately, it is not applicable to clusters with more than two nodes.
- One heartbeat is technically enough, but makes it impossible to On-Line Replace a heartbeat NIC while the node is active in the cluster. When you have two or more heartbeat interfaces, OLR of one NIC at a time is possible. (Unless you put all heartbeats on a single dual- or quad-port NIC... oops!)
- If you have two heartbeats and one of them is a crossover cable, I'd say you have enough for most common needs. If you can get a third one easily with your network topology, that's nice... but *requiring* more than three heartbeats would usually be overkill.
But if the cluster is running an air traffic control, a surgery robot or some other life-and-death-critical system, you might have stricter requirements.
MK
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-07-2009 04:55 AM
07-07-2009 04:55 AM
Re: Heartbeat Best Practices
It is recomended to have Heartbeat on diffrent lan not on Public lan.
You can use diffrent switch for Heartbeat or crosscable from node to node.
For redundancy if your Budget allows you can have two diffrent lan cards, and you can also use your Public lan for Heartbeat as well for redundancy purpose.
Regards
Sanjeev
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-07-2009 04:55 AM
07-07-2009 04:55 AM
Re: Heartbeat Best Practices
1 heartbeat is good enough.
2 is awesome.
One of the two heartbeat networks should be on a private network that can not get congested, like on a private hub, switch or even a cross connect cable.
SEP
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-07-2009 05:53 AM
07-07-2009 05:53 AM
Re: Heartbeat Best Practices
Use as many lans as you can for heartbeat.
Crossover cables are supported for a two node cluster, but they are not as good as having a hub/switch in between.
Take a read of:
http://docs.hp.com/en/serviceguard_heartbeats_conf.pdf/serviceguard_heartbeats_conf.pdf
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-15-2009 09:34 AM
07-15-2009 09:34 AM
Re: Heartbeat Best Practices
The Best Pracitices to Configure Heart Beat
for 2 Node Cluster.
2 Heart Beat Network on private network in the 2 different switch or even cross cable between 2 Servers.
Thanks.