HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: Remove a node from a 3 node SG cluster
Operating System - HP-UX
1827844
Members
1280
Online
109969
Solutions
Forums
Categories
Company
Local Language
back
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
back
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
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Go to solution
Topic Options
- 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
12-01-2007 12:43 AM
12-01-2007 12:43 AM
I want to remove "db2" from a three node cluster made up of (db1,db2,db3). I plan to then re-cluster db2 to an independent cluster with db4 .
Would this work (and not upset packages running on db1 and db3); we use quorum server that is aware of db1, db2, db3, db4 and manages quorum for these two clusters (db1,db2,db3 and db4):
From db1 with both db1 and db3 running production packages:
cmhaltnode db2
cmgetconf cmclconfig.ascii
cp cmclconfig.ascii cmclconfig.just-in-case
# edit cmclconfig.ascii, remove meantion of db2 and its network interfaces
cmcheckconf -v -C cmclconfig.ascii
cmapplyconf -v -C cmclconfig.ascii
# adjust storage presentations so that db1,db3 LUNs are not visible to db2
Do I then also need to "cmdeleteconf" on db2? before I wed it to db4?
Next, on db4:
cmgetconf cmclconfig.ascii
cmgetconf cmclconfig.just-in-case
# edit cmclconfig.ascii to include db2 networking stuff
cmcheckconf -v -C cmclconfig.ascii
cmapplyconf -v -C cmclconfig.ascii
# adjust storage presentations and make sure db2 is in packages as a candidate for failover
Would this work (and not upset packages running on db1 and db3); we use quorum server that is aware of db1, db2, db3, db4 and manages quorum for these two clusters (db1,db2,db3 and db4):
From db1 with both db1 and db3 running production packages:
cmhaltnode db2
cmgetconf cmclconfig.ascii
cp cmclconfig.ascii cmclconfig.just-in-case
# edit cmclconfig.ascii, remove meantion of db2 and its network interfaces
cmcheckconf -v -C cmclconfig.ascii
cmapplyconf -v -C cmclconfig.ascii
# adjust storage presentations so that db1,db3 LUNs are not visible to db2
Do I then also need to "cmdeleteconf" on db2? before I wed it to db4?
Next, on db4:
cmgetconf cmclconfig.ascii
cmgetconf cmclconfig.just-in-case
# edit cmclconfig.ascii to include db2 networking stuff
cmcheckconf -v -C cmclconfig.ascii
cmapplyconf -v -C cmclconfig.ascii
# adjust storage presentations and make sure db2 is in packages as a candidate for failover
Solved! Go to Solution.
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-01-2007 01:51 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-02-2007 12:37 PM
12-02-2007 12:37 PM
Re: Remove a node from a 3 node SG cluster
Do I then also need to "cmdeleteconf" on db2? before I wed it to db4?
Not required. The earlier steps mentioned is sufficient enough. You may verify the nodes active in the cluster by "cmviewcl -l node"
Not required. The earlier steps mentioned is sufficient enough. You may verify the nodes active in the cluster by "cmviewcl -l node"
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Support
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP