Wireless Access

 View Only
  • 1.  Cluster and AP Preload Image

    Posted May 20, 2025 02:26 PM

    We're running a cluster containing one hardware MM and two hardware MDs. Before upgrading the MM and MDs, I'd like to preload the APs. Do I do this from the MM or on each MD separately? I can't seem to find any documentation regarding best practices. Thank you.



  • 2.  RE: Cluster and AP Preload Image

    Posted May 20, 2025 10:46 PM

    here is the procedure for it

    https://arubanetworking.hpe.com/techdocs/ArubaOS_8.12.0_Web_Help/Content/arubaos-solutions/access-points/ap-imag-pre.htm



    ------------------------------
    If my post was useful accept solution and/or give kudos.
    Any opinions expressed here are solely my own and not necessarily that of HPE or Aruba.
    ------------------------------



  • 3.  RE: Cluster and AP Preload Image

    Posted May 21, 2025 04:00 AM

    Hi, 

    depends on the downtime that is acceptable for you. If you do not want to perform a live upgrade (these are performed via the MM), I recommend the following procedure: 

    1. On the MM:
    a) Flash and configuration backup of the MM
    b) Preload the new firmware on unused flash on the MM
    c) Reboot the MM from flash with new firmware
     
    2. On the respective MD:
    a) Flash and configuration backups of the controllers
    b) Preload the new firmware on unused flash on the MDs
    c) AP preload of the new firmware on the respective MDs (APs are distributed to all MDs by active-active-cluster)
    d) Sequential reboot of the MDs (minimizes downtime) from flash with the new firmware
     
    As soon as the first controller with new firmware comes up, the APs restart with their new firmware. Depending on the number of APs and controllers, the restarted APs can then run productively via the one controller that has already been updated.
    I always carry out the preload of the MDs and APs and the backup on the physical addresses of the respective controllers, as this is an active-active cluster and all APs and clients are therefore distributed to the controllers. 
     
    The alternative is an inplace update carried out via the MM. However, I only use this if a downtime is not possible. Such an update requires much more time to be executed. 
    Best,
    Levi



  • 4.  RE: Cluster and AP Preload Image

    Posted May 21, 2025 06:41 AM

    Before we had an active-active setup, I used to just install the image and do a straight reboot. However, moving to AOS 8 with a cluster, one of the main selling points is the upgrade feature with no downtime. It would take 3+ hours though and wasn't always problem free.




  • 5.  RE: Cluster and AP Preload Image

    Posted Jun 02, 2025 08:49 AM
    Edited by WS-97c8bb Jun 02, 2025 09:16 AM

    One part that is confusing is the AP preload gui. It asks to select a partition. Is this the partition on the AP itself to preload the image? If so, how do I know which partition to install it choose? Ideally I want to keep the old image installed alongside the new one incase we need to flip back.




  • 6.  RE: Cluster and AP Preload Image

    Posted Jun 03, 2025 05:30 AM

    Hi,

    The partitions displayed are those of the controller. You select which of the images should be pushed to the APs. 
     
    If you want to roll back, you must restart the controller from the old image. The APs will be downgraded accordingly. 
     
    As far as I know, it is not possible to select the AP image via the controllers as with an IAP installation. 
    Best


    ------------------------------
    Levi Mahncke
    - ACX-NS
    ------------------------------



  • 7.  RE: Cluster and AP Preload Image

    Posted Jun 03, 2025 09:45 AM

    I followed your step-by-step and the only part that did not work for me was after I upgraded controller #1 and rebooted, the APs just fell over to the other switch running the older version of AOS 8. It wasn't until I upgraded/rebooted controller #2 that the APs rebooted and were then redistributed between controllers. 

    For context, I went from 8.7.1.11 to 8.12.0.5.