User guide

AirWave 7.5.6 | Release Notes 5
Aruba AirMesh Enhancements
AirMesh enhancements for 7.5 fall into one of two categories: Monitoring and Configuration.
AirMesh Monitoring
 New AirMesh products were released in March 2012 with the new bootloader “APBoot <ver>” label,
which is consistent with the other Aruba APs. AirWave helps to identify this new from the old SKUs
(such as “Redboot <ver>”) by displaying the bootloader information now on the APs/Devices >
Monitor and APs/Devices > List pages as well as in the Inventory Report.
 AirWave can now automatically discover other mesh nodes in the same mesh cluster.
 AirWave warns the user if AirMesh APs in a group are not organized by mesh ID. A message will display
on all of the Group pages if the APs are not organized by the mesh ID.
 It is possible to discover orphan nodes from AirWave. User can click on the Orphan Recovery button
on the APs/Devices > Monitor page to recover the orphaned node from the neighboring node. AirWave
runs the orphan recovery from the last known neighbor of that node.
 Added support for quick links used for fetching troubleshooting information related to AirMesh APs,
radios, and clients. The following commands have been added.
 AP Monitoring commands:
 show mesh candidates
 show mesh links
 show mesh neighbors
 show mesh node-list
 show mesh portals
 show mesh route
 ping
 traceroute
 Radio Statistics commands:
 show interface dot11radio <radio_index> [bss | (sta <all>)]
 show client-list stats dot11radio 0
 show client mac <mac_address>
 AirWave added support for AC/DC variants of MSR-200/AP-175 and MSR-4000 devices.
AirMesh Configuration
 AirMesh devices can be configured using templates. AirWave automatically adds a template for the first
AirMesh AP in a group. After an AP import, some values will be retrieved by SNMP, and the template will
be written to a file in the AMP FTP server. The flow of the configuration push is done via FTP. As such,
upon completion, the AP will get the configuration by FTP. The configurations are pushed using CLI
commands.
 AMP warns the user if AirMesh APs attempting to upgrade or push configurations lack write
permissions. The Image Upgrade Log and CLI Extension Log are now retrieved from the AirMesh AP
upon completion of the upgrade and CLI execution. The logs are stored in ap.log.
 AMP now automatically restarts the FTP server during an AirMesh configuration push or upgrade.
Cisco Device Support
Support was added for the following Cisco devices in 7.5.4:
 WLC: 7500
 LWAPP: 600, 3600, AP801