Wireless Access

I am trying to upgrade our 651 Mobility Controller (which we use for testing) to ArubaOS v6.2.1.0 and I am receiving a low memory message and need to delete some files on the controller.  Which files can be deleted without affecting anything on the controller?  The controller is currently at ArubaOS v6.1.3.0. Thanks!

do show boot

It will tell you which is the config file.  None of the other files are important so you can delete them... and even ifyou tried to delete the running config file it wont let you... but still check before.}

Try deleting the bigger files like backupflash files... also check if you dont have a image file in there... i once saw a image file on it

Also if you delete files and you see that you still missing storage... well you willl need to open a support case... they are the only ones that can get into some partitians through shell to delete files....

Not sure if it's memory or storage you're short on.  If it is memory, reboot the controller then upgrade immediately.  Generally you'll probably need to do this for 600 series controllers.

From the release notes, you'll need 40 MB for cli upgrade and 60 MB for WebUI upgrade.  Confirm with a show memory.

There is more memory needed if running the upgrade from the GUI.  Run the command from the CLI and it will work.

copy tftp: 10.10.10.10 ArubaOS_xxxxx system: partition 0  or partition 1

Ok I am looking at the same thing here on one of my Lab controllers ( model 651)     I have the same issue trying to upgrade to 6.2

This controller has no config on it, I cleared the Logs and the crash - and ran Write erase all

as for config all I have done it run the Quick Start for the defaults

CPBoot 1.0.0.0 (build 23274)
Built: 2010-01-19 at 11:11:22
DDR2 DRAM running at 466Mhz
DRAM:  Total = 512 MB
POST:  Memory test: Physical 0 - 0x10000000 - quick test
       Memory test: Physical 0x10000000 - 0x20000000 - quick test

(Aruba651) #show memory

Memory (Kb): total: 387684, used: 304108, free: 83576

(Aruba651) #show storage
Filesystem                Size      Used Available Use% Mounted on
/dev/mtdblock11         156.0M    117.6M     38.4M  75% /flash
none                    300.0M      1.6M    298.4M   1% /tmp
/dev/mtdblock9           50.0M     24.6M     25.4M  49% /mnt/img0
/dev/mtdblock10          50.0M     24.3M     25.7M  49% /mnt/img1

(Aruba651) #

I wanted to Post My Solution on this one.

I started by setting up an FTP server service on my MAC.  Google is your best freind here but it is very simple.

Then I copied the AOS image onto the root of the FTP server

Next I connected MAC to the same network as the controller (in my case static IP address and just plugged into Eth 1/0)

then from CLI I ran these commands - it worked like a charm

--------------------------------------------------------

(Aruba651) #show image version
----------------------------------
Partition               : 0:0 (/dev/mtdblock9) **Default boot**
Software Version        : ArubaOS 6.1.3.5 (Digitally Signed - Production Build)
Build number            : 35523
Label                   : 35523
Built on                : Fri Sep 28 07:46:05 PDT 2012
----------------------------------
Partition               : 0:1 (/dev/mtdblock10)
Software Version        : ArubaOS 6.1.2.2 (Digitally Signed - Production Build)
Build number            : 29541
Label                   : 29541
Built on                : Tue Aug 2 07:25:18 PDT 2011

(Aruba651) #show memory

Memory (Kb): total: 387684, used: 305848, free: 81836

(Aruba651) #show stora
Filesystem                Size      Used Available Use% Mounted on
/dev/mtdblock11         156.0M    117.2M     38.8M  75% /flash
none                    300.0M      1.7M    298.3M   1% /tmp
/dev/mtdblock9           50.0M     24.6M     25.4M  49% /mnt/img0
/dev/mtdblock10          50.0M     24.3M     25.7M  49% /mnt/img1

(Aruba651) #copy ftp: 172.16.0.10 <user>  ArubaOS system: partition 1       
Password:********
Copying file:................
File copied successfully.
Saving file to flash:
............................................................................................................................................................................................................................................................................................................................................................................................................................................................................................
The system will boot from partition 1 during the next reboot.
(Aruba651) #Shutdown processing started

tftp also works great!  I was experiencing the same error message while trying to upgrade my 620 controller in the lab via the GUI.