Release Notes for MSS Version (MR8)

Transcription

1 Release Notes for MSS Version (MR8) Feedback and Support New and Enhanced Features Version Compatibility Minimum MSS Requirements for Upgrade Upgrading to MSS Version Upgrading an Individual WLC by Using the CLI Hitless Upgrade of Controllers in a Cluster Enabled Mobility Domain To Downgrade an MSS Version in a Cluster Enabled Mobility Domain Installing Upgrade Activation Keys on a WLC System Parameter Support Known Behaviors and Issues Issues Resolved in MSS (9.0MR8) Issues Resolved in MSS (9.0MR7) Issues Resolved in MSS (9.0MR6) Issues Resolved in MSS (9.0MR5) Issues Resolved in MSS (9.0MR4) Issues Resolved in MSS (9.0MR3) Issues Resolved in MSS (9.0MR2) Issues Resolved Prior to MSS (9.0MR1) Known Limitations Changes to Default Behaviors Errata in Documentation We recommend that you familiarize yourself with the Known Behaviors and Issues section of this release notes before installing Mobility System Software (MSS) Version 9.0. For additional product information, refer to the following documents: MSS Quick Start Guide Version 9.0 MSS Configuration Guide Version 9.0 MSS Command Reference Version 9.0 Copyright 2015, Juniper Networks, Inc. 1

2 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 MX-2800 MP-522 MP-632 Current Juniper Product Name WLC2 WLC8 WLC880 WLC800R WLC2800 WLA522 WLA632 Feedback and Support We encourage you to provide feedback about your experiences installing and using the product to the Juniper Networks Customer Assistance Center (JTAC). New and Enhanced Features This section describes the new features and enhancements to existing features in the following MSS releases: What s New in MSS Version 9.0 What is New in MSS Version What is New in MSS Version What s New in MSS Version 9.0 The MSS Release 9.0 provides two versions MSS Version and MSS Version and provides support for the following new features:.junosv Wireless LAN Controller (JunosV WLC) The next-generation wireless LAN controller is a virtual controller using a cloud-based architecture with physical access points. The current functionality of a physical controller is available on the virtual controller, and the virtual controller can support up to 256 access points. The virtual controller runs on a virtual machine (VM) environment that support operating systems and execute applications. For system, parameters, see Table 7. Support for Wireless LAN Controller WLC100 The MSS Version supports Juniper's next-generation WLAN controller, the WLC100, that cost-effectively enables WLAN services in small to medium-sized branches and schools, small offices, and retail stores. WLC100 will replace WLC2 and WLC8. Download MSS Version (WLC Version 9.0 (FRS) for WLC100) from the Software Download page for the WLC100 platform. All other platforms support MSS Version Wi-Fi Alliance Hot Spot 2.0 Support The Juniper wireless LAN (WLAN) solution supports Hot Spot requirements and can seamlessly onboard Wi-Fi client devices at Hot Spot deployments that enables both mobile operators and Multiple System Operators (MSOs) to offload mobile data traffic onto Wi-Fi Hot Spots. The access points WLA321, WLA322, WLA522, WLA532, and WLA632 have passed the Hot Spot 2.0 certification. 2 Feedback and Support Copyright 2015, Juniper Networks, Inc.

3 Persistent Configuration for WLAs Persistent configuration feature is an enhancement to the existing remote access point feature, which provides the ability to have the access points remember its configuration once it is configured on the controller. With this feature, the access point continues to work indefinitely without being connected to the controller. This feature is supported on WLA321, WLA322, WLA532, and WLA532E. Extended Authorization Support for WLAs To extend support for remote access points, the access points can now act as RADIUS authenticators for sessions managed by the access points and accept mac, dot1x pass-through, and last-resort connections during outage. In addition, extra functionality is added to improve the access point sessions, including time attributes and sharing access point managed client session information with controllers. The attributes that are not supported include: End Date, Start Date, and Time of Day. Access Point Power Policy (Replaces Auto-tune Power) This feature replaces the auto-tune power feature in earlier versions of MSS, and addresses customer issues with the previous implementation. A mechanism is required, particularly in dense deployments, for setting the transmit power levels of access point radios, to facilitate good roaming decisions by setting very similar power levels between WLAN radios. Enhancements to VLAN Pooling The primary goal of configuring VLAN pooling is to load balance sessions evenly across the VLANs in the pool. MSS 9.0 supports two options: MAC Address Hashing and Load-balancing. For both the options, a VLAN is selected only if it has not reached the configured cap of sessions per VLAN. What is New in MSS Version CE Compliance Declaration of Conformity with Regard to the ETSI EN v1.8.1 Standard This declaration is valid only for configurations supported or provided by Juniper Networks Systems for use within the EU. All Juniper WLA532-WW, WLA532E-WW, and WLA322-WW equipment are now compliant with the ETSI EN v1.8.1standard. The WLA devices are categorized as non-frequency Hopping Spread Spectrum (FHSS) and Adaptive devices. Specifically, this MSS release ensures that the WLAs are compliant with requirements such as Adaptivity and others detailed in Sections from through for non-fhss devices in the mentioned ETSI EN v1.8.1 standard. What is New in MSS Version CE Compliance Declaration of Conformity with Regard to the ETSI EN v1.8.1 Standard This declaration is valid only for configurations supported or provided by Juniper Networks Systems for use within the EU. All Juniper WLA321-WW equipment are now compliant with the ETSI EN v1.8.1standard. The WLA devices are categorized as non-frequency Hopping Spread Spectrum (FHSS) and Adaptive devices. Specifically, this MSS release ensures that the WLAs are compliant with requirements such as Adaptivity and others detailed in Sections from through for non-fhss devices in the mentioned ETSI EN v1.8.1 standard. Version Compatibility RingMaster This version of Mobility System Software (MSS) is intended for use with RingMaster Version 9.0 or higher only. 3 Version Compatibility Copyright 2015, Juniper Networks, Inc.

