Wireless Access

 View Only
last person joined: 4 days ago 

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

Mobility Conductor Upgrade 8.6 to 8.10

This thread has been viewed 132 times

  • 1.  Mobility Conductor Upgrade 8.6 to 8.10

    Posted Oct 26, 2022 09:33 AM
    Hi all,
    I am planning an upgrade from 8.6.0.12 to 8.10.0.4. I have a 2-node virtual Mobility Conductor cluster and several Controllers, some clustered and some not. I see in the 8.10 Release Notes that:

    Only for the ArubaOS 8.10.0.0 LSR release, ArubaOS 8.6.0.0 is treated as an LSR despite being beyond N-3. As such a Mobility Conductor running ArubaOS 8.10.0.0 supports managed devices running ArubaOS 8.10.0.0, ArubaOS 8.9.0.0, ArubaOS 8.8.0.0, ArubaOS 8.7.0.0 and ArubaOS 8.6.0.0.

    So, I wanted to confirm that I can upgrade directly from 8.6 to 8.10 and are there any problems I might run into? Can I upgrade the MM first and then maybe upgrade one controller to 8.10 to test before upgrading all the other controllers?

    Is the video ArubaOS 8.2 Series Part 6 - Upgrade MM & Cluster - YouTube
    still relevant?  Has anything changed with the upgrade process in 8.10?

    Thanks for your time.

    ------------------------------
    Dan O'Brien
    Network Admin
    Cirrus Aircraft
    ------------------------------


  • 2.  RE: Mobility Conductor Upgrade 8.6 to 8.10

    MVP GURU
    Posted Oct 26, 2022 10:00 AM
    Yes, you can go directly to 8.10.0.4 from 8.6.0.12. Start by upgrading the MMs, and then the Managed Device / Controllers. As explained with the backwards compatibility or "multi-version support", your MM can be on 8.10, and you can still manage 8.6, 8.7, 8.8, and 8.9. Usually its only supported to manage up to 3 revisions back, but Aruba extended this to 4 revisions back due to 8.6 being the last LSR.

    ------------------------------
    Dustin Burns

    Lead Mobility Engineer @Worldcom Exchange, Inc.

    ACCX 1271| ACMX 509| ACSP | ACDA | MVP Guru 2022
    If my post was useful accept solution and/or give kudos
    ------------------------------

    Original Message


  • 3.  RE: Mobility Conductor Upgrade 8.6 to 8.10

    Posted Dec 31, 2022 06:47 PM
    Hello,

    We are in the same process right now. We are purchasing the 9240s and in order to support the new hardware  we need to go to version 8.10. Were you able to do this? How long until you upgraded the  controllers to 8.10? We were told by our Aruba rep that its not recommended to run on 8.6.0.12 with 8.10.0.5 MC which I find it very odd.  Any issues you encountered?
    Original Message


  • 4.  RE: Mobility Conductor Upgrade 8.6 to 8.10

    MVP GURU
    Posted Jan 03, 2023 09:52 AM
    "We were told by our Aruba rep that its not recommended to run on 8.6.0.12 with 8.10.0.5 MC which I find it very odd.  Any issues you encountered?"

    They extended how far back 8.10 could manage (8.6) in order to help customers transition from the 8.6 long support release to the next 8.10 long support release. Unless you have a need to keep a controller at 8.6 I would upgrade.

    ------------------------------
    Dustin Burns

    Lead Mobility Engineer @Worldcom Exchange, Inc.

    ACCX 1271| ACMX 509| ACSP | ACDA | MVP Guru 2022
    If my post was useful accept solution and/or give kudos
    ------------------------------

    Original Message


  • 5.  RE: Mobility Conductor Upgrade 8.6 to 8.10

    Posted Jan 03, 2023 11:01 AM
    DB86 - Thank you for your reply. We are definitely upgrading all of them to 8.10. I just wanted to know if anyone has 8.6.0.12 with 8.10 MC and how long they have it running before upgrading to 8.10. The issue that we have is the 9240 not supported on 8.6.0.12 and we need to upgrade the MC first to 8.10. I need to create a plan on upgrading the controllers to 8.10 and test the clients first.
    Original Message


  • 6.  RE: Mobility Conductor Upgrade 8.6 to 8.10

    Posted Feb 06, 2023 05:33 PM
    I upgraded the MM 8.6 to Mobility Conductor 8.10 a couple days ago.  It wasn't as seamless as the video showed, but almost.  The backup MM took over and then I had a little trouble getting on it to do the upgrade.  But eventually I got both of them upgraded to 8.10.  Then it took a little over an hour for all the APs and clients to show up in the 8.10 dashboard.  But I can confirm that it works - I have 19 controllers still on 8.6, some clustered, some not.  Next, I will be standing up a new virtual MC and do a little testing, then upgrading them all to 8.10.

    ------------------------------
    DanOBrien
    ------------------------------

    Original Message


  • 7.  RE: Mobility Conductor Upgrade 8.6 to 8.10

    Posted Sep 06, 2024 02:12 PM

    hello there.... i know this is 1.5 yr old post by now , but i have a simple question for ya....  i also have Virtual MM, and attemtping an Upgrade 8.10.x -> 8.10.x  and got "Error in Upgrade..." prompt.

    the question is WHICH file did you use for Virt.MM upgrade.... the 'FILE' , or the OVA  or the ISO version of the file ?

    i have a TAC opened, but time isn't on my side at moment, is why i'm looking thru the Boards.

    thnx ! 


    Original Message


  • 8.  RE: Mobility Conductor Upgrade 8.6 to 8.10

    Posted Sep 06, 2024 02:23 PM

    Hi Eddie,

    It would have been the file, not the OVA and if I recall correctly, the upgrade to 8.10 worked fine.  But I never got the virtual environment to work for me.  I don't know if it was something in our VMWare infrastructure or what, but communication between the APs and the controllers was not reliable.  Provisioning new APs was pretty much impossible without a console cable and hard-coding the controller IP.

    We have since moved all 300 APs to AOS 10 and Central.  There are pros and cons to the Central vs. Controller environments, but Central is working well for us.



    ------------------------------
    DanOBrien
    ------------------------------

    Original Message