I have an issue where my new Ap's out of the box in that they are registering with the master controller, upgrading the Lwapp software then rebooting and going through the same upgrade process again and again.
Other AP's that are already registered with the controller some time ago are working fine upon power cycle.
The DHCP option is working as I can see the controller address's being obtained and of course its getting the software from the controller.
Just to toss my own idea in there... do you have multiple controllers? If so, make sure they're running the same level of code. If not, the access points will re-download code each time they connect to a different controller.
Also, check for IP conflicts with the ap-manager IP address. If you can ping the AP manager address (not the management address) you probably have an IP conflict as it normally does not reply to ping requests.
I had this issue a while back, took me some time to find the cause, but when I found it it made absolute sense.
I am curious to hear from Scott to know if any of these things resolved the issue. I am having the exact problem. I received a batch of LAPs and most worked just fine but others have this same problem right out of the box. Seems like they incorrectly mixed a batch of America region LAps with forien reg domains. Just my opinion.... I verified all of the things suggested by the posters with no hits or resolution.
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...