Ignite-UX release notes HP-UX 11iv1, HP-UX 11iv2 and HP-UX 11iv3 (5900-2307, April 2012)

6 Known Problems and Workarounds
This section describes known problems with the Ignite-UX product as well as workarounds to these
problems. More detail is often available in the FAQ available from: http://www.hp.com/go/
ignite-ux.
Required Patches
Patch PHCO_31903, s700_800 B.11.11 libc cumulative patch, is required for the correct execution
of list_expander on B.11.11 systems, and patch PHKL_31500 is required on B.11.23 systems
that are running B.11.23 September 2004 or later.
These patches supply a fix for nftw that stops it from running stat on symlinks. In an automounter
situation if there is a nonresponding NFS file system, it causes list_expander to hang on any symlink
pointing into it. The defect was not in libc.1, only in libc.2 from B.11.11 onwards.
When creating a system archive via make_sys_image or make_net_recovery, the pax utility
is used. You should install the latest patch for pax on the machine(s) where you will be creating
your archive and generating disk space impacts.
The patch numbers are:
B.11.11: PHCO_35998 s700_800 11.11 pax(1) cumulative patch
B.11.23: PHCO_39677 s700_800 11.23 Cumulative changes to pax(1)
B.11.31: PHCO_38835 11.31 pax(1) cumulative patch
If you wish to use the pax format of the pax command with make_sys_image,
make_net_recovery or make_net_recovery on B.11.23, then you will also need the PAX-Enh
product installed on the client system you intend to create the archive for.
• When creating large system archives (greater than 2 GB) over an NFS mount (which is the
case when using make_net_recovery), both the client and server must be capable of NFS
PV3. All currently supported HP-UX releases support NFS PV3.
• When an Ignite-UX server's IP address is changed via set_parms, it is desirable for the
default install server information set by instl_adm (in the install kernels) to be changed to
reflect the server's new IP address. This functionality is enabled by patches PHCO_34837
(B.11.11) and PHCO_34838 (B.11.23).
General Issues
• If an installation does not seem to be making progress after a reasonable amount of time (the
log file is not getting updated); check the client console. There are some cases where errors
are not written to the log file, but are displayed on the console. Normally, the log file should
be updated every few minutes. The only known exception is when a large archive is being
extracted.
• Ignite-UX can sometimes assign the "wrong" swap volume to be "primary". If you set up a
primary swap-only volume, and then set up a large swap/dump volume, the swap/dump
volume can become the primary swap volume. This is done to ensure the dump volume is
within the first 2 GB boundary of the disk. A future version of Ignite-UX will likely add the
ability to specify which swap volume is primary, in addition to the ability to specify swap
priorities for each swap volume.
• If you set some of the "final" system parameters (also known as set_parms information), but
not all of them, your system will come up, but will not automatically run set_parms and you
will have to take explicit action to enter the new data.
The most common case is when you have entered the final host name and IP, but have not
yet entered the time zone or root password.
26 Known Problems and Workarounds