Anybody else with this problem?
I'm having the same issue with IAP-225 that have been converted to CAP.
Power provided via Cisco 2960x.
Deployed 8 to one location, and worked for about 2 weeks, then 4 just dropped off and started doing this reboot cycle. There was power issues and networking equipment did not reboot.
Plugging the 225 directly into our 620 controller brought the 225 back up and working without any issues. Putting them back on the Cisco 2960 brought the problem back.
Alternatively, I was able to console into the AP and do a factory_reset, reconvert back to CAP and then reprovision to the local controller, and that also seemed to work.
Checked another site that had received a similar upgrade and it exhibited the same problem.
I do have a TAC case open. TAC was able to purge the boot environment and enter static information for the master, and that also seemed to work.
Since the APs with the issue were already provisioned to the local office controller, I'm not exactly sure why they boot up and look for the master first instead of the local?
Still working with TAC, but having some logicistical issues with being able to packet capture from an AP in a remote location and the master in a separate location.