SG 11.14 & 11.16 in one cluster

[Stuart Powell]

I am planning some application migrations from two two-node clusters both running SG 11.14. They will be combined into one cluster on a single two node cluster running SG 11.16. The question is; can I build a 6 node cluster with this different levels of SG?

Stuart

[Duncan Edmonstone · Accepted solution]

If I understand you correctly:

you have a 3 clusters:

cluster1 with nodeA and nodeB running 11.14
cluster2 with nodeC and nodeD running 11.14
cluster3 - the new cluster with nodeE and nodeF running 11.16

You want to add the 2 old clusters to the new cluster, migrate the packages across, and then get rid of the 4 'older' nodes?

Or am I missing the point?

Anyway, I don't think you will be able to do it the way you describe. SG does support different versions of the cluster software, but only during a rolling upgrade, and there are a bunch of limitations on the rolling upgrade. Have a look at appendix E of the Serviceguard manual here:

http://docs.hp.com/en/B3936-90079/apes03.html

The two important points are:

You cannot modify the cluster or package configuration until the upgrade is complete. You cannot modify the hardware configurationâ including the cluster's network configurationâ during rolling upgrade. This means that you must upgrade all nodes to the new release before you can modify the configuration file and copy it to all nodes

and

Rolling upgrades are not intended as a means of using mixed releases of Serviceguard or HP-UX within the cluster. It is highly recommended that you upgrade all cluster nodes as quickly as possible to the new release level.

Particularly the first one - if you can't change the cluster configuration, that implies you can't combine the clusters.

I don't think you will be able to achieve this without some package downtime, which means you may as well just do this offline...

HTH

Duncan

[Uday_S_Ankolekar]

You can not just add a server to a existing cluster without halting cluster and when you have different version of SG running within a cluster you cannot make changes in cluster or package, cmcheckconf and cmapplyconf may error out.

Read rolling upgrade tips from docs.hp.com

http://docs.hp.com/en/B3936-90079/apes02.html#d0e22382

-USA..

[Stuart Powell]

Thanks for the confirmation.