4 Minimum MSS Requirements for Upgrade Table 1 lists the minimum MSS version an WLC must be running when you upgrade to MSS Version 9.0. If your WLC is running an older MSS version, you can use the upgrade path to upgrade the WLC to 9.0. Table 1: Software Requirements for Upgrade to MSS Version 9.0 Product Minimum MSS Version Required Upgrade Path WLC880 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.x>9.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.x>9.0> 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.x>9.0> WLC800R 7.3.x 7.3.xx> 7.5.xx>7.6.xx>7.7.x>8.0.x>9.0> WLC880R 7.5.xx 7.5.xx>7.6.xx>7.7.x>8.0.x>9.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.x>9.0> WLC > JunosV WLC > Informational Note: If you have MSS Version or later versions installed on your system, you can upgrade your system directly to MSS Version However, if you have a version earlier than MSS Version , then you must first upgrade to MSS Version before upgrading to any later versions of MSS. Informational Note: 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 side of the controller. The WC0XXXXX.platform.zip software files are intended for the Juniper-branded platforms. These controllers display the Juniper logo and platform name on the front side of the controller. 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 9.0 Before you upgrade, see Version Compatibility on page 3. After you verify that the WLC is running the minimum MSS version required to upgrade to MSS Version 9.0, return to this section. 4 Upgrading to MSS Version 9.0 Copyright 2015, Juniper Networks, Inc.

5 Informational Note: 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 9.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 9.0. 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 MX for the Upgrade Informational Note: VLAN IDs higher than 3520 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 9.0. Failure to do so may result in lost configuration data Informational Note: MSS 9.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. 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 9.0 are not supported. Informational Note: Create a backup of your WLC files before you upgrade the WLC. We recommend 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 We recommend that you install the same version of MSS on all cluster members to have feature parity between the seeds and members. Additionally, use the same WLC models in a cluster configuration. You can use the following command to back up the configuration files: 5 Upgrading to MSS Version 9.0 Copyright 2015, Juniper Networks, Inc.

6 backup system [tftp:/ip-addr/]filename [all critical] To restore a WLC that is backed up, use the following command: restore system [tftp:/ip-addr/]filename [all critical] Upgrade Scenario on page 7 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 Configuration Guide. Upgrading an Individual WLC by Using the CLI Informational Note: 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 onto an inactive boot partition in the nonvolatile storage of the WLC. For example, WLC800# copy tftp:// /wc boot1:wc To get the list of images for the WLCs, go to the Software Downloads page on Informational Note: If boot1 is the active boot partition, an error is displayed. You must copy the new image to the other boot, which is boot0. If boot1 is the configured boot partition and not the active boot, an error is displayed. Change boot0 to the configured boot using the command set boot partition boot0 and then copy the image to boot1. 4. Set the partition to the boot to which the new system image is copied using the command set boot partition boot1 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 a 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. 6 Upgrading to MSS Version 9.0 Copyright 2015, Juniper Networks, Inc.

