Wireless Access

 View Only
  • 1.  ArubaOS 8.6.0.12 to 8.10.0.5

    Posted Dec 31, 2022 06:19 PM
    I am planning an upgrade from 8.6.0.12 to 8.10.0.5 on our MM about 24 MD groups all clustered except for one group. We just purchased 9240's and we need to upgrade the MM to 8.10.0.5 to support the new controllers. Any one here is running MM 8.10.0.5 and have a few clustered MCs on version 8.6.0.12? Any issues you encountered? We cannot upgrade the controllers to 8.10.0.5 right away because we need to test clients first.  


  • 2.  RE: ArubaOS 8.6.0.12 to 8.10.0.5

    Posted Jan 01, 2023 09:37 PM

    https://www.arubanetworks.com/techdocs/ArubaOS/Consolidated_8.x_RN/Content/8.10/overview-8100x.htm

    Enhancement to Multiversion Support

    Multiversion is now supported for a Mobility Conductor that is running ArubaOS 8.10.0.0 version and the managed devices are running either ArubaOS 8.6.0.0, ArubaOS 8.7.0.0, ArubaOS 8.8.0.0, ArubaOS 8.9.0.0, or ArubaOS 8.10.0.0 version.



    ------------------------------
    Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba Networks.

    HPE Design and Deploy Guides: https://community.arubanetworks.com/support/migrated-knowledge-base?attachments=&communitykey=dcc83c62-1a3a-4dd8-94dc-92968ea6fff1&pageindex=0&pagesize=12&search=&sort=most_recent&viewtype=card
    ------------------------------



  • 3.  RE: ArubaOS 8.6.0.12 to 8.10.0.5

    Posted Jan 02, 2023 09:06 AM
    Thanks for the reply. I have read the documentation and understand that 8.6.0.12 is supported version with 8.10 MM.  I'm looking if anyone who has done this and if they encountered any issues. I wanted to just upgrade the MM to 8.10 and leave the MDs to 8.6.0.12 for a couple of months.


  • 4.  RE: ArubaOS 8.6.0.12 to 8.10.0.5

    Posted Jan 03, 2023 04:19 AM
    I had a customer situation where this happened. They had 7 Controller Clusters under the MM and needed a couple of months to upgrade all from 8.6.x to 8.10.x starting with the MM first. No issue in that situation.
    No guarantee because every installation is different.
    But it is a supported environment.



  • 5.  RE: ArubaOS 8.6.0.12 to 8.10.0.5

    Posted Jan 03, 2023 04:22 AM
    There may be some problems in the large version of mm and md,

    ------------------------------
    leo ma
    ------------------------------



  • 6.  RE: ArubaOS 8.6.0.12 to 8.10.0.5

    Posted Jan 03, 2023 11:02 AM

    I just upgraded from 8.6.0.16-FIPS to 8.10.0.5-FIPS on two wireless networks stepping through the major updates (8.7, 8.8. 8.9, then 8.10) as per suggested by the Aruba Federal Support team. One had all (7210) Campus APs and the other were all (7205) Meshed APs.  There was no issue for the Campus APs (Mostly 515's some 325's, 274, 374 and 375's. However, for the meshed APs (274's and 375's), everything was great until I was updating the last Controller to 8.10.0.5. I would update the Standby to the next higher version, then transfer the APs to it from the Master, then update the Master and transfer the APs back. The AP did reboot each time I transferred them obviously since they were getting the new version. For the Mesh network, I had done the final update on the Standby to 8.10.0.5 and transferred the meshed APs to it and everything looked good. I updated the Master to this final version and three 375's (Points) went down, there Portals were 274s. Since these are mounted high, I could not console in at their location, reboots at their location didn't change anything. I configured three new 375s Points, replaced them and all came up. The next day when I was trying to see why these APs went down by consoling in (I had a Portal in my test area), one of them was seen by the Controller and because (I believe) it had the same name as one of the new ones I had replaced the day before, this conflict shut down the new one. Rebooting again at the Point did no good. I configured another one and replaced it and it came up and has been up since the 22nd of December. Now, was it by chance I had 3 or 4 bad 375s? I have attempted to reset two of the "bad" APs via the console, and they are not even being seen by the Controller anymore. I am continuing to investigate these APs; I may have to RMA them. This is what I went through.