Dell | PowerConnect W-AirWave 7.4 | User guide | Dell PowerConnect W-AirWave 7.4 User guide

AirWave 7.5.6
Release Notes
This document describes new features and resolved issues in this AirWave release.
“What’s New in This Release” on page 1
“Changes” on page 3
“Resolved Issues” on page 6
“Known Issues” on page 16
What’s New in This Release
Authentication with LDAP
AMP users can be authenticated using LDAP in addition to TACACS and RADIUS. This option is
configurable on the AMP Setup > Authentication page. When enabled, users can specify the primary and
secondary host name and port servers, the connection type, the key and role attributes, and the bind
password. This implementation also supports verification of the server's certificate when the Connection
Type is specified as start-tls. The server certificate can be added on the Device Setup > Certificates
page. After this is added, users can specify optional or require in the Verify Server Certificate drop
down menu.
More information about LDAP authentication can be found in RFC 4513.
Authentication Priority
Local and remote authentication priority order is now user selectable. If Local is selected, then remote
authentication will only be attempted if the user is not present. If Remote is selected, then the local
database is searched if authentication on the remote server fails. The order of remote authentication is
RADIUS first, followed by TACACS, and finally LDAP.
Recurring Configuration Changes
Users now have the option to schedule configuration options (such as disabling radios) as recurring.
Scheduling provides a way for you to inform users on your network of upcoming down-time and helps with
planning tasks such as upgrading. Click on Save and Apply, Import Settings, or Reboot on the APs/
Devices > Manage (for device maintenance) or on the Groups > Basic page (for group maintenance) to
view a prompt for setting the changes as recurring.
Configurable Client Diagnostics
The thresholds used for Client diagnostics are now configurable. Select a connected client from the APs/
Devices page to view the client. Navigate to the Diagnostics tab, and click the Thresholds button on the
lower-right corner of the page to adjust the threshold values for Good and Fair. The new values will be
applied globally to diagnostic views for all other AirWave user roles.
0511066-09 | Oct 2012
Suppressing Alerts if the Upstream Device is Down
A new setting available on the Device Down trigger suppresses alerts if the upstream device is down. The
behavior of existing triggers is preserved upon upgrade to 7.5, but the setting is enabled by default for new
triggers. AirWave users can combine the new setting with the Minutes Down threshold to allow enough
time for AirWave to determine the state of the upstream device.
Improved “Replace Hardware” Workflow
An improved Replace Hardware workflow makes it easier for AirWave users to find a new installed AP
and to select a replacement device for a Down AP. Users are presented with a list of devices in AirWave that
match the name or IP address of the device to be replaced. The workflow also offers users the ability to
select any device in the New Devices list or in the current folder or group.
A Replace Hardware button has been added to the AP/Devices > New Devices page and in the APs/
Devices > Manage page for a single device. In addition, users can select multiple devices to manage by
clicking on the Modify Devices link in the AP/Devices > List page. The Replace Hardware button is
included in this form so that users can replace hardware for multiple new or down devices at once.
If only one device is selected AMP provides an option to select the replacement device. When multiple
devices are selected, AirWave attempts to match the replacement device for each selected device based on
the Hostname/IP Address of the device to be replaced. Note that the Hostnane/IP Address must match in
order for the hardware replace to be successful.
MAC Address Search Enhancements
MAC address searches initiated from the Full Search screen no longer require colons, and searches will
match on substrings. For example, searching for ‘ABCD’ will now return matches that contain ‘AB:CD’ as
well as ‘A:BC:D.’ If desired, delimiters other than colons can be used, such as ‘A.B.C.D’ or ‘A-BC-D.’
Noise Floor Trigger
Added a new Noise Floor trigger. Users can specify a dBm threshold and timer value, and the trigger will
send an alert if the noise floor is greater than the specified value for the specified period of time.
Configurable Mail Relay Server
Users can now configure a single relay host for the embedded mail server on the AMP Setup > General >
Additional AMP Services page. If “Use embedded mail server” is Yes, then a “Mail relay server” field
displays along with a text input field for the relay host. This optional field accepts a single, valid host name
or IP address. If the user does not enter a relay host, the default is to use the postfix configuration in which
AMP tries to deliver mail directly.
Additional Localization Support
The AirWave login screen now provides the following additional languages.
Traditional Chinese
AMP will remember the selected language until you log out and select another. Within the UI, a limited set
of elements have been localized.
AirWave 7.5.6 | Release Notes
New Diagnostics Graph
The 7.5.4 release introduces a new graph on the System > Performance page. The graph shows the current
number of Web server connections and the current number of database connections over a period of time.
This new graph provides better visibility into errors that may occur due to Web server connection limits.
Changes to AMP were added in the following general categories:
“Browser Updates” on page 3
“VisualRF Enhancements” on page 3
“Platform Enhancements” on page 3
“Aruba Enhancements” on page 4
“Aruba AirMesh Enhancements” on page 5
“Aruba Instant Enhancements” on page 4
“Cisco Device Support” on page 5“Security” on page 6
Browser Updates
Support for IE 7 has been deprecated in this release. Users are encouraged to upgrade their browsers to
newer versions of Internet Explorer. A complete list of supported browsers is available in the AirWave
7.5.6 User Guide.
VisualRF Enhancements
When matching a new planned device with a managed device, the Match With Managed Device
window now allows you to search managed devices based on the device’s Group or Folder.
When planning a new region, users can now specify the AP to Sensor ratio. In prior versions of VisualRF,
this was hard coded to 4 APs per sensor.
Platform Enhancements
New installations of AirWave are built on the CentOS 6.2 platform. Installs performed on Red Hat
Enterprise Linux 6.2 are also supported.
In 7.5, migration from a 5.x install to 6.2 is not required, but 5.x support will end in a future release. To upgrade to
CentOS 6.2, back up your AirWave server to a safe location, and then do a clean installation from the AirWave ISO
that includes CentOS 6.2 (7.5 or higher). After CentOS 6.2 is installed, you can restore your AirWave backup. Refer
to the AirWave 7.5 User Guide for information on backing up and restoring AirWave.
A new command was added to the Run a command drop down menu on the Clients > Client Detail
show datapath session table <ip_address>
This command replaces the show datapath session | include <ip_address> command.
When the name of a device is changed under the Modify Devices window on the AP > Manage page,
the device’s check box is automatically selected.
The table on the APs/Devices > List page can now be filtered by the Type and Floor Plan columns.
The Inventory Report now displays a count of devices running each version of firmware. In addition,
the existing Firmware Version Summary section was renamed Model/Firmware Version Summary.
This summary now displays the manufacturing model information in addition to the firmware version.
AirWave 7.5.6 | Release Notes
When e-mailing an Uptime Report, users can now select whether the sort order should be based on the
lowest uptime or the highest.
An option is provided under AMP Setup > General > Additional AMP Services to configure a
collection of syslog messages and traps. Customers who are concerned about the effect that syslog
collection may have on performance of their AirWave server can either adjust how their controllers are
configured to send data or they can disable processing the data in AirWave. Please contact AirWave
customer support for more information on how to change this setting.
Improved performance speed-up for load times of the Aruba controller audit pages.
A new setting is available for specifying the number of days that pass before expiring unapplied changes
that are stored in the AirWave database. It is not uncommon for customers to perform multiple
configurations before applying the changes, and each of those unapplied changes remains as a row in
the database. This results in a much slower experience when the changes are finally applied. Allowing
users to configure the number of days before expiring unapplied changes helps to clear out orphaned
change sets and provides a more seamless experience when applying changes. Please contact AirWave
customer support for more information about configuring this new setting.
Aruba Enhancements
The SSH port for Aruba controllers is now configurable on the APs/Devices > Manage page.
Added support for the wlsxNUserEntryAuthenticated trap from Aruba devices for client-role and IP
address information.
Support has been added for the following devices:
Aruba RAP-3WN and RAP-3WNP
Aruba AP-93H
Aruba AP-104
Aruba S2500 Mobility Access Switch
AirWave users can upload and manage certificates as part of the desired configuration for Aruba
physical and virtual controllers. Certificates can be uploaded on the Groups > Certificate Detail page.
PEM, DER, PKCS#7, PFX, AND PKCS#12 are supported.
Added support for configuring the new AOS User Derivation Rule attribute ‘dhcp-option’ starting with This is available from Device Setup > Aruba Configuration when adding a new User Rule.
An Auto Detect option is now available in the AP Group drop-down menu when a user authorizes
Aruba thin APs at the group level instead of globally and then selects a different AP Group per AMP
Group. This new option is especially useful for users who perform configurations at the group level
instead of globally and for users who set the name and AP group directly on the controller, as the
information is read from the device.
Active SSIDs for Aruba radios now display on the APs/Devices > Monitor and APs/Devices > List
pages as well as in the Inventory Report.
Aruba Instant Enhancements
Added support for Aruba Instant (Titan release)
Extended support for the following features in the Aruba Instant template:
VPN Profile
DHCP Profile
OpenDNS Profile
AirWave users can upload and manage certificates as part of the desired configuration for Aruba
physical and virtual controllers. Certificates can be uploaded on the Groups > Certificate Detail page.
PEM, DER, PKCS#7, PFX, AND PKCS#12 are supported.
AirWave 7.5.6 | Release Notes
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
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
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
AirWave 7.5.6 | Release Notes
ISR: 881, 881G, 891, 1941
In addition, monitoring support was added for 7.2 Cisco WLC firmware.
The following packages were updated with security-related fixes:
lipng: (libpng-1.2.10-17.el5_8 and libpng-1.2.491.el6_2)
httpd: (httpd-2.2.3-63.el5_8.1)
 (kernel-2.6.32-220.7.1.el6)
 (kernel-2.6.32-220.17.1.el6)
 (kernel-2.6.18-308.8.1.el5)
 (Cent 6: kernel-2.6.32-220.23.1.el6)
 (kernel-2.6.18-308.8.2.el5)
 (kernel-2.6.18-308.11.1.el5)
 (kernel-2.6.32-279.1.1.el6)
 (Cent 5: openssl-0.9.8e-22.el5_8.4; Cent 6:
This version of AMP introduces Java security fixes. Updates for the Firefox browser (jre-1.6.0_27-fcs)
and AMP have been implemented (jre-1.6.0_19-fcs). Refer to the following for more information:
Resolved Issues
Table 1 below lists resolved issues in AirWave 7.5.6:
Table 1 Resolved Issues in AirWave 7.5.6
DE12571, Fixed an issue that caused VisualRF to display an incorrect number of clients. This occurred because
associated clients with no associated discovering radio failed to display as did non-associated clients.
These clients now display correctly, and the client count that displays on floor plans in AMP now
matches the number of clients that displays on the VisualRF page. In addition, the list of clients on the /
site_list page now updates correctly after a refresh.
If deployed APs do not exist in a VisualRF plan, then users are no longer able to click on a planned AP
and select “Match with Managed Device. This option is now only available when deployed devices
The Daily Network-Wide Network Usage Report and the Daily Network-Wide PCI Compliance
Report now run properly. The error occurred when an expired cookie was stored for a Managed AMP
and when AMP failed to fetch a fresh cookie.
Fixed an Upgrade Firmware issue that occurred when attempting to push firmware to VCs and Instant
APs. Firmware upgrades can only occur on VCs. When attempting to upgrade on APs, the system
would not respond. Now AMP ignores any Instant APs that are selected during the firmware upgrade
AirWave 7.5.6 | Release Notes
Table 1 Resolved Issues in AirWave 7.5.6 (Continued)
Attempting to open a Groups > Basic page by specifying “ap_group_id=” in the navigation bar no
longer results in a page error. Now, “ap_group_id=” and “id=” can be used interchangeably.
Fixed an issue that caused disc utilization to peak when the Top Clients By Total Traffic widget was
added to the Home > Overview page.
Fixed a memory issue that was caused by AMP failing to ignore interfaces on ignored member
switches. The result was that duplicate interfaces were created during polling periods. Now, AMP
ignores interfaces on ignored member switches.
Fixed an issue in which Rogues that were found, contained, and added as neighbors would then display
again as rogues during the next polling period.
DE12902, Fixed an issue that caused a config import to fail when a custom name existed for certificates on a
DE12792 controller, and that name did not match the name of the certificate on the desired configuration. Now,
the custom file name will no longer result in a mismatch.
Fixed an issue that resulted in a “Server communication error” message on pages that contain graphs.
This issue was only see in IE 8 browsers with the Do not save encrypted pages to disk setting
enabled. Now, AMP no longer caches HTTP headers for dynamic files if the browser is earlier than IE 9.
NOTE: It is not possible to provide a fix or workaround for this issue in IE 9. Microsoft recommends
turning off the “Do not save encrypted pages to disk” setting. Refer to
Fixed an issue that caused global AOS configurations to be converted to group-based configurations
after an upgrade. This occurred when the Use Global Aruba Configuration option on the AMP Setup
> General page was set to No before an upgrade and then set to Yes after the upgrade.
RAP-3WN and RAP-3WNP devices are now labeled properly in AMP, and the way that these devices
display is now consistent with the controller. In addition, clients that are associated with RAP-3 devices
are now visible in AMP.
On a VC’s Manage page, the Reboot button now indicates that the reboot applies to all APs in the
cluster and not just to the VC.
Table 2 below lists resolved issues in AirWave 7.5.5:
Table 2 Resolved Issues in AirWave 7.5.5
VisualRF now includes the option to configure external antenna orientation for the Aruba AP175 device.
Added new MIB entries for S3500, version build 34027:
 wlsxLicenseClientExpiry
 wlsxLicenseServerExpiry
 wlsxStackIfStateChangeTrap
 wlsxStackTopologyChangeTrap
The Replace Hardware feature now allows you to replace Cisco devices with Aruba devices.
Fixed an encoding issue that caused VisualRF to show an AP as “down” when the AP was in fact “up.”
Fixed an issue that caused RAP whitelist changes to not be pushed if the thin APs happen to go down
on AMP and get stuck in the configuration import state.
Updated kernel (kernel-2.6.18-308.11.1.el5). See the Security section of this document for more details.
Updated kerenl (kernel-2.6.32-279.1.1.el6). See the Security section of this document for more details.
When updating AP Groups from Modify Devices, the previous AP Group name now displays on the
confirmation page.
DE12569, Fixed an issue in which only a single Thin AP in a group was updated during an LWAPP AP Groups
DE12580 update.
DE12499, In VisualRF, fixed an issue in which the DWG Convert process resulted in 100% CPU usage.
AirWave 7.5.6 | Release Notes
Table 2 Resolved Issues in AirWave 7.5.5 (Continued)
In VisualRF, fixed an issue that caused overlays (heat maps, speed, etc.) failed to display for Cisco
881W, 881GW, and 891W devices.
Fixed an issue that resulted in an error when attempting to add Cisco AP Group a group configuration.
Fixed an issue in which an existing local controller was discovered again after upgrading, resulting in a
duplicate record.
Fixed an issue that caused an upgrade from 7.4.0 to 7.5.3 to fail. This occurred when AMP attempted to
rename a report and came across an AMPLink object.
Fixed an Instant issue that caused configurations to be built with invalid IP addresses.
Upgrading from 7.5.3 to 7.5.4 no longer fails with an RRD cache error.
Fixed an issue that cause configuration pushes to fail when attempting to modify a read-only value.
The Network-wide Client Inventory and Network-wide Client Session report definitions no longer
incorrectly include a Matching option.
DE12719, Fixed an issue that occasionally caused gaps and/or missing information in the Utilization and Goodput
DE12422, graphs for an AP radio.
Fixed an issue in which the Group display options from the master controller global group were not
inherited by the subscriber group on MAMP. In addition, the Select devices in this group link is no
longer visible for the remote Global group and the subscriber group.
Fixed SNMPv3 polling issues that occurred when a Primary device would go down. When the
Secondary switch becomes the Primary, the switch role now indicates this properly, and this new
Primary can now be polled.
Fixed an issue that caused a client-count discrepancy. The number of clients on the Groups > List page
now matches the number of clients on the Home > Overview page Clients chart. Note that when
synching these values, you may experience a 5- to 10-minute latency.
In VisualRF, Dell PowerConnect W model access points now display correctly in the device catalog.
In Visual RF, Cisco 881W, 881GW, 891W, 1941W ISRs are no longer treated as APs, and Cisco SRE
Module for 1941 ISR is no longer treated as a WLC.
Table 3 below lists resolved issues in AirWave 7.5.4:
Table 3 Resolved Issues in AirWave 7.5.4
Fixed a error that occurred when two duplicate physical interfaces existed on the same switch. In this
scenario, one of the interfaces had the proper settings, and the other showed a mismatch.
Fixed an issue in which AMP failed to retain “Channel,” “Noise,” “Power,” and “AC/Phy Error” data after
performing Replace Hardware.
Fixed an inconsistent floor-plan-import issue in VisualRF. When importing a floor plan, exporting the
plan, and then reimporting, the second import was occasionally incomplete.
Updated kernel (kernel-2.6.18-308.8.2.el5). See the Security section of this document for more details.
Fixed a PCI 1.1 Compliance issue that occurred with IAP devices. For these devices, the Daily PCI
Compliance Report no longer result in a “Device is not configured by AMP or device configuration is
not audited by AMP yet” message. In addition, the details for the status no longer show an “Unable to
Determine” message.
The e-mail output for custom reports no longer contain orphaned entries. This output now matches the
report that is generated in AMP.
AirWave removes Machine Authentication users created by AOS with no role. Note that Machine
Authentication entries are CACHED entries created by AOS when a machine does a pre-user-auth
machine login to the controller. These users are not created manually or by an external service.
AirWave 7.5.6 | Release Notes
Table 3 Resolved Issues in AirWave 7.5.4 (Continued)
Fixed an issue with the custom Capacity report. This report no longer loads slowly, and exporting this
report now works correctly.
When AirWave attempts to auto detect a language during login, the default for the “ZH-TW” language
setting now correctly points to Traditional Chinese rather than Simplified Chinese.
Updated kernel (kernel-2.6.32-220.23.1.el6). See the Security section of this document for more details.
Fixed an issue in which configurations failed to be pushed because the Virtual Controller’s
“all_aps_have_been_read” flag was set to 0. AMP changes this column from 0 to 1 for a swarm to
ensure that configurations are pushed to existing APs when upgrade AMP.
The Unused Ports histogram in custom reports now displays properly.
In VisualRF, AP135 now displays in the Add Planned AP dialog box for the Sensor device type.
Fixed an issue in which AMP pushed incorrect radio antenna gain information to the controller for AP
134. In this particular case, AMP was configured to push radio antenna gain of 802.11bgn radios to “5”
and 802.11an radios to “3.” The result, however, was that AMP had reversed these configurations.
ACLs pushed from AirWave are now configured properly. AirWave no longer issues a “no” for “rule”
Fixed a reboot issue that occurred when multiple devices were selected to be modified from the APs/
Devices List page. In this case, when the controller was in Monitor mode, and the AP was in Managed
mode, choosing Reboot resulted in AMP events claiming ‘Rebooting’, but no actual action was being
On the Master Controller, the Groups > List page no longer indicates that groups defined on the MC
groups are ‘Local Groups.’
When reviewing the AP_list.xml file on a Cisco 600 LWAPP AP, the “Display Transmit Power” value is no
longer missing for <radio index=”2”>.
A new graph was introduced on the System > Performance page that displays number of Web server
connections and the current number of database connections over a period of time. See the New
Diagnostics Graph section for more information.
Added support for additional Cisco devices. See the Cisco Device Support section for more
Table 4 below lists resolved issues in AirWave 7.5.3:
Table 4 Resolved Issues in AirWave 7.5.3
Floor plans exported from VisualRF Plan and imported into their VisualRF on AMP properly display all
required APs, switches and building floors. This resolves an issue where some parts of the floor plan
would not appear properly after importing into VisualRF.
Fixed an issue with the PopulateFromSNMPPoll migration process. For some deployments, the entire
migration can take multiple hours. As a result other processes were unable to begin or continue while
the migration was being run. This migration is now divided into multiple transactions, so other process
now need only wait until a portion of the migration process is complete before continuing.
When upgrading to 7.5, remote APs no longer mismatch after the server comes back online. This
occured because the function controlling the configuration for remote AP authentication toggled to “No”
(NULL) during the upgrade process.
Table 5 below lists resolved issues in AirWave 7.5.2:
Table 5 Resolved Issues in AirWave 7.5.2
A VC IP is required in order to enable the Instant “Dynamic RADIUS Proxy” feature. A new error
message displays when a user attempts to push a configuration in which the Instant Dynamic RADIUS
Proxy feature is enabled, but a VC IP is not provided.
AirWave 7.5.6 | Release Notes
Table 5 Resolved Issues in AirWave 7.5.2 (Continued)
When a radio is in Mesh mode and has active SSIDs, the radio will display with a “Mesh and Access”
role in the AP Monitor page. In addition, the client count now displays correctly.
For Aruba controllers that are part of a Master/Local configuration, the Master Controller ID is now
shows on the Local Controller’s monitoring page along with the Master Controller IP.
When a user selects the “XML (XHTML) export” link after running a report, the report now displays
correctly in a new tab.
When a user mouses over a Campus name, Building name, or Floor Plan name in VisualRF, non-UTF-8
characters now display correctly at the top of the pop-up boxes.
Updated kernel (kernel-2.6.18-308.8.1.el5). See the Security section of this document for more details.
Updated openssl (openssl-0.9.8e-22.el5_8.4 and openssl-1.0.0-20.el6_2.5). See the Security section of
this document for more details.
Fixed a “pre-upgrade check” issue in the reporting of disk space. In some cases, an incorrect value was
reported for the estimated disk space size when determining whether enough disk was available to
upgrade AirWave.
Fixed an error that occurred when attempting to disable LWAPP APs. The “Disable” setting is now
pushed correctly.
When selecting or viewing APs in VisualRF, Dell APs now display with a “PowerConnect W-AP” label
that prepends the model number.
AP 93H BSSIDs are now collected when added to AMP or when the AP is audited. Not having the
correct BSSIDs prevented the users from showing up in AMP. (There is a calculation method for BSSIDs
done in AMP for regular APs. For APs that have at least 1 radio and at least 2 wired ethernet ports, the
AMP must get the BSSIDs from the controller - these SSIDs can't be calculated by any specific
Table 6 below lists resolved issues in AirWave 7.5.1:
Table 6 Resolved Issues in AirWave 7.5.1
Fixed a regression that in some cases caused confirmation page settings to be applied incorrectly for
Aruba profiles.
Table 7 below lists resolved issues in AirWave 7.5.0:
Table 7 Resolved Issues in AirWave 7.5.0
When restoring a backup from the controller into VisualRF, the “Validate” link no longer remains enabled
after it has been clicked.
AirWave no longer updates the device state from ‘Importing’ to ‘Mismatched’ before the import is
Added a warning to the confirmation page when changing a group time zone reminding the user that
this change can have an impact on maintenance windows.
The Failover server no longer includes a read-only user role.
The VisualRF Frequency selection option now works properly for overlay bleed through.
On the Master Controller, a confirmation page now displays when you attempt to remove a Managed
AMP. In prior versions, AMP was immediately deleted.
When an Aruba Mobility Access Switch is deleted from a stack group, the status message “Deleting
Devices in the Background” no longer remains on the page when there are no devices on the
ap_monitoring page.
AirWave 7.5.6 | Release Notes
Table 7 Resolved Issues in AirWave 7.5.0 (Continued)
In VisualRF, a restart is no longer required to view overlays after importing a controller’s floor plan
An Access Denied page no longer displays when attempting to view a rogue detail page from a Master
Console using the rogue client report.
APs without management mode and whose group has config-audit disabled do not have maintenance
On the Clients > Diagnostic page, graphs that contain no data now display with a “No Data Found”
message rather than as a empty gap in the page.
Empty Channel Utilization and Noise graphs are now hidden in Client Diagnostics view. These graphs
will appear when data is available.
The script no longer deletes APs that have an empty Device Serial\Lan
MAC\Chassis ID setting. A new option, --delete_null_devices, was created to remove these APs.
VisualRF: Users are no longer required to clear their browser cache after upgrading from previous
versions of AMP in order to see campuses in the proper location.
SNMP community strings are now obfuscated in trap messages instead of being readable.
Device override now persists after a VisualRF restart.
AMP installations now clear any existing disk partition labels because pre-existing disk labels may
cause installations to fail.
Fixed an issue in VisualRF that caused the AMP status header and the top-level navigation header to
display after resizing a floor plan.
When a firmware job fails, links on the Firmware File column of the Firmware details page now points to
the correct location.
On the controller Monitor page, monitor-only users can no longer view the system event log.
Added a CAD Layout panel to the image upload wizard in VisualRF. This new panel includes a
checkbox that allows users to toggle on/off Active Layout in the dwgconvert command, which is
useful when displaying DWF files.
Fixed an issue in which AMP failed to notify the user of a mismatch when a VLAN changed. This
occurred when an AP lost power or rebooted. The AP reported on the controller that the VLAN
associated with some SSID had changed, and the SSID is now associated with new VLAN. AMP did not
display this as mismatch. Instead, AMP showed the SSID with the new VLAN in the manage page
without doing any import on the AP or on the controller.
AMP no longer allows users to create multiple templates for the same device type with Restrict to this
version set to No on both templates. In addition, a Template Firmware Version is required when
specifying Restrict to this version.
The upgrade script no longer automatically overwrites a pre-upgrade backup. Instead, users who have
an existing pre-upgrade backup are prompted whether to overwrite pre-upgrade backup.
If an Aruba controller is moved to a new group in AirWave, the Aruba controller AP Group for the
controller thin APs is no longer automatically changed as well.
Increased the page load speed of the APs/Devices > Monitor pages by relocating audit logs to their
own page.
For Cisco controllers that do not include support for remote WLANs (prior to firmware version 7.0.116),
AMP will not push a remote WLAN profile even though the remote WLAN profile is configured on AMP.
In addition, AMP ignores the remote WLAN profile while performing the device configuration audit.
When a Device Down trigger is specified for a switch, the trigger no longer sends an alert each time an
AP on the switch goes down.
The TX Power column on the Wireless Settings > Radios table now shows 0 dbm instead of
<unknown> when the value of an AirMesh AP radio’s transmit power is 0.
Clients with a signal quality of less than 1 are no longer tracked in the Client Signal Distribution chart.
Fixed an issue to speed up the restarting of daemons.
AirWave 7.5.6 | Release Notes
Table 7 Resolved Issues in AirWave 7.5.0 (Continued)
Mesh/Overhead BW graph lines no longer display for APs that do not support radio bandwidth fetching.
Fixed an issue that caused upgrading to fail with a ‘No Disk Space Left’ error even when the hardware
specs meet the recommendations. AMP now verifies the disk space before starting based on the size of
the largest existing database table or the estimated size to migrate a large round-robin database.
The Rogues Contained table on the APs/Devices > Rogues Contained page can now be sorted by
the “Last Seen” date.
The Threshold values available on the Clients > Diagnostics page no longer includes ‘Poor’ values.
Data that matches ‘Good’ or better falls in the Good category. Data that matches between ‘Good’ and
‘Fair’ fall in the ‘Fair’ category. Anything below ‘Fair’ is by default considered as ‘Poor.’
The Aruba License Report now displays information for standalone Aruba master controllers.
In VisualRF, the alert that displays for the AP Bandwidth now matches the information that displays in
the left-click popup.
AirMesh users who lack write permissions now receive a warning message when they attempt to
upgrade firmware or push configuration changes.
The timeout value for remote authentication in RADIUS, TACACS, and LDAP modes now defaults to 15
seconds. In the event that remote authentication fails, this ensures that the time it takes to log in to AMP
with local priority will take less than a minute. Note that this value is not configurable on the UI, but this
can be modified with the remote_auth_timeout setting in the seas_config table. Contact
technical support for more information.
The Inventory Report now shows the correct bootloader and version summary information.
Error logging for AirMesh firmware upgrades has been improved.
AMP now treats ‘0’ as ‘empty’ when importing a 0 antenna gain from a device. Because the antenna
range is 1-255, a value of ‘0’ would result in a validation error.
The Export CSV button has been removed from the System > Syslog & Traps page. This export can be
done from the Device Events page within the AP Monitoring and Client Monitoring pages.
The “Use DHCP” option is now imported correctly for AirMesh gigabit interfaces.
Resolved an issue for under Groups > Cisco WLC Config > Mobility Management, where changes
made to the Automatically create mobility group elements for <default mobility domain> setting in
the drop down menu were not being recognized.
On AirMesh MSR APs, the AP Monitoring page now loads properly when users navigate there
immediately after editing an interface.
The password in the AirMesh configuration template is now encrypted.
When upgrading failover AMP, users with a default role of “Read-Only Monitoring & Auditing” are
deleted as is the role itself. This is because non-admin roles cannot be created on failover AMP.
All AirMesh MSR2000 devices (PoE, AC, DC) now share the same template.
When a device includes more than 1000 clients, the client count that displays in the associated Client
Count graph is no longer truncated. (For example, “1420” clients no longer displays as “1.4k” clients.)
When you display a floor plan on the VisualRF tab and select the Display > Relations > APs option, the
relational lines between APs are no longer retained when you click the page refresh icon ( ) in the
upper right corner of the window.
Fixed a VisualRF issue in which the direction of the breadcrumb arrows did not reset. This occurred
when locating a whose Host AP resided on another floor, and the user selected the Show Host AP
Floor Plan link. In addition, attempting to return to the previous floor resulted in an error.
The upper limit for the SNMP Retries setting on the Device Setup > Communication page has
changed from 20 to 40. Note that some SNMP libraries still have a hard limit of 20 retries. In these
cases, any retry value that is set above 20 will still stop at 20.
The TX Power value now displays correctly on the Manage page for AirMesh MSR4000 APs.
The size of the visualrf_msg.log file no longer increases significantly when RTLS messages are included.
AirWave 7.5.6 | Release Notes
Table 7 Resolved Issues in AirWave 7.5.0 (Continued)
The Interface tables that displays AirMesh MSR2000 and for MST200 AP now contain the same fields.
Changed the way that client connect/disconnect times are collected. Client disconnect time now comes
from the payload and not the time of processing the payload.
Fixed an issue that caused the TX Power value for an Aruba AP with a role of Spectrum Sensor or
AirMonitor to display on the Groups > Monitor page but not on the associated APs/Devices > Monitor
Fixed a mismatch issue that occurred when AP Longitude and Latitude values ending in ‘0’ were
entered correctly on the device but then truncated on AMP during an audit.
For mesh APs, which only use FTP for firmware upgrades, the Server Protocol field is now auto-filled
when uploading firmware and files.
40MHz Intolerance and Greenfield IDS traps now display under the IDS category and show up as IDS
failure events rather than hardware traps.
DE11266, Added support for certificate configuration management for group AOS configurations. Certificates that
DE11270, are added and specified for a group cannot be deleted. For groups that are configured as a Global
DE11271 Group, an override option is now available. Users can select whether a certificate should be pushed
using this setting rather than relying on another group's configuration.
The “Format,” “Type,” and “Expiry” columns now sort properly in the Device Setup > Certificate and
Groups > Certificate tables.
AMP no longer displays a Save and Apply button when no changes are made to maintenance
Fixed a potential security issue where arbitrary pieces of AirWave’s code could be started by crafting a
specific URL.
The server protocol for upgrading firmware on mesh APs is now FTP rather than TFTP.
Fixed an issue that caused VisualRF to fail to load in IE8.
For AirMesh APs, the Orphan Node Recovery button on the AP > Monitor page now only displays
when the downed AP has a potential neighbor AP that can be used for recovery.
DE11312, Fix the importing of aruba_ap_group for Aruba Thin APs. AMP now allow users to import
DE11535 aruba_ap_groups that may not exist as objects on AMP. When the fields are cleared out for import
settings, then include aruba_ap_group is included. If no aruba_ap_group is successfully retrieved for the
AP, then aruba_ap_group is now set to Default.
The View Running Configuration link on the controller audit page now displays the AOS running
configuration details rather than a normal audit configuration.
AMP now warns the user that a reboot is required in order to apply changes to a template.
NMS servers added by a user with an AMP Administrator role can now be used by any other user with a
role definition that is specified as AMP Administrator.
The email output for custom reports now matches the output generated by the report in AMP.
Additional headers that do not display in the report will not display in the email output.
This version of AMP limits the amount of memory usage on web server processing in order to prevent
memory overflow.
When a radio interface is shut down, the AMP no longer displays “shutdown” twice, causing a
The time range that displays within the graphs on the Clients > Connected page now match the times
and timezones that display in the table below the graphs. In prior versions, the graphs displayed the
server timezone, and the table below displayed the client timezone. All times that display now represent
the server timezone.
When changing the AP group name that includes a Cisco LWAPP AP, the LWAPP AP now reboots
automatically so that the change can take effect immediately. Users who do not want the AP to reboot
automatically can take advantage of AMP maintenance windows.
An error message now displays on the Home > Overview page for failed migration jobs.
AirWave 7.5.6 | Release Notes
Table 7 Resolved Issues in AirWave 7.5.0 (Continued)
Fixed an issue that prevented users from using non-ASCII characters (for example, Chinese characters)
in the “Notes” and “Down Status Message” fields on the APs/Devices > Manage page. Inputting nonASCII characters no longer results in an error message.
Support has been added for automatic static IP assignment for AirMesh devices on a per-group basis.
An interface on an AirMesh AP that is specified as ‘management’ and that is using DHCP will be
assigned a static IP.
On the APs/Devices > Monitor page for AirMesh devices, radios with a channel width of either 40plus
or 40minus now display as 40MHz.
Fixed an issue in VisualRF in which a change to the transmit power of a planned AP was not reflected
when viewing the heatmap overlay. Note that this issue only occurred when the Overlay Style for
Heatmap was set to Vector.
After creating two walls in VisualRF, users can now drag one wall and connect it to the other. In prior
versions, attempting to drag a wall sometimes resulted in the wall remaining attached to the mouse
even after clicking on the mouse.
Scrolling while the mouse is outside of a VisualRF background no longer results in an image zoom.
The way that information displays on the System > Configuration Change Jobs page has been
improved. Instead of displaying the entire message with a horizontal scroll bar, messages that include
more than 75 characters are now truncated, and the user can click on the tooltip to view the entire
On the APs/Devices > Monitoring page, fixed an issue that caused CSV exports to return blank
information for switch members and WiFi tag lists.
Fixed a timeout issue that caused ConfigVerifier to display a “Too many errors...” message in
management_status_message while auditing controllers on an AirWave server.
When creating AOS WLANs using the WLAN wizard, AMP will only associate the WLAN with the default
Aruba AP Group if the current user has visibility into that group. Users who do not have the appropriate
privileges must now explicitly assign a WLAN to an AP Group. (Note that this behavior only applies to
Global Config mode.)
LAN IP configuration is now supported for AirMesh APs. In addition, the AirMesh interface netmask is
now configured in IP format rather than with a mask length.
“Uninitialized value” errors no longer display in the Web Server log (/var/log/httpd/error_log file).
Only ASCII characters can be entered as SSH/Telnet credentials.
A link to the VisualRF diagnostics report file is now hidden on System > Status page for the master
controller, the failover server, and AMPs with Display VisualRF specified as No.
For Aruba controllers, enum values that are unsupported (e.g. usb-type ‘ether-lte’ on v6.1.3.0) are no
longer pushed. In addition, the audit page indicates that the value will not be pushed to the controller by
including a ‘<not supported>’ tag next to the desired value. These values that are not pushed previously
displayed as <unset>.
Fixed an issue in which the Failover AMP did not take over after a watched AMP database stopped
responding. Now, when an authentication is attempted while the database is busy, a “503 (Service
Temporarily Unavailable)” message will display. In addition, the Failover AMP will retry logging in to the
Watched AMP as long as the database is busy and until the missed polls threshold is met. After this
value is met, a failover will be initiated.
AirWave 7.5.6 | Release Notes
Table 7 Resolved Issues in AirWave 7.5.0 (Continued)
Added a new “Auth” traps category and moved the following auth traps from IDS Events to Auth:
 wlsxNAuthServerReqTimedOut
 authenticationFailure
 wlsxAuthMaxAclEntries
 wlsxAuthMaxBWContracts
 wlsxAuthMaxUserEntries
 wlsxAuthServerIsUp
 wlsxAuthServerReqTimedOut
 wlsxAuthServerTimedOut
 wlsxNAuthMaxAclEntries
 wlsxNAuthMaxBWContracts
 wlsxNAuthMaxUserEntries
 wlsxNAuthMaxXsecUserEntries
 wlsxNAuthServerAllInService
 wlsxNAuthServerIsDown
 wlsxNAuthServerIsUp
 wlsxNAuthServerTimedOut
Fixed an issue in which AMP was slow to bring up an Aruba controller. This occurred when the
controller included good SNMP credentials but no CLI credentials or when the controller did not contain
information required for the WMS Offload provisioning.
Fixed an issue that caused new_config to be incorrectly deleted. This impacted APs that included
scheduled recurring configuration jobs. When clicking Apply Changes Now through the Configuration
Change Jobs page, the changes were applied correctly, but the scheduled changes were deleted.
Fixed an issue that caused Forward Mode, Sig. Qual., and Ch BW values to display incorrectly on the
Clients > Client Detail page.
When replacing hardware, if a user does not have access to a folder, then devices in that folder can no
longer be seen under the ‘Devices in Group’ section.
When changing credentials on a controller, config_verify_failures is now reset for both the controller and
its thin APs. As a result, if config verification fails due to bad credentials and the user changes those
credentials to correct ones, the configuration for the thin APs can now be verified.
Fixed an issue that caused a user-count discrepancy between a folder and an AP within that folder. The
updating folder and group RRD rules now only count clients from SNMP polls. This prevents the
discrepancy between the AP and Folder/Group client count graphs. Previously, clients processed by
traps may have been counted in folder graphs, but not in AP graphs which led to the discrepancy.
Fixed a crash in the APs/Devices > List and APs/Devices > Down pages that was caused by a switch
on an AMP that was designated as a “standalone” switch_role.
Running AP Controller commands without an <apname> will use an <ip_address> instead.
Fixed an issue in which IDS events for IAPs failed to appear in AirWave after upgrading.
When monitoring interface bandwidth, AirWave checks the calculated bandwidth against the known
maximum for that interface. However, if that is missing, then the following values will now be used:
 For non-802.11n Aruba thin APs, 100 Mbps
 For 802.11n Aruba thin APs, 1 Gbps
 For all other devices, 10 Gbps
The device “Type” label now displays general device information for Alcatel-Lucent devices on the APs/
Devices > Monitor page.
Fixed an issue that prevented AirWave from displaying the complete list of clients present on the
Fixed an issue in which a wiring closet name change failed to update.
Fixed an issue that occurred when emailing a Rogue Containment Report with the Disable AirWave
Links option enabled. The Classifying Rule and Location columns still linked the user to the AMP that
generated the report. Links are now disabled correctly when this option is selected.
AirWave 7.5.6 | Release Notes
Table 7 Resolved Issues in AirWave 7.5.0 (Continued)
Added Alcatel Lucent AP 68 (and 68p) to the VisualRF catalog_repository.xml. These devices are now
available for selection and now display heat maps.
For fresh installs beginning with AMP 7.5, the Use Global Aruba Configuration value on AMP Setup >
General now defaults to No. Note that for upgrades to AirWave 7.5, this value will still default to Yes.
Known Issues
Table 8 below lists known issues in AirWave 7.5.6:
Table 8 Known Issues in AirWave 7.5.6
In VisualRF, exporting a set of floor plans from one AMP and importing them into another can
sometimes result in missing floor plans.
An issue exists with Rogue Containment. In some cases, AMP does not push the Contained Rogue
RAPIDS Classification override to the controller. This behavior can occur even if the Manage rogue AP
containment and Manage rogue AP containment in monitor-only mode options are set to Yes.
A “Server communication error” message can sometimes be seen on pages that contain graphs. This
issue occurs in IE 9 browsers that have the Do not save encrypted pages to disk setting enabled.
Microsoft recommends turning off this setting. Refer to for
additional information.
Table 9 below lists known issues in AirWave 7.5.5:
Table 9 Known Issues in AirWave 7.5.5
An issue exists with regards to lingering interface data after devices are swapped. When a switch1 is
unplugged, and switch2 is given switch1’s IP address, the interface data from swtich1 still exists.
In some cases, the Daily Wireless Network Usage report might not include any data in the Usage
graph. This is currently being investigated.
When a Management Captive Portal certificate exists on a master controller, a mismatch that cannot be
overridden can occur when uploading a different certificate on a local controller.
When a radio noise trigger is set for noise levels greater than a certain dBm value, alerts are being sent
for values less than the set value. For example, if a trigger is set for values equal to or greater than
-70dBm, alerts are still being sent when the noise level falls between -90 and -80dBm.
A Device Down alert may be reported even though the reported device was never down. The
circumstances under which this behavior occurs is currently being investigated.
In some cases, AMP may report that clients are connected to a radio that is actually disabled on the
In VisualRF, DWG files that include cross-reference bindings are not supported. Attempting to import
these into AMP can result in poor-quality images.
An issue exists when creating a global group and allowing subscriber overrides for the Device Type
setting. When overrides are allowed on the master controller Group Display options, a configured
“copy” of the global group does not properly remove devices that are removed from the master
controller group. If you notice this issue, then please perform the following steps:
1. Discontinue managing group configuration for the MAMP from the MC. (It is not necessary to delete
the MAMP from the MC; not managing group configuration is sufficient.)
2. On the MAMP, determine if there are any subscriber groups for the affected global group. If there
are none, delete the global group on the MAMP and skip to step four. Otherwise, continue with step
3. Edit the device preferences on the global group of the MAMP so that the preferences match the MC.
4. Enable managing of group configuration for the MAMP on the MC.
AirWave 7.5.6 | Release Notes
Table 9 Known Issues in AirWave 7.5.5 (Continued)
An issue exists in which the Asynch Logger fails, and AMP stops monitoring devices for approximately
one hour. The circumstances under which this behavior occurs is currently being investigate.
Table 10 below lists known issues in AirWave 7.5.4:
Table 10 Known Issues in AirWave 7.5.4
A configuration push inconsistency exists. After updating the RADIUS shared secret for a group and
then putting the controllers in that group into Manages mode, it is possible that the config will not be
pushed to all of those controllers.
When upgrading to 7.5.x from a version prior to 7.5, existing devices may show up as “Discovered” after
the upgrade.
In VisualRF, when an AP acts as both an AP for one radio and a sensor for the other radio, the device
will only show up as a sensor. It does not display as an AP.
When monitoring a controller, the Modify Devices feature does not work if you attempt to modify
devices associated with the controller. Note that this behavior only exists in Internet Explorer.
Table 11 below lists known issues for AirWave 7.5.2:
Table 11 Known Issues in AirWave 7.5.2
A Service Type of “arp” is an available option in AirWave for ArubaConfig, but this setting is not
supported on the controller.
Clicking on the Help link in AirWave may not open to the correct location in the User Guide PDF file. If
you use IE or Firefox, then your browser must be set up to open Adobe PDF files within the browser. If
you use Google Chrome, then you must use the Adobe Reader plugin in order to enable this support.
In VisualRF, when the application window is maximized, the client history playback widget displays.
AirWave removes Machine Authentication users created by AOS with no role. Note that Machine
Authentication entries are CACHED entries created by AOS when a machine does a pre-user-auth
machine login to the controller. These users are not created manually or by an external service.
In some cases, the snmp_fetcher function can restart multiple times each day, resulting in error
messages and an incorrect client count in AirWave.
An issue exists with Aruba Instant in which configurations may be built with invalid IP addresses.
Table 12 below lists the known issues for AirWave 7.5.0:
Table 12 Known Issues in AirWave 7.5.0
Two different users who do not have visibility into each other’s floor plans can potentially create
duplicate floor plans in the same building. The floor plan upload wizard does not check for duplicates in
this scenario.
Google Earth fails to launch for Mesh APs when using IE8.
DE10667 VisualRF can stop running without warning if it runs out of memory.
DE10674 A VisualRF restart is required in order to view overlays after importing a controller’s FP backup and
restoring it to VisualRF.
DE10720 Unexpected behavior can occur when specifying a PDF file as the image upload type in VisualRF. The
image may display as blank and/or corrupted. When specifying PDFs, be sure that the PDF was
generated from a source file and not, for example, scanned from a printer. Also, be sure to keep the PDF
file size as small as possible.
AirWave 7.5.6 | Release Notes
Table 12 Known Issues in AirWave 7.5.0 (Continued)
DE10741 Some POE devices that are categorized as Universal Network Devices and that have been up for over
248 days may show up as offline in the Daily Device Uptime report. In addition, while viewing the device
directly in AirWave, the device shows the status as OK, though the monitor page will show an ‘out of
range for type integer’ message. Attempting to discover and re-add the device results in a continual
down/awaiting SNMP contact message. A workaround is to reboot the device before rediscovering it.
DE10786 A limitation in Aruba Instant can result in a mismatch when adding the Instant AP using a template
DE10791 If you approve a thin AP that already has a roaming client (recently associated to another thin AP), the
result may be that the client is double counted for a single polling period.
DE10875 In VisualRF, APs that appear to be placed at a correct location may still result in a “wrong location” error.
DE10892 A limitation in Aruba Instant causes configuration pushes for some VCs to break when the dynamicradius-proxy command is included in the configuration.
DE10902 If a virtual controller is added to AMP, taken offline, reset with factory settings, and then re-added using
the same initial settings, AMPdoes not delete the initial, down VC when creating the duplicate. As a
result, both VCs will display in the APs/Devices > List page. In this case, the initial VC will show a
status of Down, and the APs will migrate to the new VC. A workaround is to select the down device and
then manually delete it in the APs/Devices > Manage page.
DE10907 When a virtual controller (IAP1) with a connected Instant AP (IAP2) is discovered in AMP, placed into a
group folder, and then brought down, AMP sets the down VC’s AMP (IAP2) as the new VC for the
cluster. When the original VC (IAP1) is brought up after a factory reset, AMP discovers this AP as
connected to the new VC (IAP2).
DE10915 When updating VisualRF APs preferences from within a quick view page (APs/Devices > Monitor), a
page refresh is required after changing the settings for Preferences > APs > AP Location and
Preferences > Navigation > % APs Up.
DE10925 In VisualRF, the site list on the bottom of the page disappears after entering/viewing a floor plan and
then refreshing the page in Chrome or Firefox. This behavior does not occur in Internet Explorer.
DE10929 The Clients > Client Detail page currently displays two graphs side-by-side that provide the same
DE10959 AirWave is not able to push a 32-character value for Organization to Aruba Instant virtual controllers.
The commands of Organization configuration sent from AMP to Aruba Instant are quoted strings
because the Organization name may contain blank spaces. Aruba Instant includes the quotes in the
length of the string.
DE10975 In some cases after a server upgrade, ICMP ping may not update on the System > Performance page.
This issue is still under investigation and may be server related as it is not seen in all environments.
DE10977 When attempting to back up all floor plans in VisualRF using Google Chrome, selecting the Network
check box will only enable a backup for all campuses rather than for campuses, buildings, and floors. If
you deselect Network and then select it again, all check boxes will be selected. Note that this issue
does not exist in other supported browsers.
DE11001 When uploading a new floor plan in VisualRF, the screen may remain blank after the upload is complete.
Close the Floor Plan Upload wizard and reload the main page to view the new floor plan.
DE11107 When using IE 8 to launch the VisualRF Image Wizard, the image screen remains blank after the custom
background image is uploaded. Images display properly in other supported browsers.
DE11154 VisualRF may need to be restarted in order to see the mesh view.
DE11163 Errors can occur if you make changes to a device in AirWave, leave the confirmation window/tab open,
and then make additional changes to that device in another tab. Be sure that all changes are confirmed
before opening another tab, or perform all edits within the same tab.
DE11188 The Daily Wireless Network Usage Report may display an error message instead of an empty graph
when no graph points are available.
DE11230 Certificates that are added directly on the certificates page rather than through the Global Aruba
Configuration option do not display in the VC drop down on the Groups > Basic page.
DE11247 Interfering, non 802.11n objects might not display in VisualRF even when they are shown as Active on
the AP/Devices > Monitor > Radio page.
AirWave 7.5.6 | Release Notes
Table 12 Known Issues in AirWave 7.5.0 (Continued)
DE11264 A VisualRF floor plan may occasionally show multiple device types with the same MAC address.
DE11309 In VisualRF, be sure to drag new building icons away from the very upper-left corner of the canvas.
Failing to do so can cause inconsistent right-click menus to display. Specifically, you may right-click on
the building and see options specific for the background/canvas rather than for the building. Note that
this does not occur if you move the building away from the upper-left corner.
DE11316 A limitation in Aruba Instant causes a VC to send duplicate payload information to the Events log.
DE11343 Reports do not currently run in parallel, but rather one at a time. As a result, if a report is being run that
takes a long time to generate, other reports may not run until that one is completed.
DE11562 In cases where ports are connected with IP phones, and PCs are connected into those IP phones,
AirWave can display an incorrect port mode on the switch interface. This is because AirWave detects
more than one MAC address communicating through the port and, as a result, marks it as a distributed
port even if it is configured as an Access port on the switch.
DE11594 Moving a large number of controllers from one group to another all at once can take a long period of
time or can sometimes fail. If you notice this behavior, we recommend that you reduce the size of your
bulk moves.
DE11604 Ignoring mismatches for a large number of controllers all at once can take a long period of time or can
sometimes fail. If you notice this behavior, we recommend that you reduce the size of the number of
configuration mismatches that you ignore all at once.
DE11705 If the Max-tx-power for an Instant device is configured to be Max (greater than 33), then the value that
displays may differ than the value that displays on the AMP audit page.
DE11718 IE 8/9 users may notice broken or missing pie chart images when selecting Print or Print Preview within
the browser. If you notice this behavior, one workaround is to add the AirWave IP as a “Trusted Site” in
IE. Another workaround is to select Override automatic cookie handling in Internet Options >
Privacy > Advanced and then refresh the page.
DE11740 Stacked switches only allow interface editing from the master/primary switch. Currently, information
within the audit log is populated based on the interface that is edited. So if a change is made on the
member switch interface, the member switch audit log is populated with the change. As a result, users
must navigate to that member switch in order to verify the audit log.
DE11754 When the radio mode on a Mesh AP changes from 802.11an 40MHz plus to 802.11ng 40MHz minus, on
a portion of the change is reflected on AMP.
DE11757 While logged in as a Helpdesk user, the User Info page provides options for viewing Alerts and Severe
Alerts even though Helpdesk users cannot view these alerts.
DE11773 The default value for the Session ACL option is “none” when configuring AP Profiles through the Device
Setup > Aruba Configuration page in AMP. The controller (Configuration > All profiles > AP > AP
System Profile) shows this default value as “ap-uplink-acl.”
DE11835 In some cases, importing older Cisco wireless LAN controller (5.0 or earlier) can result in mismatches for
options that do not exist. The root cause is still under investigation; however, these mismatches can be
DE11838 Newly added devices do not show up in a Quick Search.
DE11851 In some cases, users may be unable to resolve rogue classification mismatches. This is because it is
not possible to fix a controller’s rogue classification setting by importing.
DE11889 When adding a region in VisualRF, be sure to specify a region type before drawing the region. An error
will occur if a type is not selected.
DE11897 When a user adds a Cisco or Alcatel-Lucent switch stack, updates sysLocation on the stack using the
CLI, and then imports settings, the primary switch updates successfully, but member switches do not.
A current workaround is to delete and then re-add the members of the switch stack.
DE11910 Importing from controllers that do not have licenses can result in mismatches that may not be resolved.
DE11945 A web error can occur if you press Restart AMP and the page refresh does not complete before the
web server restarts.
AirWave 7.5.6 | Release Notes
Table 12 Known Issues in AirWave 7.5.0 (Continued)
DE11986 In some cases, Device events (traps) can correlate to a client rather than an AP. This can occur, for
example, when a RAP-2 device is plugged into a RAP-5 device. In this case, the RAP-2 has its own
clients, but will now also appear as a wired client of the RAP-5. Because of the way that device event
logging works, when a device event message tied to a particular MAC address is logged, the link from
that MAC address on the device event page will always link to the client page associated with that
MAC, even if that MAC also happens to be an AP LAN MAC.
DE12004 The graphs shown in wired/wireless up/down pages consider both wired and wireless devices when
Expand folders to show all APs/Devices is selected.
DE12017 Using amp_upgrade to perform an upgrade may result in errors. Only start_amp_upgrade is
supported for customer use.
DE12029 AP Groups that are configured with the Audit Configuration on Devices option set to No can still view
maintenance windows.
DE12047 In AMP Setup > Network, after removing both the Primary and Secondary NTP IP addresses and then
entering an IP address in the Secondary field only, the IP will shift to Primary after selecting Save. In
addition, Save takes a long time.
DE12098 Clients on a Corvina stack are not aggregated on the primary member.
DE12150 Due to limitations in some web servers, attempting to add hundreds of newly discovered devices to
AMP all at once can result in an ‘Internal server error’ message. We recommend that you add newly
discovered devices in smaller batches to avoid this error.
DE12181 The number of clients listed in the Device Info section on the APs/Devices > Monitor page may differ
from the number listed in the APs Managed By This Controller section. This can occur because the
client data for Device Info gets pulled in from Swarm more frequently than the APListCacher group
client polling period.
DE12202 Adding a controller to an AMP twice in succession can cause the controller to fail.
DE12228 In some cases, the Channel Utilization graphs may appear with large gaps. This is currently under
investigation and may be due to an incorrect message count in the AMON header.
DE12230 The syncd function will run continually if an MDM server on your AMP is disabled. This loop results
because MDMPoller will assume that the next run time is ‘now,’ while the code in DB::MDMServer
returns no information.
DE12271 A symlink is created to svn/mercury/install/amp-centos-upgrade in /root/ during installation even
though an OS upgrade is not currently supported.
Emailed reports now have an option to disable links back to the AMP. Note that this does not prevent
email clients from determining certain text a hostname or email address and then providing links to
those. If you do not want report readers to have access to or knowledge of your network, then be sure
to not email any reports that contain hostnames and/or IP addresses.
Customers running should be aware that the ‘flash’ symlink is now removed to comply with
security policy. This will break Aruba Instant deployments as well as the ability to serve firmware from
the AMP. Customers needing these features can replace this link, as long as they are aware that they
are assuming a security risk by doing so.
1344 Crossman Avenue
Sunnyvale, California 94089
© 2012 Aruba Networks, Inc. All rights reserved.
Phone: 1-800-WIFI-LAN (+800-943-4526)
Fax 408.227.4550
AirWave 7.5.6 | Release Notes
Download PDF