7 Upgrade Scenario To upgrade a WLC2800, use the following upgrade example. Informational Note: 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. WLC2800# save config success: configuration saved. WLC2800# backup system tftp:/ /sysa_bak success: sent bytes in seconds [ bytes/sec] WLC2800# copy tftp:// /images/ /wc boot1:wc success: received bytes in seconds [ bytes/sec] success: copy complete. WLC2800# set boot partition boot1 success: Boot partition set to boot1:wc ( ). WLC2800# show boot Configured boot version: Configured boot image: boot1:wc Configured boot configuration: file:configuration Backup boot configuration: file:rmbackup Booted version: Booted image: boot0:wc Booted configuration: file:configuration Product model: WLC2800 WLC2800# reset system This will reset the entire system. Are you sure (y/n)y Closing network connections... Preserving command audit logs. Size of preserved command audit log is now 7394 blocks Shutting down daemons... Shutting down filesystems......system will reboot... 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. Hitless Upgrade of Controllers in a Cluster Enabled Mobility Domain To upgrade all the controllers in a cluster enabled mobility domain: 1. Back up the WLC, using the backup system command. 2. Copy the new system image from a TFTP server onto the inactive boot partitions of all the controllers in a mobility domain. The boot partition should not be the configured partition or the active boot partition. For example, to copy the new system image from a TFTP server to the inactive boot partition, type the following command: copy tftp://<tftp-server-ip-address>/<image-name>/ boot1:<image-name> To get the list of images for the WLCs, go to the Software Downloads page on 7 Upgrading to MSS Version 9.0 Copyright 2015, Juniper Networks, Inc.

8 Informational Note: If boot1 is the active boot partition, an error is displayed. You must copy the new image to the other boot, which is boot0. If boot1 is the configured boot partition and not the active boot, an error is displayed. Change boot0 to the configured boot using the command set boot partition boot0 and then copy the image to boot1. 3. Set the partition to the boot to which the new system image is copied in every controller using the command set boot partition boot1 4. Save the configuration in every controller. Enter the following command in the primary seed, secondary seed, and all member controllers: save configuration (primary and secondary seeds) and save configuration local for all member controllers 5. Enter the following command in the primary seed of the mobility domain. upgrade cluster To Downgrade an MSS Version in a Cluster Enabled Mobility Domain 1. Copy the image from a TFTP server onto the inactive boot partitions of all the controllers in a mobility domain. The boot partition should not be the configured partition or the active boot partition. For example, to copy the new system image from a TFTP server to the inactive boot partition, type the following command: copy tftp://<tftp-server-ip-address>/<image-name>/ boot1:<image-name> To get the list of images for the WLCs, go to the Software Downloads page on 2. Set the partition to the boot to which the new system image is copied in every controller using the command set boot partition boot1 3. Save the configuration in every controller. Enter the following command in the primary seed, secondary seed, and all member controllers, save configuration (primary and secondary seeds) and save configuration local for all member controllers 4. Enter the following command in every controller in the mobility domain: reset system Installing Upgrade Activation Keys on a WLC WLA licensing is supported on WLC platforms as shown in the following Table : 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 128 WLC JunosV WLC , 8, or 32 8 Upgrading to MSS Version 9.0 Copyright 2015, Juniper Networks, Inc.

9 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 2. Table 2: WLC Feature Licensing Matrix Spectrum Analysis High Availability (WLA522, WLA532, WLC Model Advance Voice Module Module Mesh/Bridging Module WLA321, 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) WLC100 Supported Supported Up to 32 WLAs (128 in Cluster mode) WLC880 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 (2048 in Cluster Mode) WLC2800 Supported Supported Up to 512 WLAs (2048 in Cluster mode) JunosV WLC Supported Supported Up to 256 WLAs (2048 in Cluster mode) Supported Supported Supported Supported Supported Supported Supported Supported Informational Note: Spectrum analysis is supported on WLCs as follows: WLC2 and WLC8 - support one radio on simultaneous WLAs in spectral graphing mode. WLC880 - supports four radios on simultaneous WLAs in spectral graphing mode. WLC800R, WLC880R, and WLC support six radios on simultaneous WLAs in spectral graphing mode. WLC100 - support one radio on simultaneous WLAs in spectral graphing mode.junosv 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 a 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 JJ : 9 Upgrading to MSS Version 9.0 Copyright 2015, Juniper Networks, Inc.

10 WLC880-M20# show version Mobility System Software, Version: REL Copyright (c) Juniper Networks, Inc. All rights reserved. Build Information: (build#0) REL_9_0_2_branch :37:00 Model: WLC880R Hardware Mainboard: version 20 ; revision A00 ; FPGA version 10 Serial number JJ Flash: Kernel: BootLoader: 7.8 / Use a Web browser to access the Juniper Networks license server at the following URL: or 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 WLC800: 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. System Parameter Support Table 3, Table 4, and Table 5 list the recommended or maximum supported values for major system parameters. Table 3: 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) WLC880: 256 total (128 configured) WLC8: 256 total (128 configured) WLC2: 256 total (128 configured) WLC100: 128 JunosV WLC: 256 VLANs per Mobility Domain System Parameter Support Copyright 2015, Juniper Networks, Inc.

