Introduction
Cisco Aironet Access Points IOS Recovery.
Configuration Steps
- Cisco AP (1200 Serials and 1300 Serials) only can carry one IOS.
- “boot system flash:/xxx.bin" does not work for AP. Command line take the statement, but "sh run" does not show it. "sh boot" will reflect the IOS which is specified.
- Never use "copy tftp flash:" in Cisco AP. It does not work.
Cisco 1310G IOS Upgrade Procedure
Following is the proper command that you should use for a regular IOS upgrade with a .tar file on these Aironet devices:
ap#archive download-sw /overwrite /force-reload tftp://IP Address of the PC/the name of the IOS image you downloaded, even with the .tar extension.
Note: The IOS image name of the .tar file is case sensitive, and it should be complete.
Recovery Steps
Using the CLI
Follow the steps below to reload the wireless device image using the CLI. When the wireless device begins to boot, you interrupt the boot process and use boot loader commands to load an image from a TFTP server to replace the image in the wireless device.
Note Your wireless device configuration is not changed when using the CLI to reload the image file.
Step 1 Open the CLI using a Telnet session or a connection to the wireless device console port.
Step 2 Reboot the wireless device by removing power and reapplying power.
Step 3 Let the wireless device boot until it begins to inflate the image. When you see these lines on the CLI, press Esc:
Loading “flash:/c350-k9w7-mx.v122_13_ja.20031010/c350-k9w7-mx.v122_13_ja.20031010″ …########################################################################### ################################################################################ ################################################################################ ####################
Step 4 When the AP: command prompt appears, enter the set command to assign an IP address,
subnet mask, and default gateway to the wireless device.
Note You must use upper-case characters when you enter the IP-ADDR, NETMASK, and DEFAULT_ROUTER
options with the set command.
Your entries might look like this example:
ap: set IP_ADDR 192.168.133.160
ap: set NETMASK 255.255.255.0
ap: set DEFAULT_ROUTER 192.168.133.1
Step 5 Enter the tftp_init command to prepare the wireless device for TFTP. ap: tftp_init
Step 6 Enter the tar command to load and inflate the new image from your TFTP server. The command must include this information:
•the -xtract option, which inflates the image when it is loaded
•the IP address of your TFTP server
•the directory on the TFTP server that contains the image
•the name of the image
•the destination for the image (the wireless device Flash)
Your entry might look like this example:
ap: tar -xtract tftp://192.168.130.222/images/c350-k9w7-tar.122-13.JA1.tar flash:
Step 7 When the display becomes full, the CLI pauses and displays <!–
-->--MORE--. Press the spacebar to continue.
extracting info (229 bytes)
c350-k9w7-mx.122-13.JA1/ (directory) 0 (bytes)
c350-k9w7-mx.122-13.JA1/html/ (directory) 0 (bytes)
c350-k9w7-mx.122-13.JA1/html/level1/ (directory) 0 (bytes)
extracting c350-k9w7-mx.122-13.JA1/html/level1/appsui.js (558 bytes)
extracting c350-k9w7-mx.122-13.JA1/html/level1/back.htm (205 bytes)
extracting c350-k9w7-mx.122-13.JA1/html/level1/cookies.js (5027 bytes).
extracting c350-k9w7-mx.122-13.JA1/html/level1/forms.js (15704 bytes)…
extracting c350-k9w7-mx.122-13.JA1/html/level1/sitewide.js (14621 bytes)…
extracting c350-k9w7-mx.122-13.JA1/html/level1/config.js (2554 bytes)
extracting c350-k9w7-mx.122-13.JA1/html/level1/stylesheet.css (3215 bytes)
c350-k9w7-mx.122-13.JA1/html/level1/images/ (directory) 0 (bytes)
extracting c350-k9w7-mx.122-13.JA1/html/level1/images/ap_title_appname.gif (1422 bytes)
extracting c350-k9w7-mx.122-13.JA1/html/level1/images/apps_button_1st.gif (1171 bytes)
extracting c350-k9w7-mx.122-13.JA1/html/level1/images/apps_button_cbottom.gif (318 bytes)
extracting c350-k9w7-mx.122-13.JA1/html/level1/images/apps_button_current.gif (348 bytes)
extracting c350-k9w7-mx.122-13.JA1/html/level1/images/apps_button_last.gif (386 bytes)
extracting c350-k9w7-mx.122-13.JA1/html/level1/images/apps_button_last_filler.gif (327 bytes)
extracting c350-k9w7-mx.122-13.JA1/html/level1/images/apps_button_last_flat.gif (318 bytes)
extracting c350-k9w7-mx.122-13.JA1/html/level1/images/apps_button_nth.gif (1177 bytes)
extracting c350-k9w7-mx.122-13.JA1/html/level1/images/apps_leftnav_dkgreen.gif (869 bytes)
– MORE –
Note Keep pressing spacebar to complete decompress the file. If you do not press the spacebar to continue, the process eventually times out and the wireless device stops inflating the image.
Step 8 Enter the set BOOT command to designate the new image as the image that the wireless device uses when it reboots. The wireless device creates a directory for the image that has the same name as the image, and you must include the directory in the command. Your entry might look like this example:
ap: set BOOT flash:/c350-k9w7-mx.122-13.JA1/c350-k9w7-mx.122-13.JA1
Step 9 Enter the set command to check your bootloader entries.
ap: set
BOOT=flash:/c350-k9w7-mx.122-13.JA1/c350-k9w7-mx.122-13.JA1
DEFAULT_ROUTER=192.168.133.1
IP_ADDR=192.168.133.160
NETMASK=255.255.255.0
Step 10 Enter the boot command to reboot the wireless device. When the wireless device reboots, it loads the new image.
ap: boot.
FAQ
Question: User is using 1310, its in bridge: mode after he lost the password and deleted all files from it as per some pw recovery link he followed.
He assigned an IP, SM, DR and the device isn't accessible to be pinged etc. Step 6 just times out. The lights are red, yellow, red and orange (left to right top to bottom).
Also when i do this i get that:
bridge: dir flash0
unable to stat flash0/: permission denied
Answer: After going from steps 1 to 5 you need to start your tftp server and make sure that your firewall and antivirus is turned off as it blocks the content carried from tftp server to the device... also make sure that the path to the file in the tftp server is correct.. once the process of tftp upload is done than you can check the file by "set" command...
Verification:
The issue use had was due to the unpingable nature of the bridge: mode. User was under impression that it was not connecting, along with folder vs. file name error it made him think there was no connection. Above mentioned advice was correct, after following it, process was successful.
Reference
