AMP 6.1 Known Issues
AMP 6.1 Known Issues
The following is from the release notes, which are also available in the support docs section of the AirWave website:
4.1 AMP does not support per-SSID web authentication type overrides on Airespace controllers. If such an override is set, and the devices group does not have the AIRESPACE_WEB_AUTH_POLICY_CUSTOM web auth policy type, this may cause web bundle mismatches but AMP will not push the change.
4.2 If a web auth bundle is first uploaded to the controller and then uploaded to AMP, AMP will mismatch on the file name. Web auth bundles that are uploaded to AMP have a file added, which is named with the first 30 characters of an MD5 checksum of the rest of the bundle. The file itself is empty. This is done to differentiate between bundles with different content but the same set of file names.
4.3 Guest Access Provisioning: Guest Users for Airespace can be created with an expiration time or with no expiration time. If you create guest users with expiration times and then create a guest user with no expiration, the controller will report over SNMP that all of the other guest users have no start time or time remaining.
4.4 Guest Access Provisioning: Guest Users with expirations on Airespace controllers, the AMP and the controllers must agree on the current time (including the time zone).
4.5 Global Groups: The Proxim Mesh and PTMP/WiMAX Group tabs will not appear on a Master Console, and are not available for Global Group configuration from a Master Console.
4.6 Global Groups: when group configs are being pushed from the master console to subscriber groups, it is possible to encounter a race condition where the push times out and the master console enters an infinite loop. Pushes to other groups are not affected.
4.7 Global Groups: logs in the Master Console might indicate that there are multiple mc_stats_collector processes running. This is a benign issue and does not affect system performance (DE88860).
4.8 Global Groups: the apply to other groups option cannot be used to change all of your subscriber groups to local groups.
4.9 Global Templates: changing the version-specific flag on a template that has % variables duplicates the % variables in the subscriber groups templates.
4.10 Cisco Airespace: an SSID configured to use 802.1x and WEP cannot be enabled in AMP (DE8873).
4.11 Cisco Airespace: firmware versions 5.0 and greater do not support peer-to-peer blocking. This will be a mismatch in AWMS upon upgrading (DE8870).
4.12 Cisco Airespace: customers upgrading from the 6.1rc4 beta may find that LWAPP APs cannot be enabled or disabled in AMP. Please contact firstname.lastname@example.org for a script that will correctly update the radio status.
4.13 Symbol: When upgrading firmware via AMP, the firmware upgrade might have a task status of complete before the job finishes. The upgrade eventually completes as expected.
4.14 When Alcatel-Lucent controllers are added, interfaces may be added as Aruba Controller in AWMS. This will be fixed in a future build.
4.15 Upon upgrading firmware, Meru devices may become snmp disabled. They will need to be manually enabled before AMP will be able to communicate with them.
4.16 After manually enabling or disabling an Aruba thin AP that is configured for mesh, AMP may report the non-mesh radio has having the wrong type, or may report the mesh radio has being in the wrong enabled or disabled state. This can be resolved by polling the controller.
4.17 The Total RADIUS Authentication Trigger now only supports visibility by role (and not by triggering agent). All current triggers and generated alerts will be migrated to have visibility by role so that only the role that created that trigger will be able to see the alert.
4.18 Customers can remove the airwave.com and dev.airwave.com dns search paths from /etc/resolv.conf if desired. These were previously added during network setup on install, but are not added starting in 6.1.
4.19 In the postgres update, AMP switched to installing postgres in /opt/airwave instead of in /usr/bin. The prefix aw- was also added to the rpm names. This was done to keep AMPs postrgres install from conflicting with an existing install on the system. However, the old 8.2 rpms are left installed because they cannot be distinguished from stock RHEL 4 rpms. They can be removed by hand if they are not desired, and they will not be installed on a fresh install.
4.20 It is possible that using the Poll Now button in AMP may cause AMP to indicate that the device has rebooted, even though it has not done so. This may also cause thin APs to display as down in AMP. This is the result of a race condition between two AMP processes.
4.21 Customers could see a spike in the User Graphs after upgrading to 6.0 because of changes to the format of the cached user information.
4.22 For Aruba controllers, the controller role field on the monitoring page might not show up.
4.23 If AMP does not have correct telnet credentials, it will not be able to fetch certain information, including serial number, controller role and licenses.
4.24 If an Aruba config is mismatched, the audit page will not display the hashed password.
4.25 The provision_from_csv and create_groups_from_csv files scripts in /root/svn/mercury/tools are not fully supported in 6.1, but will be included in 6.2. Please email@example.com for further assistance with provisioning.
4.26 When using the create_groups_from_csv script in /root/svn/mercury/scripts, if the script fails for any reason all newly created groups should be deleted from the Group?List page of the AMPs web UI before the script is run again.
4.27 When using Windows-generated CSV files for scripts in /root/svn/mercury/tools and /root/svn/mercury/scripts, it is possible that the command dos2unix <name of file> will need to be run before the script will work successfully. This can be verified by opening the script on the AMP server and verifying if the dos identifier appears at the bottom of the file.
4.28 VisualRF: after upgrading, the browser cache should be cleared to ensure VisualRF functions as expected.
4.29 VisualRF: when importing data using the VisualRF?Import page, if any import fails or needs to be rerun all partially imported VisualRF data must first be deleted from the web UI.
4.30 VisualRF: When adding a new user or role in the AMP GUI, the browser must be restarted in order for the new permissions to take effect for VisualRF.
4.31 VisualRF: buttons to create a new campus or building may disappear in IE when the page is refreshed. Refresh the page again or restart the browser to restore the buttons.
4.32 VisualRF: Set Building Type buttons may appear within the QuickView frame when accessed via the site list page.
4.33 VisualRF: Vector datarate coveraget will be offset for planned APs when it is displayed for the first time after VisualRF restarts
4.34 VisualRF: the Bill of Materials font is very small.
4.35 VisualRF: radio tilt cannot be changed.
4.36 VisualRF: page crash on iimport page when any of the imports fail.
4.37 VisualRF: floor plan import methods are supported only in IE.
4.38 If VisualRF fails to shut down during the AMPs nightly maintenance period, it is possible that VisualRF floor plans and sites might fail to be backed up. If you notice error messages about nightly maintenance on AMPs home page, please contact AirWave support.