11 Table 3: Mobility System Parameters (continued) Parameter WLAs per WLC WLC2800: 4096 configured, 512 active Minimum link speed between WLCs in a Mobility Domain Supported Value WLC880R: 2048 configured, 256 active WLC800R: 512 configured, 128 active WLC880: 768 configured, 192 active WLC8: 48 configured, 12 active WLC2: 16 configured, 4 active WLC100: 256 configured, 32 active Includes directly attached WLAs and Distributed WLAs. Inactive configurations are backups. JunosV WLC: 256 active, 2048 configured in cluster 128 Kbps 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 WLC100: 64 WLC880: 192 WLC800: 128 WLC2800: 512 JunosV WLC: 256 Number of Radio Profiles per WLC WLC2: 4 WLC8: 12 WLC100: 32 WLC880: 192 WLC800R/WLC880R: 128 WLC2800: 512 JunosV WLC: 256 Copyright 2015, Juniper Networks, Inc. System Parameter Support 11

12 Table 4: Network Parameters Parameter Supported Value Forwarding database entries (maximum supported) WLC2800: WLC800R/WLC880R: WLC880: 8192 WLC100: 8192 WLC8: 8192 WLC2: 8192 JunosV WLC: Statically configured VLANs WLC2800: 512 configured WLC800R/WLC880R: 256 configured WLC880: 128 configured WLC8: 128 configured WLC2: 128 configured WLC100: 128 configured JunosV WLC: 256 configured Tunneled or Dynamic VLANs per controller WLC2800: 510 WLC800R/WLC880R: 256 WLC8: 128 WLC2: 128 WLC100: 128 JunosV WLC: 256 Spanning trees (STP/PVST+ instances) 64 ACLs ACLs per WLC 170 ACEs per ACL: WLC2800: 256 WLC800R/WLC880R: 256 WLC880: 256 WLC8: 25 WLC2: 25 WLC100: 50 JunosV WLC: 256 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 12 System Parameter Support Copyright 2015, Juniper Networks, Inc.

13 Table 5: Management Parameters Parameter Supported Value Maximum instances of RingMaster simultaneously 32 managing a network Telnet management sessions WLC2800: 8 WLC800R/WLC880R: 8 WLC880: 8 WLC8: 4 WLC2: 4 WLC100: 4 JunosV WLC: 4 The maximum combined number of management sessions for Telnet and SSH together is 8 for the WLC880, or 4 for the WLC8 and WLC2, in any combination. SSHv2 management sessions WLC2800: 8 WLC800R/WLC880R: 8 WLC880: 8 WLC8: 4 WLC2: 4 WLC100: 4 JunosV WLC: 4 Telnet client sessions (client for remote login) WLC2800: 8 WLC800R/WLC880R: 8 WLC880R: 8 WLC8: 4 WLC2: 4 WLC100: 4 JunosV WLC: 4 NTP servers 3 SNMP trap receivers 8 Syslog servers 4 RADIUS and LDAP servers 40 configured on the WLC 100 RADIUS groups per WLC 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 6: Client and Session Parameters Parameter Maximum number of authenticated and associated clients per access point Active clients per radio Supported Value 500 Total number of active clients simultaneously sending or receiving data. This is a subjective number based on the performance requirement. Copyright 2015, Juniper Networks, Inc. System Parameter Support 13

14 Table 6: 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 WLC8: 300 WLC2: 100 WLC100: 800 JunosV WLC: 6400 AAA users configured in local database WLC2800: 1000 WLC800R/WLC880R: 1000 WLC8: 250 WLC2: 250 WLC100: 1000 JunosV WLC: 999 Table 7: JunosV Wireless LAN Controller Parameters Parameter Description or Supported Value Form factor Virtual Machine Software Deployment modes Local switching mode Yes Overlay mode Yes Mesh Yes Scale Minimum access points 4 Maximum access points 256 Active Maximum client support 6400 Maximum number of remote WLA groups 256 Active, 2048 in cluster Maximum access points per remote WLA 100 group Maximum SSIDs 128 Maximum VLANs 256 Minimum Hardware Specification Interfaces or network I/O 1 GE CPU 2 GHz Memory 2 GB recommended Disk Space 16 GB Features Supported Auto-tune Yes Bandwidth Control (Identity based) Yes Admission Control (CAC)/Wi-Fi Multimedia Yes (WMM) Guest services (wireless) Yes Wired Authentication Yes Access Control Lists (ACLs) Yes JunosV WLC High Availability WLC Controller Clustering 14 System Parameter Support Copyright 2015, Juniper Networks, Inc.

