HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: Heartbeat messages
Operating System - HP-UX
1838108
Members
3396
Online
110124
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
Forums
Discussions
Discussions
Discussions
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
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
05-13-2003 11:55 PM
05-13-2003 11:55 PM
Hi,
I'm configuring several Heartbeat pathes (one dedicated with small hub and one through the network) in order to prevent from SPOF.
NODE_NAME ftsys9
NETWORK_INTERFACE lan0
HEARTBEAT_IP 15.13.171.32
NETWORK_INTERFACE lan3
HEARTBEAT_IP 192.6.7.3
But I wonder if HB messages are sent to both ways simultaneously (lan0 and lan3) or if one way (f.e. dedicated one - lan0) is primary and the other one (lan3) secondary ??
Are Heartbeat messages working in active/standby mode ??
I'm configuring several Heartbeat pathes (one dedicated with small hub and one through the network) in order to prevent from SPOF.
NODE_NAME ftsys9
NETWORK_INTERFACE lan0
HEARTBEAT_IP 15.13.171.32
NETWORK_INTERFACE lan3
HEARTBEAT_IP 192.6.7.3
But I wonder if HB messages are sent to both ways simultaneously (lan0 and lan3) or if one way (f.e. dedicated one - lan0) is primary and the other one (lan3) secondary ??
Are Heartbeat messages working in active/standby mode ??
Solved! Go to Solution.
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-14-2003 12:20 AM
05-14-2003 12:20 AM
Solution
The HB messages are sent in parallel using all configured HB networks. Of course, the cluster is happy to get messages through at least one of the paths.
Best regards...
Dietmar.
Best regards...
Dietmar.
"Logic is the beginning of wisdom; not the end." -- Spock (Star Trek VI: The Undiscovered Country)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-15-2003 01:11 AM
05-15-2003 01:11 AM
Re: Heartbeat messages
Hi Dietmar
is right ... I hope you are
not under the impression that
lan3 can be used as a standy
for lan0 in the configuration
you sent ...
The main data standby lan has
to be unconfigured in order to be used by MCSG.
Regards
Christos
is right ... I hope you are
not under the impression that
lan3 can be used as a standy
for lan0 in the configuration
you sent ...
The main data standby lan has
to be unconfigured in order to be used by MCSG.
Regards
Christos
Together we stand divided we fall
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-15-2003 03:50 AM
05-15-2003 03:50 AM
Re: Heartbeat messages
Very good question. To the best of my knowledge MC/SG has always just provided one primary heartbeat for signaling. Use 'cmverify -v' or 'cmscancl -o file' for this.
Having two LANs designated as heartbeat LANs within the cluster.ascii file is an indication that they qualified during the creation of the cluster binary. 'cmquerycl' performs this qualifying.
There are disasters to test for during your failover testing after the cluster has been created. You should be pulling LAN cables as a part of this testing to see how the primary heartbeat LAN is picked up by the standby heartbeat LAN. Again, use 'cmviewcl -v' and 'cmscancl -o file' for this.
This URL gives a nice example. Please ignore the SAM references. I'm not advocating that you use SAM for this, in fact, just the contrary.
http://docs.hp.com/cgi-bin/fsearch/framedisplay?top=/hpux/onlinedocs/B3936-90053/B3936-90053_top.html&con=/hpux/onlinedocs/B3936-90053/00/00/36-con.html&toc=/hpux/onlinedocs/B3936-90053/00/00/36-toc.html&searchterms=heartbeat%7ccmquerycl%7ccluster&queryid=20030515-054222
Having two LANs designated as heartbeat LANs within the cluster.ascii file is an indication that they qualified during the creation of the cluster binary. 'cmquerycl' performs this qualifying.
There are disasters to test for during your failover testing after the cluster has been created. You should be pulling LAN cables as a part of this testing to see how the primary heartbeat LAN is picked up by the standby heartbeat LAN. Again, use 'cmviewcl -v' and 'cmscancl -o file' for this.
This URL gives a nice example. Please ignore the SAM references. I'm not advocating that you use SAM for this, in fact, just the contrary.
http://docs.hp.com/cgi-bin/fsearch/framedisplay?top=/hpux/onlinedocs/B3936-90053/B3936-90053_top.html&con=/hpux/onlinedocs/B3936-90053/00/00/36-con.html&toc=/hpux/onlinedocs/B3936-90053/00/00/36-toc.html&searchterms=heartbeat%7ccmquerycl%7ccluster&queryid=20030515-054222
Support Fatherhood - Stop Family Law
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.
Company
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP