- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- MCSG Config Dilemma
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
03-07-2002 06:09 AM
03-07-2002 06:09 AM
MCSG Config Dilemma
I cannot cmdeleteconf (even with the -f option) to permit the creation of a new configuration on node2/2 because the node1 does not exist and this prevents the cmdeleteconf from completing.
I guess there's some tidying up to be done somewhere, but where and how ?
TIA
Rob
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-07-2002 06:30 AM
03-07-2002 06:30 AM
Re: MCSG Config Dilemma
you can try this,
Do a cmgetcong to generate the ascii configuration file from your present cluster binary file. Then modify this file to exclude node1 and do a cmcheckconf. Then do a cmapplyconf to apply the new ascii configuration which exludes the node1.
Hope this helps.
regds
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-07-2002 06:38 AM
03-07-2002 06:38 AM
Re: MCSG Config Dilemma
Try this link from hp docs site,
http://docs.hp.com/cgi-bin/fsearch/framedisplay?top=/hpux/onlinedocs/B3936-90065/B3936-90065_top.html&con=/hpux/onlinedocs/B3936-90065/00/00/51-con.html&toc=/hpux/onlinedocs/B3936-90065/00/00/51-toc.html&searchterms=delete%20cluster%20node%20down&queryid=20020307-063832
This link is from itrc,
http://us-support3.external.hp.com/cki/bin/doc.pl/sid=7259a1ba1b2b90d7f4/screen=ckiDisplayDocument?docId=200000059167468
Hope this helps.
regds
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-07-2002 07:43 AM
03-07-2002 07:43 AM
Re: MCSG Config Dilemma
You need to do the following:
1) edit /etc/cmcluster/cmclnodelist and ensure that the 2 nodes remaining are present.
2)cmquerycl -v -C /etc/cmcluster/cmclconf.ascii -n node1 -n node2
3) cmcheckconf -v -C /etc/cmcluster/cmclconf.ascii
4) cmapplyconf -v -C /etc/cmcluster/cmclconf.ascii
5) cmruncl -f -v
6) cmviewcl -v
This is all designed to regenerate your cluster using only the 2 existing nodes.
Anything further let us know.
Gl.
FG.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-07-2002 08:44 AM
03-07-2002 08:44 AM
Re: MCSG Config Dilemma
1)backup the /etc/cmcluster directories ;-}
2)halt the cluster completely
3)edit the ascii file to just refer to the two nodes and ENSURE you have a cluster lock disc coinfigured.
4)remove the current binary cmclconfig on each node
5)cmcheckconf
6)vgchange -c n on the vg's
7)vgchange -a y for all the vg's to be used (this ensures they get writen with the new cluster id)
8)cmapplyconf
9)vgchange -a n all vg's
10) cmruncl
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-07-2002 08:47 AM
03-07-2002 08:47 AM
Re: MCSG Config Dilemma
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-08-2002 09:07 AM
03-08-2002 09:07 AM
Re: MCSG Config Dilemma
You only have two machines in a previous 3 node cluster. IF that node has been removed & say re commissioned then you probably only have one choice.
# rm /etc/cmcluster/cmclconfig
then redo a new cluster.ascii with the node removed then
# cmapplyconf -C /etc/cmcluster/cluster.ascii -P /etc/cmcluster/
Regards
Tim