service guard upgrade

[abhishek8191]

I have a two node cluster and planning to upgrade to 11.16 from 11.14

I am thinking to switch the packages and upgrade one node at a time

I am curious if I install new version of service guard will i loose all cluster and package config files on that node, or will they get upgraded with new version and data will remain intact

[Steven E. Protter]

Shalom,

You should at least have a downtime window set up and here is why.

You can stay up and running by migrating all your packages to one node and upgrading the other.

It gets a little tricky, because the newly minted 11.16 node can not join a cluster running 11.14. Therefore the cluster needs to briefly be halted while you bring up these same services on the new 11.16 node.

Once the node is up and running all packages, the second node can be upgraded at your leisure.

There are a few brave souls who have figured out how to do this upgrade without downtime, but most who tried have ended up with TOC on one node.

SEP

[abhishek8191]

do I need to use new package config files or the ones currently being used for 11.14 can be used for 11.16?

[Ishwar_1]

Find the below link for your reference:-

http://forums11.itrc.hp.com/service/forums/questionanswer.do?threadId=1050309

http://forums11.itrc.hp.com/service/forums/questionanswer.do?threadId=1384357

[Bhadresh · Accepted solution]

Please have a look at the â upgrading Serviceguardâ and â if you are upgrading from earlier releasesâ section from Serviceguard Version A11.16 release notes:

http://docs.hp.com/en/B3935-90078/B3935-90078.pdf

Regards,
Bhadresh

[melvyn burnard]

doing an upgrade of Serviceguard does NOT touch the /etc/cmcluster directory, except when it updates the cmclconfig binary in that directory..
So, to answer your questions:
> will i loose all cluster and package config files
No, they stay there.
>will they get upgraded with new version
Only the cmclconfig file will be updated.
To use the new functionality/format f the SG A.11.16 pcakge control and config files, you would need to use cmmakepkg to create a new config and a new control script, then merge your current variable settings fo rthe package into the newer ones, and reapply them.
But they will continue to work with the old ones, you just do not get the newfunctionality etc.

[John Bigg]

Note that what Steven says is NOT correct.

You do not have to halt the entire cluster. The new 11.16 node CAN join the exiting running 11.14 cluster.

This is clearly described in the Managing Serviceguard manual in appendix E. Rolling Software Upgrades. This is step 3 on page 395 of the 2nd edition of the 11.16 manual. To quote the text to demonstrate this:

----
When upgrading is finished, enter the following command on node 1 to
restart the cluster on node 1.

# cmrunnode -n node1

At this point, different versions of the Serviceguard daemon (cmcld) are
running on the two nodes, as shown in Figure E-4.
----

The key to note here is that when you are running a mixed revision cluster in the middle of an upgrade, you should run all commands (other than cmrunnode and cmhaltnode) from the higher revision node. i.e. if you need to move a package from the 11.14 node to the 11.16 node you should do this running commands from the 11.16 node.