BootP and DHCP
Bootp (Bootstrap Protocol) is a protocol that runs over UDP. It uses two
UDP port numbers, 67 and 68. UDP port 67 specifies a Bootp server. UDP
port 68 specifies a Bootp client. In operation, a client sends a Bootrequest to
a server using a destination port of 67. The server then sends a Bootreply
back to the client using a destination port of 68.
DHCP (Dynamic Host Configuration Protocol) is an extension to Bootp to
allow hosts to obtain more configuration parameters and temporary IP
addresses from a DHCP server. DHCP is backwards compatible with Bootp,
to allow a Bootp client to communicate with a DHCP server. DHCP and
Bootp use the same packet formats.
An HP router can be a Bootp client and a Bootp relay agent. As a client, it
can boot from a Bootp server or DHCP server. As a relay agent, it can relay
both Bootp and DHCP packets. The HP router also can be a Bootp server,
but only to boot another HP router that is directly attached on one of its
WAN links. The HP router cannot be a file server, so it is not a Bootp server
with the ability to download an entire boot file (configuration file) to the
other router. In its replies to Bootp requests, it can supply the essential
configuration parameters needed by an HP router to boot and
route
, and it
can supply the names of the Bootp file server and full boot file. This Smart-
boot use of Bootp and IP is configured on the HP routers by default. See the
discussion of “Instant On” and Smartboot earlier in this chapter.
In the remainder of this discussion, “Bootp” is used to refer to the
combination of Bootp and the DHCP extension.
The most common networking application of Bootp is for downloading
operating system code to a diskless workstation (client). The client may not
know either its IP address or the IP address of its boot server. It broadcasts a
Bootrequest packet to the IP broadcast address, with the client station
(MAC) address. A Bootp server that receives the request looks up the client’s
station address in its server table to discover what the client’s IP address and
boot file name should be. The server then sends this information back to the
client in a Bootreply packet addressed to the client at the MAC and IP level.
The client then uses TFTP to get its boot file from the server. Another
application is to download full configuration files for routers from file
servers, such as from HP network and router management applications.
Bootp Relay Agent
In these applications over the network, if the client and server reside on dif-
ferent subnets, then the Bootrequest must be relayed by a Bootp relay agent.
Internet Protocol Routing Service
BootP and DHCP
2-86
Содержание 600 Series
Страница 1: ...Hewlett Packard Series 200 400 and 600 Routers HP Routing Services and Applications ...
Страница 4: ......
Страница 5: ...1 Product Notes ...
Страница 6: ...Features of HP Routers Architecture and Technology Branch Office Routing Product Notes 1 2 ...
Страница 38: ...Architecture and Technology Software Control Path Architecture 1 34 ...
Страница 52: ...Branch Office Routing Future Directions 1 48 ...
Страница 53: ...2 Routing Services Notes ...
Страница 106: ...Bridging Service Traffic Prioritization 2 54 ...
Страница 158: ...Novell IPX Routing Service NetBIOS Protocol Support 2 106 ...
Страница 194: ...Data Compression for WAN Links Conclusion 2 142 ...
Страница 195: ...3 Application Notes and Case Studies ...
Страница 224: ...Improving Network Availability Application Recovery 3 30 ...
Страница 234: ...ISDN Wide Area Network Design Dry Creek Joint Elem School District Performance 3 40 ...
Страница 316: ......