Release Notes for Mobility System Software Version

Transcription

1 Release Notes for Mobility System Software Version Feedback and Support What s New in MSS Version Version Compatibility Upgrading to MSS Version Installing Upgrade Activation Keys on an WLC System Parameter Support Known Behaviors and Issues Changes to Default Behaviors Issues Resolved Since MSS Issues Resolved Since MSS Issues Resolved Since MSS Juniper Networks recommends that you familiarize yourself with the Known Behaviors and Issues section in this document before installing Mobility System Software (MSS) Version 8.0. For additional product information, refer to the following manual in addition to these release notes: MSS Quick Start Guide Version 8.0 MSS Configuration Guide Version 8.0 MSS Command Reference Version 8.0 Informational Note: Please note that the tracking numbers for issues open and resolved have changed to reflect the Juniper Networks Problem Report (PR) tracking system. Product Name Changes Please note that the former Trapeze products now reflect the Juniper Networks product names.. Former Trapeze Name MXR-2 MX-8 MX-200 MX-800 Current Juniper Product Name WLC2 WLC8 WLC200 WLC800R Copyright 2013, Juniper Networks, Inc. 1

2 Former Trapeze Name MX-2800 MP-522 MP-632 Current Juniper Product Name WLC2800 WLA522 WLA632 Feedback and Support Juniper Networks encourages you to provide feedback about your experiences installing and using the product to the Juniper Networks Customer Assistance Center (TAC). What s New in MSS Version 8.0 MSS Version 8.0 contains the following new features: WLA532E - the WLA532E is a new access point model that supports external antennas. Adaptive Channel Planner (Auto-Tune Enhancements) Adaptive Channel Planner (ACP) dynamically assigns the WLA operating channel so that the wireless network can efficiently adapt to the RF environment conditions. Dynamic assignment can be changed when significant changes are measured in the interference level or in the network topology. Eventually, Wi-Fi bandwidth is maximized and maintains the efficiency of communication over the wireless network. Transmit Beam-forming Transmit beam-forming (TxBF) is a technique that uses an array of transmitting antennas to send radio signals with adjusted magnitude and phase at each antenna to achieve a focused beam target to the receiver. TxBF can increase the Signal-to-Noise Ratio (SNR) at the receiver and improve performance. This feature is supported on the WLA532,WLA321, and WLA322. IPv6 Support In this release of MSS, configuring IPv6 addresses is not supported, but IPv6 clients are supported. You can view IPv6 session information and control IPv6 ACLs using MSS. Device Fingerprinting (MSS, RingMaster, and SmartPass) - Manage different devices such as iphones, ipads, and other wireless devices connecting to the wireless network. Version Compatibility RingMaster This version of Mobility System Software (MSS) is intended for use with RingMaster Version 8.0 or higher only. Minimum MSS Requirements for Upgrade Table 1 lists the minimum MSS version an WLC must be running when you upgrade to MSS Version 8.0. If your WLC is running an older MSS version, you can use the upgrade path to upgrade the WLC to 8.0. Informational Note: It is strongly recommended that you follow the upgrade path to install new versions of MSS. In most cases, you cannot upgrade directly to this release from an MSS version earlier than 7.X as recommended in the table. Table 1: Software Requirements for Upgrade to MSS Version 8.0 Product Minimum MSS Version Required Upgrade Path WLC200 7.x 7.0.x.x->7.1.x.x -> 7.3.x.x > 7.5.x.x > 7.6.x.x>7.7.x>8.0 WLC2 7.x 7.0.x.x->7.1.x.x -> 7.3.x.x > 7.5.x.x > 7.6.x.x>7.7.x>8.0 2 Feedback and Support Copyright 2013, Juniper Networks, Inc.

