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

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 only used
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
autonegotiate 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:
# instl_adm -d -F /opt/ignite/boot/INSTALLFS > /tmp/installfs.out
Edit /tmp/installfs.out to add the following line:
_hp_nfs_mount_opts="-oproto=udp"
(or change the _hp_nfs_mount_opts variable if it already exists to
add -oproto=udp) then save the changes back into the INSTALLFS
after saving the file:
# instl_adm -F /opt/ignite/boot/INSTALLFS -f /tmp/installfs.out
3. Ignite-UX provides the libraries needed to use the lanadmin -X
option with 100BT and 1000BT interfaces. You can add the lanadmin
options to be applied to a LAN interface with the
_hp_lanadmin_args variable in the INSTALLFS use the same commands
as in option 2. An example of what you would need to add to put a
100BT LAN interface into 100 full duplex mode would be:
(lan[].driver == "btlan")
{
_hp_lanadmin_args="-X 100FD"
}
Please consult the documentation for lanadmin(1M) for more
information about the options that are available.
Note: If the Ignite-UX server is multi-homed and connected to one or
more non-ethernet networking technologies over which it provides
Ignite-UX installation/recovery services, Ignite-UX will attempt to
use the _hp_lanadmin_args settings on the network interface you are
using for installation. (You will see errors from lanadmin if the
options you have provided are not applicable to that interface.)
=============================================================================
==
1.10
Q: My VxVM installation has stopped with the message: ERROR: Disk
group dg02:cannot create: Disk group exists and is imported. What
is the problem and how can I resolve it?
A: This is a known issue with Ignite-UX and VxVM installations involving
disk group names that were used on disks in a prior installation