DHCP persistence

The DHCP persistence feature on the 7705 SAR Gen 2 retains information learned through DHCP snooping across reboots. This information can include data such as the IP address, MAC binding information, lease length information, and ingress SAP information (required for VPLS snooping to identify the ingress interface). This information is referred to as the DHCP lease-state information.

When a DHCP message is snooped, the system performs the following steps to make the data persistent. For systems with only one CPM, only step 1 applies; for those with dual CPMs, all steps apply.

  1. When a DHCP ACK is received from a DHCP server, the entry information is written to the active CPM compact flash. If writing is successful, the ACK is forwarded to the DHCP client. If persistency fails completely (for example, because of a bad compact flash), a trap is generated indicating that persistency can no longer be guaranteed.

    If the complete persistency system fails, the DHCP ACKs are still forwarded to the DHCP clients. DHCP ACKs may get dropped and not forwarded to the DHCP clients only during small persistency interruptions, or in overload conditions of the compact flash.

  2. DHCP message information is sent to the standby CPM, where the DHCP information is also logged on the compact flash. If persistency fails on the standby CPM, a trap is generated.