3 Table 1: Software Requirements for Upgrade to MSS Version 8.0 (continued) Product Minimum MSS Version Required Upgrade Path WLC8 7.x 7.0.x.x->7.1.x.x -> 7.3.x.x > 7.5.x.x > 7.6.x.x>7.7.x>8.0 WLC800R 7.3.x 7.3.xx> 7.5.xx>7.6.xx>7.7.x>8.0 WLC880R 7.5.xx 7.5.xx>7.6.xx>7.7.x>8.0 WLC2800R x.x->7.1.x.x -> 7.3.x.x > 7.5.x.x > 7.6.x.x>7.7.x >8.0 Software Versions on the Juniper Support Site When you go to the Software downloads page at to download new software versions, you should note that there are two different files for each WLC/MX platform. The software files labeled with the MX0XXXX.platform.zip are intended for the legacy platforms sold by Trapeze Networks. These controllers have the Trapeze logo and platform name on the front. The WLC0XXXXX.platform.zip software files are intended for the Juniper-branded platforms. These controllers display the Juniper logo and platform name on the front. WARNING! The two file types are not interchangeable between Trapeze-branded and Juniper-branded platforms. You must install the MX file version on Trapeze products, and the WLC file version on Juniper products. Upgrading to MSS Version 8.0 Before you upgrade, see Version Compatibility on page 2. After you verify that the WLC is running the last MSS version required before upgrading to MSS Version 8.0, return to this section. Warning: This release of MSS software no longer supports older MXR-2, MX-8, and MX-8R WLAN controller platforms that were initially built with 32MB of flash. Newer models support 128MB or 256MB. The best method for determining if your controller can support MSS 8.0 is by checking the revision label on the unit: Models MX-8 and MX-8R controller - Revision "P" and above Model MXR-2 controller - Revision "N" and above All Juniper-branded equivalents will support MSS 8.0. Warning: The following MPs are no longer supported in this version of MSS: MP-71 MP-371 (all related models) MP-372 (all related models) Preparing the MX for the Upgrade VLAN IDs higher than 3520 Informational Note: To avoid conflicts with the Juniper internal VLAN numbering scheme, it is strongly advised to use VLAN IDs less then 3520 on WLCs that are upgrading to MSS Version 8.0. Failure to do so may result in lost configuration data. Informational Note: MSS 8.0 includes changes to the storage location of system debug files. Debug information is now stored in persistent user-accessible storage for retrieval after a system restart. 3 Version Compatibility Copyright 2013, Juniper Networks, Inc.

4 Informational Note: Mobility Domains and Mixed Versions of MSS When deploying a mixed version Mobility Domain, VLAN tunnels between WLCs with MSS 7.1 and WLC800/WLC880s with MSS 8.0 are not supported. Caution: Create a backup of your WLC files before you upgrade the WLC. Juniper Networks recommends that you save a backup configuration of the WLC, before you install the upgrade. If an error occurs during the upgrade, you can restore your WLC to a previous configuration. Informational Note: When saving the backup file, MSS copies the file to a temporary location to compare it against an existing file for any errors that may have been introduced during the copying process. After verifying that the file is error-free, MSS deletes the file from the temporary location. Informational Note: Virtual Controller Cluster Configuration Recommendation It is recommended that you install the same version of MSS on all cluster members to have feature parity between the seeds and members. Additionally, it is recommended to use the same WLC models in a cluster configuration. You can use the following command to back up the configuration files: backup system [tftp:/ip-addr/]filename [all critical] To restore an WLC that is backed up, use the following command: restore system [tftp:/ip-addr/]filename [all critical] Upgrade Scenario on page 5 shows an example of the backup command. For more information about these commands, see the Backing Up and Restoring the System section in the Managing System Files chapter of the Juniper Networks Mobility System Software User s Guide. Upgrading an Individual WLC Using the CLI Caution: If you have made configuration changes but have not saved the changes, use the save config command to save the changes, before you backup the WLC. 1. Back up the WLC, using the backup system command. 2. Copy the new system image onto a TFTP server. For example, log into using a Web browser on your TFTP server and download the image onto the server. 3. Copy the new system image file from the TFTP server into a boot partition in the nonvolatile storage of the WLC. For example, WLC800# copy tftp:// /mx boot1:mx You can copy the image file only into the boot partition that was not used for the most recent restart. For example, if the currently running image was booted from partition 0, you can copy the new image only into partition Set the boot partition to the one with the upgrade image for the next restart. 4 Version Compatibility Copyright 2013, Juniper Networks, Inc.

