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

When a client system broadcasts a request for network boot, the bootp relay boot helper will
forward the request to the master bootp server indicated in the bootptab. The master bootp
server will respond to the bootp relay boot helper, which will then forward the response back to
the client system. The master Ignite boot server and master bootp server should be the same
system.
The bp option must be specified in the bootp relay boot helper's /etc/bootptab file to forward
boot requests to the master bootp server. The bp value should be the IP address of the master
bootp server. The ip option must not be specified since that value will be provided from the
master bootp server. Often an hm option is also specified so a single bootptab relay configuration
may be used for many or any clients. The hm option is a MAC address mask used to determine if
the MAC address of the requestor matches the MAC address of the ha bootptab option.
ha=000000000000:\
hm=000000000000:\
bp=10.2.1.11
Note that care is needed if the system is connected to multiple subnets, since the bootp relay
helper will respond to boot requests detected on any NIC. 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)
See bootpd(1M) for details of configuration.
Note that this approach works for PA-RISC systems but might not work for Integrity systems. For
Integrity systems, the HP-UX boot loader configures the bootp relay boot helper as a gateway
system for network configuration. If that system does not route packets between subnets, this might
impede successful use of this approach. If the system routes packets, it will be attached to multiple
subnets and therefore respond to boot requests detected on multiple subnets.
Ignite-UX software does not have to be installed on the bootp boot helper.
The following is an example of a local bootp relay boot helper /etc/bootptab content to
respond to any client MAC address:
bootp-relay:\
ht=ether:\
ha=000000000000:\
hm=000000000000:\
bp=15.2.1.11
The following is an example of selective, MAC-specific /etc/bootptab content:
hpfcixa:
ht=ether:\
ha=001083352de5:\
bp=15.2.1.11
A block of MAC addresses may be specified using the ha and hm options. This approach might
be very useful with HP systems supporting HP Virtual Connect technology.
The master Ignite server needs to have entries for the client system boot requests forwarded from
the bootp forward boot helper:
ignite-defaults:\
bf=/opt/ignite/boot/nbp.efi:\
ht=ethernet:\
hn:\
bs=48:\
dn=xyzco.com:\
gw=10.4.1.1:\
sm=255.255.255.0:\
ds=10.2.1.11
hpfcixa:\
ht=ignite-defaults:\
ha=001083352de5:\
58 Complex Networks: Challenges and Solutions