AP migration - Stuck in downloading status

[mkardos1]

Hello all,

We are trying to migrate access-points 2702 from the WLC 5508 (8.0.152.0) to the different controller WLC 5508 (8.5.140.0). Once the AP joins a new controller, it downloads a new softare, reloads and is in the donwloading status again - showing it has a new software.. Have you ever seen such a behaviour?

Many thanks for any advice!

[Rich R]

- Are you sure the APs are not roaming to another WLC on different code version before coming back? (meaning they download different version then come back and have to download new version again)
- You might also be suffering side effect of flash corruption since earlier code versions - refer to https://www.cisco.com/c/en/us/support/docs/field-notices/703/fn70330.html and https://www.cisco.com/c/en/us/support/docs/wireless-mobility/wireless-lan-wlan/213317-understanding-various-ap-ios-flash-corru.html

[mkardos1]

Well, they use DHCP option 43 to receive the WLC information and they have set the primary base to the new controller only.. But I will check this to make sure. Thanks.

[Rich R]

Watch the AP console and you'll see exactly what it's doing.
Remember AP can learn other WLC details in other ways even when it gets boot info from option 43 - eg AP HA config, mobility group etc
https://www.cisco.com/c/en/us/td/docs/wireless/controller/8-5/config-guide/b_cg85/ap_connectivity_to_cisco_wlc.html#discover-and-join-controllers

[ECheng2]

Encountered this issue with the Cisco 9800 WLC and 9120 APs, after our upgrade. 
Two APs kept restarting and not pingable. Tried to do the factory reset with the MODE button but it did not work. 

- Had to use the console, press ESC to enter into the U-Boot
- The IP configuration were gone, so had to enter again. (printenv to view config)

Setenv ipaddr x.x.x.x

Setenv netmask 255.255.255.0

Setenv gatewayip x.x.x.1
saveenv

- tried to change the boot partition (printenv BOOT to view current partition used)

setenv BOOT (part1 or part2)
saveenv
Boot

- after this the AP rebooted and came up. 
HTH!

[Rich R]

That's great to hear @ECheng2 but the 9120 runs a completely different OS to the 2702.  2702 runs Cisco IOS while 9120 runs AP COS.

Static IP config for CAPWAP APs is generally not the preferred method and remember reverting to DHCP is the default recovery mechanism even for an AP with static IP config when it can't reach the controller.