I am trying to upgrade the firmware on a Cisco 1200 AP via the web interface but keep getting an error saying not enough room on flash.
The firware currently on the AP is c1200-k9w7-tar.123-8.JA2 and I am tring to upgrade to c1200-k9w7-tar.123-8.JEC2.tar.
The Web interface will not work for you any longer since the images got too big. The Web interface likes to copy over the new image first and then delete the old one once it confirms it copied over successfully. Now you have to make a little leap of faith and use the command line to overwrite the existing software. Set up a TFTP server somewhere with the software image on it. Then telnet or SSH to the AP and use the following command syntax to load it on the AP:
archive download-sw /overwrite /reload tftp://10.0.0.10/c1200-k9w7-tar.12.3(8)JEC2.tar
Substitute your TFTP server's IP address for the 10.0.0.10 and then it's just a matter of verifying your software filename.
Enjoy. Have had to do this for years here, ever since the images got too large for WLSE to handle the upgrades.
Typically you don't need to do anything special. The /overwrite option will take care of removing the old files prior to actually downloading the new image.
Unless your NVRAM is completely full of bogus files and crashdumps I don't think you should need to delete anything manually.
If it is full of files then you may want to telnet to a couple of different AP's to see what the "normal" files that are present are and then you could manually delete the extras. But from my experience I have only encountered this a couple of times and we have about 350+ 1200 series APs that I have done this for on several occasions. Crashdump files appeared to be the problems for those times.
Thank you for your advice. I tried to load the firmware using Telnet and the command you suggest and this is what I get:
Loading c1200-k9w7-tar.123-8.JEC2.tar from 10.54.50.10 (via BVI1): !
extracting info (277 bytes)
Version Suffix: k9w7-.123-8.JEC2
Image Name: c1200-k9w7-mx.123-8.JEC2
Version Directory: c1200-k9w7-mx.123-8.JEC2
Ios Image Size: 4342272
Total Image Size: 5079552
Image Feature: WIRELESS LAN
Image Family: C1200
Wireless Switch Management Version: 1.0
ERROR: Not enough free space in "flash:/"
ERROR: Clean up and try again.archive download: takes 4 seconds
What does a dir of your AP look like? If I look at one of my APs this is what I show for a "normal" list of files:
Directory of flash:/
2 -rwx 4816 Apr 22 2009 15:54:55 -05:00 config.txt
4 -rwx 1945 Apr 22 2009 15:54:55 -05:00 private-config
7 drwx 512 Nov 24 2008 19:30:40 -06:00 c1200-k9w7-mx.123-8.JEC2
5 -rwx 525184 Feb 29 2008 17:01:51 -06:00 r0.rcore
3 -rwx 2072 Apr 22 2009 15:54:55 -05:00 private-multiple-fs
159 -rwx 378 May 19 2009 23:35:03 -05:00 env_vars
7741440 bytes total (2200064 bytes free)
And, as luck would have it, I have an r0.rcore file out there which is about half a MB. I believe that is a core dump file which you can delete to free up space if needed. But I am curious what kind of files you have on your system. An unsuccessful upgrade attempt from the web interface may have left some other remnants behind that could be removed.
Actually, when I looked at the files on the AP, there were alot of Crash Reports has you had said, and so I deleted those, and it then managed to update the firmware.
Thank you for your help, much appreciated.
Just as another query, I was wondering if you use a WLAN Controller as you have a large number of APs.
We have around 32, all on the same SSID, but the problem we have is that if a member of staff moves from one end of the school, they may drop their connectivity. We would like to have a seamless network. Would you have any suggestions.
We actually have a large project going on right now to revamp our network. We do have a couple of WiSM switches with a total of 4 WiSM blades (8 controllers) total. It is moving slowly but we are ripping out are old 1200's and currently we are deploying the AP1252 APs. Not sure if that will be changing in the future to the 1131 or 1140.
The drops you talk of could be caused by a number of reasons. Does the client's IP address need to change when the wireless device moves from one end of the school to the other? If so, then the "drop" is a very normal thing without a controller as the client must get a new IP address and that can be very disruptive to communications/applications. We actually have a very large ugly campus-wide vlan for most of our wireless users which gets us around a lot of those types of roaming issues but I would have a hard time recommending that to anyone.
If you are on the same subnet throughout the client roam then I guess I don't know why you would be dropping your connections. Is there thorough wireless coverage or what else is different about the environment where they start and where they end their roam?
And by same SSID, is the security also identical from AP to AP? That would be a killer.
Same issue here, I don't see anything obvious that is filling up flash.
Currently running: Cisco IOS Software, C1200 Software (C1200-K9W7-M), Version 12.3(7)JA, RELEASE SOFTWARE (fc1)
Unfortunately, your AP1200 is the first generation that came with a beagar's 8mb of flash. This means that you will need to delete the current IOS (delete /f /r flash:c1200-k9w7-mx.123-7.JA) and upload the new IOS.
Unfortunate because when you have deleted the old IOS you must'nt reboot the AP or that means that you have to add another process to your task.
Hope this helps.
Worked perfectly, thanks!
It's still did not solve my original problem however -- I was sure it would :-)
I am trying to turn the 1200 into a workgroup bridge to connect to a 3rd party AP (linksys) and it appeared that CSCsb31178 would have been fixed after any version other than the one I had on there. I am now at Version 12.3(8)JA2
Instead of the the original error message about WPA2 from the bug, it now says:
*Mar 1 00:10:42.627: %DOT11-4-CANT_ASSOC: Interface Dot11Radio0, cannot associate: No Response
The AP with SSID partridge.net works just fine with any standard wireless client, wide open: broadcast ssid and no wep/wpa
Access Point as a Workgroup Bridge Configuration Example