server” (page 55) and “Install remote clients through a network router” (page 54). This changes the configuration content in [WVI]INSTALLFS. For more information, see instl_adm(1M).

#instl_adm -tIgnite-UX_server_IP

3.Verify that the server is set to the correct Ignite-UX server and gateway for your subnet.

#instl_adm -d

4.If the gateway value is incorrect, you can use instl_adm -gyourgatewayIP to correct it. This value is set by swinstall when the Ignite-UX product is installed.

5.On the boot helper system, configure the /etc/opt/ignite/instl_boottab file as described in “Getting the client the correct networking information” (page 55).

For more information, see /etc/opt/ignite/instl_boottab on your Ignite-UX server.

HP-UX DHCP PXE Next server boot helper for integrity systems

To support Integrity systems, a lightweight Next Server boot helper may be set up on each subnet. A DHCP PXE response includes a Server Address (SiAddr) field that indicates where to get additional network boot content. Normally, the value in a response informs the client to get subsequent boot content from the same boot server. The /etc/bootptab file can be configured to inform the client to switch to the master Ignite server for other boot content. The bootptab sa option is used to indicate the value. This is commonly described as a Next Server value, since the Server Address value is typically only given when the value differs from the initial boot server. The master Ignite server IP address must be used.

In this approach, each subnet must have a DHCP PXE server, but Ignite does not need to be installed on that system. Therefore, there is no need to have multiple systems with the same Ignite software version installed on them. The HP-UX bootp server may use the Next Server field to direct the client system to get the HP-UX OS content from an Ignite server on a different subnet.

Using this approach, all the HP-UX installation and recovery content may be managed on one system. However, each local subnet Next Server DHCP PXE boot helper 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 selective response using client-specific network configurations.

Note that this Next Server boot helper does not have to be an HP-UX system. If it's not an HP-UX system, care must be taken to make sure the PXE response is consistent with the Ignite server. In particular, the boottab bf option provided from the Next Server boot helper must be consistent with where the boot content is located on the master Ignite server. Symbolic links may be used to allow a nonstandard location to be supported on the master Ignite server, if needed.

Configuring a Next server boot helper for Integrity systems

A Next Server boot helper does not require Ignite-UX software.

If the DHCP PXE server is an HP-UX system, it must be running 11i v2 (B.11.23) or later. If 11i v2 is used, PHNE_36209 or a superseding bootpd patch must be used to enable the configuration of Next Server response.

The nbp.efi boot loader file must be present on the Next Server boot helper:

#cp /usr/lib/efi/EFI/HPUX/nbp.efi /opt/ignite/boot/nbp.efi

If the Next Server boot helper is a PA-RISC system, this boot loader file will have to be copied from an Integrity system. Note that the Ignite-UX product may be installed instead of copying this file in place.

The Next Server response is configured in /etc/bootptab using the sa option. The IP address given with the sa option must be the DHCP PXE Next Server (SiAddr) IP address for additional boot content.

This example configuration is for the following complex network diagram.

Complex network solutions 57