Ignite-UX Administration Guide for HP-UX 11i (B3921-90079, October 2013)

Having the Client Contact the Correct Server
The server keyword in the IINSTALLFS configuration information specifies the IP address for your
Ignite-UX server. It refers to a specific LAN interface on the Ignite-UX server. The same is true for
the sd_server keyword that specifies the depot server IP address for any depots needed for
installation.
If a client is on a subnet that does not have a route to the IP address specified by server, then it
will not be able to contact the server after it boots.
For performance reasons, you might want to use the IP address of the Ignite-UX server LAN interface
directly connected to the same subnet as the client.
If packets are not routed between different subnets connected to the Ignite-UX server, the client
must use the IP address of the Ignite-UX server LAN interface on the same subnet.
Individual clients might use different IP addresses to access the Ignite server due to performance
reasons or routing reasons as described in “Install Remote Clients Through a Network Router”
(page 53). To customize the IP address used to access the Ignite server on a per client basis, use
the LLA keyword as described below.
Workarounds to specify the IP address of the Ignite server are:
• Correct the server's IP address on the Ignite-UX network setup screen that appears on the client
console when you boot the client.
• Change the configuration content in IINSTALLFS to select the Ignite-UX server and depot server
IP addresses connected to their local subnet.
server = "10.1.1.11"
sd_server = "10.1.1.11"
LLA[] == "00306E4A03C2" {server = "10.1.1.11" sd_server = "10.1.1.11"}
LLA[] == "00306E4A03C3" {server = "10.2.1.11" sd_server = "10.2.1.11"}
IMPORTANT: The sd_server IP address setting in the installation file system will be overridden
by sd_server settings in configuration files created by make_config. To use IINSTALLFS to
control the sd_server setting you must comment-out or remove the sd_server settings within
each sw_source clause in the affected configuration files.
For more information about changing IINSTALLFS content, see instl_adm(1M) and instl_adm(4).
Ignite-UX bootp Boot Helper
An HP-UX server may be used as a boot helper to support boot on a subnet while installation is
accomplished via a master Ignite server connected to a different subnet.
A system with Ignite software installed may be located on each subnet to support initial boot. This
subnet-local Ignite server may be set up with IINSTALLFS configuration content to specify the single
Ignite master server.
Using this approach, all the HP-UX installation and recovery content may be managed on one
system. However, each local subnet Ignite boot helper server must be configured to support network
boot for all the clients on that subnet. The boot helper server may be configured for promiscuous
network boot or via selective MAC address response.
The advantage of this approach is there can be a single Ignite server that handles all HP-UX
installation and recovery content. A significant disadvantage of this approach is that Ignite software
must be installed on each boot helper. The version of Ignite installed on these boot helpers must
always match the version installed on the master Ignite server.
The Ignite product content located in /opt/ignite/boot must be present on the Ignite boot
helper so it may be used to accomplish network boot.
Follow these steps to set up an Ignite-UX boot helper system on the local subnet:
Complex Network Solutions 55