5 5. To verify that the new image file is installed, type show boot. 6. Reboot the software. To restart a WLC and reboot the software, type the following command: reset system When you restart the WLC, the WLC boots using the new MSS image. The WLC also sends the WLA version of the new boot image to WLAs and restarts the WLAs. After an WLA restarts, the version of the new WLA boot image is checked to make sure the version is newer than the version currently installed on the WLA. If the version is newer, the WLA completes installation of the new boot image by copying the boot image into the WLA flash memory, which takes about 30 seconds, then restarts again. The upgrade of the WLA is complete after the second restart. Upgrade Scenario To upgrade an WLC800, use the following upgrade example. Caution: This example copies the image file into boot partition 1. On your WLC, copy the image file into the boot partition that was not used the last time the WLC was restarted. For example, if the WLC booted from boot partition 1, copy the new image into boot partition 0. To see boot partition information, type the show boot command. WLC800# save config success: configuration saved. WLC800# backup system tftp:/ /sysa_bak success: sent bytes in seconds [ bytes/sec] WLC800# copy tftp:// /mx boot1:mx success: received bytes in seconds [ bytes/sec] WLC800# set boot partition boot1 success: Boot partition set to boot1:mx ( ). WLC800# show boot Configured boot version: Configured boot image: boot1:mx Configured boot configuration: file:configuration Backup boot configuration: file:backup.cfg Booted version: Booted image: boot1:mx Booted configuration: file:configuration Product model: WLC WLC800# reset system... rebooting... When saving the backup file, MSS copies the file to a temporary location to compare it against an existing file for any errors that may have been introduced during the copying process. After verifying that the file is error-free, MSS deletes the file from the temporary location. Installing Upgrade Activation Keys on an WLC WLA licensing is supported on WLC platforms as shown in Table 2: Table 2: Licensing and Upgrade Increments for the WLC Models WLC Model Base WLA Support Maximum WLA Support Upgrade Increment WLC800R/880R / or 32 WLC WLC or Version Compatibility Copyright 2013, Juniper Networks, Inc.

6 Caution: If you downgrade to a previous version of MSS that does not support the higher capacity licenses, the number of allowed WLAs is reduced to comply with the older software limitations. Feature licensing is supported on WLC platforms as show in Table 3. Table 3: WLC Feature Licensing Matrix Spectrum Analysis High Availability (WLA522, WLA532, WLA321 WLC Model Advance Voice Module Module Mesh/Bridging Module and WLA322) WLC2 Supported Supported Up to 4 WLAs (16 WLAs in Cluster mode) WLC8 Supported Supported Up to 12 WLAs (48 in Cluster mode) WLC200 Supported Supported Up to 192WLAs (768 in Cluster mode) WLC800R Supported Supported Up to 128 WLAs (512 WLAs in Cluster mode) WLC880R Supported Supported Up to 256 WLAs Supported Supported Supported Supported Supported (2048 in Cluster Mode) WLC2800 Supported Supported Up to 512 WLAs (4096 in Cluster mode) Supported Informational Note: Spectrum analysis is supported on WLCs as follows: WLC2 and WLC8 - support one radio on simultaneous WLAs in spectral graphing mode. WLC200 - supports four radios on simultaneous WLAs in spectral graphing mode. WLC800R, WLC880R, and WLC support six radios on simultaneous WLAs in spectral graphing mode. Informational Note: Spectrum Analysis licensing for cluster configuration is applied to the Primary Seed and propagated to the Secondary Seed. However in a Mobility Domain without a cluster configuration, Spectrum Analysis licensing is applied to any WLC with a WLA capable of running Spectrum Analysis. To upgrade an WLC license: 1. Obtain a license coupon for the upgrade from Juniper Networks or your reseller. 2. Establish a management session with the WLC to display the serial number. To display the serial number, type the following command: show version In the following example, the WLC serial number is : WLC800> show version Mobility System Software, Version: REL Copyright (c) Juniper Networks, Inc. All rights reserved. 6 Version Compatibility Copyright 2013, Juniper Networks, Inc.

7 Build Information: (build#0) REL_8_0_0_branch :21:00 Model: WLC800R Hardware Mainboard: version 24 ; revision 3 ; FPGA version 24 PoE board: version 1 ; FPGA version 6 Serial number Flash: md0a Kernel: 3.0.0#112: Wed Aug 2 10:26:32 PDT 2009 BootLoader: 8.0 / Use a Web browser to access the Juniper Networks license server at the following URL: 4. On the WLC, use the following command at the enable (configuration) level of the CLI to install the activation key: set license activation-key In the following example, an activation key for an additional 96 WLAs is installed on an WLC200: WLC800# set license 3B02-D821-6C19-CE8B-F20E success: license accepted 5. Verify installation of the new license by typing the following command: WLC800# show licenses Feature : 96 additional MPs Support for the additional WLAs begins immediately. You do not need to restart the WLC to place the upgrade into effect. 7 Version Compatibility Copyright 2013, Juniper Networks, Inc.

8 System Parameter Support Table 4, Table 5, and Table 6 list the recommended or maximum supported values for major system parameters. Table 4: Mobility System Parameters Parameter Supported Value WLC switches in a single Network Domain 500 WLC switches in a single Mobility Domain 64 Roaming VLANs per WLC WLC2800: 256 total (256 configured) WLC800R/WLC880R: 256 total (128 configured) WLC200: 256 total (128 configured) WLC8: 256 total (128 configured) WLC2: 256 total (128 configured) VLANs per Mobility Domain 2048 WLAs per WLC WLC2800: 4096 configured, 512 active WLC880R: 2048 configured, 256 active WLC800R: 512 configured, 128 active WLC200: 768 configured, 192 active WLC8: 48 configured, 12 active WLC2: 16 configured, 4 active Includes directly attached WLAs and Distributed WLAs. Inactive configurations are backups. Minimum link speed between WLCs in a Mobility 128 Kbps Domain Minimum link speed between an WLC and WLA in 128 Kbps and 95ms round trip latency - this value is different if the a Mobility Domain WLAs are configured as remote WLAs. Number of Service Profiles per WLC WLC2: 32 WLC8: 32 WLC200: 192 WLC800/WLC880: 128 WLC2800: 512 Number of Radio Profiles per WLC WLC2: 4 WLC8: 12 WLC200: 192 WLC800R/WLC880R: 128 WLC2800: System Parameter Support Copyright 2013, Juniper Networks, Inc.

9 Table 5: Network Parameters Parameter Supported Value Forwarding database entries WLC2800: WLC800R/WLC880R: WLC200: 8192 WLC8: 8192 WLC2: 8192 Statically configured VLANs WLC2800: 512 configured WLC800R/WLC880R: 256 configured WLC200: 128 configured WLC8: 128 configured WLC2: 128 configured Spanning trees (STP/PVST+ instances) 64 ACLs ACLs per WLC 170 ACEs per ACL: WLC2800: 256 WLC800R/WLC880R: 256 WLC200: 256 WLC8: 25 WLC2: 25 Location Policies Location Policies per WLC: All models: 1 The Location Policy can have up to 150 rules. IGMP streams 500 Note: Replication of a stream on multiple VLANs counts as a separate stream on each VLAN. Mesh Services and Bridging Mesh Depth 3 Mesh Links (Portal<->Mesh WLA<->Mesh WLA) Mesh Fan Out 6 WLAs Maximum Supported Mesh Nodes per Mesh Portal 6 Bridge Links 1:1:1 9 System Parameter Support Copyright 2013, Juniper Networks, Inc.

10 Table 6: Management Parameters Parameter Supported Value Maximum instances of RingMaster simultaneously 32 managing a network Telnet management sessions WLC2800: 8 WLC800R/WLC880R: 8 WLC200: 8 WLC8: 4 WLC2: 4 The maximum combined number of management sessions for Telnet and SSH together is 8 for the WLC200, or 4 for the WLC8 and WLC2, in any combination. SSHv2 management sessions WLC2800: 8 WLC800R/WLC880R: 8 WLC200R: 8 WLC8: 4 WLC2: 4 Telnet client sessions (client for remote login) WLC2800: 8 WLC800R/WLC880R: 8 WLC200R: 8 WLC8: 4 WLC2: 4 NTP servers 3 SNMP trap receivers 8 Syslog servers 4 RADIUS and LDAP servers 40 configured on the WLC 10 in a server group 4 server groups in a AAA rule A maximum of 40 servers in any combination of RADIUS and LDAP - for example, 30 RADIUS servers and 10 LDAP servers. Table 7: Client and Session Parameters Parameter Supported Value Authenticated and associated clients per radio 100 Clients who are authenticated but not yet associated are included in the total. Active clients per radio 50 Total number of active clients simultaneously sending or receiving data. 10 System Parameter Support Copyright 2013, Juniper Networks, Inc.

11 Table 7: Client and Session Parameters (continued) Parameter Active AAA sessions (or clients trying to establish active connections) per WLC Supported Value WLC2800: WLC800R: 3200 WLC880R: 6400 WLC200R: 4800 WLC8: 300 WLC2: 100 AAA users configured in local database WLC2800: 1000 WLC800R/WLC880R: 1000 WLC200R: 1000 WLC8: 250 WLC2: 250 Known Behaviors and Issues The following issues are known behaviors and issues in this version of Mobility System Software. ICMPv6 Router Advertisement ACL does not work on a WLC880 when mapped with the uplink port direction out. [PR800132] Description Configuring an IPv6 ICMP ACL on a WLC880 does not work as expected. The ACL should block router advertisements to the WLC880, but the advertisements are not blocked. Workaround No workaround at this time. Attempts to insert duplicate record in class autorf/cohorts with key 51fb9c68 len 2 from source IP Address. [PR ] Description In a large scale setup (for example, if you have more than eight WLC200 in the cluster, more than 700 WLAs and more than 19,000 client sessions), you may see the following error message: ERROR CLUSTER_BAD_DATATYPE: cc_lookup_rec_params:autorf_cohort_use_table_insert: Attempt to insert duplicate record in class autorf/cohorts with key 51fb9c68 len 2 from source <src ip> Workaround No workaround at this time. AutoRF error messages may be displayed on the release build. [PR883887] Description You may see AutoRF error messages on the release build for MSS x. However, this message should not influence the functionality of the AutoRF feature. Workaround No workaround at this time. Third Party neighbor access points (WLAs) are not considered in the auto-channel plans. [PR883986] Description Currently, third party neighbor access points (WLAs) are not considered in the auto-channel algorithm. Workaround No workaround at this time. Auto-tune schedule does not deploy channels for all the WLAs in a cluster during the cluster failover. [PR888703] Description In a cluster, when the primary seed is down and the secondary seed takes over, then the Auto-tune schedule does not deploy channels for all the WLAs in the cluster. Workaround No workaround at this time. Copyright 2013, Juniper Networks, Inc. Known Behaviors and Issues 11

12 Auto-tune power-lockdown option does not work in x release. [PR883843] Description The power-lockdown option in Auto-tune feature does not lock the current channel transmit power settings on IEE a band, and the system raises error for invalid tx-power on channel 36. Workaround No workaround at this time. Auto-tune power-lockdown option causes the controller to crash. [PR890615] Description If the command auto-ap is enabled in the controller configuration, then do not use auto-tune power-lockdown option. The controller may crash. Workaround No workaround at this time. Changes to Default Behaviors When WLAs use DHCP Discovery to locate WLCs on the network, the ability to use Option 12 and Option 77, in addition to Option 43, as part of the discovery process is now available. In previous releases of MSS, the WebAAA Web Portal allowed a user to submit a valid username and an empty password. This has now changed to require that the user enter a non-zero length password to log onto the network. [PR802552] Issues Resolved Since MSS Traffic becomes unstable after enabling per user bandwidth limit in the QoS profile on the wireless LAN controllers. [PR852638] Issues Resolved Since MSS The SNMP process crashed during an SNMPwalk for lldpremmanaddroid. [PR ] While running MSS 8.0 MR1 with the auto-tune function enabled, some of the WLAs that were reset did not manage to enable radio 2 after rebooting. This issue occurred because the DFS channels were enabled prior to the deployment of the channels to the WLA. [PR ] A primary seed became unresponsive when configured in a Mobility Domain consisting of three WLC2800s. [PR883378] A WLC880 stopped responding on the network. [PR882922] Using the URL attribute for Web Portal configuration did not work properly. [PR873790] A primary access manager (PAM) became unresponsive after a client disconnected and used multiple IPv6 addresses. [PR876277] When requesting sessions for a specific VLAN pool, sessions for all VLANs are displayed. [PR869550] When blacklist configuration changes were made, the primary seed in a cluster was unreachable for a period of time. [PR854887] If the mesh feature was configured on an UNII2 and UNII2-extended band, the mesh WLA did not connect to the portal WLA. [PR850189] HTTPS was causing error messages on input socket 14. [PR849588] A WLC880R ceased responding on the network after upgrading to MSS [PR847973] Countermeasures was not activating properly and displayed no output when using the show rfdetect data command. [PR845430] Clients could not consistently connect to the wireless network after upgrading to MSS [PR840246] 12 Changes to Default Behaviors Copyright 2013, Juniper Networks, Inc.

13 Wired authentication did not work on the network. [PR839020] High traffic load on the MP-82 caused the MP to stop sending network traffic. [PR834832] The redirect page was not working correctly for the Web Portal feature. [PR828281] Poor performance on the WLA322 was caused by configuring overlay mode with frame aggregation enabled.[pr827678] Excessive retransmits were causing the four-way handshake authentication to fail on the wireless network. [PR824160] If spectral analysis is configured on both radios of a WLA322, the performance of the WLA is severely impacted. [PR823075] Station queued packets were not scheduled for transmission and caused connectivity issues on the network. [PR820422] Using the show port transceiver command did not display information about the XFPs plugged into a port. [PR819956] ipad devices were unable to connect on the wireless network. [PR816489] Member WLCs in a cluster sync had to be rebooted to successfully rejoin and sync to the cluster. [PR813478] The WLA MAC address was incorrectly displayed in the output of the show auto-tune neighbors command. [PR805324] When auto-tune failed on the network, the SNMP trap trapautotunefailuretraps was not sent. [PR792028] When configuring a WLA-WW for a remote site and using a different country code, the configuration was rejected. [PR790516] The device type and device profile were not identified when using uppercase letters for a MAC rule. [PR787993] Auto-tune error messages were displayed after the cluster configuration is disabled or a Mobility Domain is deleted. [PR774557] Multiple issues with the VLAN Pool commands were resolved. [PR737081] The client VLAN name was not case-sensitive when a client connected locally, but the VLAN name was case-sensitive when using WLC-WLC tunnels. [PR736494] Using an incorrect VLAN tag when removing VLAN port mapping cleared the mapping.[pr734104] A wireless client could not access the network if AP-AP tunnel was enabled and WAN outage mode configured for one of the WLAs. [PR730928] You could not add more than one VLAN to a VLAN pool in a single command. [PR729004] Using the show config area service-profile all command displayed hidden commands. [PR719862] A security ACL did not work properly if local switching was enabled. [PR718670] No warning was issued if you set the mode to 11n required and attempted to use unsupported crypto types. [PR691808] RADIUS VLAN CoA for locally switched Web portal session timed out when the VLAN was on the WLA but the WLC did not time out. [PR657157] Issues Resolved Since MSS Daylight Savings Time settings were displayed incorrectly. [PR825593] MSS 8.0 did not support MP-82 memory capability. [PR817598] Wireless client could not redirect and log into the network due to tunnel limitations on the WLC. [PR813987] Copyright 2013, Juniper Networks, Inc. Issues Resolved Since MSS

14 A cluster configuration caused the WLCs to become unresponsive on the network. [PR812281] An incorrect value for the RADIUS attribute Tunnel-Private-Group-ID caused bad processing on the WLC. [PR812272] An erroneous calculation during the SNMP process caused the WLC to become unresponsive. [PR809268] Enabling auto-tune on WLAs configured using the auto ap feature did not work. [PR807642] Enabling RADIUS trace on the WLC caused it to become unresponsive.[pr804331] A Web AAA client could log onto the network using LDAP and simple authentication.[pr801923] If you had a large number of WLAs with location strings configured and you upgraded to MSS (FRS), the configuration would not load. After upgrading to MSS Version (MR1) and you need to downgrade to the previous version, a Service Release of MSS (FRS) is available from JTAC that corrects this problem. [PR810036] The CLI displayed configuration error messages when there no issues with the configuration. [PR799797] CoA request was dropped if the last-resort user did not match. [PR795173] WLAS would not boot if there were two entries in the DNS record resolving the domain name. [PR794134] After rebooting and synchronizing the cluster configuration, the WLC became unresponsive on the network. [PR794815] ARP error messages were incorrectly displayed on a WLC.[PR786894] Bad error messages were generated in the forwarding port database. [PR778462] Poor download performance was reported on WLA522 and WLA5332 running MSS 7.6 code. [PR752905] Clients could not roam from mesh to mesh WLAs. [PR750687] A RADIUS server was incorrectly reported as inactive on the network. [PR724279] Cluster configuration was unstable due to IGMP scaling limitations. [PR705667] No warning messages was displayed when the incorrect crypto types were configured for a n profile. [691808] Identical WLA models using the same radio channel, and radio profile, displayed different tx-power limits when autotune was enabled. [PR691013] If you have an ACL mapped on the user direction IN, clearing the ACL has no effect on the configuration. [PR683781] The attribute VLAN is now required when configuring MAC and User groups. [PR670577] The Web attribute was missing from the login type when configuring CoA for a AAA Profile. [PR656785] 14 Issues Resolved Since MSS Copyright 2013, Juniper Networks, Inc.