- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Serviceguard error trying to rename a cluster.
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
Discussions
Discussions
Discussions
Forums
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
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
тАО08-25-2010 10:54 PM
тАО08-25-2010 10:54 PM
I created a new ServiceGuard cluster but I forgot to give it a proper name so I decided to change the default name "cluster1). I did the following steps:
1) cmhaltcl
2) cmdeleteconf
3) cmapplyconf -v -k -C /etc/cmcluster/mycluster/cluster.ascii
Im stuck at this since I cant apply the new configuration file with the new name, receiving this error message:
Defaulting MAX_CONFIGURED_PACKAGES to 300.
Checking nodes ... Done
Checking existing configuration ... cmapplyconf : Command can not be executed remotely.
Addition of node sdppapl1 to cluster PRUEBA-NFS is possible only when
command is issued from a node which is already a part of the cluster.
Please login to one of the cluster member nodes of cluster PRUEBA-NFS
and reissue the command.
Any way to fix this?
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-26-2010 04:26 AM
тАО08-26-2010 04:26 AM
SolutionIt's just a suggestion, but you might try rebuilding your new cluster, with just the one node.
Then once it builds, add the other node.
Just a quick thought,
Rita
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-26-2010 06:17 AM
тАО08-26-2010 06:17 AM
Re: Serviceguard error trying to rename a cluster.
Use cmquerycl -C new.ascii -n
Include all nodes that will be in the cluster.
This will create a fresh cluster configuration ASCII file. Then modify the cluster name in the file and other parameter values as needed, then use cmapplyconf.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-28-2010 12:35 AM
тАО08-28-2010 12:35 AM
Re: Serviceguard error trying to rename a cluster.
revert to original configuration.
halt the cluster cmhaltcl -f
1) cmdeleteconf -P
2) cmdeletconf -c <> to remove the cluster config
halt the cluster cmhaltcl -f
3) edit the cluster config file for new cluster name
4) cmchekconf and applyconf
5) cmruncl
6) add packahes using cmcheckconf -P <> and cmapplyconf -P <>
regards
sujit
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-29-2010 10:46 PM
тАО08-29-2010 10:46 PM
Re: Serviceguard error trying to rename a cluster.
Problem solved. What happened was that I was trying to rename the cluster with the same name of another cluster in the same subnet so I got that error, simply changed the named to whatever and it worked.
Thanks folks!