top of page
Search
anenarman1975

C1240 k9w7 tar 124 25d ja2 tar: Steps to Recover Cisco 1240 AP from Corrupted or Missing IOS Image



Remember some facts/clue about images:Autonomous image: k9w7Lightweight image: k9w8To know more about AP images, please visit my post: Understanding AP images.


I have this image: c1240-k9w7-mx.124-25d.JA2Step2: 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:




C1240 k9w7 tar 124 25d ja2 tar




Looking to change Cisco AIR-AP1242AG-A-K9 from mode reset lightweight to autonomous. Downloaded the Cisco file "1240-k9w7-tar.123-8.JEA3" & unzipped it to "c1240-k9w7-mx.123-8.JEA3". Finally renaming it to "c1240-k9w7-tar.default" & following the PuTTY / Tftpd64 procedure to upload image in order to change to autonomous. Have doe this several times with the same error noted below "Tar checksum error in t -k9w7-tar.default". Any help would be much appreciated.


Reset done!ethernet link up, 100 mbps, full-duplexEthernet port 0 initialized: link is upbutton pressed for 24 secondsprocess_config_recovery: set IP address and config to default 10.0.0.1process_config_recovery: image recoveryimage_recovery: Download default IOS tar image t -k9w7-tar.default


Thanks for the suggestion...unfortunately it did not work. A different error popped up as noted below. Do I have the right Autonomous file which was downloaded from Cisco website "1240-k9w7-tar.123-8.JEA3" & unzipped it to "c1240-k9w7-mx.123-8.JEA3". Tried WinZip & 7z to unzip file.


The updated file "c1240-k9w7-tar.124-25d.JA2.tar" is only available for download with a valid service contract associated my Cisco.com profile, which I do not have. If anyone can access this file & send it to me, it would be very much appreciated.


Following the steps, I downloaded the Cisco file "1240-k9w7-tar.123-8.JEA3" & unzipped it to "c1240-k9w7-mx.123-8.JEA3". I then renamed the unzipped "c1240-k9w7-mx.123-8.JEA3" file to "c1240-k9w7-tar.default" which was placed in the tftp directory, which resulted in the original "Tar Checksum Error". Thus, it is correctly placed in the tftp directory. Is there any other files which must be present as this is the only file I placed there...there were a few other small files upon unzipping the file?


button pressed for 20 secondsprocess_config_recovery: set IP address and config to default 10.0.0.1process_config_recovery: image recoveryimage_recovery: Download default IOS tar image t -k9w7-tar.default


button pressed for 168 secondsprocess_config_recovery: set IP address and config to default 10.0.0.1process_config_recovery: image recoveryimage_recovery: Download default IOS tar image t -k9w7-tar.default


If you choose to overwrite the existing 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:


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


CAP-AIR3702iFlash is empy!PC settings IP 10.0.0.2 255.255.255.0FW disabledTFTPD32Image placed ap3g2-k9w7-tar.default in c:\tmpSet this folder in TFTPD32Adjust timeout settings to 30secConnect straight UTP cable (cat6a) from PC to APUsed both PoE adapter and power adapter 42vRommon mode by mode button IP 10.0.0.1 255.255.255.224After DPAA_INIT = 0x0 error opening t -k9w7-tar.default (connection time out)


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


I used this method to convert a ciscoap3502 putting a ip on interface g0 . I can ping int intraface for a short time.When I try to run. archive download-sw /force-reload /overwrite t -k9w7-tar.defaultError opening t -k9w7-tar.default no shuch file or directory


Hi. Please I have a challenge. I want to convert a new 2602e with LWAPP to autonomous. I am using PoE. When I set power AP while pressing the mode button, after releasing the button, I get error message on console: %Error opening t -k9w7-tar.default (connection timed out)ap:. have put the two ports on same vlan but cannot ping the AP (10.0.0.1) using my PC (10.0.0.2) that contains the tftp for the image. What more can I do?


this is the output:process_config_recovery: set IP address and config to default 10.0.0.1process_config_recovery: image recoveryimage_recovery: Download default IOS tar image t -k9w7-tar.default


Also, I had to grab another AP and try to associate it with the WLC.While converting a Cisco AP2702i from Autonomous to LWAPP, I tried the following commands several times, but it would still boot with the k9w7 image.


2 -rwx 282 Jan 1 1970 00:10:17 +00:00 info 3 -rwx 6174720 Mar 1 1993 00:21:01 +00:00 ap3g2-rcvk9w8-tar.153-3.JA7.tar 4 -rwx 34650 Mar 1 1993 02:40:31 +00:00 event.log 5 -rwx 1048 Mar 1 1993 02:40:21 +00:00 private-multiple-fs 7 -rwx 13557760 Mar 1 1993 00:24:09 +00:00 ap3g2-k9w8-tar.153-3.JA7.tar 48 drwx 2176 Jan 1 1970 00:16:06 +00:00 ap3g2-k9w7-mx.153-3.JA7 8 -rwx 1765 Mar 1 1993 02:40:21 +00:00 config.txt 9 -rwx 5 Mar 1 1993 02:40:21 +00:00 private-config 10 -rwx 432 Mar 1 1993 02:40:28 +00:00 env_vars


I did mine a little differently. I noticed my ap was only booting up on the ap3g2-rcvk9w8-mx image with is for CAPWAP, but it also had the k9w7 image in the directory as well. I logged in and did my capwap commands to get into cli:debug capwap con clidebug capwap client no-reload 2ff7e9595c


0 views0 comments

Recent Posts

See All

Comments


bottom of page