- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- heartbeat IP
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
09-13-2006 10:20 AM
09-13-2006 10:20 AM
heartbeat IP
/etc/hosts and /netconf files on both the nodes.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-13-2006 10:33 AM
09-13-2006 10:33 AM
Re: heartbeat IP
compile cluster ascii file using cmcheckconf and cmapplyconf. If you get any errors, you need to fix them during compilation.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-13-2006 10:36 AM
09-13-2006 10:36 AM
Re: heartbeat IP
after entring /dev/vglock i got the below message
FIRST_CLUSTER_LOCK_VG /dev/vglock
# Warning: Either no volume groups were found on all nodes and no
# Quorum Server specified,
# or all shared volume groups belong to an existing cluster.
# Use cmdeleteconf to delete existing configuration.
# A Quorum Server or a cluster lock volume group
# is required for clusters of only two nodes.
FIRST_CLUSTER_LOCK_VG
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-13-2006 10:47 AM
09-13-2006 10:47 AM
Re: heartbeat IP
Ex: /dev/dsk/c2t3d4 using as cluster lock disk
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-13-2006 10:55 AM
09-13-2006 10:55 AM
Re: heartbeat IP
i mean how do we come to know..
which disk has to be used and can u tell me about that as well.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-13-2006 11:06 AM
09-13-2006 11:06 AM
Re: heartbeat IP
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-13-2006 07:45 PM
09-13-2006 07:45 PM
Re: heartbeat IP
To answer your question, if you follow the steps outlined in the Managing Serviceguard manual you will see that you first creat a VG and then share it using vgexport/vgimport.
Once that is done, you ensure the VG is activated on one node, and then you do the cmquerycl comand, which will detect a shared Vg and pick a physical disk to be the cluster lock disk, and it will fill this in automatiocally into the ascii file