netmask[] = "255.255.255.0" route_gateway[0] = "10.3.1.1" route_destination[0] = "default" disable_dhcp = "true"
If DHCP is used, this will not be required since the DHCP server must 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
For more information about changing IINSTALLFS content, see instl_adm(1M) and instl_adm(4).
Multiple NICs attach the Ignite server to multiple subnetsIt 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
Getting the client the correct networking information
The
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 43) for more information.
Having the client contact the correct server
The server keyword in the IINSTALLFS configuration information specifies the IP address for your
Complex network solutions 55