HP Serviceguard Extension for RAC (SGeRAC) manual Limitations of Rolling Upgrades

Figure 25 Running Cluster After Upgrades

Limitations of Rolling Upgrades

The following limitations apply to rolling upgrades:

•During a rolling upgrade, you should issue Serviceguard/SGeRAC commands (other than cmrunnode and cmhaltnode) only on a node containing the latest revision of the software. Performing tasks on a node containing an earlier revision of the software will not work or will cause inconsistent results.

•You cannot modify the cluster or package configuration until the upgrade is complete. Also, you cannot modify the hardware configuration—including the cluster’s network configuration—during a 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.

•The new features of the Serviceguard/SGeRAC release may not work until all nodes have been upgraded.

•Binary configuration files may be incompatible between releases of Serviceguard/SGeRAC. Do not manually copy configuration files between nodes.

•Within a Serviceguard/SGeRAC cluster, no more than two versions of Serviceguard and SGeRAC can be running while the rolling upgrade is in progress.

•You can perform a rolling upgrade only on a configuration that has not been modified since the last time the cluster was started.

•Rolling upgrades are not intended as a means of using mixed releases of HP-UX, Serviceguard, or SGeRAC within the same cluster. HP recommends to upgrade all the cluster nodes to the new release level at the earliest.

You can upgrade OS during rolling upgrade only if your cluster uses SLVM over Raw disks, ASM over Raw disks, or ASM over SLVM configuration for the shared storage.

For more information see, http://www.hp.com/go/hpux-serviceguard-docs—> HP Serviceguard manual.

Rolling Software Upgrades 147