- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Any way to tell what file was used to build cmclco...
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
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
тАО05-19-2009 01:19 PM
тАО05-19-2009 01:19 PM
Any way to tell what file was used to build cmclconfig ?
Alternatively, is there a way to force cmapplyconf to build a differently named cmclconfig so I can do a series of cmapplyconf's against the different ascii files and then compare the cmclconfig outputs to the currently running version ?
Aah - standards and documentation - it's always fun when they're missing.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-19-2009 10:07 PM
тАО05-19-2009 10:07 PM
Re: Any way to tell what file was used to build cmclconfig ?
simply you can build the original cluster configuration file from the current binary file using cmgetconf and save it any where.
cmgetconf -c
cmgetconf -p
thanks
kamal
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-19-2009 10:11 PM
тАО05-19-2009 10:11 PM
Re: Any way to tell what file was used to build cmclconfig ?
You can use cmgetconf command to create an ascii file from the current runing cluster.then you can keep that as the current cluster configuration or if you are so eager to find out the asci file which was applied last, do compare the old files with newly created ascii file :-)
the commad syntax is
#cmgetconf -c
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-21-2009 03:39 AM
тАО05-21-2009 03:39 AM
Re: Any way to tell what file was used to build cmclconfig ?
There is no way to say which file was used.
rather you can do the following:
use :
cmgetconf -c
cmgetconf -p
to generate the ascii files.
--and---
run a
# diff /tmp/cluster.ascii /ASCII_FILE_IN_Question
# cmp /tmp/cluster.ascii /ASCII_FILE_IN_Question
Question: Is there a way to force cmapplyconf to build a differently named cmclconfig so I can do a series of cmapplyconf's against the different ascii files and then compare the cmclconfig outputs to the currently running version ?
Answer :
NO, cmapplyconf will over write the exisiting cmclconfig.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-22-2009 05:32 AM
тАО05-22-2009 05:32 AM
Re: Any way to tell what file was used to build cmclconfig ?
As others have stated, cmgetconf can be used to reconstitute the source ASCII file.