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

3 Server setup
Frequently asked questions
Following are the frequently asked questions for setting the server, which is a compilation of all
the available feedback from the users.
Should I use DHCP or bootp?
There are some advantages and disadvantages to both DHCP and bootp. In general, DHCP allows
you to specify more complete networking information. However, there are no 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.
In case you want to use the Ignite-UX GUI to set up the range of IP addresses which the server must
manage with DHCP (If you have not already set the range). You must 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 6.4 “I do not want to use DHCP, can I still have Ignite-UX automatically determine
networking information for all my clients?” (page 26) also.
Why did it call my client <hostname>.0x080009....?
If your client has multiple LAN interfaces, and you have previously installed the client using one
interface, and 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 might 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→
Change icon name to rename one or both of the clients.
How can I set the timezone for messages during the install?
The HP-UX install kernel defaults to eastern US timezone. If you would like the log messages to
come out in some other timezone, you can set the TZ environment variable within the *INSTALLFS
files using instl_adm. Doing this will not impact the very first message that Ignite-UX produces,
but it will take effect as soon as Ignite processes that variable setting. For example, to set TZ to
mountain timezone:
# instl_adm -d > /tmp/installfs.out
# echo 'env_vars += "TZ=MST7MDT"' >> /tmp/installfs.out
# instl_adm -f /tmp/installfs.out
NOTE: The timezone keyword in the Ignite-UX config file determines what timezone is actually
applied to the system after the installation is complete. Setting the TZ environment variable as
shown above is only used during the installation. For more information about the timezone
keyword, see instl_adm(4).
Frequently asked questions 19