Related Documentation
- M, MX, T Series
- DHCP Access Service Overview
- M, T Series
- Configuring a Static IP Address as DHCP Server Identifier
Configuring a DHCP Boot File and DHCP Boot Server
When a DHCP client starts, it contacts a boot server to download the boot file.
To configure a boot file and boot server, include the boot-file and boot-server statements:
You can include these statements at the following hierarchy levels:
After a client receives a DHCPOFFER response from a DHCP server, the client can communicate directly
with the boot server (instead of the DHCP server) to download the
boot file. This minimizes network traffic and enables you to specify
separate boot server/file pairs for each client pool or subnetwork.
The boot-file statement configures the name and location of the initial boot file that the DHCP client loads and executes. This file stores the boot image for the client. In most cases, the boot image is the operating system the client uses to load.
The boot-server statement configures the IP address of the TFTP server that contains the client’s initial boot file. You must configure an IP address or a hostname for the server.
You must configure at least one boot file and boot server. Optionally, you can configure multiple boot files and boot servers. For example, you might configure two separate boot servers and files: one for static binding and one for address pools. Boot file configurations for pools or static bindings take precedence over boot file configurations at the [edit system services dhcp] hierarchy level.
The following example specifies a boot file and server for an address pool:
Related Documentation
- M, MX, T Series
- DHCP Access Service Overview
- M, T Series
- Configuring a Static IP Address as DHCP Server Identifier
Published: 2013-07-17
Related Documentation
- M, MX, T Series
- DHCP Access Service Overview
- M, T Series
- Configuring a Static IP Address as DHCP Server Identifier
