Wireless Access

trying to upgrade 620 controller and i get the error "Not enough flash space".  cleaned everything out of filesystem that is not needed and rebooted still not enough space.

(controller_140) #dir  
-rw-r--r--    1 root     root        22111 Mar 15 09:15 20130313-config
-rw-r--r--    1 root     root        22266 Mar 15 10:13 default.cfg
drwx------    2 root     root            0 Mar 15 09:36 tpm

(controller_140) #show memory
Memory (Kb): total: 387684, used: 294104, free: 93580

(controller_140) #show storage
Filesystem                Size      Used Available Use% Mounted on
/dev/mtdblock11         156.0M    118.7M     37.3M  76% /flash
none                    300.0M      2.2M    297.8M   1% /tmp
/dev/mtdblock9           50.0M     24.8M     25.3M  50% /mnt/img0
/dev/mtdblock10          50.0M     24.5M     25.5M  49% /mnt/img1

type "tar crash" to see if there is a crash.tar file.  If there is, delete it, reboot and try again.

(controller_140) #tar crash
No crashes found on this machine.

Please open a support case.  TAC could see if there are any "hidden" files that can be removed...

I had the same problem and got back enough space after deleting all but two saved configs.

Upgraded the Controller using the CLI instead of GUI and it worked fine.

(controller_140) #copy tftp: 172.20.21.145 ArubaOS_6xx_6.1.3.7_37112 system: partition 1
Copying file:..........................
Saving file to flash:
..........................................................
(controller_140) #
(controller_140) #show image version
----------------------------------
Partition               : 0:0 (/dev/mtdblock9)
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) **Default boot**
Software Version        : ArubaOS 6.1.3.7 (Digitally Signed - Production Build)
Build number            : 37112
Label                   : 37112
Built on                : Fri Feb 8 18:08:20 PST 2013

(controller_140) #
(controller_140) #write memory
Saving Configuration...

Configuration Saved.

(controller_140) #

it worked with me just one time, when i tried again i got the free space error message!!!, any help please??!!!1

Try from the commandline or contact tac to see if there are any hidden files.

i did from CLI , no result, i am waiting reply from the TAC team

ran into the same problem trying to upgrade my controller to 6.3 only  this time the GUI and the CLI did not work.  I had to boot off the inactive partition (1) then upgrade partition 0 with the CLI and it worked.

Reboot the controller with the secondary boot partition is the best solution to upgrade a controller without free space in the flash.

After the rleoad with the second partition I can upgrade the ARUBA 650 controller with a new firmware:

(Aruba650) #boot system partition 1

(Aruba650) #reload

(Aruba650) #copy tftp: 10.10.10.10 ArubaOS_6xx_6.4.4.9_55980 system: partition 0

Will the controller automatically try to boot from the newer OS - and revert to the backup OS - when it is rebooted?  Or do I have to set the boot partition to the newer image?

check and see which partition is being used to boot. with the command show image version. Set the system to boot from a partition with the command boot system partition 0 OR boot system partition 1

(controller_140) #show image version
----------------------------------
Partition               : 0:0 (/dev/mtdblock9) **Default boot**
Software Version        : ArubaOS 6.3.1.2 (Digitally Signed - Production Build)
Build number            : 41362
Label                   : 41362
Built on                : Wed Dec 18 17:35:16 PST 2013
----------------------------------
Partition               : 0:1 (/dev/mtdblock10)
Software Version        : ArubaOS 6.1.3.7 (Digitally Signed - Production Build)
Build number            : 37112
Label                   : 37112
Built on                : Fri Feb 8 18:08:20 PST 2013

(controller_140) #boot system partition 1

Thank you.  That's what I thought.  It would be nice if the OS could automatically try to boot from the newer OS version first and then fail to the other partition if it can't boot.  this would allow you to force the boot partion with the boot system partition command, or have it boot to the newer OS automatically.

Actually that is what happens. Let me be more clear. When you upgrade a partition to a new version of code that partition gets set as the default boot partition on the next boot.  It does not automatically boot the system b/c that allows you to load the software during production hours and reboot/upgrade the system after hours.  If the system cannot boot off the new code it will reboot into the old partition with the previous version.

Thank you.  That was helpful.  I've been waiting for about 45 minutes for the tftp upload to complete.  I'm still getting the scrolling periods (.........), but I'm beginning to think that this thing is in trouble.

I had first tried doing this upgrade through the GUI, but that failed.  I got the "not enough space" error, then rebooted and tried again.  I didn't get the error the second time, but something happened and the older image in partition 1 (3.4) got corrupted - I am booted off of partition 0.