3702 LWAPP to standalone: AP reboots b4 completing the read from TFTP.

[Gioacchino]

Hi,

I'm following the standard procedure to upload the k9 image onto the AP, i.e.

debug capwap console cli
archive download-sw /force-reload /overwrite tftp://x.y.z.w/ ap3g2-k9w7-mx.153-3.JC1

however the AP keeps searching for the controller and after a while it decides to reboot.
Because of this the image transfer of the standlone image from the TFTP stops.
I see that while the image is transferred the AP decompress and read it, this slows down the process and leads to the reboot of the AP.

Is there another way of having the AP read the new image? Maybe by trasferring the image first on the local flash and then having the AP reading it from there? OR there won't be any space left. eventually?

Gio

[marce1000]

 - This might help : https://community.cisco.com/t5/wireless/recover-1200ap-ios/m-p/1140904#M186661

 M.

[Rich R]

That does suggest the file is corrupt so consider the possibility that your source file is corrupt unless you have verified the file size and MD5 checksum and/or SHA512 hash supplied by Cisco for that image?
https://software.cisco.com/download/home/285029865/type/284180979/release/15.3.3-JPJ3?releaseIndicator=DEFERRED
Note that 15.3(3)JPJ3 is a deferred release.

Yes flash corruption is a known issue with those APs especially running lightweight IOS - there's a field notice and doc about it:
https://www.cisco.com/c/en/us/support/docs/field-notices/703/fn70330.html
https://www.cisco.com/c/en/us/support/docs/wireless-mobility/wireless-lan-wlan/213317-understanding-various-ap-ios-flash-corru.html
So I *always* delete unneeded files and do "fsck flash:" before copying any new image on.
You can also format the flash: which effectively does the same.  Do another fsck after that because there's always a possibility that you actually have faulty flash which will constantly give errors when you do fsck.  You might sometimes have to do it a second time (after deleting recovered files) but more than twice usually means a hardware fault.  Sometimes it can mark all the bad blocks but otherwise there's nothing you can do but replace the hardware.

[Gioacchino]

Indeed, @Rich R after formatting the flash, the AP could read the K9 image with no problem.

Since I had to configure multiple SSID linked to different VLANs, I share the link I used for this last task

https://community.cisco.com/t5/wireless-mobility-knowledge-base/multiple-ssid-with-multiple-vlans-configuration-example-on-cisco/ta-p/3118056

Thank you to all, for helping me along with this issue!
Gio