The following notes provide important information you need to be aware of before installing the Version 5.1B-4 kit.
3-1-1 Presence of Some Insight Management Agents Kits Might Require Additional Steps |
 |
The following installation-related release notes pertain to the Insight Management Agents. See “Insight Manager Components Dump Core” for information about a potential problem with Insight Management Agents that can occur after Version 5.1B-4 is installed.
3-1-1-1 Obtain the Latest Kit from the Web
After Installing Version 5.1B-4, HP recommends that you download the most current version of the Insight Management Agents kit available. You can find the kit at the following site:
http://h30097.www3.hp.com/manage/index.html
3-1-1-2 Some Insight Management Agents Kits Might Prevent V5.1B-4 Installation
Under certain conditions, you will be prevented from installing Version 5.1B-4 if you are running HP Insight Management Agents Version 3.1 or higher or a version of the kit was previously installed. Those conditions are as follows:
Your system contains a pre-Version 5.1B-4 kit and the Insight Management Agents kit.
In this case, upgrading to this kit gives the following error message:
Patch 26020.00 - SP04 OSFCLINET540 (SSRT3653 SSRT2384 SSRT2275 ...)
./sbin/init.d/snmpd: its origin can not be identified.
This patch will not be installed. |
Your system contains Patch Kit 2, Patch Kit 3, or Patch Kit 4 and the Insight Management Agents kit was once installed but has since been removed.
In this case, upgrading to Version 5.1B-4 gives the following error message:
Patch 26020.00 - SP04 OSFCLINET540 (SSRT3653 SSRT2384 SSRT2275...)
./etc/pmgrd_iorate.config: does not exist on your system,
however, it is in the inventory of installed subsets.
This patch will not be installed. |
To work around this problem, run the dupatch baseline process before installing Version 5.1B-4. The following steps will guide you through the process:
Make a backup copy of the /sbin/init.d/snmpd script. For example:
# cp /sbin/init.d/snmpd /tmp |
An alternative to backing up this file, in which you manually modify it, is provided following step 7.
Run the Version 5.1B-4 dupatch utility and select Option 5, Patch Baseline Analysis/Adjustment. See the Patch Kit Installation Instructions for detailed instructions.
After Phase 5 of the baseline procedure, answer y to the following question:
Do you want to enable the installation of any of these patches? [y/n]: y |
Phase 5 reports patches that do not pass installation applicability tests due to the current state of your system. The installation of Patch 26020.00 was prevented because of changed system files. The dupatch utility reports the known information about the files contained in each patch and asks if you want to enable the installation. Answering yes enables dupatch to install patches that were prevented from being installed due to unknown files.
Install Version 5.1B-4.
After the system is running with Version 5.1B-4 installed, stop the snmpd and insightd daemons as follows:
# /sbin/init.d/snmpd stop
# /sbin/init.d/insightd stop |
Replace the /sbin/init.d/snmpd script with the one you copied in step 1; for example:
# cp /tmp/snmpd /sbin/init.d/snmpd |
Start the snmpd and insightd daemons as follows:
# /sbin/init.d/snmpd start
# /sbin/init.d/insightd start |
If you did not back up the /sbin/init.d/snmpd file in step 1, you can modify it after you install Version 5.1B-4 (step 4) and stop the snmpd and insightd daemons (step 5) as follows (the XXX represents the revision, such as CPQ360):
Edit the line that reads CPQMIBS=/usr/sbin/cpq_mibs as follows:
CPQMIBS=/var/opt/CPQIMXXX/bin/cpq_mibs |
Edit the line that reads PMGRD=/usr/sbin/pmgrd as follows:
PMGRD=/var/opt/CPQIMXXX/bin/pmgrd |
Edit the line that reads $PMGRD > /dev/console 2>&1 & as follows:
$PMGRD `$RCMGR get PMGRD_FLAGS` > /dev/console 2>&1 & |
3-1-1-3 V5.1B-4 Installation Might Overwrite snmpd File
When you install a newer version of the Insight Management Agents kit, the paths to the cpq_mibs and pmgrd subagents are changed in the snmpd script. By installing Version 5.1B-4, the snmpd script is replaced by the original version provided in the base version of the Insight Management Agents kit.
Because the use of the snmpd script causes problems when you use Insight Manager, you must restore the script to the latest version. To do this, create a backup file of the snmpd script, and restore the backup version after installing V5.1B-4. (See step 1 of the workaround described in “Some Insight Management Agents Kits Might Prevent V5.1B-4 Installation.”)
If you did not back up the snmpd file before installing V5.1B-4, you can modify the file after the installation, as described in “Some Insight Management Agents Kits Might Prevent V5.1B-4 Installation.”
3-1-2 Stop sendmail Before Installing Kit |
|
Stop the sendmail mailer daemon before installing this kit. Failing to do so can lead to the loss of queued mail. Lost mail cannot be recovered.
To stop the daemon, enter the following command:
# /sbin/init.d/sendmail stop |
3-1-3 Run Commands on BIND Systems After Kit Installation |
|
After installing this kit on a system configured to be BIND server, run the following command:
# rcmgr set BIND_SERVERARGS "-c /etc/namedb/named.conf" |
On a cluster configured to be a BIND server, run the following command:
# rcmgr -c set BIND_SERVERARGS "-c /etc/namedb/named.conf" |
Stop the named daemon and restart it in order to have the new named daemon take effect:
For standalone systems:
# /sbin/init.d/named stop
# /sbin/init.d/named start |
For clusters:
# /sbin/init.d/named cluster_stop
# /sbin/init.d/named start |
To verify that your configuration files are compatible with Bind 9, run the following commands:
# named-checkconf /etc/namedb/named.conf
# named-checkzone example.com /etc/namedb/hosts.db |
|
| |
|
 | NOTE: With BIND 9, CNAME entries no longer accept quotes. For example, "hosts-1" IN CNAME A needs to be changed to hosts-1 IN CNAME A. |
