Dual node cluster - different versions of Serviceguard

[Simon P White]

We are planning to upgrade the version of Serviceguard on one of our applications. Are there any known issues with having nodes within the same cluster on different versions? We are currently running 11.15 and plan to upgrade to 11.16. The nodes are in Production and we plan to have them on different versions for 1 week.

[melvyn burnard · Accepted solution]

This is standard when going through a rolling upgrade, and it is the only time we support nodes in a cluster having different versions of SG.
Just be aware of patching, read the Release Notes etc and be aware of the new security features in 11.16.
Also you should run SG commands from the upgraded node, and no configuration changes are allowed while in this mode.

[Simon P White]

Melvyn - thanks for the reply. The user is asking for further clarification. The plan is to remove the inactive node from the 2 node cluster, upgrade SG from 11.15 to 11.16. Make some kernel changes for Oracle 10G and reboot. Put the node back into the cluster. Run for another week and then failover from active node (11.15) to inactive (11.16). Then do the same upgrade on the inactive node, remove from cluster, upgrade SG, kernel changes and put back into the cluster. Is this all supported and do you see any issues with this?

[melvyn burnard]

Please clarify "remove the inactive node ".
By this do you mean simply cmhaltnode? Or are you talking about removing it from the cluster configuration.
If the latter, this is not supported and will not work

[Simon P White]

Melvyn - sorry just cmhaltnode

[melvyn burnard]

that is the correct way to do the upgrade

[Simon P White]

Melvyn - thanks for your help