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

# sysman -clone -apply -force config.cdf
For more information, see the note titled Correction to Configuration Cloning Restrictions in the
“Corrections to Manuals” section of the online Technical Updates document for Version 5.1B.
The following link will take you to the Technical Updates document:
http://h30097.www3.hp.com/docs/updates/V51B/html/index.html
2.2.1.6 Run ipsec Command After Installing Kit (new)
If you are running IP Security (ipsec) on your system, run the following command after installing
this kit to determine if any unsafe connections exist:
# /usr/sbin/sysman ipsec
A warning message will alert you to any potential problems.
2.2.1.7 Procedure to Update lprsetup.dat File (new)
If you use the /usr/sbin/printconfig application to configure printer queues, run the
following command as root to update the /etc/lprsetup.dat file:
# /usr/sbin/lprsetup -c update
2.2.1.8 AdvFS Domain Differences May Affect Version Upgrades (new)
A difference in the structure of Version 5.1A and early 5.1B AdvFS domains verses later V5.1B
domains can cause a problem when upgrading to Version 5.1B-4.
This potential problem involves a metadata file called the RBMT that exists on each volume of
a version 4 domain.
Although an RBMT is generally only one page long, it can be longer on large volumes or domains
that have many files. If an RBMT file was larger than one page long under 5.1A or an early 5.1B
version and then grows again after a system upgrade to 5.1B-4, the RBMT file can cause a problem
in which any command that tries to activate that domain will fail. This includes mounting filesets
from the affected domain.
Following a system upgrade to Version 5.1B-4, the problem can occur after all the filesets in a
domain are unmounted. (The problem will not occur as long as the filesets remain mounted.)
The solution is to use the fixfdmn utility to correct the problem. For example:
# /sbin/advfs/fixfdmn domain_name
fixfdmn: Checking the RBMT.
fixfdmn: Clearing the log on volume /dev/disk/dsk10c.
fixfdmn: Checking the BMT mcell data.
fixfdmn: Checking the deferred delete list.
fixfdmn: Checking the root tag file.
fixfdmn: Checking the tag file(s).
fixfdmn: Checking the mcell nodes.
fixfdmn: Checking the BMT chains.
fixfdmn: Checking the frag file group headers.
fixfdmn: Checking for frag overlaps.
fixfdmn: Checking for BMT mcell orphans.
fixfdmn: Checking for file overlaps.
fixfdmn: Checking the directories.
fixfdmn: Checking the frag file(s).
fixfdmn: Checking the quota files.
fixfdmn: Checking the SBM.
fixfdmn: Completed.
You can use this command proactively before the RBMT grows to prevent the problem from
occurring or you can use it after the problem occurs.
2.2 Important Kit Installation and Removal Release Notes 35