- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Multiple Heartbeat Lans
Operating System - HP-UX
1754323
Members
2513
Online
108813
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
Go to solution
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
тАО06-27-2002 10:29 AM
тАО06-27-2002 10:29 AM
The MC/Service Guard book says: "It is recommended that you configure heartbeats on all subnets, including those to be used for client data."
I'm having a hard time understanding how this is done.
Let me give my example with the gaping holes in it.
I have a 2 node cluster (called clust), with computer A and B on it.
Node A has 4 lan cards on 3 different subnets.
lan1 1.2.10.x is where the applications and main host connects are.
lan2 1.2.20.x is where the heartbeat mini network is.
lan3 1.2.30.x is a network that backs up filesystems to tape.
lan4 is unconfigured. It would be for lan failover.
Node B has the same configuration.
Here's what I can see for the clust.ascii file.
CLUSTER_NAME clust
FIRST_CLUSTER_LOCK_VG /dev/vg01
NODE_NAME nodeA
NETWORK_INTERFACE lan1
STATIONARY_IP 1.2.10.88
NETWORK_INTERFACE lan2
HEARTBEAT_IP 1.2.20.5
NETWORK_INTERFACE lan3
STATIONARY_IP 1.2.30.5
NETWORK_INTERFACE lan4
NODE_NAME nodeB
NETWORK_INTERFACE lan1
STATIONARY_IP 1.2.10.89
NETWORK_INTERFACE lan2
HEARTBEAT_IP 1.2.20.6
NETWORK_INTERFACE lan3
STATIONARY_IP 1.2.30.6
NETWORK_INTERFACE lan4
As shown above, I have only one heartbeat card on each node, not three. Do I change the words "STATIONARY_IP" to "HEARTBEAT_IP"?
My packages would run on lan1 on both nodes.
Thanks for any help.
I'm having a hard time understanding how this is done.
Let me give my example with the gaping holes in it.
I have a 2 node cluster (called clust), with computer A and B on it.
Node A has 4 lan cards on 3 different subnets.
lan1 1.2.10.x is where the applications and main host connects are.
lan2 1.2.20.x is where the heartbeat mini network is.
lan3 1.2.30.x is a network that backs up filesystems to tape.
lan4 is unconfigured. It would be for lan failover.
Node B has the same configuration.
Here's what I can see for the clust.ascii file.
CLUSTER_NAME clust
FIRST_CLUSTER_LOCK_VG /dev/vg01
NODE_NAME nodeA
NETWORK_INTERFACE lan1
STATIONARY_IP 1.2.10.88
NETWORK_INTERFACE lan2
HEARTBEAT_IP 1.2.20.5
NETWORK_INTERFACE lan3
STATIONARY_IP 1.2.30.5
NETWORK_INTERFACE lan4
NODE_NAME nodeB
NETWORK_INTERFACE lan1
STATIONARY_IP 1.2.10.89
NETWORK_INTERFACE lan2
HEARTBEAT_IP 1.2.20.6
NETWORK_INTERFACE lan3
STATIONARY_IP 1.2.30.6
NETWORK_INTERFACE lan4
As shown above, I have only one heartbeat card on each node, not three. Do I change the words "STATIONARY_IP" to "HEARTBEAT_IP"?
My packages would run on lan1 on both nodes.
Thanks for any help.
Solved! Go to Solution.
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-27-2002 10:37 AM
тАО06-27-2002 10:37 AM
Solution
You should at least change the STATIONARY_IP's to HEARTBEAT_IP's. This would give you two heartbeats on each node. That should be adequate if these LAN connections go through independent switches/hubs. Bear in mind that for a 2-node cluster you can simply use a crossover cable in lieu of a hub or switch for the heartbeat lan.
If it ain't broke, I can fix that.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-27-2002 10:39 AM
тАО06-27-2002 10:39 AM
Re: Multiple Heartbeat Lans
Hello,
The entry "HEARTBEAT_IP" means that that network interface is used as a heartbeat network and potentially data traffic. The answer is yes, if you want to have a heartbeat on all subnets, then you will need to change the "STATIONARY_IP" to "HEARTBEAT_IP" then cmcheckconf and cmapplyconf with the cluster down.
Everything should be just fine
Good luck
Chris
The entry "HEARTBEAT_IP" means that that network interface is used as a heartbeat network and potentially data traffic. The answer is yes, if you want to have a heartbeat on all subnets, then you will need to change the "STATIONARY_IP" to "HEARTBEAT_IP" then cmcheckconf and cmapplyconf with the cluster down.
Everything should be just fine
Good luck
Chris
It wasn't me!!!!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-27-2002 10:43 AM
тАО06-27-2002 10:43 AM
Re: Multiple Heartbeat Lans
So you guys mean.....
NODE_NAME nodeA
NETWORK_INTERFACE lan1
HEARTBEAT_IP 1.2.10.88
NETWORK_INTERFACE lan2
HEARTBEAT_IP 1.2.20.5
NETWORK_INTERFACE lan3
HEARTBEAT_IP 1.2.30.5
NETWORK_INTERFACE lan4
NODE_NAME nodeB
NETWORK_INTERFACE lan1
HEARTBEAT_IP 1.2.10.89
NETWORK_INTERFACE lan2
HEARTBEAT_IP 1.2.20.6
NETWORK_INTERFACE lan3
HEARTBEAT_IP 1.2.30.6
NETWORK_INTERFACE lan4
Ok. I can do that. And even though I only have a two node network (soon). I have a heartbeat lan that has been around in anticipation of service guard.
Thanks. Points are coming.
steve
NODE_NAME nodeA
NETWORK_INTERFACE lan1
HEARTBEAT_IP 1.2.10.88
NETWORK_INTERFACE lan2
HEARTBEAT_IP 1.2.20.5
NETWORK_INTERFACE lan3
HEARTBEAT_IP 1.2.30.5
NETWORK_INTERFACE lan4
NODE_NAME nodeB
NETWORK_INTERFACE lan1
HEARTBEAT_IP 1.2.10.89
NETWORK_INTERFACE lan2
HEARTBEAT_IP 1.2.20.6
NETWORK_INTERFACE lan3
HEARTBEAT_IP 1.2.30.6
NETWORK_INTERFACE lan4
Ok. I can do that. And even though I only have a two node network (soon). I have a heartbeat lan that has been around in anticipation of service guard.
Thanks. Points are coming.
steve
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