Operating System - HP-UX
1836786 Members
3093 Online
110110 Solutions
New Discussion

Rolling upgrade from 11.05 to 11.14 ?

 
Arne Wattman
Advisor

Rolling upgrade from 11.05 to 11.14 ?

Hi,
we have a 2 node cluster running MC/SG A.11.05.
I would like to upgrade it to A.11.14. Can I do that using HP's Rolling upgrade documentation ?
Any traps ?

We are running HP-UX 11.0 on both nodes.
3 REPLIES 3
Bernhard Mueller
Honored Contributor

Re: Rolling upgrade from 11.05 to 11.14 ?

Arne,

the Release Notes:

http://docs.hp.com/hpux/onlinedocs/B3935-90055/00/00/6-con.html

say yes, it will be quite unlikely you find s.b. who did an upgrade from exactly this version (11.05) to 11.14

Guess most people should be at least on 11.09 as the oldest currently supported platform release.

You might want to do a QPK patch upgrade before upgrading MC/SG.

Regards,
Bernhard
Jeff Schussele
Honored Contributor

Re: Rolling upgrade from 11.05 to 11.14 ?

I agree with Bernhard,
11.05 to 11.14 is a BIG jump.

If this is a Production cluster, take the outage & do this offline. Sounds like you're probably fairly out of date on patches anyway.

Rgds,
Jeff
PERSEVERANCE -- Remember, whatever does not kill you only makes you stronger!
Stephen Doud
Honored Contributor

Re: Rolling upgrade from 11.05 to 11.14 ?

Per the manual at http://docs.hp.com/hpux/onlinedocs/B3936-90065/B3936-90065.html - Appendix E:

"Rolling upgrade is supported with any of the supported revisions of MC/ServiceGuard. You can roll forward from any previous revision to any higher revision. For example, it is possible to roll from MC/ServiceGuard version A.10.05 on HP-UX 10.10 to version A.11.12 on HP-UX 11.00."

The intent of a rolling upgrade is to minimize package downtime while bringing one cluster node at a time up to a newer version of ServiceGuard (and allow patching). That's why Appendix E is in the manual.

The process entails moving packages off of the node to be upgraded, disabling it from automatically joining the cluster, upgrading the server and finally rejoining it into the cluster.

Be forewarned that during a rolling upgrade, cmapplyconf is disabled from updating cluster or package information in the cluster binary.

StephenD.