Monitoring, Management & Location Tracking

How does Airwave handles upgrades of hybrid IAP cluster

I have a cluster of 5 IAP - 105's and they are being monitored/managed by Airwave. What should I expect when I add an IAP 135 to the existing cluster.


This article implies to all versions of Airwave


Different IAP hardware requires different firmware version to operate. Below is the details of it.


Firmware Hardware
ArubaInstant_Aries   Aruba Instant code for RAP-155 and RAP-155P
ArubaInstant_Cassiopeia   Aruba Instant code for IAP-134 and IAP-135
ArubaInstant_Centaurus     Aruba Instant code for IAP-224 and IAP-225
ArubaInstant_Orion           Aruba Instant code for IAP-92, IAP-93, IAP-104, IAP-105, IAP-175, RAP-3WN and RAP-3WNP
ArubaInstant_Pegasus   Aruba Instant code for RAP-108, RAP-109, IAP-114 and IAP-115

If we have a cluster with IAP 105's (they run on ArubaInstant_Orion) and we add a new IAP - 135 (it runs ArubaInstant_Cassiopeia), then the VC (Virtual Controller) would not be able to upgrade the IAP - 135 to the code of the cluster.

If Airwave is monitoring or managing the cluster and we have the below options enabled, the IAP will fetch the firmware file from Airwave and instantly upgrade to the code of the cluster.

We must have the firmware file uploaded on the Airwave.

Navigate to Device Setup -> Upload Firmware and files and add the firmware file.


If the IAP are in monitor mode, we must allow firmware upgrade in Monitor only Mode.

Navigate to AMP Setup -> general page and enable the below option.


Version history
Revision #:
1 of 1
Last update:
‎06-26-2014 02:03 PM
Updated by:
Labels (1)
Search Airheads
Showing results for 
Search instead for 
Did you mean: 
Is this a frequent problem?

Request an official Aruba knowledge base article to be written by our experts.