The most common failure is the "Studying CAPWAP" loop. You uploaded the autonomous TAR, but the AP keeps looking for a Wireless LAN Controller.
Cause: The AP’s bootloader is still set to lightweight mode.
The Fix (Convert Lightweight to Autonomous): From the console (rommon or booted lightweight OS), you need a special "Clear" file. Ap3g2-k9w7-tar.153-3.jbb1.tar WORK
If the above fails, your only solution is the ROMmon + TAR method described in Part 3. The TAR file contains the necessary info file that automatically rewrites the bootloader parameters.
Is this build enterprise-ready?
The single biggest question is hardware compatibility. A "successful flash" requires a match between the firmware architecture and the AP's bootloader.
| Access Point Series | Supported | Notes |
| :--- | :--- | :--- |
| Aironet 2600 Series | Yes | Fully supported. Use for standalone retail or branch offices. |
| Aironet 2700 Series | Yes | Works with 802.11ac (Wave 1). |
| Aironet 3500/3600 Series | Yes | Legacy support. This image is often the last stable release for these 802.11n models. |
| Aironet 3700 Series | Yes | High-performance target. |
| Aironet 2800/3800 Series | No | These use the ap3g3 (AP8030) architecture. Do not attempt. |
| Aironet 1800/4800 | No | Mismatched hardware drivers. | The most common failure is the "Studying CAPWAP" loop
Important: If your AP is currently running Lightweight OS (k9w8), simply uploading this TAR file via TFTP will not work by default. You must first change the AP’s boot mode (see Part 5).
A car parts manufacturer had 50 Cisco 2602i APs running 12.4(25d)JA. They experienced random reboots and DFS issues. Upgrading to ap3g2-k9w7-tar.153-3.jbb1.tar resolved memory leaks and introduced 802.11w (Management Frame Protection), stabilizing their warehouse scanners. If the above fails, your only solution is
