List of AWMS 6.2 Known Issues
The following is copied/pasted from the 6.2 Release Notes:
4.1 For WMS offload configuration, if there are already two mobility managers configured one of them must be deleted on the controller by hand for the configuration to proceed.
4.2 WMS offload requires that SNMPv3 users are configured to use SHA.
4.3 In WLC 5.1, AMP will mismatch on voice parameters when voice ACM is turned off.
4.4 In WLC 4.2 and 5.0, the radio is not disabled before voice ACM settings are pushed.
4.5 In WLC 5.2 firmware, wpa1-only mode is not supported. This may cause mismatches in AMP.
4.6 For WLC devices, the available transmit power levels are now read and displayed in a drop down menu on the APs manage page. In the event that the device fails to report available transmit power levels (but does report other information about that radio), the drop down menu will not appear on the APs manage page. No error or log message is provided.
4.7 Supported transmit power settings for WLC 1250s depend on the firmware version: on 5.1, the a radio supports 1-7, and the b radio supports 1-8; on 5.2, both radios support 1-8. AMP supports 1-8 for both radios on both firmware versions.
4.8 If no syslog server is defined on the WLC controller (firmware version 4.2), AMP will mismatch because of the value the controller returns. The workaround is to define a syslog server of 0.0.0.0 in AMP and push config to the controller.
4.9 For Cisco 5.2 firmware, the AP Groups VLAN feature is always enabled. In addition, there is a default AP Group (default-group) that contains every SSID defined on the controller. If AMP shows mismatches desiring the default-group AP Group and all of the SSIDs, there are two workarounds: (1) Import group settings on the controller. This will create the default-group on the controllers group page in AMP (note: this may also change other group settings) or (2) Create the default-group setting by hand to match the settings on the controller on the GroupÀÆSecurity tab under Create and Edit LWAPP AP Groups.
4.10 For Aruba devices, AMP graphs may display a bandwidth spike when a devices bandwidth counter rolls over, causing the device to report elevated bandwidth data.
4.11 Because of the way AMP polls for user data, it is possible that the user count graph on the HomeÀÆOverview page might drop to zero intermittently; wait a moment and refresh the screen to restore the correct data.
4.12 AMP now pushes all RADIUS management servers defined on the Group ÀÆ AAA page to controllers. Consequently, the RADIUS management section on the GroupÀÆSecurity page was redundant, and has been removed.
4.13 If the User Session report is run on a Master Console with managed AMPs that contain very large amounts of data, the report may fail if it runs for a time period that spans more than a day. Contact firstname.lastname@example.org if you experience this issue.
4.14 The Device Uptime report may show inaccurate information for data over one day; this will be resolved as soon as possible in a maintenance release.
4.15 On the Symbol WS5100, if thin APs are configured to change channels independently of AMP (such as random channel selection), then the APs radios will mismatch on channel whenever a new channel is selected.
4.16 If an AP is marked as down, AMP does not log excessive SNMP error messages.
4.17 When switching a subscriber group from one global group to another, the group should first be changed from Use Global Group yes to no on the GroupsÀÆBasic page. The group should then be changed back to Use Global Group yes, and the new global group should be selected from the dropdown menu.
4.18 Group variable changes cannot be applied between subscriber groups.
4.19 If a WLAN override is created for 802.11bg radios, AMP will show a mismatch that cannot be resolved for the 802.11a radio.
4.20 VisualRF: during the upgrade to 6.2, VisualRF may take as long as 10 minutes to shut down during Step 4 (Stopping AMP Services). It is important to let an upgrade run to completion once it is initiated; do not abort or Control+C the upgrade if this step seems to take longer than usual.
4.21 VisualRF: APs take longer than the synchronization time to appear in VisualRF. The synchronization timer will fetch the AP state data at the specified interval. Device permissions are polled every 15 minutes. It may take up to 15 minutes for new devices to appear in VisualRF.
4.22 VisualRF: Clients may take a long time to age off a site when all APs have been removed.
4.23 VisualRF: Clients associated to APs on other floors will have an unknown phy type. Visit the client monitoring page to view the phy and association information.
4.24 VisualRF: Left-clicking on a planned AP will bring up the Match with Deployed AP instead of the Planned AP menu.
4.25 VisualRF: The server may create two default campuses on a fresh install. One or both of the default campuses can be removed as you create new campuses and deploy your network.
4.26 VisualRF: The Bill of Materials report may not render properly from IE unless certain browser settings are changed: (1) Open IEÀÆToolsÀÆInternet Options (2) Go to the Security tab and click the trusted sites icon (3) Add whatever names you use to refer to that server. For example, if you sometimes call the server amp.corp and sometimes call itamp.corp.yourdomain.com you will need to add both names (5) Set the security slider for trusted sites to medium-low.
4.27 VisualRF: Campuses and buildings may be relocated during an upgrade from 6.1 or 6.1rc4 to the 6.2 general release. Buildings that were originally deployed outside of a background image will be relocated to the top left of the image.
4.28 VisualRF: The default campus or building may lose background during the upgrade if the background was uploaded as a DWG file. Redefine the background images and they will be stored properly.
4.29 VisualRF: Wall attenuation values may change when restoring from a backup. Visit the VisualRFÀÆSetup page and verify that wall attenuation values are correct.
4.30 VisualRF: If an AP is configured to be an air monitor on one radio, VisualRF will not display a heatmap but show associated clients.
4.31 VisualRF: If a client device type or transmit power is overridden, the change will not be reflected in VisualRF until the client is rediscovered or VisualRF is restarted.
4.32 VisualRF: If zoom is used during a floor plan resize, inaccurate client location will result. Zoom to the appropriate level before clicking on the Resize Floor icon.
4.33 VisualRF: The WCS floor plan importation can duplicate floor plans if it is run twice. Radio index, channel and MAC are not retained from WCS, but they will be refetched after the device is matched to AMP.
4.34 VisualRF: The Floor Plan Upload Wizard only supports DWF versions 5.5 and below.
4.35 VisualRF: Rapid changes to the VisualRFÀÆSetup page may cause the server to lock. Disabling the engine and then re-enabling it will resolve any problems.
4.36 VisualRF: The Floor Plan Upload Wizard only retains CAD files. Original files for other types are not retained after importation.