|
| |
|
See “BIND Updated to Version 9.2.5 ” for information about BIND 9.
3-1-4 inetd Daemon Restart Required |
|
Because of changes made to the Internet services daemon introduced in this release, you need to stop and then restart inetd after installing or removing this kit. You can do this from the command line or by using the sysman application. From the command line, enter the following commands:
# /sbin/init.d/inetd stop
# /sbin/init.d/inetd start |
Failure to do this results in an older version of inetd running on your system.
3-1-5 Kit Installation Causes Configuration File Restoration Failure |
|
After installing this kit, attempts to restore the configuration file (config.cdf) saved prior to the installation of this patch will fail due to a checksum error. You can, however, force the operation by using the following sysman command:
# 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 takes you to the Technical Updates document:
http://h30097.www3.hp.com/docs/updates/V51B/html/index.html
3-1-6 Run ipsec Command After Installing Kit |
|
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:
A warning message alerts you to potential problems.
3-1-7 Update lprsetup.dat File When Using printconfg |
|
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 |
3-1-8 AdvFS Domain Differences Can Affect Version Upgrades |
|
A difference in the structure of Version 5.1A and early 5.1B AdvFS domains versus 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 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 any command that tries to activate that domain to 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 does 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.
In summary, the following domains are not in danger:
Domains created under Version 5.1B-4
Domains with RBMT files that are not longer than one page
The showfile and showdmn commands can provide information about your domains.
Use the showdmn command to find out what volumes a domain has. For example:
# /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.
3-1-9 Possible Errors Seen After Kit Installation |
|
The following problems have been known to occur after Version 5.1B-4 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/ |
3-1-10 Message Seen During Reboot Can Be Ignored |
|
The following error message is displayed after you reboot your system the first time after installing Version 5.1B-4:
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. They do not pose a problem and can be ignored.
Printable version
