Users Guide

Table Of Contents
By default, DHCP snooping is disabled globally and enabled on VLANs. For the DHCP snooping feature to work, enable it
globally.
NOTE: If you move a DHCP client from an untrusted interface to another untrusted interface within the VLAN, the DHCP
snooping binding database is not updated. The switch drops subsequent packets from the client. However, if you move a
DHCP client from an untrusted interface to a trusted interface, there is no impact to the traffic from the client.
Restrictions for DHCP snooping
The management VLAN does not support DHCP snooping.
VxLAN bridges do not support DHCP snooping.
The maximum number of supported DHCP snooping binding entries is 4000.
OS10 does not support multi-hop DHCP snooping.
For the DHCP snooping functionality to work correctly, ensure that the DHCP server supports option 82 (RFC 3046).
Enable option 82 (RFC 3046) on the DHCP server for the DHCP Snooping functionality to work correctly.
Rogue DHCP server detection
In the following topology, a trusted DHCP server, a DHCP client, and a rogue DHCP server are connected to the DHCP
snooping switch. The DHCP client and DHCP server are on the same VLAN. The physical interface eth 1/1/2 is a trusted
interface. When the rogue DHCP server sends a DHCP packet to the client, the switch analyzes the packet. As the rogue server
is connected to the switch to an untrusted eth 1/1/3 interface the switch deems the server as a rogue DHCP server and drops
the packet.
DHCP snooping with DHCP relay
In the following topology, the DHCP snooping switch is the DHCP relay agent for DHCP clients on VLAN 100. The DHCP server
is reachable on VLAN 200 through eth 1/1/2. The switch forwards the client DHCP messages to the trusted DHCP server.
The switch processes DHCP packets from the DHCP server before forwarding them to DHCP clients. As the rogue server is
connected to the switch to the eth 1/1/3 interface which is untrusted, the switch drops DHCP packets from that interface.
System management
209