Managing Serviceguard Eighteenth Edition, September 2010

Performing a Rolling Upgrade Using DRD
IMPORTANT: All the limitations listed under “Guidelines for Rolling Upgrade”
(page 450) and “Limitations of Rolling Upgrades ” (page 451) also apply to a rolling
upgrade with DRD. You should read the entire section on “Performing a Rolling
Upgrade” (page 451) before you proceed.
Before You Start
CAUTION: Do not proceed with an upgrade to A.11.19 until you have read and
understood the Special Considerations for Upgrade to Serviceguard A.11.19 (page 447).
IMPORTANT: Not all paths that are supported for rolling upgrade are supported
for an upgrade using DRD, and there are additional requirements and restrictions
for paths that are supported.
Do not proceed until you have read the “Announcements”, “Compatibility”, and
“Installing Serviceguard” sections of the latest version of the Serviceguard Release
Notes, made sure your cluster meets the current requirements, and taken any necessary
preparation steps as instructed in the release notes.
• Make sure you plan sufficient system capacity to allow moving the packages from
node to node during the process without an unacceptable loss of performance.
• Make sure you have read and understood the “Restrictions for DRD Upgrades”
(page 449).
• Make sure that you have downloaded the latest DRD software and are thoroughly
familiar with the DRD documentation. See “Rolling Upgrade Using DRD” (page 449)
for more information.
Running the Rolling Upgrade Using DRD
1. On the node you want to upgrade, edit /etc/rc.config.d/cmcluster to
include the following line:
AUTOSTART_CMCLD = 0
This value will be replicated on the clone root disk and will keep the upgraded
node from automatically rejoining the cluster when it reboots.
2. Create a clone root disk for the node you want to upgrade.
3. Upgrade the clone disk to the new HP-UX release (if necessary), including
Serviceguard (using drd runcmd update-ux), or upgrade Serviceguard alone
(using drd runcmd swinstall).
4. Halt the node. You can do this in Serviceguard Manager, or use the cmhaltnode
(1m) command. This will cause the node’s packages to start up on an adoptive
node.
5. Reboot the node from updated clone root disk.
6. Edit the /etc/rc.config.d/cmcluster file to include the following line:
454 Software Upgrades