Saving Dhcp Snooping Entries - H3C MSR 2600 Configuration Manual

Step
6. (Optional.) Configure the
padding content and code
type for the remote ID
sub-option.

Saving DHCP snooping entries

DHCP snooping entries cannot survive a reboot. If the DHCP snooping device is rebooted, security
features (such as IP source guard) that use DHCP snooping entries to authenticate users reject requests
from clients until new entries are learned.
To avoid this problem, you can save DHCP snooping entries in a file so that DHCP snooping can read
DHCP snooping entries from this file during a reboot.
NOTE:
If you disable DHCP snooping with the undo dhcp snooping enable command, the device deletes all
DHCP snooping entries, including those stored in the specified file.
To save DHCP snooping entries:
Step
1. Enter system view.
2. Specify a file to save DHCP
snooping entries.
3. (Optional.) Manually save
DHCP snooping entries to the
file.
4. (Optional.) Set the amount of
time to wait after a DHCP
snooping entry changes
before updating the database
file.
Command
dhcp snooping information remote-id
{ normal [ format { ascii | hex } ] | [ vlan
vlan-id ] string remote-id | sysname }
Command
system-view
dhcp snooping binding database
filename { filename | url url
[ username username
[ password { cipher | simple }
key ] ] }
dhcp snooping binding database
update now
dhcp snooping binding database
update interval seconds
73
Remarks
By default, the padding
format is normal and the
code type is hex for the
remote ID sub-option.
Remarks
N/A
By default, no file is specified.
This command enables the device to
immediately save DHCP snooping
entries to the specified database file.
If the file does not exist, the device
automatically creates the file. The
device does not update the file for a
specified amount of time after a
DHCP snooping entry changes. The
default period is 300 seconds. To
change the value, use the dhcp
snooping binding database update
interval command.
DHCP snooping entries are saved to
the database file each time this
command is executed.
The default setting is 300 seconds.
When a DHCP snooping entry is
learned or removed, the device does
not update the database file until
after the specified waiting period.
All changed entries during that
period will be updated.