HP Tru64 UNIX and TruCluster Server Version 5.1.B-4 Patch Summary and Release Notes (13156)

ideally, you must first remove the CSP using dupatch.
Before performing this action, you should contact your
HP Service Representative to determine if this patch kit
contains the CSP. If it does not, you may need to obtain a new
CSP from HP in order to install the patch kit and retain the
CSP fix. Or, you may use dupatch baselining to enable the
patch installation.
The recommended action is to perform dupatch baselining on your existing system to enable
the patch installation process and retain the CSP on your system. Removing the CSP (as mentioned
in message) could eliminate the fixes made by that CSP.
After running the baselining process on your existing system, you will need to begin the cloning
process from the beginning by reduplicating your system on an alternate set of disks and
rerunning the dupatch cloning process. See the Patch Kit Installation Instructions for information
about performing baselining and on the patch cloning process.
2.2.3.3 Migrating a Patched Standalone System to a Cluster (new)
Installing only the base patches on a non-cluster system omits various patches (including some
security patches) because of dependencies on TruCluster Server patches. Such patches are not
needed in standalone systems. However, if the standalone system is then clustered using the
clu_create command and you attempt to apply the cluster patches, many patches will fail
with errors because various prerequisite patches failed.
These errors do not necessarily indicate that the patch process has failed, but they are numerous,
can be confusing and might obscure genuine errors.
The preferred procedure for adding a standalone system into a cluster is as follows:
1. Reinstall the operating system on the standalone system.
2. Run the clu_create command and bring the standalone system as a cluster node.
3. Apply all base and cluster patches.
2.2.3.4 Disable vfast Utility if Running On Cluster Domains (new)
If the vfast utility is running on the TruCluster domains cluster_root and cluster_var,
deactivate it on the domains before installing or removing this kit. To deactivate vfast on the
two domains, use the following command:
# vfast deactivate cluster_root
# vfast deactivate cluster_var
See the vfast(8) reference page for more information.
2.2.3.5 Creation of Some MFS File Systems Depends on Version Switch (new)
During the installation of this kit, MFS file systems that are 4 GB and larger (or 2 GB and larger
if a 1024-byte sector size is used) cannot be created until after the version switch is thrown. (See
the Patch Kit Installation Instructions for information about the version switch.)
2.2.3.6 Workaround Saves Files to Allow Patch Kit Removal (new)
If you upgrade the operating system and install a patch kit within the same roll, the contents of
the patch backups are inadvertently removed. The result is that the patches most recently installed
cannot be removed because the backups are missing.
The following procedure saves then restores backups so they will be available if you later decided
to remove the patch kit:
1. Create backup files of the /backup and /doc directories after the postinstall step
(clu_upgrade postinstall) as follows:
2.2 Important Kit Installation and Removal Release Notes 39