I had configured a Cisco 5508 series WLC. The APs used are Cisco 3502 LAP. The APs are configured to use DHCP for this ip addresses.
We had configured the DHCP server on the 2 Windows AD server previously and the APs were not able to get an IP address when the WLC was rebooted. To isolate the cause, we configured the DHCP server on a cisco 6500 switch. When we reboot the WLC, most of the APs are not able to grab an IP address. We had to remove and reconfigure the DHCP pool on the cisco 6500 for the APs to capture the IP addresses.
My colleague had feedback that they gotten a message that the DHCP pool had been used up. We tried to do a "show ip DHCP pool" but the switch did not recognise the command. IOS version used is Version 12.2(50r)SYS2.
We had a problem with the wireless client getting ip addresses from the windows DHCP server previously but problem was resolved after we disabled the DHCP proxy on the WLC.
What we are curious is why was the DHCP pool fully used on the Cisco switch and how could we check the number of addresses used other than running "show ip dhcp binding" and doing a count of the IP addresses?
Also why did we have to disable the DHCP proxy on the cisco WLC for the wireless clients to be able to get an IP address from the windows DHCP server?
We seem to be facing a number of problems with the DHCP functions for the wireless setup. Anything in particular that we should take note?
Re: AP unable to get IP address after WLC is rebooted
Make sure the APs are in it's own subnet and not mixed in with user. Set the lease to 4-8 hours if the dhcp scope is for the APs only. I don't like using the switch for dhcp and also make sure you have an ip helper address on the ap subnet pointing to your dhcp server.
Transferring Crash file from standby: Login to the Active WLC in HA.
From CLI: (Cisco Controller) >transfer upload datatype crash (Cisco
Controller) >transfer upload filename (Cisco
Controller) >transfer upload mode tftp (Cisco Controller) >transfer
This is the start of a display filter cross reference between Wireshark
and OmniPeek. The 1st installment is a table of advanced filters. More
filters will be added as time allows. It is a living doc, so check back
for changes every so often Please feel f...