You will probably have to do the update through the command line interface (CLI).
To do this, you will need a machine on the network acting as a TFTP server, preferebly on the same LAN, some like to directly connect it with a crossover cable to the Ethernet port.
3COM's 3Cdaemon (version 2 only!) is very popular, Cisco offers a TFTP server (available from the same page / table as the AP IOS list), or Pumpkin ... all will fit the bill and are easy to set up. All are MS Windows GUIs.
Put your new AP images in the proper directory on the TFTP server ... the directory is configurable in all of the server apps ... the chosen directory becomes the apparent root directory to the client (the AP, in this case).
Bring up a console session on the AP, login, make sure your are at the 'Enable" (Your_AP_Name#) and run the following command:
copy run tftp
and follow the prompts - this will backup your curent running config (!ALWAYS! backup before doing a major change/ upgrade)
Once you have the running config saved to the TFTP server, you can bring down the new IOS:
archive download-sw /force-reload /overwrite tftp://servername/IOS_IMAGE_NAME.TAR (case sensitive, type the IOS name EXACTLY .... not in all caps like I did)
and watch the magic happen.
*NOTE*: You must point to the .tar file, do not extract it on thehost machine. The ARCHIVE command will do the extraction and put the files where they belong.
*ALSO NOTE*: It's recommened in the Release Notes that you SHUT DOWN the radios before doing the update. Apparently there may be an issue where having the radios active may cause a reboot in the middle of the load ... which will corrupt both images and force you to do a cold load (not fun ... not horrible, but certainly no fun).
When it's all done, you should have a new image ... reboot again to make sure everything is good, re-enable the radios, change your NTP parameters to SNTP parameters (if you use a timeserver), and verify that your old running config is working well with the new IOS ... some commands have been added, some old commands have been dropped, and some have more or less options (like cipher now will have CCK-AES and is WPA2 enabled).
Also, your next update will (almost certainly, probably, maybe) be able to be done with the WebGUI via HTTP again.
It might not hurt to search the main Cisco site for the printed procedure for a CLI IOS update, ust to make sure I didn't leave anything out.
(and save the old running config for possible use later)
That's it.
Good Luck
Scott
Edit: Also, please accept my condolances to you & your countrymen on the losses and injuries suffered in the recent barbaric attacks in London. Best wishes to you all.
