Building Disaster Recovery Serviceguard Solutions Using Metrocluster with Continuous Access XP P9000 for Linux B.12.00.00

on completing a rolling upgrade of HP Serviceguard, see the latest edition of Managing HP
Serviceguard A.12.00.00 for Linux available at http://www.hp.com/go/linux-serviceguard-docs.
Upgrading Metrocluster software
To perform a rolling upgrade of Metrocluster software:
1. Disable package switching for all Metrocluster packages.
2. Install the new Metrocluster software on all the nodes.
3. Enable package switching for all Metrocluster packages.
To upgrade Raid Manager software, see “Upgrading the XP or P9000 Raid Manager software
for Metrocluster with Continuous Access XP P9000 for Linux” (page 46).
Limitations of the rolling upgrade for Metrocluster
Limitations of the rolling upgrade for Metrocluster:
• The cluster or package configuration cannot be modified until the rolling upgrade is completed.
If the configuration must be edited, upgrade all the nodes to the new release, and then modify
the configuration file and copy it to all the nodes in the cluster.
• New features of the latest version of Metrocluster cannot be used until all the nodes are
upgraded to the latest version.
• No more than two versions of Metrocluster can be running in the cluster while the rolling
upgrade is in progress.
• The rolling upgrade procedure cannot be used as a means of using multiple versions of
Metrocluster software within the cluster. HP recommends that you upgrade all the cluster nodes
to the latest version as quickly as possible.
• HP Serviceguard cannot be deleted on any node when the rolling upgrade is in progress in
the cluster.
Upgrading the XP or P9000 Raid Manager software for Metrocluster with Continuous
Access XP P9000 for Linux
To upgrade the XP or P9000 RAID Manager software online without any disruption in the
Metrocluster, follow the instructions included in the HP P9000 RAID Manager User Guide available
at http://www.hp.com/support/manuals -> storage -> Storage Software -> Storage Device
Management Software -> HP XP RAID Manager Software . Metrocluster communicates with XP or
P9000 Raid Manager software only when Metrocluster packages are starting up. So, Metrocluster
package failover or package movement must be avoided until all the nodes in the Metrocluster
are upgraded to the same version of the P9000 or XP RAID Manager software. When using the
disk monitoring feature, Metrocluster packages access the RAID Manager instances on the nodes
that the packages are running on. So, in such configurations, ensure that all Metrocluster packages
are moved to a different node prior to updating the XP or P9000 RAID Manager software.
Other considerations on asynchronous mode
The following are additional points to consideration when using asynchronous mode:
• When adding a new volume to an existing device group, the new volume state is SMPL. The
XP disk array controller (DKC) is smart enough to do the paircreate only on the new volume.
If the device group has mixed volume states such as PAIR and SMPL, the pairvolchk returns
EX_ENQVOL, and horctakeover fails.
• If you change the LDEV number associated with a given target/LUN, you must restart all the
Raid Manager instances even though the Raid Manager configuration file is not modified.
• Any firmware update, cache expansion, or board change, requires a restart of all the Raid
Manager instances.
46 Administering Metrocluster