HP Tru64 UNIX and TruCluster Server Version 5.1B-6 Patch Summary and Release Notes

# /sbin/showfdmn domain_name
Id Date Created LogPgs Version Domain Name
447350cd.000eba90 Tue May 23 11:13:33 2006 512 4 domain_name
Vol 512-Blks Free % Used Cmode Rblks Wblks Vol Name
1L 71132000 71121632 0% on 256 256 /dev/disk/dsk4c
Use the showfile command to determine if an RBMT file has more than one page. To do this,
select any mounted fileset from the domain in question, find the mount point for the fileset, and
enter the following command. (Note that .tags/M-6 represents volume 1. Subsequent volumes
are incremented by a factor of six, so that volume 2 uses .tags/M-12, volume 3 uses
.tags/M-18, and so on.) For example:
# /usr/sbin/showfile mountpoint/.tags/M-6
Id Vol PgSz Pages XtntType Segs SegSz I/O Perf File
fffffffa.0000 1 16 1 simple ** ** ftx 100% M-6
See the fixfdmn(8), showfile(8), and showfile(8) reference pages for information about using these
commands.
Possible Errors Seen After Kit Installation
The following problems have been known to occur after Version 5.1B-4 or higher has been
installed:
• The Common Data Security Architecture (CDSA), IP Security Protocol (IPsec), or Single
Sign-On (SSO) do not work.
• The following error message is displayed during boot time:
CSSM_ModuleLoad: CSSM error 4107
If you experience these problems, make sure that the following command line has been executed:
# /usr/sbin/cdsa/mod_install -f -i -s \
/usr/lib/cdsa/libt64csp.so -d /usr/lib/cdsa/
Message Seen During Reboot Can Be Ignored
The following error message will be displayed after you reboot your system the first time after
installing Version 5.1B-4 or higher:
AllowCshrcSourcingWithSubsystems is not valid
ForcePTTYAllocation is not valid
IdentityFile is not valid
AuthorizationFile is not valid
These messages are caused by a new version of SSH included in Version 5.1B-4 or higher. They
do not pose a problem and can be ignored.
Kit Removal Release Notes
The following sections describe actions you have to take if you decided to uninstall Version
5.1B-4 or higher. Read each section before running the patch deletion procedure.
Some Patch Kits Cannot Be Removed
You cannot remove a patch kit on systems that have New Hardware Delivery 7 (NHD-7) kit
installed when either of the following conditions exist:
• The patch kit you want to remove was installed before the NHD (New Hardware Delivery)
kit.
For example, if you installed Patch Kit 2 and then installed NHD-7, you cannot remove that
patch kit. However, if you later installed Patch Kit 4, you can remove that patch kit.
• The patch kit was installed with NHD-7.
Beginning with the release of Patch Kit 3, patch kits were incorporated into the NHD-7 kits.
As a result, when you installed NHD-7, you automatically installed the current patch kit.
18 Kit Installation and Removal