I believe that the DHCP server on the WLC's themselves are for the clients and not for the Mgmt VLAN for the AP's. So, you're better off just creating the DHCP scope for the WAP's on your router with option 60/43 unless all your AP's and the AP Manager/Management interface on your controller are on the same network. At that point, you don't even need to define options.
Typical installs, you do not DHCP your management interfaces. You would be better static on these.
Specific to the APs, it would be best to put these in their own VLAN. I have not used the controller for AP DHCP, but i wouldnt see why it would not work. But i have never done it personally.
"Satisfaction does not come from knowing the solution, it comes from knowing why." - Rosalind Franklin
You can setup a dhcp on the wlc for the ap's to obtain an IP Address, but I would only do this if you are staging the ap's then I would disable the scope. As long as the AP's are on the same subnet as the wlc management and ap-managers interface, there is no need for option 43 or dns to resolve the ip of the wlc. If you setup the dhcp on the management, make sure you specify the ip address for the dhcp server (mangement ip of the wlc) on th emanagement interface primary dhcp.
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...