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 should be the DHCP PXE Next Server (SiAddr) IP address for additional boot content.

This example configuration is for the following complex network diagram.

A sample /etc/bootptab for Next Server boot helper configuration follows:

next-server:\ bf=/opt/ignite/boot/nbp.efi:\ ht=ethernet:\

hn=:\

bs=48:\

dn=xyzco.com:\

gw=15.1.128.1:\

sm=255.255.255.0:\

ds=10.2.1.11

hpuxsysa:\ tc=next-server:\ ha=00306E4A03C2:\ ip=10.4.1.140:\ sa=10.2.1.11:

During DHCP PXE boot, the boot helper server provides the network configuration (IP address, netmask, gateway, etc.). The boot helper also provides the initial boot loader (nbp.efi ). All other boot content is taken from the master Ignite-UX server. Thus, this boot helper server requires no Ignite-UX product content.

Note that the bf option path must match the path where other boot content is located on the master Ignite server. The bf path must be valid on the boot helper and the Ignite master server.

Make sure the correct server is set and any network routing is configured as described in “Having the Client Contact the Correct Server” (page 55) and “Install Remote Clients Through a Network Router” (page 53).

Forwarding Boot Requests via bootp Relay

The HP-UX bootp server has the ability to forward boot requests. With this approach, each subnet must have a bootp relay boot helper, but that system does not need to have Ignite software installed. Therefore, there is no need to have multiple systems with the same Ignite software version on them.

Complex Network Solutions 57