15 Known Behaviors and Issues The following are the known behavior and issues in this version of Mobility System Software. MAC ACLs that use a redirect port are sent to cluster members on which that port does not exist. [PR ] Description A MAC permit ACL that uses a redirect port configured on primary seed is sent to all cluster members even if the port configured in the ACL does not exist on one or some of the cluster members. Because of this, the traffic matched by the ACL might not be redirected as the physical port is missing. Enabling multicast key rotation disconnect clients then reconnects after about 30 minutes. [PR ] Description After you connect 802.1X clients to a wireless network, if you enable multicast key rotation and set the rotation time to a valid interval, until about 30 mins, clients do not receive EAPoL messages from the WLC. Because of this delay clients might disconnect and then reconnect to the network. If you enable a radio profile for a WLA, the explicitly disabled radios of that WLA are also enabled. [PR ] Description Assign a radio profile to a few WLAs and then disable the radios on some of the WLAs. If you now disable and then enable the radio profile, all the explicitly disabled radios are also enabled. The explicitly disabled radios should remain disabled even if you disable and then enable the radio profile assigned to the WLAs. Clients might face connectivity issues when they roam between network domains. [PR ] Description After you configure a network domain by using RingMaster and push the configuration to a WLC, the VLAN tunnel between the WLC and the remote WLC is not created. Hence, the roaming clients are unable to establish a successful network connection. In MSS and MSS , WLA632 boots up with? when no channels are available for it in the current regulatory domain. [PR ] Description When you add a WLA632 to a WLC with country code US and then change the country code to Germany (DE), the following behavior is observed in MSS and MSS respectively: The country code is not accepted as no channels are available for it to be allocated. Therefore, you need to first delete the existing WLA country code settings and then add the WLA to the WLC. The WLA boots up with? in channel. The WLA boots with? in channel if you change the country code or if you delete the existing WLA country code settings. A VLAN name that has a numeral is accepted. [PR ] Description When you execute the set service-profile sms attr vlan-name? command, you must specify the VLAN name. The VLAN name must not start with a numeral. However, if you specify a numeral as the first character of the VLAN name, no error message is shown. The show remote-site command shows incorrect output. [PR ] Description After you configure the WAN-outage mode with local switching enabled, the information is not updated in the show remote-site command. Copyright 2015, Juniper Networks, Inc. Known Behaviors and Issues 15

16 When WLANs are in outage mode, the last packet rate is not shown. [PR ] Description The output of the show session command shows <unknown> Mbps as the value for the parameter Last packet rate. This issue is observed only when the WLAs are in outage mode. Wireless networks does not identify devices when authenticating the devices by using DHCP authentication. [PR ] Description If you create device fingerprint rules to identify devices based on the MAC address and host name of the client devices and combine these rules by using the AND operation, the devices are not identified in the wireless networks. However, if you use only one of the rules, that is, combine the rules by using the OR operation, the devices are detected. The output of the show session network command shows incorrect client count. [PR ] Description If you change the VLAN pool selection method to load-balancing from client mac hash or the reverse, the client count changes. This change is not shown in the output of the show session network command. The output of the show vlan-pool command shows more number of clients than its configured capacity for some of the VLANs. [PR ] Description If you configure a certain number of clients for some of the VLANs and issue show vlan-pool, the number of clients is more than the configured value. Repetitive field and description table headers are is seen in the output of the show ap counter <ap num> wfq command. [PR ] Description The output of the show ap counter <ap num> wfq command output shows two field and descriptions table headers in between the output, which are not necessary. Reverse display of clients IP address in show sessions network command. [PR ] Description Reverse octets for the IP addresses are displayed in the output of the show session network. For example the client IP address is displayed as If an ACL is applied on a WLA, after connecting the clients, the ACL does not work for 15 through 20 or until the clients are disconnected and reconnected. [PR ] Description If you connect two wireless clients to an SSID, the clients gets connected. Even after configuring the ACL for the ICMP traffic, the ICMP traffic is still transits from one client to another. Incorrect filtering of MCS index occurs. [PR ] Description MCS index list present in the service profile and show ap counters are different. The output of the show ap counters (ap_num) qos command displays increments in the voice counters when no client is connected. [PR ] Description If you enable WLAs for both the radios and issue the show ap counter (ap_num) qos command, but do not connect any clients, the voice counter is incremented on the BestEffort counter. Workaround No known workaround 16 Known Behaviors and Issues Copyright 2015, Juniper Networks, Inc.

