An encrypted file integrity check code is added to the lease.txt and conflict.txt files to prevent tampering. After the device restarts, the system decrypts this code and uses it to verify the file integrity before restoring the address lease and conflict information from the lease.txt and conflict.txt files. If the verification is successful, the data is restored; otherwise, it is discarded and a log is recorded.
- If you manually modify the content of a file, run the dhcp server database authentication-mode no-check command to set the file integrity authentication mode to no-check before the restart.
- The root keys for decrypting and encrypting the file integrity check code must be the same. Otherwise, the decryption fails. The root key on each device is unique to that device. If you use a backup file generated on another device to restore data, run the dhcp server database authentication-mode no-check command to set the file integrity authentication mode to no-check before the restart.
- For compatibility with earlier versions, data can be restored based on an earlier version of a file that does not carry the file integrity check code after a restart. To forcibly check whether data is tampered with based on an earlier version of a file, run the dhcp server database authentication-mode force-check command to set the file integrity authentication mode to force-check before a restart.