User guide

6 AirWave 7.4.0 | Release Notes
 IAPs in an Aruba Instant implementation can be rebooted all at once in AMP.
Support has been extended for Aruba Remote Access Points (RAPs) that will run an upcoming version of
ArubaOS:
 The Device Info section in the APs/Devices > Monitor page for a RAP now displays the Remote LAN
IP Address (used for local network troubleshooting), Tunnel IP Address (used for testing controller
connectivity), and Outer IP Address (tracks RAP location or an ISP-modified address). Any changes to
any of these IP addresses are logged.
 The Device Info section also includes Active Uplink (either Ethernet or USB) information for the
RAP if it’s on a 6.2.x.x controller.
 The APs/Devices > Monitor page for a RAP includes a USB Interface Summary section with the
device number, network service level, status, operational status, RSSI, and usage. USB usage is tracked
in the RAP’s Usage (formerly Bandwidth) graph.
 A new trigger called Device Uplink Status has been added to System > Triggers. This trigger deploys
whenever the active uplink changes from Ethernet to USB or vice versa. The corresponding events are
captured in a RAP’s APs/Devices > Monitor page.
 APs/Devices > Monitor pages for RAP devices now include a second set of Quick Links with RAP-
specific debugging commands such as
show ap database usb, show ap debug usb ap-name <ap-
name>
, ping and traceroute.
Added mesh support for the Aruba AP-175 such as link signal, link signal-noise ratio, link tx/rx rate, and
mesh cluster ID.
Added support for Aruba AP Up/Down traps. On ArubaOS firmware version 6.1, AMP only responds to the
wlsxNAPMasterStatusChange trap. On earlier versions, AMP uses the wlsxNAccessPointIsUp and
wlsxNAccessPointIsDown traps.
Additionally, AMP ignores wlsxNAccessPointIsDown if it arrives from a different controller than the AMP
knows it to be on. Polling is necessary with this change because previously AMP would not detect a change
in the switch role unless AMP audited the controller, and groups can now have audit disabled.
AMP now monitors interfaces on Aruba controllers to help facilitate wired user monitoring. On an Aruba
controller that uses templates for configuration, the interfaces that go into the template are now called
“Managed Interfaces” on the APs/Devices > Manage page to prevent confusion with the monitored Aruba
interfaces that will appear in the APs/Devices > Interface Monitoring tab.
Wired users can be monitored on Aruba controllers, including tunneled users. The total client count on an
Aruba AP Group page now includes clients on controllers. The Client Count graph in APs/Devices >
Monitor page for Aruba controllers now includes wired clients.
RAPIDS
Rogue clients are now tracked on AMP as follows:
 Full search results on a regular AMP (not Master Console) now include rogue clients in their own
section, visible only to users with access to RAPIDS information.
 A new subtab has been added under the Clients (formerly Users) tab named Rogue Clients, which
displays valid and currently connected rogue clients. Selecting a MAC address will jump to the Clients >
Client Detail page for that rogue client. Selecting the Rogue AP link will jump to the RAPIDS > Detail
page for that AP.
 In Clients > Client Detail, a new table called Rogue Association History displays historical rogue
associations for the selected client.
 In RAPIDS > Detail, a new table has been added called Rogue Client Associations.
 A new trigger called Client on Rogue AP has been added under IDS Events, with two conditions:
Classification of Rogue Device, and Client Type (valid or otherwise). For instance, this trigger can be set