- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- cmdeleteconf
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
06-16-2004 01:56 AM
06-16-2004 01:56 AM
cmdeleteconf
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-16-2004 02:05 AM
06-16-2004 02:05 AM
Re: cmdeleteconf
I see one saving grace...cmgetconf.
from the man page.
To generate the cluster ASCII configuration file for clusterA, and
store the information in clusterA.config, do the following:
cmgetconf -c clusterA clusterA.config
To generate the package ASCII configuration file for pkg1, and store
the information in pkg1.config, do the following:
cmgetconf -p pkg1 pkg1.config
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-16-2004 02:05 AM
06-16-2004 02:05 AM
Re: cmdeleteconf
So all your ascii fiels should still be there on all your nodes .
Just reapply them using cmapplyconf and bring up your cluster .
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-16-2004 02:11 AM
06-16-2004 02:11 AM
Re: cmdeleteconf
Rgds...Geoff
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-16-2004 02:12 AM
06-16-2004 02:12 AM
Re: cmdeleteconf
AFAIK, cmdeleteconf removes only /etc/cmcluster/cmclconfig file. Try to restore it from a backup, otherwise you'll have to do the following:
In order to restore cluster one have to find the ascii file, which was created by cmqyerycl command (usually in /etc/cmcluster) and a list of the cluster packages. If the ascii file can't be found, it might be easily recreated by the command
cmquerycl -C /etc/cmcluster cluster.ascii -n node1 -n node2 -n node 3 etc.
The cluster.ascii file should be edited in order to change cluster name and max number of packages.
List of packages, if it's not found, can be created without big problems. It looks like this:
/etc/cmcluster/PACKAGE1DIR/PKG1NAME.conf
/etc/cmcluster/PACKAGE2DIR/PKG2NAME.conf
etc.
HTH
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-16-2004 02:28 AM
06-16-2004 02:28 AM
Re: cmdeleteconf
It should have prompted you to respond to actually delete the configuration.
You can simply reapply the configuration.
#for the cluster - replace cmclconfig.ascii with whatever the name you gave for the cluster configuration
cmapplyconf -C /etc/cmcluster/cmclconfig.ascii
#For each of the packages. Replace pkg.conf with your package configuration file.
cmapplyconf -P /etc/cmcluster/
-Sri