Upgrading service guard

[Trng]

Hi All,

I need to upgrade the hpux 11.23 Cluster which is running with Service guard A.11.16.00 to 11.18 and service guard extension for SAP from B.03.11 to 4.51..

Pls let me know how to upgrade and challenges ..which one i hv to upgrade first(mcsg or sesap )..

[Steven E. Protter]

Shalom,

To upgrade SG itself, I recommend planning for a little downtime.

Basics:
Fail all packages to the node you are not upgrading.
cmhaltnode the first node to upgrade.

Perform the swinstall installation of SG 11.18

cmhaltnode the running second node.

Attempt to start the upgraded node.

If this node starts all packages, perform the upgrade on the second node.

I recommend trying this out in a lab environment prior to trying it live in production.

There are differences in how SG handles network issues and I would alert my user community to a significant downtime prior to doing it in production.

SEP

[Stephen Doud]

The SGeSAP lab does not provide an "upgrade" document but insist on a new implementation when upgrading to a newer version.

Be sure to review the Release Notes at http://docs.hp.com/en/T2803-90010/ch01s03.html and the
Managing Serviceguard Extension for SAP, December 2007 at http://docs.hp.com/en/T2803-90011/index.html for instructions on the implementation.

[Rita C Workman]

Here's a caveat to watch for - Rolling MC/SG upgrade.

General with MC/SG you can do a rolling upgrade. In the past it was great and gave you time to spread out the upgrade.
But starting around MC/SG version 11.17 it doesn't like if you run the older versions within the cluster.

You can do it, but it means that you can't cleanly do a rolling upgrade. Failover gets affected temporarily. Worse, if you have nodes within the same cluster running 11.16 & 11.18, you won't be able to make ANY changes until everything is up and at the new version. No new vg's, no new pkgs, basically no changes at all.

So if you start your upgrade, you need to finish it - or - you would have to run sort of "moving" upgrade by basically creating a new cluster, and removing nodes from old cluster, upgrade SG on node and add node to the new 11.18 SG cluster.

Since you don't mention how many nodes are in your cluster, thought you might want to be aware of this.

Regards,
Rita