11v3 and SG migration

[sanish]

Hi Gurus,

I need to do a HPUX Upgrade to 11v3 from 11v2.
I need to upgrade 4 nodes running 2 clusters (2 node DB cluster and 2 Node App cluster)
It need be be done using the rolling upgrade . One DB node and 1App node at a time after unjoining it from the clusters .

My concern is after the upgrade , is there any issue to join the cluster which running on 11.v2 with lower version of SG and failback
to the new Upgraded boxes. Is SG will work with diff version of OS as well as SG.
Do we need to verify the cluster after the upgrade ?

[Wim Rombauts · Accepted solution]

You don't say what version of ServiceGuard you are currently running on HP-UX 11i v2.
If it is 11.17, first do a rolling upgrade of ServiceGuard to 11.18 and add the latets patches for ServiceGuard

Then upgrade the OS to 11i v3, but at this time both 11i v3 and 11i v2 will be running the same ServiceGuard version.

[sanish]

I am not gonna upgrade Service guard now ..
SG is 11.17 and i am gonna keep the same version some more time :)
I think 11.17 will work on 11.v3 without any issues .

[sanish]

to more specific , v2 is running with A.11.17.00 SG and V3 will be A.11.17.01.

[Steven E. Protter]

Shalom,

The update-ux process if flawed, and fails much of the time.

Experienced admins such as myself do not recommend upgrading the OS.

Instead the process should be to do a clean install of the OS, then necessary patches, then applications.

The configuration of the cluster itself is something you can migrate.

I would recommend reducing each cluster to 1 node each, upgrade and prepare two new nodes. Then cmhaltcl both working clusters and start the cluster on the newly prepared nodes.

Schedule some downtime for this because disruption is required.

Once working on your 11.31/11.17 based cluster, you can repeat the process on the recently shut down nodes and maintain up applications through the rest of the process.

SEP

[sanish]

The Update-Ux got failed and we rolled back the change