Wireless Access

last person joined: yesterday 

Access network design for branch, remote, outdoor, and campus locations with HPE Aruba Networking access points and mobility controllers.
Back to discussions
Expand all | Collapse all

Controllers 600 and 3000 Series Memory issue

This thread has been viewed 0 times

  • 1.  Controllers 600 and 3000 Series Memory issue

    Posted May 11, 2015 07:23 AM

    Dear All,

    we got many problems when Uploading The new ArubaOs FearmWere into the old mobility controllers , even when we empty the memory , any idea ?!

    Regards



  • 2.  RE: Controllers 600 and 3000 Series Memory issue

    EMPLOYEE
    Posted May 11, 2015 07:25 AM
    Tar logs tech support and then delete the file off the flash. That should clear a good amount of space.

    Thanks,
    Tim


  • 3.  RE: Controllers 600 and 3000 Series Memory issue

    Posted May 11, 2015 10:07 AM

    Hi,

     

    As colin suggested, try to use CLI to upgrade still if it is not resolved, we have to delete some files from the shell mode.



  • 4.  RE: Controllers 600 and 3000 Series Memory issue

    Posted May 19, 2015 07:07 AM

    some times the even the CLI upgrade do not work (specialy with 650 Conrolleur).



  • 5.  RE: Controllers 600 and 3000 Series Memory issue

    EMPLOYEE
    Posted May 19, 2015 07:10 AM
    ...and when that happens you should contact TAC to see if there are hidden files taking up space.


  • 6.  RE: Controllers 600 and 3000 Series Memory issue

    EMPLOYEE
    Posted May 11, 2015 07:25 AM

    1.  Try uploading firmware using the commandline (ftp, tftp), because it uses less memory.

    2.  If that does not work, open a TAC case, because they can delete hidden files that could consume memory.



  • 7.  RE: Controllers 600 and 3000 Series Memory issue

    EMPLOYEE
    Posted May 14, 2015 04:07 AM

    if there is enough flash but not enough memory, then you can also try upgrade from the CLI directly after rebooting the controller. The controller reboot will clear out a fair whack of memory (i.e. logs). Failing that, you may also need to purge the databases which run from memory after reboot, including WMS and AAA deviceid cache etc., then try reboot again.

    regards

    -jeff