17 Issues Resolved in MSS (9.0MR8) Juniper WLCs do not send RADIUS server s interim-update date to the firewall filters until 3 minutes after the network comes up. [PR : This issue has been resolved.] RingMaster displays FakeBSSID alarms on all channels. [PR : This issue has been resolved.] There is incompatibility between Juniper WLAN devices and Ekahau WLC devices. [PR : This issue has been resolved.] SNMP traps are not generated for AutoTuneRadioPowerChange and AutoTuneRadioChannelChange traps. [PR : This issue has been resolved.] WLA322-WW Radio 2 (5 GHz) does not work after you upgrade the controllers from MSS to MSS [PR : This issue has been resolved.] Issues Resolved in MSS (9.0MR7) In a cluster comprising WLCs in a virtual machine networking configuration, there is loss of connectivity between the cluster members if a port on one of the cluster members is disabled. [PR : This issue has been resolved.] WLA532-US crashes intermittently with signal 6 (SIGABRT) error on a WLC2800 running MSS [PR : This issue has been resolved.] Netsys core files are generated on a WLC2800 running MSS [PR : This issue has been resolved.] Configuration core files crash when the command show_session_x_x is issued. [PR : This issue has been resolved.] When Backup system command is issued, MSS gives an error message Failed to create VIF TOC. [PR : This issue has been resolved.] Netsys core files are generated on a WLC2800 running MSS [PR : This issue has been resolved.] SmartPass is unable to disconnect sessions with 1-hour duration on MSS [PR : This issue has been resolved.] WLCs on WLA532 running MSS crash, displaying the error message Process 185 crashed - signal 6 (SIGABRT)! [PR : This issue has been resolved.] The system uptime value retrieved using the XML interface are negative values. [PR : This issue has been resolved.] After you upgrade WLA322-WW and WLA532-WW console to MSS version, the error message atheros_transmit_complete: Returning as TX Descriptor status is 15 is displayed. [PR : This issue has been resolved.] Issues Resolved in MSS (9.0MR6) After an upgrade to MSS version, new clients are unable to associate with the WLAs until the WLAs are rebooted. This issue does not occur with already existing clients. [PR : This issue has been resolved.] Some of the WLAs reboot and do not enter outage mode even though they are configured to enter outage mode. [PR : This issue has been resolved.] WLA 522 reboots because of a corrupted entry in the station database. [PR : This issue has been resolved.] WLC800R controllers running MSS version do not prioritize QoS traffic for voice over the video. [PR : This issue has been resolved.] WLAs crash when changes are made to the Radio Profile. [PR : This issue has been resolved.] Copyright 2015, Juniper Networks, Inc. Issues Resolved in MSS (9.0MR8) 17

18 WLC2800 crashes unexpectedly generating a core file. [PR : This issue has been resolved.] Clients are unable to switch from clear SSIDs to encrypted SSIDs even on entering the correct password. [PR : This issue has been resolved.] Clients are not redirected to the web-portal authentication page. [PR : This issue has been resolved.] A Radio profile name becomes case-sensitive only when you clear the service profile from the Radio profile. [PR : This issue has been resolved.] The homologation table for the WLA321-WW series WLAs does not show the values as per the new EU regulation for EU countries. [PR : This issue has been resolved.] Issues Resolved in MSS (9.0MR5) After upgrading to MSS version , the HTTPD process in the controller fails. [PR ] WLCs are vulnerable to the POODLE exploit (CVE ) for SSL version 1.0, 2.0, or 3.0. [PR ] Clients are unable to connect to WLA432 after upgrade to MSS version and The SSID also disappears periodically. The issue was observed when the beacons are not sent regularly. There is a delay in the beacon interval even though the beacon interval is not changed. Apart from this, the LED blinks amber and green continuously even though no clients are connected. [PR ] After upgrading to MSS version , WLA532 crashes, generating the message Process 185 crashed - signal 6 (SIGABRT)!. [PR ] Issues Resolved in MSS (9.0MR4) The number of L2 MAC, or forwarding database (FDB) entries on the WLC2800 exceed the maximum limit of 32,000 entries because of delayed aging of the L2 MAC table. [PR ] Non-bonded clients are unable to connect to the SSIDs with bonded authentication. [PR ] When you add new WLAs in a mobility domain, secondary seed becomes active even though the primary seed is active during mobility domain synchronization. Therefore, there are two active seed controllers in the network at the same time causing the WLAs to reboot. [PR ] The WLC sends a missing class-attribute to SBR, as a result authentication between account start packets and account stop packets does not occur and billing issues are observed. [PR ] Configuration changes in secondary seed are observed after it reboots. [PR ] Issues Resolved in MSS (9.0MR3) Unless WLAs receive timeout requests, they do not send out SIP packets; and only buffer these packets. As a result, SIP calls are not initiated. [PR ] The MX-800R controller restarts generating netsys core files. [PR ] WLAs that have the primary access manager connection to the primary seed reboot randomly after the scheduled restart of the primary seed. [PR ] WLAs that belong to a Radio profile in which the countermeasure feature is enabled, prevent the SSID from appearing as an available network for the client, even though the SSID belong to the same mobility domain. [PR ] After upgrading to MSS , the local switching WLAs do not broadcast multicast traffic. [PR ] The signal values are always incorrect when performing a packet capture with a snoop filter attached to any given WLA. [PR ] 18 Issues Resolved in MSS (9.0MR5) Copyright 2015, Juniper Networks, Inc.

