- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: clustername
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
01-24-2012 07:43 AM
01-24-2012 07:43 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-24-2012 08:08 AM
01-24-2012 08:08 AM
SolutionWith my crystal ball, I'm seeing that you are talking about Serviceguard yes?
The answer is yes, there is a way, but why do you want to do this?
The cluster name is directly associated with the unique cluster ID loaded into the VGDA (LVM structure) on each of the disks used by the packages in the cluster. If the cluster name is changed, the cluster ID must be removed and replaced with the new ID associated with the new cluster name for all the volume groups in the cluster.
Which basically means saving the package and cluster configs to text files using cmgetconf, stopping the cluster using cmhaltcl, deleting the existing cluster config using cmdeleteconf, changing the cluster name in the cluster config text file, re-applying the cluster and package configs using cmapplyconf, and then restarting the cluster using cmruncl
Lots of work, for what is usually a cosmetic change - the only time you should really consider doing this is if you have a duplicate cluster name in the same subnet, or using the same quorum server.
I am an HPE Employee

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-24-2012 11:36 PM
01-24-2012 11:36 PM
Re: clustername
Hello Duncan,
I think You don't need a crystall ball for that. It is the serviceguard section off the forum;)
If it would be easy, I would think about changing the name.
Thanks for the answer.
Groeten, Alfons
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-25-2012 12:03 AM
01-25-2012 12:03 AM
Re: clustername
>> I think You don't need a crystall ball for that. It is the serviceguard section off the forum;)
D'oh! I still can't get used to these new forums! I miss ITRC!
I am an HPE Employee

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-07-2012 01:31 AM
02-07-2012 01:31 AM
Re: clustername
No problem Duncan.
You are not the only one that misses ITRC......
Groeten, Alfons
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-07-2012 01:34 AM
02-07-2012 01:34 AM
Re: clustername
Thanks, Uday.
I will try to find some offline time to change it.
Groeten, Alfons