Network Management

last person joined: yesterday 

Keep an informative eye on your network with HPE Aruba Networking network management solutions
Expand all | Collapse all

AirWave IAP Firmware Upgrade Reboot Behavior

This thread has been viewed 3 times
  • 1.  AirWave IAP Firmware Upgrade Reboot Behavior

    Posted Feb 16, 2016 11:32 AM

    Hi All, When scheduling an AirWave controlled firmware upgrade for an IAP cluster I can specify how many devices per job will upgrade at a time. How do the APs get selected for this? Does it perform a staggered upgrade approach so that some services are available nearby?

     

    Use case: If I have 20 APs and I specify a max of 2 at a time, will the cluster clientmatch clients to other APs and perform upgrades on APs that are not in the same RF neighborhood?

     

    Trying to figure out a minimal impact daytime upgrade process if its possible.

     

    Thank you,

     

    -n



  • 2.  RE: AirWave IAP Firmware Upgrade Reboot Behavior
    Best Answer

    EMPLOYEE
    Posted Feb 16, 2016 12:20 PM

    "Firmware Image Management -- AirWave pushes firmware to the Aruba Instant Virtual Controller, and the Virtual Controller pushes the firmware to the rest of its IAPs. When using AirWave to manage IAPs, you can upgrade the firmware by loading the firmware onto AirWave, and then scheduling an upgrade from AirWave. If you have a mixed deployment with multiple Instant products, AirWave allows you to upload firmware for each of the device types."  - http://community.arubanetworks.com/aruba/attachments/aruba/SoftwareUserReferenceGuides/56/1/DeployingInstantInAirWave.pdf

     

    If you have a cluster with only a single model, Airwave only pushes it to the Virtual Controller and the virtual controller is responsible for pushing it to the other APs in the cluster.  You need to schedule downtime, because there is not a planned effort to maintiain uptime for clients when a firmware upgrade is going on...



  • 3.  RE: AirWave IAP Firmware Upgrade Reboot Behavior

    Posted Feb 16, 2016 02:15 PM

    That clears it up, thanks!