Cisco Access Point Conversion (AP Conversion)

May 24, 2020



We hope you are fine and healthy during this horrible pandemic. Regardless of which CCIE path you decided to take, you must know some hard facts about Access Points (APs)


Lightweight image: k9w8
Autonomous image: k9w7


Make sure the autonomous access points must be running Cisco IOS Release 12.3(7) JA or later to perform the lightweight mode conversion. If necessary, upgrade the access point to Cisco IOS Release 12.3(7)JA or later.

Now we will see how to convert from LAP to AAP



Let's jump in! 

Lightweight to Autonomous Conversion:



Step1: Download the software from




Start TFTP server and put the IOS image (k9w7) in TFTP root directory.

I have this image: c1240-k9w7-mx.124-25d.JA2

Step2: Connect PC and AP with an Ethernet cable. Make sure that both AP and PC should be in same subnet.

Step3: Issue this commands on AP:




My PC IP address is
Try to ping from AP to PC.





Then run this command:




To verify image on AP, issue this command:





Autonomous to Lightweight Conversion




Step1: Download the software from

First of all, we need to obtain the recovery image for a given access point. This is obtained through > Download and then we can enter the AP number.
Choose to download Lightweight AP IOS Software.
Example for1240AP, I already have a recovery image “1240-rcvk9w8-tar.123-11JX1.tar”
You can download it from here:




Step2: If there is enough space then Move the software image file to access Point via TFTP By using this command:



AP# copy tftp:// flash:/





Step3: Install the image on AP

*** Be aware, in this case we will loose the configuration of AP so don’t forget to backup the config before applying new Image.

Or if we have the image on TFTP root directory then From the Access Point CLI runs the command







Issue the command and wait for reboot

The Access Point will download the file and overwrite the existing image file (/overwrite) in the flash and then reboot (/reload) into LWAPP mode. If the reload does not happen, enter the reload command manually.






Let's verify this: