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

subset name. For example, TruCluster software subset names start with the TruCluster
software three-letter product code: TCRBASE510, TCRMAN510, and TCRMIGRATE510.)
• By default, files that are associated with other layered products do not have tagged files
created for them. Tagged files are created only for layered products that have been modified
to support tagged files during a rolling upgrade.
Caution:
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.
The clu_upgrade command provides several tagged command options to manipulate tagged
files: check, add, remove, enable, and disable. When dealing with tagged files, take the
following into consideration:
• During a normal rolling upgrade you do not have to manually add or remove tagged files.
The clu_upgrade command calls the tagged commands as needed to control the creation
and removal of tagged files.
• If you run a clu_upgrade tagged command, run the check, add, and remove
commands on a member that is not running on tagged files; for example, the lead member.
You can run the disable and enable commands on any member.
• The target for a check, add, or remove tagged file operation is a product code that represents
an entire product. The clu_upgrade tagged commands operate on all inventory files for
the specified product or products. For example, the following command verifies the
correctness of all the tagged files created for the TCR kernel layered product (the TruCluster
software subsets):
# clu_upgrade tagged check TCR
If you inadvertently remove a .Old.. copy of a file, you must create tagged files for the
entire layered product to re-create that one file. For example, the vdump command is in the
OSFADVFSxxx subset, which is part of the OSF product. If you mistakenly remove /sbin/
.Old..vdump, run the following command to re-create tagged files for the entire layered
product:
# clu_upgrade tagged add OSF
• The enable and disable commands enable or disable the use of tagged files by a cluster
member. You do not have to use enable or disable during a normal rolling upgrade.
The disable command is useful if you have to undo the setup stage. Because no members
can be running with tagged files when undoing the setup stage, you can use the disable
command to disable tagged files on any cluster member that is currently running on tagged
files. For example, to disable tagged files for a member whose ID is 3:
# clu_upgrade tagged disable 3
The enable command is provided in case you make a mistake with the disable command.
Version Switch
A version switch manages the transition of the active version to the new version of an operating
system. The active version is the one that is currently in use. The purpose of a version switch in
a cluster is to prevent the introduction of potentially incompatible new features until all members
have been updated. For example, if a new version introduces a change to a kernel structure that
is incompatible with the current structure, you do not want cluster members to use the new
structure until all members have updated to the version that supports it.
70 Patching a Cluster