User guide

© 2012 Aruba Networks, Inc. All rights reserved.
www.arubanetworks.com
1344 Crossman Avenue
Sunnyvale, California 94089
Phone: 1-800-WIFI-LAN (+800-943-4526)
Fax 408.227.4550
20 AirWave 7.5.6 | Release Notes
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.
US8466 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.
N/A Customers running stig.pl 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.
Table 12 Known Issues in AirWave 7.5.0 (Continued)
ID Description