11-02-2011 11:46 AM - edited 02-07-2024 08:57 AM
All Cisco Aironet 802.11a/b/g/n and 11ac Wave 1 wireless access points and bridges ran IOS, except for the OEAP602.
The newer 802.11ax and 11ac Wave 2 APs, including the C9100 and 1800, 2800 and 3800 series, run AP-COS.
Note: Some very old, no longer supported, Cisco access points ran VxWorks, such as the Aironet 342 and the 1010/1020 lightweight APs.
Access Point IOS is distributed as a tar file. These tar files can be downloaded from Cisco Software Download page; lightweight IOS images (k9w8) are also bundled in the WLC software images (.aes.)
The AP image names include the following components:
platform-featureset-tar.version.tar
ap1g2 - 1600 series
ap1g3 - 1530 series, AP803 embedded in IR829 router
ap1g4 - 1850/1830/1810 series (AP-COS)
ap3g2 - 3700/3600/2700/2600/1700 series (aIOS, and lightweight up through 8.4/15.3(3)JE branch)
c1240-k9w7-tar.124-25d.JA1.tar
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.)
AP1260#archive download-sw /overwrite tftp://10.95.42.136/ap3g1-k9w7-tar.124-25d.JA1
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.
To see what IOS image the AP is configured to boot, examine the BOOT variable.
AP3502i#more flash:/env_vars | include BOOT
BOOT=flash:/ap3g1-k9w8-mx.152-2.JA/ap3g1-k9w8-mx.152-2.JA
To change the BOOT variable, use the IOS config mode boot system command.
AP3502i(config)#boot system flash:/ap3g1-k9w8-mx.124-25e.JA2/ap3g1-k9w8-mx.124-25e.JA2
Aaron,
Thanks for this information. I struggle with how to install an IOS into an AP. And I am still not very clear on how this is to be accomplished. I have an 881W and have downloaded what I believe to be the latest IOS for this AP (ap801-k9w7-tar.152-2.JA). Problem is that I have not really found a good or at least clear set of instructions in how to load this IOS into my AP, so I have not done that yet.
Does the IOS that is currently installed into the AP remain after an update or does the new IOS overwrite the current IOS. And how does one recover from a, heaven forbid, faulty installation. What is the fallback from that. I'd appreciate any information you can point me to to help me better understand how I can update my AP. Because, right now, I am most certainly hesitant to even attempt an upgrade.
Thank you for this very usefull document!
I see that you updated it in March to reflect the new corsica software (COS).
Could you please add the 1810 series to ap1g4?
Could you also please update the section regarding archive, image name in flash and boot variable to relect the changes COS made in comparision to IOS?
E.g.:
Thank you!
Aaron,
Thanks for your information.
I currently use AIR-AP1572EAC.
I would like to use this Access Point in Autonomous mode, is "c1520-k9w7-tar.xxx-x.xxx.tar" valid?
Can I only use "c1570-k9w7-tar.xxx-x.xxx.tar" for the 1570 series?
The method I use to update an IOS on an AP is as follows (this deletes all config and was done on an AIR-LAP1142N-N-K9):
1. Use a laptop with Win 7 and OpenTFTP installed.
2. Set your ethernet NIC to use 10.0.0.2 255.255.255.0. The AP uses 10.0.0.1 255.255.255.255 as its IP address.
3. Copy the IOS file into your tftp directory that you set up with OpenTFTP. Start OpenTFTP.
4. Rename it from (for example) c1140-k9w7-tar.153-3.JD16.tar to c1140-k9w7-tar.default
5. Connect the AP to the laptop (via power supply if used).
6. Hold the reset button in whilst turning on the AP. The light should start flashing and turn red after about 20 seconds.
7. Release the reset button and the AP should pick up the TFTP server and start the upgrade. This takes about 5 minutes.
8. The AP will reboot at the end and boot into a working IOS.
9. AP can then be reconfigured using the config you (hopefully) saved before you started this process.
Hi Aaron,
The link to the new discussion could not be opened: https://supportforums.cisco.com/thread/2178594 .
Could you please also explain what are the major differences between COS and IOS?
How is COS different from IOS and the purpose of introducing it.
Could not find any information on COS on the internet.
i think this page as mentioned above is not working and should have bene moved by CISCO for various reason. can we get this document? I am trying to understand the file system structure in AP 4800 which is running CAPWAP mode and uboot, a linux open source software. i think its COS.
I've removed Aaron's mention of a "new" page - that was from 2012 and clearly out of date.
AP-COS is a Cisco AP customised version of ClickOS used on all the more recent Cisco APs.
As I've already replied on your other post it's not intended for users to be fiddling with the file system - you'll need to RMA the AP which you wiped.
hi Rich - thanks and i did responded to you in my other thread. i am still having issues on getting RMA because i do not have support which is expired and this AP is also expired as per CISCO. but i heard that these AP are comes with life time warrenty
I've replied about the warranty at https://community.cisco.com/t5/wireless/how-to-format-clickos-ap/m-p/4934411/highlight/true#M261356
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: