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

aruba controller upgrade procedure

This thread has been viewed 9 times

  • 1.  aruba controller upgrade procedure

    Posted Mar 08, 2016 10:14 PM

    Hi All,

     

    I'm Tasked to upgrade a set of Aruba controllers,

     

    1 Master controller , 1 backup controller and 8 Local controllers.

    10xAruba7220

     

    Please advise how to proceed the upgrade with the local first or master or sec.

    and also please advise which is suitable new AOS for Aruba7220.

     

    Thanks in advance.



  • 2.  RE: aruba controller upgrade procedure

    EMPLOYEE
    Posted Mar 09, 2016 06:27 AM

    The big question is, why are you upgrading in the first place?

    If you are planning to upgrade, the release notes will give you the proper upgrade instructions.

     



  • 3.  RE: aruba controller upgrade procedure

    Posted Mar 09, 2016 06:35 AM

    Hi,

     

    Customer is planning additional Aruba 205 APs, current version of AOS doesn't support this APs.

    Aruba 205 requires Minimum ArubaOS 6.4.1.0.

    Current AOS in all controllers are 6.3

     

    Thanks.



  • 4.  RE: aruba controller upgrade procedure
    Best Answer

    EMPLOYEE
    Posted Mar 09, 2016 06:45 AM

    ArubaOS 6.4.3.7  is the latest GA code, and that is what you should use.  

    You would typically

     

    - Identify any current issues with the customer's network.  If they are bad issues, they should be troubleshot until resolved, before your upgrade.

    - Upgrade the master and backup master

    - Upgrade all of the other controllers at the same time, if possible.

     

    If you want to upgrade them all at the same time, it is important that you do not have any access points rebooting, because having the master and any of the locals on a different version of code could cause a bootloop, where rebooting access points will not recover until all controllers are on the same version of code.