Ignite-UX Administration Guide for HP-UX 11i (B3921-90080, November 2013)

Figure 26 Port Usage: Initiate LAN Boot for Itanium-Based Clients
PXE/DHCP (udp)
Client Timeline
Server
67
68
68
67
Initiate LAN Boot: Itanium-Based Systems
[Request IP address for boot]
DHCP/bootp (udp)
[Network boot information]
1
1. The client sends a boot request to the server over port 67. The request is handled by the
bootpd daemon on the server. If the client is registered, the /etc/bootptab file is referenced
for the boot IP address; if the client is anonymous, DHCP services are used to assign the boot
IP address. The server then sends the networking information to the client on port 68. For more
information on booting registered Itanium-based clients, see “Configuring the Ignite-UX Server
for Itanium-Based Clients” (page 35). For more information on booting anonymous
Itanium-based clients, see “Configuring an Ignite Server to Boot Anonymous Itanium-Based
Clients” (page 44). For more information on bootpd, see bootpd(1M).
Figure 27 Port Usage: Initiate LAN Boot for PA-RISC Clients
bootp (udp)
bootp (udp)
Client Timeline
Server
1067
Initiate LAN Boot: PA-RISC Systems
[Request IP address for boot]
[Network boot information]
1068 1068
1067
2
2. The client sends a boot request to the server over port 1067. The request is handled by the
instl_bootd daemon on the server. The /etc/opt/ignite/instl_boottab file is
referenced whether the client is registered or anonymous. The server then sends the networking
information to the client on port 1068. For more information on booting registered PA-RISC
clients, see “Configuring the Ignite-UX Server for PA-RISC Clients” (page 31). For more
information on booting anonymous PA-RISC clients, see “Configuring an Ignite Server to Boot
Anonymous PA-RISC Clients” (page 43). For more information on instl_bootd, see
instl_bootd(1M).
86 Security