HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- device file name of the cluster lock disk
Operating System - HP-UX
1833760
Members
2508
Online
110063
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-17-2006 07:18 AM
05-17-2006 07:18 AM
I have a cluster of two nodes and one package with a Storage EMC Symmetrix. Therefore my disc of look this lost, I can repair this situation and to connect the server to another port of the EMC.
But the question is, i cant change the name c_t_d_ of device file in the .cfg file only halting the cluster changing the file and restating the cluster and pkg ?
But the question is, i cant change the name c_t_d_ of device file in the .cfg file only halting the cluster changing the file and restating the cluster and pkg ?
Solved! Go to Solution.
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-17-2006 07:39 AM
05-17-2006 07:39 AM
Solution
If your question is:
Must I halt the cluster to change the cluster lock disk device name in the cluster, the answer is YES, you must do this and re-apply the cluster binary with cmapplyconf.
Must I halt the cluster to change the cluster lock disk device name in the cluster, the answer is YES, you must do this and re-apply the cluster binary with cmapplyconf.
My house is the bank's, my money the wife's, But my opinions belong to me, not HP!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-17-2006 07:56 AM
05-17-2006 07:56 AM
Re: device file name of the cluster lock disk
You are correct.
The ServiceGuard manual is very clear on this:
http://docs.hp.com/en/B3936-90100/ch07s04.html
Table 7-1 lists various kinds of changes to the cluster configuration and the required state for each.
"Change Cluster Lock Configuration - Cluster must not be running."
If you're running a 24/7/365 operation and need to make storage configuration changes, cluster lock disks are a big pain.
You can change the ASCII configuration file any time you wish - but to make the change take effect, you must run cmapplyconf. If the cluster is running and the lock disk path has changed, the cmapplyconf will not make the change.
There is an alternative: set up a Quorum Server and use it instead of a lock disk.
With QS, redundant SAN connections and some use of MirrorDisk/UX, you can migrate the cluster from old storage to new with no downtime at all.
The ServiceGuard manual is very clear on this:
http://docs.hp.com/en/B3936-90100/ch07s04.html
Table 7-1 lists various kinds of changes to the cluster configuration and the required state for each.
"Change Cluster Lock Configuration - Cluster must not be running."
If you're running a 24/7/365 operation and need to make storage configuration changes, cluster lock disks are a big pain.
You can change the ASCII configuration file any time you wish - but to make the change take effect, you must run cmapplyconf. If the cluster is running and the lock disk path has changed, the cmapplyconf will not make the change.
There is an alternative: set up a Quorum Server and use it instead of a lock disk.
With QS, redundant SAN connections and some use of MirrorDisk/UX, you can migrate the cluster from old storage to new with no downtime at all.
MK
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