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

Note:
Before undoing any stage, we recommend that you read the relevant version of the Cluster Release
Notes to determine whether there are restrictions related to the undoing of any stage.
To undo a stage, use the undo command with the stage that you want to undo. The clu_upgrade
command determines whether the specified stage is a valid stage to undo. Table 4-3 “Undoing
a Stage” outlines the requirements for undoing a stage:
Table 4-3 Undoing a Stage
CommentsCommandStage to Undo
You must run this command on the lead member. In addition, no
members can be running on tagged files when you undo the setup
stage.
Before you undo the setup stage, use the clu_upgrade -v status
command to determine which members are running on tagged files.
Then use the clu_upgrade tagged disable memberid command
to disable tagged files on those members. (See “Tagged Files” for
information about tagged files and the commands used to manipulate
them.)
When no members are running on tagged files, run the clu_upgrade
undo setup command on the lead member.
clu_upgrade undo
setup
Setup
You must run this command on the lead member.
clu_upgrade undo
preinstall
Preinstall
You can run this command on any member except the lead member.
Halt the lead member. Then run the clu_upgrade undo install
command on any member that has access to the halted lead member's
boot disk. When the command completes, boot the lead member.
If you installed a patch kit or individual patches during the install
stage, you must first run dupatch to uninstall the patch kit before
running the clu_upgrade undo install command. “Removing
Patches Installed During a Rolling Upgrade” describes the steps for
removing a patch kit during a rolling upgrade.
clu_upgrade undo
install
Install
You must run this command on the lead member.
clu_upgrade undo
postinstall
Postinstall
You can run this command on any member except the member whose
roll stage will be undone.
Halt the member whose roll stage is being undone. Then run the
clu_upgrade undo roll memberid command on any other
member that has access to the halted member's boot disk. When the
command completes, boot the halted member. The member will now
be using tagged files.
clu_upgrade undo
roll memberid
Roll
Rolling Upgrade Commands
The clu_upgrade command, described in clu_upgrade(8), controls the overall flow of a rolling
upgrade and ensures that the stages are run in order. During the install stage, you run one or
more of installupdate, dupatch, or nhd_install to load and install software. These
commands are rolling upgrade aware; they are modified to understand which actions they are
allowed to take during the install and roll stages of a rolling upgrade.
When you start a rolling upgrade, the cluster is running the software from the previous release.
For the first part of any rolling upgrade, you are running the clu_upgrade command that is
already installed on the cluster. If a new version is installed during the rolling upgrade, there
may be minor differences in the on-screen display and behavior between the two versions of the
command.
Rolling Upgrade 59