Technical data

Table Of Contents
81
Example:
This command lists the subnet 192.168.254.0 including any options set specifically for that subnet:
dhcp list 192.168.254.0
BootP
Administrators may wish to specify that certain client leases AND certain subnetworks can satisfy BootP requests.
About BootP and DHCP
BootP and DHCP provide services that are very similar. However, as an older service, BootP offers only a
subset of the services provided by DHCP.
The main difference between BootP and DHCP is that the client lease expiration for a BootP client is always
INFINITE.
Caution:
Remember that when BootP is enabled, the client assumes that the lease is infinite.
By default, the DHCP server will NOT satisfy BootP requests unless the administrator has explicitly enabled
BootP (at the subnetwork or lease level).
Enable/Disable BootP
To allow BootP request processing for a particular client/subnet, use the command:
dhcp bootp allow <
net
>|<
ipaddr
>
To disallow BootP request processing for a particular client/subnet, type:
dhcp bootp disallow
<
net
>|<
ipaddr
>
Use BootP to specify the boot server
The following commands let the administrator specify the TFTP server (boot server) and boot file name. The
administrator will first configure the IP address of the TFTP server and file name (kernel) from which to boot.
This is particularly useful if the kernel in the router’s flash is corrupt or does not exist.
To set the IP address of the server and the file to boot from, use the command:
dhcp bootp tftpserver
[
<
net
>|<
ipaddr
>
]
<
tftpserver ipaddr
>
dhcp bootp file
[
<
net
>|<
ipaddr
>
]
<
file name
>
To clear the IP address of the server and the file to boot from, use:
dhcp bootp tftpserver
[<net>|<
ipaddr
>] 0.0.0.0