Ignite-UX (IUX) Document for Frequently Asked Questions (FAQ) (762793-001, March 2014) (Edition: 3)

Why do the iux_postconfig scripts associated with EMS KRM sometimes fail?
On some HP-UX 11.x clients you might encounter the following errors when recovering a client
from a make_net_recovery or make_tape_recovery tape, or a make_net_recovery
image:
Executing:
"/var/adm/sw/products/EMS-KRMonitor/KRMON-RUN/iux_postconfig".
ERROR: Cannot install a dlkm driver.
ERROR: Cannot configure a dlkm driver.
ERROR: The script:
"/var/adm/sw/products/EMS-KRMonitor/KRMON-RUN/iux_postconfig"
failed, exit code was 1.
The reason for this is when the recovery archive was created, the kernel which the client was
running was not created correctly (the DLKM information was out of sync). You must use kmupdate
to move a new kernel into place after creating it with mk_kernel. This will move the DLKM
information into place when the new vmunix is moved into place at the next shutdown.
To solve this problem, create a kernel in the way described above. Then, recreate the recovery
tape or network recovery archive. This message must not appear next time you use the new tape
or network recovery archive (the old tape or network recovery archive will always show this
problem).
Can I run make_net_recovery from a PA-RISC server to create an archive for an
Itanium-based client or vice versa?
Yes
Why does installing or recovering a client via NFS from an HP-UX 11i v1 Ignite-UX
server take so long compared to an 11.00 server?
To answer this, we need to look at some background before considering the available options for
resolving this issue.
If you use 100BT or 1000BT interfaces, you must check the duplex setting of the port on the switch
that the Ignite-UX client is connected to. When a client boots, the kernel driver automatically
negotiates the speed and duplex settings of 100BT and 1000BT interfaces.
If auto-negotiation fails, the interface defaults to half-duplex (the speed may vary depending on
the speed of the switch port). When a normal client boots, its startup scripts are used to change
the interface speed and duplex values to match that of the switch port. If the switch port is set to
full duplex, you will have a duplex mismatch.
This causes a problem for interfaces connected to switches that have not been set to auto-negotiate.
These interfaces will run at half duplex for the duration of the installation. From observation, the
duplex value reduces the throughput that NFS over TCP can achieve, but NFS over UDP performance
does not seem to suffer.
Ignite-UX uses an 11i installation kernel with versions Ignite-UX B.3.x, so if the Ignite-UX server is
an 11i system the transport for NFS will be TCP and performance will suffer. HP-UX 11.00 is only
transported via UDP for NFS by default, so the performance problems are not seen. There are
several solutions available:
1. Change the switch duplex setting of the client being installed to auto-negotiate for the duration
of the installation.
2. Change the _hp_nfs_mount_opts in the INSTALLFS to force UDP to be used as the
protocol. For example:
Frequently asked questions 11