Ignite-UX (IUX) Frequently Asked Questions (July 2013)

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 the client was running was not created correctly (the DLKM
information was out of sync). You should always 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. You
should not see this message the next time you use the new tape or
network recovery archive (the old tape or network recovery archive
will always show this problem).
=============================================================================
==
1.8
Q: Can I run make_net_recovery from a PA-RISC server to create an
archive for an Itanium-based client or vice versa?
A: Yes
=============================================================================
==
1.9
Q: 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?
A: To answer this we need to look at some background before looking at
what options are available 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 autonegotiation 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 autonegotiate. 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,