- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Service Guard upgrade and migration
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
04-07-2004 09:03 PM
04-07-2004 09:03 PM
Service Guard upgrade and migration
I'm in for a rolling upgrade from SG 11.12 to 11.14 on HPUX 11.0
The procedure seems quite straight forward.
However in the procedure the student materials mentions 'Turn off auto cluster configuration' before upgrade.
I don't recall any auto cluster configuration setting in Service Guard, am I missing out on something ?
After upgrading to 11.14 I am in for a migration from quorum lock disk to a quorum server.
As far as I understand this means I need to stop whole cluster, cmhaltcl, and uncomment
FIRST_CLUSTER_LOCK_VG /dev/vg01
FIRST_CLUSTER_LOCK_PV /dev/dsk/c2t1d0
and add
QS_HOST kaka1
QS_POLLING_INTERVAL 120000000
then run cmapplyconf and cmruncl.
(and of course add the clustermembers to qs_authfile and qs -update on the quorum server)
Is this the right way to go ?
TIA
Johan
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-07-2004 09:07 PM
04-07-2004 09:07 PM
Re: Service Guard upgrade and migration
Set AUTOSTART_CMCLD to 0 on both nodes during the upgrade.
For the quorum server changes - that looks correct to me.
HTH
Duncan
I am an HPE Employee

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-07-2004 09:56 PM
04-07-2004 09:56 PM
Re: Service Guard upgrade and migration
Since you need to change the quorum lock disk, why do a rolling upgrade. You can just stop the cluster, install the software on all nodes and apply the new config file ans start the cluster again.
HTH,
Gideon
PS I am awaire it will take some extra down time, but the change something go's wrong is a lot smaller.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-07-2004 10:27 PM
04-07-2004 10:27 PM
Re: Service Guard upgrade and migration
Yes, it might be smart to do everything in an offline mode.
However, when you apply that much changes at one time and something goes wrong the troubleshooting can become more tricky.
/Johan
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-07-2004 11:02 PM
04-07-2004 11:02 PM
Re: Service Guard upgrade and migration
I find it only complicating if your MC/SG versions differ among nodes. If the MC/SG version is the upgraded at once, you can check & apply the old ascii file ( including lock disks) first, if this works, you can check and apply the new file. For fall back we always use a standby ingite tape ( or image ).
HTH,
Gideon
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-07-2004 11:03 PM
04-07-2004 11:03 PM
Re: Service Guard upgrade and migration
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-08-2004 03:23 AM
04-08-2004 03:23 AM
Re: Service Guard upgrade and migration
This means set the variable in /etc/rc.config.d/cmcluster from 1 to 0
While doing your upgrade, have you chosen to go to the Quorum Server method? This is not mandatory, you could first upgrade your servers, run them with the cluster lock disc for a time while confirming all is well, and then plan to change to a quorum server setting.
Just a thought
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-08-2004 08:30 AM
04-08-2004 08:30 AM
Re: Service Guard upgrade and migration
cmapplyconf will not work when mixed versions of SG are on nodes in the cluster.
.SD.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-12-2004 09:08 PM
04-12-2004 09:08 PM
Re: Service Guard upgrade and migration
It'll be hard to configure the nodes for quorum server before the upgrade since QS was first availible in 11.14 :)
----
Thanks for all replies!
I'll will probably go for an 'offline' upgrade and first test it with the old config (with lock disk). Then bring the cluster down and change to quorum server and bring it back up.
As mentioned above, ignite is the way to go before doing anything!
/Johan