116
Configuring DHCP binding auto backup
The auto backup feature saves bindings to a backup file and allows the DHCP server to download
the bindings from the backup file at the server reboot. The bindings include the lease bindings and
conflicted IP addresses. They cannot survive a reboot on the DHCP server.
The DHCP server does not provide services during the download process. If a connection error
occurs during the process and cannot be repaired in a short amount of time, you can terminate the
download operation. Manual interruption allows the DHCP server to provide services without waiting
for the connection to be repaired.
To configure DHCP binding auto backup:
Step Command
Remarks
1.
Enter system view.
system-view
N/A
2.
Configure the DHCP server to
back up the bindings to a file.
dhcp server database filename
{
filename
|
url
url
[
username
username
[
password
{
cipher
|
simple
}
string
] ] }
By default, the DHCP server
does not back up the DHCP
bindings.
With this command executed,
the DHCP server backs up its
bindings immediately and runs
auto backup.
3.
(Optional.) Manually save the
DHCP bindings to the backup
file.
dhcp server database update
now
N/A
4.
(Optional.) Set the waiting
time after a DHCP binding
change for the DHCP server
to update the backup file.
dhcp server database update
interval
interval
The default waiting time is 300
seconds.
If no DHCP binding changes,
the backup file is not updated.
5.
(Optional.) Terminate the
download of DHCP bindings
from the backup file.
dhcp server database update
stop
N/A
Binding gateways to DHCP server's MAC address
This feature enables the DHCP server to assign different gateway IP addresses to DHCP clients. In
addition, the DHCP server uses the gateway IP addresses and the server's MAC address to reply to
ARP requests from the clients.
As shown in
, the DHCP server is configured on the access device that provides access for
clients of different service types, such as broadband, IPTV, and IP telephone. The clients of different
types obtain IP addresses on different subnets. For the clients to access the network, the access
interface typically has no IP address configured. You must bind the gateways to the DHCP server's
MAC address when specifying gateways for the DHCP clients.
