Showing results for 
Search instead for 
Did you mean: 

1530AP boot loop - recovery?


1530AP is stuck in a boot loop after changing high availability settings to point to a new controller running 

The old controller is still online (version Did the same thing with APs including 1530s and they are all registered, upgraded and working.


The 1530AP shows up on the new controller with ip address even though it has an ip address.

It won't upgrade and won't go back to the old controller. On the WLC I get AP Disassociated. Base Radio MAC x:x:x:x  ApName -  APblahblah

Packet captures show it doing discovery, and it seems to negotiate capwap/dtls with the new controller.

The AP syslogs show:

%CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully peer_ip: x.x.x peer_port: 5246
 %CAPWAP-5-SENDJOIN: sending Join Request to x.x.x.x
 %SYS-5-RELOAD: Reload requested by CAPWAP CLIENT. Reload Reason: Reload.


Edit: fixed it by putting on the same vlan as the old controller and adding an ACL on the AP switch port blocking access to the new controller. The AP then registered back on the old controller.


5 Replies 5

Flavio Miranda


 1530 is outdoor AP. They need to be permited on the WLC. SECURITY > AP Policy

Add the AP to the authorization list.

The AP MIC is already set in AP policy on the new controller. 

VIP Advocate VIP Advocate
VIP Advocate

Looks like the new AP code is indeed corrupt.


1530 is registered to old WLC and I enabled SSH

From ap:

#archive upload-sw /version ap1g3-k9w8-mx.153-3.JD17 ftp://x.x.x.x/test.tar


With bash cli:

tar xf test.tar
cd ap1g3-k9w8-mx.153-3.JD17
$ sha512sum -c < file_hashes
CA2.bin: OK
CA5.bin: OK
CO2.bin: OK
CO5.bin: OK
RO2.bin: OK
RO5.bin: OK
ap1g3-k9w8-mx.153-3.JD17: FAILED
img_sign_rel.cert: OK
img_sign_rel_sha2.cert: OK
info: OK
sha512sum: WARNING: 1 computed checksum did NOT match

To recap, recovery required:
1. create an ACL on switch port so the AP could not talk to the new WLC. This broke the boot loop and let it revert to old WLC
2. When the AP finally reverted to the old WLC, I enabled SSH
3. log in to AP, rename corrupt file to ap1g3-k9w8-mx.153-3.JD17.bad to make sure re-downloading didn't hit the same bad spot in flash
4. copy good file, delete bad file
5. reconfigure for new WLC



VIP Advocate VIP Advocate
VIP Advocate

Did you fsck the flash? (read the links I shared)

If not it will just keep causing more problems for that AP until you do!

You're lucky you only had 1 AP with the problem.  When upgrading from an affected version of code you should be checking every AP as per the field notice - simply prevents problems like this.

Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community:

Recognize Your Peers