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

Table 4-1 Rolling Upgrade Tasks Supported by Version 5.1A and Version 5.1B (continued)
An update installation from Version 5.1A to Version 5.1B followed by the installation of an NHD kit for Version
5.1B
An update installation from Version 5.1B to the next release of the base operating system and cluster software
followed by the installation of an NHD kit for that next release
2
An update installation from Version 5.1A to Version 5.1B, followed by the installation of an NHD kit for Version
5.1B, followed by a patch of Version 5.1B
An update installation from Version 5.1B to the next release, followed by the installation of an NHD kit for the next
release, followed by a patch of the next release
2
1 Within one rolling upgrade, you can combine an upgrade of the base operating system and cluster software with a
patch of the new software. This means that during the install stage, you can run installupdate on the first member
followed by dupatch to patch the newly installed software. When you roll the remaining members they automatically
get both the new software and the patches.
However, you cannot patch the current software and then upgrade the base operating system and cluster software
within one rolling upgrade. This operation requires two rolling upgrades.
2 Allowed only if you have already installed an NHD kit on the Version 5.1A or Version 5.1B cluster.
Unsupported Tasks
The following list describes tasks that you cannot perform or that we recommend you do not
attempt during a rolling upgrade:
• Do not remove or modify files in the /var/adm/update directory. The files in this directory
are critical to the roll. Removing them can cause a rolling upgrade to fail.
• During the install stage, you cannot run a dupatch command followed by an
installupdate command. To patch the current software before you perform a rolling
upgrade, you must perform two complete rolling upgrade operations: one to patch the
current software, and one to perform the update installation.
• You cannot bypass versions when performing a rolling upgrade of the base operating system
and cluster software. You can only roll from one version to the next version.
• Do not use the /usr/sbin/setld command to add or delete any of the following subsets:
— Base Operating System subsets (those with the prefix OSF).
— TruCluster Server subsets (those with the prefix TCR).
— Worldwide Language Support (WLS) subsets (those with the prefix IOS).
Adding or deleting these subsets during a roll creates inconsistencies in the tagged files.
• Do not install a layered product during the roll.
Unless a layered product's documentation specifically states that you can install a newer
version of the product on the first rolled member, and that the layered product knows what
actions to take in a mixed-version cluster, we strongly recommend that you do not install
either a new layered product or a new version of a currently installed layered product during
a rolling upgrade.
For more information about layered products and rolling upgrades, see “Rolling Upgrade
and Layered Products”.
Rolling Upgrade Procedure
In the procedure in this section, unless otherwise stated, run commands in multi-user mode.
Each step that corresponds to a stage refers to the section that describes that stage in detail. We
recommend that you read the detailed description of stages in “Rolling Upgrade Stages” before
performing the rolling upgrade procedure.
Some stages of a rolling upgrade take longer to complete than others. Table 4-2 “Time Estimates
for Rolling Upgrade Stages” lists the approximate time it takes to complete each stage.
48 Patching a Cluster