Upgrading to HP Serviceguard 11.17 with Cluster Volume Manager/Cluster File Systems, December 2005

Other considerations

Configuring SGeRAC with Oracle RAC 9i and 10g is described in detail in the Using Serviceguard

Extension for RAC Third Edition manual. Most of the upgrade considerations applicable to SGeRAC

have already been described previously.

One desirable application property that becomes feasible with CFS is the capability of cluster-wide

installation, configuration, or both. Because this typically requires some support from the application

and explicit awareness of the cluster environment, it will be up to vendors of individual applications to

provide these capabilities. Oracle is a good example of this type of application because it supports

placing ORACLE_HOME on a CFS file system.

Migration from Tru64 UNIX and TruCluster platforms is being addressed and covered separately.

Detailed information is available from the Tru64 Transition site at

http://www.hp.com/go/tru64transition/.

Upgrade roadmap

To perform the upgrade:

1. Perform a complete backup of existing configuration.

2. If one of the Serviceguard Storage Management bundles or stand-alone CVM will be installed:

a. Halt and delete from the cluster any application packages that use CVM. Retain the package

configuration files to be applied after the upgrade.

b. Halt and delete from the cluster the CVM package VxVM-CVM-pkg, if present.

3. Halt the Serviceguard cluster.

4. Prevent Serviceguard from starting automatically during boot by changing the line

AUTOSTART_CMCLD=1 in /etc/rc.config.d/cmcluster to AUTOSTART_CMCLD=0.

5. Upgrade network hardware components as needed.

6. If a Serviceguard Storage Management bundle will be installed and CVM is currently installed on

the cluster, remove it from each node with the following command:

# swremove B9117AA

7. Install the new software.

8. Make and apply any changes needed to the Serviceguard cluster ASCII configuration file to reflect

network modifications.

9. If CVM was installed above as part of a CFS bundle, configure and apply the new CVM package

SG-CFS-pkg with the following command:

# cfscluster config

10. If stand-alone CVM 4.1 was installed, apply the CVM 4.1 SMNP with:

# cmapplyconf /etc/cmcluster/cfs/SG-CFS-pkg

11. If CVM 3.5 is installed, apply the CVM 3.5 SMNP with:

# cmapplyconf /etc/cmcluster/cvm/VxVM-CVM-pkg

12. Migrate existing package configurations to use the new dependency infrastructure:

a. Create CVM disk group MNPs for the disk groups used by the packages.

b. Remove any STORAGE_GROUP attributes from the application packages’ ASCII configuration

files.

c. Add dependencies on the disk group packages to the application packages’ ASCII

configuration files.

d. Create new control scripts for the packages with cmmakepkg –s. Edit the resulting scripts to

add any custom script functions from the previous version of the control scripts.

e. Apply the resulting packages to the cluster.