19 After upgrading to MSS , the mesh WLAs do not reboot after a scheduled reboot. [PR ] WLAs rebooted because the mobility domain members gradually lost connectivity to each other. [PR ] In MSS , WLAs reboot because of a corrupted entry in the station database. [PR ] In MSS error message ERROR CLI_CONFIG_ERR: cli_get_aaa_avpair_list stat_get_aaa_avpair_list result=2018 ((null)) spams the trace logs. [PR ] In MSS , WLC880R crashes, creating a configuration core file. [PR ] The high CPU load in large wireless networks causes multiple WLAs to crash. [PR ] After an upgrade to MSS , multiple NETSYS crashes occur in WLCs in the secondary seed and also in one of the member WLCs. [PR ] WLAs reboot and WLCs generate netsys core file due to FDs exhaustion. [PR ] WLA322-WW crashes in MSS release [PR ] Mesh does not form for WLA532-US/WW Radio 1 and Radio 2. [PR ] Users are unable to disable Radio 1 of WLA322, because of which the WLA continues to be in Sentry mode forever. [PR ] WLCs do not establish a TCP connection to preferred network domain seed unless the existing TCP connection in the network domain seed that is in outage mode. [PR ] The command sh accounting statistics does not display logs in sequence as per the time stamp they are received. [PR ] Security ACLs can be mapped to user names as filter IDs. When certain security ACLs are removed, the mappings still exist referring to the non-existent ACLs. Because of this, the clients disconnect and do not connect back unless the security ACLs that are mapped to the user names as filter IDs are cleared. [PR ] When the auto-tune channel set and the channel sets supported by WLAs do not have a common channel, Radio 2 of WLAs do not turn up to operational state. [PR ] Spanning tree configurations are incorrectly applied to port groups. [PR ] Help description for ssid-name is missing in the CLI; it shows only the character string. [PR ] The AAA profile name supports special characters such as #,$,&,?,",\,',<, and >. [PR ] The number of characters supported for pre-shared key is not mentioned in the CLI help. [PR ] When the run auto-tune calculate-deploy command is executed, the auto-tune algorithm calculates the channel-set and writes it as an.xml file multiple times with the same time stamp. [PR ] A channel abort warning message is displayed when the channel auto-tuning accepts channels that are not part of channel settings. [PR ] The show session command output displays incorrect VLAN names. [PR ] The WLCs classify the neighboring WLAs as rogue WLAs even though they are part of the SSID list. [PR ] MX-800R controllers running MSS release reboot, creating a configuration core file. [PR ] During Web Authentication, if LDAP authentication fails, the LDAP server does not failover, because of which the authentication does not occur locally. [PR ] SNMP client data-rate is incorrectly polled for n band clients. [PR ] When the local authentication for a Web portal fails, it does not failover to other authentication methods. [PR ] The clients that are configured to connect in local-switching mode connect in overlay mode instead of local-switching mode. [PR ] Copyright 2015, Juniper Networks, Inc. Issues Resolved in MSS (9.0MR3) 19

