Known Problems Discovered in this Release

Visual Conference Product Does Not Install or Update with CD Media

On the latest release of HP-UX11i v1, a checkinstall script error causes the Visual Conference product to be excluded from the TCOE operating environment.

How Do You Know If This Affects You?

If you are installing or updating to the June 2004 TCOE operating environment from CD media (not DVD) you will be affected.

What To Do

You must resinstall the Visual Conference product after you’ve completed your cold install or update using swinstall.

PHSS_29731 X/Motif Runtime Periodic Patch Could Not Be Installed

During a cold install or update, you may encounter the following warning:

WARNING: [140394] The patch ‘PHSS_29731, l=/, r=1.0’ contains some filesets which
are superseded and some filesets which are not superseded. The superseding patch
may be incorrect or may need to be reapplied.

This warning is caused by the following bundles being installed during the same session:

What To Do

Patch PHSS_29371 must be reinstalled.

vPars™ version A.02.03 Required for rp7405, rp7410 and rp8400 Servers with PDC Firmware Version 17.005

If you received an rp7405, rp7410 or rp8400 server with PDC firmware version 17.005 (overall firmware version 6.0), and you intend to use Virtual Partitions (vPars), you must obtain vPars version A.02.03. This latest version of vPars addresses compatibility issues with PDC firmware version 17.005.

rp7405, rp7410 and rp8400 servers shipped from the factory on or after September 5, 2003 have PDC version 17.005 installed. Otherwise, to determine if you are using this PDC firmware version, see “How to Verify Your Firmware Version”.

PDC firmware version 17.005 is required to support the latest PCI and PCI-X I/O cards.

If you have any questions, please contact your Customer Support Engineer for additional details and information.

EMS checkinstall Script Fails When Updating From HP-UX 11.0 to HP-UX 11i v1

During an update from HP-UX 11.0 to HP-UX 11i v1, you may encounter the following warning message:

* [20255] Running "checkinstall" script for fileset
"EMS-Core.EMS-CORE".
touch: /etc/opt/resmon/monitors/ems_sys_update cannot create

How Do You Know if This Affects You

You will encounter this warning if EMS was not installed on your HP-UX 11.0 system. The /etc/opt/resmon/monitors/ems_sys_update flag file is required to ensure that earlier versions of the EMS p_client do not attempt to link to newer EMS libraries during an update, causing a core dump.

What To Do

You can safely disregard the warning.

EMS May Fail on IPv4 Systems

The latest release of EMS (A.04.00) has been enabled to support IPv6 on HP-UX 11i v1. The EMS client may fail or produce a core dump if you attempt to run on an IPv4 system.

What To Do

To resolve this problem, you will need to change the following entry in your inetd.conf file:

registrar stream tcp6 nowait root
/etc/opt/resmon/lbin/registrar
/etc/opt/resmon/lbin/registrar

with:

registrar stream tcp nowait root
/etc/opt/resmon/lbin/registrar
/etc/opt/resmon/lbin/registrar

Problems Reading HP-UX 11i v1 DVD Media

The HP-UX 11i v1 DVD media contain large volumes of data that may cause your DVD device to fail while reading the DVD media contents during an update. This particularly affects you if you use Update-UX or other Software Distributor (SD) tools. For example, you may encounter similar error messages if you attempt to read DVD media with a large volume of data from Update-UX:

ERROR: File "/dvd/catalog/SOE/SOE.2/INFO": No such file or
directory(2). Cannot copy it to file 
"/var/tmp/BAAa04482/catalog/SOE/SOE.2/INFO". 
 
ERROR: File "/var/tmp/BAAa04482/catalog/SOE/SOE.2/INFO" does
not exist. 
 
ERROR: The catalog files for product "SOE,r=B.11.11" failed to
load. Check the above output for details. 
 
ERROR: Cannot continue the Analysis Phase until the previous
errors are corrected. 

To resolve this problem, do one of the following:

To patch your system use the following patches (patch descriptions are in parenthesis) for your current OS version:

	NOTE: The HP-UX 11i v1 patches listed below are included in the December 2003 (and later) version of the HP-UX 11i v1 install kernel. If you are planning to cold-install HP-UX 11i v1 (December 2003 or later), you do not need to install these patches, nor do you need to use the pfs_mount(1M) command to mount the DVD.

For Systems Currently Running HP-UX 11i v1: 

For Systems Currently Running HP-UX 11.0: 

For Systems Currently Running HP-UX 10.20: There are no patches available. Use the pfs_mount(1M) command to mount the DVD and update to HP-UX 11i v1.

Determining If You Need to Install the Patches. To determine if your system already has the listed patches installed, run the following:

/usr/sbin/swlist -l patch | grep <patch_name>

where <patch_name> is one of the patches listed above for your operating system version. If nothing is printed to standard output, you need to install the patches from one of the following sources:

Ignore Warning Message When Installing PHCO_29566

The patch PHCO_29566 and dependent patches enable attention buttons (also known as Doorbells) for PCI OLAR operations on HP-UX 11i v1 servers. When you install this patch on systems with no OLAR capability, it issues a warning message during the patch installation. If you see the following warning message in the swagent.log file, you can safely ignore it.

* Installing fileset "PHCO_29566.UX-CORE,r=1.0" (79 of 102).
Creating OLA/R device node at major 5...
Note that this system must have OLA/R capable hardware 
and firmware for these features to be enabled. 
 
WARNING: OLA/R capabilities not supported on this platform
WARNING: The "postinstall" script for "PHCO_29566" had a
         warning (exit    code "2"). The script location was
"/var/tmp/BAAa05060/catalog/PHCO_29566/pfiles/postinstall"

PHCO_29566 is found the December 2003 HWEnable11i (B.11.11.0312.4) bundle.

xntpd Fails to Start on Reboot After Installing GOLDQPK11i Patch Bundle

After installing the GOLDQPK11i patch bundle, xntpd may fail to start after the initial reboot of the system.

How Do You Know If This Affects You

In your syslog.log file, you may encounter a similar message:

Sep 23 14:46:23 <system_name> xntpd[1812]: tickadj = 625, tick = 10000, 
tvu_maxslew = 6
1875
 
Sep 23 14:46:23 <system_name> xntpd[1812]: precision = 6 usec
Sep 23 14:46:23 <system_name> xntpd[1812]: bind() fd 4, family 2, port 123, 
addr 000000
00, in_classd=0 flags=1 fails: Address already in use

Additionally, you might find a similar message in your rc.log file:

Start time synchronization
Output from ‘/sbin/rc2.d/S660xntpd start’:
----------------------------
23 Sep 14:46:23 ntpdate[1810]: the NTP socket is in use,
exiting xntpd

What To Do

To resolve this problem: