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

The server keyword 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.
server = "10.2.1.11"
sd_server = "10.2.1.11"
netmask[] = "255.255.255.0"
route_gateway[0] = "10.3.1.1"
route_destination[0] = "default"
disable_dhcp = "true"
If DHCP is used, this should not be needed since the DHCP server should provide appropriate
routing information.
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).
Multiple NICs Attach the Ignite Server to Multiple Subnets
It is possible to connect one Ignite server to multiple subnets using multiple network interface cards
(NICs). The Ignite server can then be used to support network boot and installation on each of
these separate subnets. The following diagram is an example of a multiple subnet complex network.
There are some special Ignite configuration considerations for supporting multiple subnets from
one server. You must be careful to configure the server so it sends the client correct networking
information for its subnet, and you must configure the client so it contacts the correct Ignite-UX
server.
Getting the Client the Correct Networking Information
The HP-UX Ignite server needs to be configured so the client receives a response from the server
with the correct network configuration for its subnet.
The bootptab content for each MAC address needs to have correct networking configuration for
the system's subnet. In particular, IP addresses, netmasks, and gateways need to be valid from the
client system's perspective. Thus, bootptab will need to include information for all the different
subnets used by clients supported by the master Ignite server.
If anonymous network boot is used, care is needed to ensure boot responses are correct. See
Chapter 4 (page 42) for more information.
54 Complex Networks: Challenges and Solutions