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

Note:
During the install stage you load the new software on the lead member, in effect rolling that
member. When you perform the roll stage, this new software is propagated to the remaining
members of the cluster.
The clu_upgrade command does not load software during the install stage. The loading
of software is controlled by the commands you run: installupdate, dupatch, or
nhd_install.
See Table 4-1 “Rolling Upgrade Tasks Supported by Version 5.1A and Version 5.1B” for the
list of rolling upgrade tasks and combination of tasks supported for Version 5.1A and Version
5.1B.
a. See Chapter 3 “Patch Installation and Removal Instructions” for instructions on installing
a patch kit using the dupatch command.
See the Tru64 UNIX Installation Guide for detailed information on using the
installupdate command.
See the Tru64 UNIX New Hardware Delivery Release Notes and Installation Instructions that
came with your NHD kit for detailed information on using the nhd_install command.
b. If the software you are installing requires that its installation command be run from
single-user mode, halt the system and boot the system to single-user mode:
# shutdown -h now
>>> boot -fl s
Note:
Halting and booting the system ensures that it provides the minimal set of services to
the cluster and that the running cluster has a minimal reliance on the member running
in single-user mode. In particular, halting the member satisfies services that require the
cluster member to have a status of DOWN before completing a service failover. If you
do not first halt the cluster member, services will probably not fail over as expected.
When the system reaches single-user mode, run the following commands:
# init s
# bcheckrc
# lmf reset
c. Run the installupdate, dupatch, or nhd_install command.
To roll in multiple patch kits, you can invoke dupatch multiple times in a single install
stage. Be aware that doing so may make it difficult to isolate problems should any arise
after the patch process is completed and the cluster is in use.
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.
6. (Optional) After the lead member performs its final reboot with its new custom kernel, you
can perform the following manual tests before you roll any additional members:
a. Verify that the newly rolled lead member can serve the shared root (/) file system.
Rolling Upgrade 51