HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: FIRST_CLUSTER_LOCK_PV
Operating System - HP-UX
1832854
Members
3265
Online
110047
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
10-03-2002 05:41 AM
10-03-2002 05:41 AM
Solution
well it depends how you are configuring this.
If you configure the two nodes into the same cluster, this is a two node cluster, and each node is a member and runs hte cmcld daemon and talks to each other. the package you run will hten run on one node, and if that node fails, should switch to the other node if configured to do so.
If you are only configuring one node as the cluster, you have a single node cluster and the applicatin package will not and cannot switch.
It is up to you to define whether you have a single node or two node cluster.
I would also strongly recommend you look at attending one of hte many Hands On With MC/ServiceGuard courses tat are run by HP Education, as this would be invaluable exposure and experience.
If you configure the two nodes into the same cluster, this is a two node cluster, and each node is a member and runs hte cmcld daemon and talks to each other. the package you run will hten run on one node, and if that node fails, should switch to the other node if configured to do so.
If you are only configuring one node as the cluster, you have a single node cluster and the applicatin package will not and cannot switch.
It is up to you to define whether you have a single node or two node cluster.
I would also strongly recommend you look at attending one of hte many Hands On With MC/ServiceGuard courses tat are run by HP Education, as this would be invaluable exposure and experience.
My house is the bank's, my money the wife's, But my opinions belong to me, not HP!
- « Previous
-
- 1
- 2
- Next »
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