**PLEASE NOTE: This articles assumes that all devices are already added to Airwave successfully with valid SNMP credentials and are NOT in the "New Devices" list.
If you are monitoring your Aruba Controller Network with Airwave, you SHOULD always have AMON turned on. Here's why:
- Spectrum information, like discovered non-wifi interferring devices is only transmitted to Airwave over Amon:
*Spectrum Information requires that access points are put into Spectrum Mode or Hybrid Spectrum Mode. Spectrum Analysis requires the RFProtect License http://www.arubanetworks.com/assets/ds/DS_AOS_RFPR
- Access Point Channel Utilization information like Channel Busy, Interference, Receiving and Transmission time is only transmitted to Airwave over Amon: (search for access point> click on radio and you should see this graph).
- Client statistics like goodput and client association rate (speed) is only transmitted over Amon. This also allows the latest versions of Airwave to present RF performance statistics by folder. (in Airwave, click on Home> RF performance to see this graph).
- Clients associating and leaving the user table are updated to Airwave more frequently via AMON vs. every 5 or 10 minutes via SNMP polling. In ArubaOS 6.2 and above you can also observe how frquently the station statistics are sent. with the "show mgmt-server message-counters process wms" command. You will see less lag between when a client associates and when it shows up in Airwave.
Okay. So how do you configure Amon?
1. Configure your Aruba Controller to send Amon statistics to an Airwave server using the "mgmt-server type amp primary <ip address of Airwave Server>" command on the commandline (220.127.116.11 ONLY).
EDIT: Please note, that as of ArubaOS 18.104.22.168 the format of that command has changed and now you have to define a mgmt-server profile first to send that information to airwave: You need to define a profile, configure what type of stats you want sent and then turn it on:
(3600Controller) config t
(3600Controller) (config)mgmt-server profile default-amp <----------Define Profile
(3600Controller) (Mgmt Config profile "default-amp") #?
clone Copy data from another Mgmt Config profile
location-enable Station RSSI/AP Neighbours enable <---- Send Location Info
misc-enable AP System Stats/Spec Dev/Station Steer Info enable <------- Send ClientMatch Stats
monitored-info-enable Monitored AP/Station Info enable <------ AP Station Info
monitored-stats-enable Monitored AP/Station Stats enable <---------- AP Station Stats
no Delete Command
sessions-enable Firewall DNA/App/Aggregate Sessions enable <---------- Send Firewall Data
stats-enable Radio/VAP/Station Stats enable <------- Send AP radio Info
tag-enable Tag enable
voiceinfo-enable Voice Call Record enable
(3600Controller) (Mgmt Config profile "default-amp") #stats-enable
(3600Controller) (Mgmt Config profile "default-amp") #sessions-enable
(3600Controller) (Mgmt Config profile "default-amp") #misc-enable
(3600Controller) (Mgmt Config profile "default-amp") #location-enable
(3600Controller) (config) mgmt-server type amp primary-server 192.168.1.6 profile default-amp <------Set the server and attach the profile
2. On the Airwave Under AMP Setup> General> Additional AMP Services, make sure the "Enable AMON Data Collection:" option has a Yes radio button selected next to it.
3. Make sure that if you have a firewall between your controllers and your Airwave Server you are allowing the PAPI protocol or UDP 8211 in both directions between them.
In addition, in ArubaOS 6.3 if you enable Application Visibility on the controller (config t firewall-visibility) and you are running Airwave 7.7 and above, you will also be able to visualize application traffic in realtime, as weill as historically in Airwave:
Last but not least, in Airwave 7.7.0 and above, under AMP Setup> General > Additional AMP Options you need to enable the following options:
More information on additional settings to get the most out of Airwave is in the AMP AirWave and Aruba Best Practices guide on the support site here: