Operating System - HP-UX
1833796 Members
4686 Online
110063 Solutions
New Discussion

Service Guard upgrade and migration

 
UNIXGRUPPEN
Advisor

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
8 REPLIES 8

Re: Service Guard upgrade and migration

I suspect the 'Turn off auto cluster configuration' is referring to the start at boot setting in /etc/rc.config.d/cmcluster

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
Accept or Kudo
G. Vrijhoeven
Honored Contributor

Re: Service Guard upgrade and migration

Hi Johan,

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.
UNIXGRUPPEN
Advisor

Re: Service Guard upgrade and migration

Hi Gideon,

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
G. Vrijhoeven
Honored Contributor

Re: Service Guard upgrade and migration

Hi again Johan,

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
G. Vrijhoeven
Honored Contributor

Re: Service Guard upgrade and migration

PS, we never needed the ignite tape though.
melvyn burnard
Honored Contributor

Re: Service Guard upgrade and migration

'Turn off auto cluster configuration' before upgrade.
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

My house is the bank's, my money the wife's, But my opinions belong to me, not HP!
Stephen Doud
Honored Contributor

Re: Service Guard upgrade and migration

If you want to go to a quorum server, do it before you upgrade the one node, or you will have to wait until all nodes are at the same version.

cmapplyconf will not work when mixed versions of SG are on nodes in the cluster.

.SD.
UNIXGRUPPEN
Advisor

Re: Service Guard upgrade and migration

Stephen,
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