Upgrade from 11.14 to 11.16

[Alex Lavrov.]

Hello,

I would like to know the steps (or some docs) about upgradig from 11.14 to 11.16, in SC documentation I failed to find upgrade instructions.

The main question is, if it's OK to keep the same configuration files and only to compile them again after the product installation?

thanx.

[melvyn burnard]

Firstly, this is generally quite simple to do,
cmhaltnode node1, swinstall new version of SG plus any SG patch, cmrunnode node1.
Move packages to node1, cmhaltnode node2, swinstall, cmrunnode node2.

This is all documented in the Managing Serviceguard manuals at http://docs.hp.com/en/ha
specifically:
http://docs.hp.com/en/B3935-90078/B3935-90078.pdf
Refer to Appendix E

However, as SG 11.16 has new access policies, first read the Release Notes for 11.16 at:
http://docs.hp.com/en/B3935-90078/B3935-90078.pdf
paying attention to page 18.

[Alex Lavrov.]

YEs, I read this document, but it does not answer the question, how should I treat configuration files. Recreate them or it's ok to keep the "old" ones.

[melvyn burnard]

if you refer to the cluster ascii files and package files, then keep them as is, Sg does all the conversion for you.
Once the cluster is up with all nodes at 11.16, you could look at doing cmgetconf to recreate your cluster ascii file from the newer running binary with the new 11.16 additions.
Likewise youu can then look at possibly migrating your package config and control scripts by creating new ones using cmmakepkg, then migrating your info from the older version into the newer versions.

[Alex Lavrov.]

That was the big issue, the ascii files.
Is it officially supported to keep the "old" configuration files?

[melvyn burnard · Accepted solution]

In a word, YES.
Newer vesions of Serviceguard are compatible with older version scripts and config files, but you will not be able to use any newer functionality in those files unless you migrate.
From the Release Notes:
..

Access policies are not supported in a mixed revision cluster.

If you relied on .rhosts for access, be sure to manually configure policies for those users.

When you upgrade from an earlier version, Serviceguard converts cmclnodelist entries into Access Control Policies when every node in the cluster finishes updating. All are given the role of Monitor in the cluster configuration file.

After you complete a rolling upgrade, be sure to create and save a copy of the new configuration, using the cmgetconf command. If an cmapplyconf is issued, you want to be sure it applies the newly migrated Access Control Policies.

..

I have worked on a number of clusters that are running 11.14 or 11.15 but using 11.05 scripts and config files.

But you may find in future that you may have to migrate so keep that in mind.

[Alex Lavrov.]

Thanx a lot!

Yep, I read this document and I don't think it's gonna be a problem.