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

==========================
This dupatch session is logged in /var/adm/patch/log/session.log
Main Menu:
---------
1) Patch Kit Installation
2) Patch Kit Deletion
3) Patch Kit Documentation
4) Patch Tracking
5) Patch Baseline Analysis/Adjustment
h) Help on Command Line Interface
q) Quit
Enter your choice:
2. From the main menu select the patch installation or patch deletion option. (See “Installing
Patches from Multi-User Mode”.)
3. If dupatch determines it is running on a cluster that has not been prepared to do a rolling
patch, it asks if you want to do the patch operation without rolling. You will see a message
similar to the following:
Checking Cluster State...done
This system is part of a cluster which has not been prepared to do a
rolling patch installation or deletion. Do you wish to perform this
patch operation cluster-wide without using the rolling-patch mechanism?
Please answer y or n ? [y/n]:
If you choose y, dupatch proceeds by allowing you to do the analysis and selection of
patches to be installed or removed, after which the whole cluster is brought down to init
level 2 via an Event Management System event.
If you are using dupatch from the command line and do not specify the -proceed option,
you will need to press Return in order to transition the cluster from level 3 to level 2. If the
-proceed option was set, the transition will occur automatically.
After dupatch completes its patch analysis, it will perform the patch operation on the member
on which you ran dupatch. After the patches are installed or removed, dupatch will issue a
second event to the remaining cluster members that will instruct them to complete their patch
operations in parallel.
The dupatch utility then waits a calculated time-out period for all the other cluster members
to complete their operations. The time-out period is based on the time it took to perform the
patch operation on the member running dupatch.
After the patch operation is completed on all other cluster members, dupatch will complete the
procedure on the member on which the dupatch command was issued.
If a cluster member times out or encounters an error, dupatch will report the problem, suspend
the process, and send you a message to check the problematic member in order to resolve the
problem. Once dupatch has resumed, it will complete the patch process on the rest of the cluster.
If a cluster member is known to be down when you issue the dupatch command, an /sbin/it
job will be posted for the member to run the cluster patch script upon reboot. (For more
information, see the it(8) reference page.)
Because all patches currently require a reboot, the whole cluster will reboot after all the members
report back.
74 Patching a Cluster