HP StorageWorks Clustered File System 3.1.1p1 Linux Edition Upgrade Guide (February 2006)

Chapter 3: Rolling Upgrade Procedure 7
• During the rolling upgrade, the cluster will include a mix of servers
running 3.1.1p1 and the earlier release 3.1.0. As long as the cluster
includes at least one active server running 3.1.0, other servers running
that version will be able to join the cluster (for example, following a
reboot). However, after the last server running 3.1.0 has left the
cluster, only servers running 3.1.1p1 can join the cluster.
Although HP Clustered File System supports a mix of servers running
3.1.1p1 and 3.1.0 during the rolling upgrade, on-going operation of a
mixed-version cluster is not supported. All servers should be
upgraded to 3.1.1p1 as quickly as possible.
• During the upgrade, a mix of servers running 3.1.1p1 and 3.1.0 may
have a PSFS filesystem mounted. After the PSFS filesystem has been
unmounted on the last node running 3.1.0, the filesystem cannot be
mounted on a 3.1.0 node unless it is first unmounted on the nodes
running 3.1.1p1.
• For best results while the cluster includes a mix of 3.1.1p1 and 3.1.0
servers, all UI operations (either via the Management Console or the
mx command-line utility) should be connected to a 3.1.0 server.
• During the rolling upgrade, filesystems cannot be upgraded to add
new features such as filesystem quotas. Instead, you will need to
complete the rolling upgrade first. Then unmount the filesystems
either one-at-a-time or, for CFS-Linux, one export group at a time and
perform the filesystem upgrade.
• You do not need to run mxconfig when upgrading to 3.1.1p1. If you
want to change any of the parameters that you originally specified
with mxconfig, first upgrade all servers to 3.1.1p1. After the upgrade
is complete, stop HP Clustered File System on each server (use /etc/
init.d/pmxs stop), and then rerun mxconfig.