HP Tru64 UNIX Version 5.1B-2 and Higher Patch Kit Installation Instructions (March 2009)

4. Run the clu_upgrade -v check setup lead_memberid command, which verifies
the following information:
• No rolling upgrade is in progress.
• All members are running the same versions of the base operating system and cluster
software.
• No members are running on tagged files.
• There is adequate free disk space.
5. Verify that each system's firmware will support the new software. Update firmware as
needed before starting the rolling upgrade.
A cluster can continue to operate during a rolling upgrade because two copies exist of the
operating system and cluster software files. (Only one copy exists of shared configuration files
so that changes made by any member are visible to all members.) This approach makes it possible
to run two different versions of the base operating system and the cluster software at the same
time in the same cluster. The trade-off is that, before you start an upgrade, you must make sure
that there is adequate free space in each of the clusterwide root (/), /usr, and /var file systems,
and, if a separate domain exists for the Worldwide Language Support (WLS) subsets, in the i18n
file system.
A rolling upgrade has the following disk space requirements:
• At least 50 percent free space in root (/), cluster_root#root.
• At least 50 percent free space in /usr, cluster_usr#usr.
• At least 50 percent free space in /var, cluster_var#var, plus, if updating the operating
system, an additional 425 MB to hold the subsets for the new version of the base operating
system.
• If a separate i18n domain exists for the WLS subsets, at least 50 percent free space in that
domain.
• No tagged files are placed on member boot partitions. However, programs might need free
space when moving kernels to boot partitions. We recommend that you reserve at least 50
MB free space on each member's boot partition.
Note:
You cannot use the addvol command to add volumes to a member's root domain (the a
partition on the member's boot disk). Instead, you must delete the member from the cluster,
use diskconfig or SysMan to configure the disk appropriately, and then add the member
back into the cluster.
• See the Patch Summary and Release Notes that came with your patch kit to find the amount
of space you will need to install that kit. If installing an NHD kit, see the New Hardware
Delivery Release Notes and Installation Instructions that came with your NHD kit to find the
amount of space you will need to install that kit.
If a file system needs more free space, use AdvFS utilities such as addvol to add volumes to
domains as needed. For information on managing AdvFS domains, see the Tru64 UNIX AdvFS
Administration manual. (The AdvFS Utilities require a separate license.) You can also expand the
clusterwide root (/) domain.
Rolling Upgrade 63