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

Halted
P00>>
On SERVER2 (Member2 or any Non-Lead Member) run enter the clu_upgrade undo
install command. It warns to use dupatch, which has already completed, so answer
yes. This restores tagged files and may take a few minutes (for example, 20 minutes on an
ES45 using EVA5000 SAN storage):
# clu_upgrade undo install
6. Boot the Lead Member into multi-user mode and perform undo of the Preinstall Stage.
# clu_upgrade undo preinstall
7. Undo Setup Stage. To do this first you have to disable tagged files on other members (Member
2 (SERVER2) and so on).
a. Check the status of the clu_upgrade process and if non-lead member is running on
Tagged Files, perform the following command to disabled tagged files. The non-lead
members should be running on tagged files at this time.
# clu_upgrade tagged disable 2
NOTE: This command is run on Member2 (SERVER2) and the member ID 2 is passed
as a parameter for this member. Any additional members need to be disabled also.
b. Reboot the member that the Tagged Files where disabled on to complete the process;
in this example, Member 2 (SERVER2).
c. Run the undo Setup Stage on the lead member (SERVER1) to complete the deletion of
the patch. This task takes approximately 10 minutes to complete.
# clu_upgrade undo setup
The cluster is now backed out from the clu_upgrade patch installation.
Caution on Removing Version Switched Patches
When removing version switched patches on a cluster, do not remove version switched patches
that were successfully installed in a previous rolling upgrade.
This situation can occur because more than one patch subset may contain the same version
switched patch. Although both the new and old patches can be removed during a roll, only the
most recently installed, newer version switched patch can be properly removed.
The older version switched patch can only be properly removed according to the documented
procedure associated with that patch. This usually requires running some program before
beginning the rolling upgrade to remove the patch.
If you accidentally remove the older version switched patch, the rolling upgrade will most likely
fail on the switch stage. To correct this situation, you will have to undo the upgrade by undoing
all the stages up to and including the "install" stage. You will then need to reinstall the original
version switched patch from the original patch kit that contained it.
Steps Prior to the Switch Stage
You can remove a patch kit you installed during the rolling upgrade at any time prior to issuing
the clu_upgrade switch command by returning to the install stage, rerunning dupatch,
and selecting the Patch Deletion item in the Main Menu. See “Removing Patches” for
information about removing patches with dupatch.
The procedure is as follows:
56 Patching a Cluster