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

# 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 required 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 using the same commands as in option
2. An example of what you need to add to include a 100BT LAN interface into 100 full duplex
mode would be:
(lan[].driver == "btlan")
{
_hp_lanadmin_args="-X 100FD"
}
For more information about the admin options, see lanadmin(1M).
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 uses the
_hp_lanadmin_args settings on the network interface you are using for installation. (Errors
occur if the lanadmin options you have provided are not applicable to that interface.)
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?
This is a known issue with Ignite-UX and VxVM installations involving disk group names that were
used on disks in a prior installation though not in the current installation.
Be careful when creating extra VxVM disk groups other than rootdg via the Ignite-UX GUI. During
installation, no validation is done on a disk group name to see if it conflicts with a disk group name
already in use for another unused disk on the system. If the name conflicts with another disk group,
the attempt to create a disk group of the same name fails. This is a feature of VxVM to prevent the
creation of duplicate disk groups. If you do encounter this problem, you are presented with
something like the following:
* Starting VxVM
* Creating VxVM Disk "c17t13d0" (1/0/12/0/0/4/1.13.0).
* Creating VxVM Disk "c17t12d0" (1/0/12/0/0/4/1.12.0).
* Creating VxVM Disk "c17t11d0" (1/0/12/0/0/4/1.11.0).
* Creating VxVM Disk "c17t10d0" (1/0/12/0/0/4/1.10.0).
* Adding disk "c17t10d0" to rootdg.
* Enabling VxVM
* Creating disk group "dg01".
* Creating disk group "dg02".
vxvm:vxdg:
12 Known problems