Dhcp Snooping Configured Properly But Client Not Assigned Ip - Avaya 8800 Troubleshooting Manual

Upper layer troubleshooting
1. Disable global DHCP Snooping and verify that the DHCP client is able to obtain an
2. Verify global DHCP Snooping is enabled:
3. Verify that DHCP Snooping is enabled on the VLAN:
4. Verify that DHCP Snooping trusted and untrusted ports are properly configured:
5. Check the DHCP Snooping binding table:

DHCP Snooping configured properly but client not assigned IP

If DHCP Snooping is configured properly, but the client is still not assigned an IP address, you
can enable a trace for DHCP Snooping events to troubleshoot the source of the problem.
454 Troubleshooting
address.
config ip dhcp-snooping disable (CLI)
no ip dhcp snooping enable (ACLI)
If the problem persists with DHCP Snooping disabled, then the issue is outside the
scope of the DHCP Snooping feature. In this case, check ports, VLANs, and all
applicable configurations and connections between the DHCP client and server.
If the DHCP client and server function properly when DHCP Snooping is disabled,
reenable DHCP snooping and continue with the following steps to verify the
configuration.
show ip dhcp-snooping info (CLI)
show ip dhcp snooping (ACLI)
show ip dhcp-snooping vlan(CLI)
show ip dhcp snooping vlan (ACLI)
Verify that access and all core VLANs have DHCP Snooping enabled.
show ip dhcp-snooping port [<portlist>] (CLI)
show ip dhcp snooping interface [<interface-type>]
[<portlist>] (ACLI)
Verify that the access port is untrusted and all core ports are trusted. The default
value is untrusted.
show ip dhcp-snooping binding (CLI)
show ip dhcp snooping binding (ACLI)
If there is no entry in the DHCP Snooping binding table, check whether the DHCP
server has been connected to the DHCP Snooping trusted port.
Comments? infodev@avaya.com
July 2013