Configuration Guide Vol. 2


13.1.7 Notes on using DHCP snooping

<Structure of this section>

(1) Coexistence with Layer 2 Switch Function

See "Configuration Guide: Coexistence of Vol.1" "24.3 Layer 2 Switch Function and Other Functions".

(2) Coexistence with Layer 2 authentication

[See "5.2.1 Coexistence of Layer 2 authentication and other functions."

(3) Notes on configuring authentication-only IPv4 access lists

When you enable DHCP snooping and use the authentication-dedicated IPv4 access lists, if you specify the protocol name bootps or bootpc as a filtering condition in the authentication-dedicated IPv4 access lists, the packets of both bootps and bootpc are passed regardless of other filter conditions.

(4) About Saving and Restoring Binding Databases

(5) Understanding Receive Rate-Limiting for DHCP Packets

When both the DHCP packet reception rate and the ARP packet reception rate have limits, the switch monitors packets for the total value of both limits.

(6) About Dynamic ARP Checking

(7) Understanding Receive Rate-Limiting for ARP Packets

When both the ARP packet reception rate and the DHCP packet reception rate have limits, the switch monitors packets for the total value of both limits.

(8) Capacity limits for terminal filters

If the capacity limit of the terminal filter is exceeded, it is retained in the binding database, but terminal filter registration fails. While clients that fail to register are kept in the binding database, they are not automatically registered in the terminal filter.

To register a terminal filter, you must first delete it from the binding database of the Switch and then re-learn it. For example, perform the following steps:

  1. Delete unnecessary binding entries (the capacity limit is exceeded).

  2. Release the addresson the client that you want to re-register (notify DHCP server of the release).

  3. Execute address issuance at the client to be re-registered.