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

======= 06/21/13 09:05:29 EDT Starting system configuration...
* Configure_Disks: Begin
* Will install B.11.31 onto this system.
#
If you were installing it from physical or virtual DVD media
previously, a possible workaround is to use Ignite-UX server for
installing the client. HP recommends you to try this workaround,
though it might not be always successful.
For getting the latest ISO images, contact HP Support Center.
Mention that fixed HP-UX 1303 OE ISO images must be provided.
=============================================================================
==
----------------------------------------
2. Server Setup
----------------------------------------
2.1
Q: Should I use DHCP or bootp?
A: As with anything, there are some advantages and disadvantages to both
BOOTP and DHCP. In general, DHCP allows you to specify more complete
networking information. However, there are no really good tools to
manage the database so that you can enforce the LLA <-> IP-address
mapping ahead of time. By its very design, DHCP dynamically
allocates addresses.
You will probably want to use the Ignite-UX GUI to set up the range
of IP addresses that you will want your server to manage with DHCP,
if you have not already done so. You need to use SAM to make any
future changes to the DHCP address pool.
If you are dealing with multiple subnets you will either need to have
one DHCP server on each subnet or set up bootp relay agents.
See question 5.4 (I do not want to use DHCP, can I still have
Ignite-UX automatically determine networking information for all my
clients?) also.
=============================================================================
==
2.2
Q: Why did it call my client "<hostname>.0x080009...."?
A: If your client has multiple LAN interfaces, and you have previously
installed the client using one interface, and then later chose to use
the other interface during the installation, then the client name
will have the LLA (link-level address) appended to the host name so
that it does not conflict with the prior host name left from the
prior installation.
This may also happen if you had to replace the LAN interface in your
client since the last time you installed it. The LLA number is
attached to the LAN interface, not the client.
It is only the name of the icon that has been renamed. You can use
the Ignite-UX GUI "Action" menu to "Change icon name" to rename one