C1240 K9w7 Tar 124 25d Ja2 Tar 26
Sharolyn Uriegas
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: Run this commands on AP:
If you choose to overwrite the current file, issue the archive download-sw /overwrite /reload t -name command. The / overwrite option overwrites the software image in flash with the downloaded image. The /reload option reloads the system after you download the image unless the configuration is changed and not saved. For //location , specify the IP address of the TFTP server. For image name , specify the Cisco IOS filename that you plan to use to upgrade the access point. In this example, the command is archive download-sw /overwrite /reload t -k9w7-tar.124-10b.JA3.tar. As mentioned earlier, do not change the name of the Cisco IOS file. Leave it as the default. You find these logs during the successful file transfer:
Under the heading: Reverting from LWAPP Mode to Autonomous Mode. Doesn't matter that it is already autonomous or not. This means the AP will go looking for c1200-k9w7-tar.default so you need to rename the software to that (or a copy of it to that name).
8705_t1_0_4_3c (1).tar 20.83Mb December 12 2014 at 06:53 8705_t1_0_4_3c.tar 20.83Mb December 12 2014 at 06:55 8790_k2_0_7_52 (1).tar 16.02Mb December 12 2014 at 06:53 8790_k2_0_7_52.tar 16.02Mb December 12 2014 at 06:55 air-ct2500-k9-7-6-120-0.aes 139.61Mb December 12 2014 at 06:56 AIR-CT5500-K9-7-6-120-0.aes 139.61Mb December 12 2014 at 06:56 AIR-WLCM-K9-7-0-235-0-ER.aes 3.15Mb November 28 2014 at 01:28 AIR-WLCM-K9-7-0-235-0.aes 75.58Mb November 28 2014 at 01:29 AIR-WLCM-K9-7-0-240-0-ER.aes 3.15Mb November 28 2014 at 01:27 AIR-WLCM-K9-7-0-240-0.aes 76.45Mb November 28 2014 at 01:28 AIR-WLCM-K9-7-0-250-0-ER.aes 3.15Mb December 13 2014 at 20:58 AIR-WLCM-K9-7-0-250-0.aes 76.54Mb December 13 2014 at 20:56 ap3g1-k9w7-tar.152-2.JA.tar 9.34Mb December 12 2014 at 06:56 ap3g1-k9w7-tar.152-2.JB.tar 11.69Mb December 12 2014 at 06:55 ap3g1-k9w8-tar.152-2.JA.tar 10.81Mb December 12 2014 at 06:55 ap3g1-rcvk9w8-tar.152-2.JA.tar 7.24Mb December 12 2014 at 06:55 asa922-8-k8.bin 29.09Mb December 12 2014 at 06:53 c1140-k9w7-tar.152-2.JB.tar 9.87Mb December 12 2014 at 06:55 c1200-k9w7-tar.123-8.JEE.tar 4.87Mb December 12 2014 at 06:56 c1240-k9w7-tar.124-25d.JA2.tar 5.50Mb December 12 2014 at 06:56 c1240-k9w8-tar.124-25e.JAP.tar 4.80Mb December 1 2014 at 04:25 c1240-rcvk9w8-tar.124-25e.JAP.tar 2.82Mb December 1 2014 at 04:26 c1250-k9w8-tar.152-2.JA.tar 6.61Mb December 12 2014 at 06:56 c1310-k9w7-tar.124-25d.JA2.tar 5.36Mb December 12 2014 at 06:56 c1700-adventerprisek9-mz.124-15.T10.bin 25.45Mb December 12 2014 at 06:54 c1700-advsecurityk9-mz.124-15.T14.bin 16.03Mb December 12 2014 at 06:54 c181x-adventerprisek9-mz.151-4.M8.bin 29.16Mb December 12 2014 at 06:42 c1841-adventerprisek9-mz.124-22.YB6.bin 37.89Mb December 12 2014 at 06:44 c1841-adventerprisek9-mz.151-4.M.bin 45.10Mb December 12 2014 at 06:44 c1841-adventerprisek9-mz.151-4.M1.bin 45.14Mb December 12 2014 at 06:44
In this example I am using 3500 series AP & therefore I have downloaded ap3g1-k9w7-tar.152-4.JA1.tar & ap3g1-rcvk9w8-tar.152-4.JA1.tar files onto my TFTP server. Now you need to rename these in order to load it to AP when it is resetting using mode button. Below shows the how it should be renamed. Since it expecting same default filename you have to make sure correct file renames depend on you are doing LAP-> AAP or AAP->LAP conversion process.
If a AP already being used, that can be converted in the past eitherway. Only way to verify is power up the AP & see show version. If image comewith k9w7 that indicate an autonomous image. if it is k9w8 then it is lightweight.
Hello, I have an AIR-CAP-2602I-A-K9 and I am trying to make it into an autonomous device. I have the ap3g2-k9w7-tar.153-3.JD.tar file, I renamed it to ap3g2-k9w7-tar.default connected the Ethernet port and the console cable opened teraterm and then unplugged the Ethernet held down the reset and plugged her back in.
I have set my address to 10.0.0.2 255.0.0.0 Gateway 10.0.0.1 this is is what I get
As AP IOS is always distributed as a tar file, the AP cannot directly execute such a file (thus, if you were to copy c1240-k9w7-tar.124-25d.JA1.tar directly onto AP flash, and then try to boot it, this could not work.) The tar file contains, in addition to the IOS image proper, the radio firmware files, the HTML GUI files (if present), and various other files. The AP IOS tar file must be unbundled into AP flash using the archive exec command (this is done in an automated fashion when a lightweight AP is upgraded after joining a WLC.) After unbundling, the IOS image itself be in a file called flash:/platform-featureset-mx.version/platform-featureset-mx.version - for example, flash:/c1240-k9w7-mx.124-25d.JA1/c1240-k9w7-mx.124-25d.JA1. The AP is configured to boot this image if the bootloader BOOT environmental variable is set accordingly.
As AP IOS is always distributed as a tar file, the AP cannot directly execute such a file (thus, if you were to copy c1240-k9w7-tar.124-25d.JA1.tar directly onto AP flash, and then try to boot it, this could not work.) The tar file contains, in addition to the IOS image proper, the radio firmware files, the HTML GUI files (if present), and various other files.
e2b47a7662