20 The WLAs time out during auto-tune operation. The auto-rf process fails and starts again because of the interference from the neighboring WLAs. [PR ] Maximum power calculations output do not match the values mentioned in the product specification. [PR ] Maximum transmit power for WLA522E-WW does not match the values mentioned in the product specifications. [PR ] Unable to configure the antenna type in MSS 9.1 for WLA532-WW. [PR ] Between the Web portal timeout and the idle timeout period, clients that are connected to WLAs are disconnected and reconnected. [PR ] Clients with the wireless card Qualcomm Atheros with AR9285 disconnect from the wireless network when connected to WLA532-WW through vwlc. [PR ] Incorrect SNMP traps are sent by the controllers when a WLA moves from one controller to another, in a cluster. [PR ] On a WLC880R controller, after you upgrade to MSS , WLA532-US series WLAs connected to the controller crash. [PR ] The speed of the WLC880 fans is inconsistent and cannot be controlled. [PR ] All the WLAs with WLA532 series are crashing with the message "ERROR AP 8999 uucp: <67>Dec 13 20:27:15 syslog: Process 264 crashed - signal 11 (SIGSEGV). [PR ] Issues Resolved in MSS (9.0MR2) When an access point is booted over an HL link, the wireless client does not authenticate with a latency of 800 ms or more if WPA-PSK with TKIP is used for authentication. [PR ] If the maximum transmission unit (MTU) for a path is set to 896, the WLC does not update the status of a WLA322 access point from outage mode to active mode even after the access point has recovered from the outage. [PR ] The interworking-profile configuration of a service-profile cannot be changed. [PR ] If WLC-polling is enabled at a remote site, a WLA532-US access point that is in outage mode does not recover from the outage, but continues to serve clients while still in outage mode. [PR ] Issues Resolved Prior to MSS (9.0MR1) The access point managed global session ID changes when there is a failover of the access point. [PR ] WLC100 shows high load on CPU when device is idle. With MSS 9.0 running on WLC100, even when there is no load on the controller, the CPU usage displays high load. [PR ]. When Hot Spot 2.0 is enabled, RSN-IE and Dot1x should be enable on SP. [PR ] The access points on radio 2 are using channels that are not defined in the auto-tune channel list. [PR ] WLC2800 with MSS Version Several access points were lost during hitless upgrade. [PR ] A strange accounting packet is sent out from the controller during a VoIP call. [PR ] When a WLC rejoins a cluster a message SM-EVENT: APM reports WLA is down is logged by other controllers. [PR ] Some access points got rebooted and displayed an error message ERROR soc_mem_read: invalid index for memory SOURCE_TRUNK_MAP_TABLE on the controller. [PR ] Clients/access point output issue while using WebGUI on the secondary seed controller. [PR ] 20 Issues Resolved in MSS (9.0MR2) Copyright 2015, Juniper Networks, Inc.

21 After downgrade from MSS_9.0 to MSS_8.0 the access points that enter outage mode will not become operational until extended-timeout expires. [PR ] Several WLA532s crashing at customer environment. [PR ] Cluster interruptions followed by access point reboots. [PR ] Synchronization issues with cluster members. [PR ] SNMP agent and system log message displays the old system IP address when the system IP address is modified without rebooting the controller. [PR ] Remote WLA reboots when WLC recovers from reboot. [PR ] The error "atheros->key_cache.entry[indx].sta_desc_ctrl[q_type].queued_packet_count > 0" is still seen in MSS Version at customer environment. [PR ] Channel overlap occurs when auto-tune channel is enabled with 40 Mhz channel width. [PR ] Cluster failover issue. After the primary seed comes up from a failover and after the access point and client sessions move back to the primary seed, the client does not receive a ping reply from the gateway. [PR ] Members of the Cluster are dropping out and going into synchronization state. [PR ] Add Macau (MO) country code and update Hong Kong (HK) output power in the MSS Versions 8.0 and 9.0 Homologation Tables. [PR ] Spectralink 8440 phones slows down the ICMP performance and the voice quality reduces. [PR ] All access points rebooted at the same time during hitless upgrade. [PR ] Output from show mobility-domain stat command is inconsistent and also multiple WLCs reported with latency -1. [PR ] Cluster member not accepting new sessions and causes authorization failures. [PR ] After upgrade from MSS to MSS the WLC stopped responding through the uplink of SFP port 5/6. [PR ] The access points are not accepting new sessions and having excessive retransmits. [PR ] Client load-balancing and band-steering is causing incompatibility issues. [PR ] Controller issues after the upgrade to MSS Version (fp and netsys core issues). [PR ] The access point crashes when you issue RFlink test from web interface. [PR ] The access point crashes in a cluster with controller running MSS Version [PR ] High number of retransmits from Philips MX40 wireless monitors, when associated to a WLA532. [PR ] Controller issues after the upgrade to MSS Version (netsys cores). [PR ] Device fingerprint feature can be configured only on the primary seed and not on the secondary seed. [PR ] Remote access points rebooting after upgrade to MSS Version [PR ] The primary seed in the cluster has lost the configurations for over 1000 WLAs. [PR ] Clients not receiving the IP Address when connecting using WEP keys 2-4. [PR ] SNMP core file dropped on one of the cluster WLCs running MSS [PR ] Some WLAs show WLA reboots after WLCs sync back into cluster, Buffered Log (0): agent: WLA Reset: TAPA reboot by WLC. [PR ] NetSys core dump found in Secondary Seed [PR ] Cluster instability issue with WLC880R cluster. [PR ] Bandwidth limitation feature not working when applied to web-portal service-profiles. [PR ] Copyright 2015, Juniper Networks, Inc. Issues Resolved Prior to MSS (9.0MR1) 21