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

At the start of a rolling upgrade, each member's active version is the same as its new version.
When a member rolls, its new version is updated. After all members have rolled, the switch stage
sets the active version to the new version on all members. At the completion of the upgrade, all
members' active versions are again the same as their new versions. The following simple example
uses an active version of 1 and a new version of 2 to illustrate the version transitions during a
rolling upgrade:
All members at start of roll: active (1) = new (1)
Each member after its roll: active (1) != new (2)
All members after switch stage: active (2) = new (2)
The clu_upgrade command uses the versw command, which is described in versw(8), to
manage version transitions. The clu_upgrade command manages all the version switch activity
when rolling individual members. In the switch stage, after all members have rolled, the following
command completes the transition to the new software:
# clu_upgrade switch
Rolling Upgrade and Layered Products
This section discusses the interaction of layered products and rolling upgrades:
• General guidelines (“General Guidelines”)
• Blocking layered products (“Blocking Layered Products”)
General Guidelines
The clu_upgrade setup command prepares a cluster for a rolling upgrade of the operating
system. Do not use the setld command to load software onto the cluster between performing
the clu_upgrade setup command and rolling the first cluster member to the new version. If
you install software between performing the clu_upgrade setup command and rolling a
cluster member to the new version, the new files will not have been processed by clu_upgrade
setup. As a result, when you roll the first cluster member, these new files will be overwritten.
If you must load software:
• Wait until at least one member has rolled.
• Install the software on a member that has rolled.
Blocking Layered Products
A blocking layered product is a product that prevents the installupdate command from
completing. Blocking layered products must be removed from the cluster before starting a rolling
upgrade that will include running the installupdate command. You do not have to remove
blocking layered products when performing a rolling upgrade solely to patch the cluster or install
an NHD kit.
Table 4-6 “Blocking Layered Products” lists blocking layered products for this release.
Table 4-6 Blocking Layered Products
DescriptionProduct Code
Open3D3X0
Open3D4DT
Atom Advanced Developers KitATM
Distributed Computing EnvironmentDCE
DECnetDNA
Developer's Toolkit (Program Analysis Tools)DTA
Developer's Toolkit (C compiler)DTC
Rolling Upgrade 71