Release Notes for Mobility System Software Version 7.7.4

Copyright © 2013, Juniper Networks, Inc. 1

Release Notes for Mobility System Software Version 7.7.4.4

Juniper Networks recommends that you familiarize yourself with the Known Behaviors and Issues section in this document

before installing Mobility System Software (MSS) Version 7.7. For additional product information, refer to the following manual

in addition to these release notes:

Guides for MSS, RingMaster, and SmartPass Versions 7.7

Product Name Changes

Please note that the former Trapeze products now reflect the Juniper Networks product names. .

Feedback and Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

What’s New in MSS Version 7.7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

Version Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Upgrading to MSS Version 7.7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Installing Upgrade Activation Keys on an WLC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

System Parameter Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Known Behaviors and Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Issues Resolved Since 7.7.4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Issues Resolved Since MSS 7.7.3.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12




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.

Former Trapeze Name Current Juniper Product Name

MXR-2 WLC2

MX-8 WLC8

MX-200 WLC200

MX-800 WLC800R

MX-2800 WLC2800


2 Feedback and Support Copyright © 2013, Juniper Networks, Inc.

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 7.7

MSS Version 7.7 contains the following new features:

Support for the WLA321 and WLA322 — low cost solutions for wireless access points on your network.

VLAN Pooling - VLAN Pooling is a new feature that allows you to associate "equivalent" VLANs to a service which

then improves scalability and reduces broadcast domains across VLANs. Multiple VLANs can be grouped to form a

VLAN Pool and all VLANs in the VLAN Pool are available at any time in a location. VLAN assignment is performed

dynamically when a wireless client accesses the network and a VLAN is assigned to the wireless client.

WAN Outage Enhancements including WIDS Logging — When the WAN link between the main site and a remote

site goes down, communication between the WLC and the WLA is interrupted. The WLC and the WLA determine that

the other is unreachable over the network.

When this outage occurs, the WLA now accepts new client requests in the remote branch and now supports some of

the functionality previously supported on the controller. Clients can also roam between WLAs at the remote site.

With this feature, the following functionality is supported:

− WLAs are assigned a site name to designate the grouping at the remote site.

− Backup SSIDs can be defined and sent automatically to the radio profiles on the WLA.

− All WLAs at the remote site are configured with a common VLAN profile.

− WLAs can be assigned a different country code from the WLC country code.

− Local switching is automatically enabled when an outage occurs on the network. This allows direct packet

forwarding to local VLANs.

The following is a list of features not supported on WLAs configured in WAN Outage mode:

− WLAs do not provide DHCP services.

− WEP is not supported.

− CAC is not supported and CAC validity and enforcement are not applied.

− More than 100 WLAs are not supported.

− Over 25 clients on a backup SSID is not supported.

− Mesh and Auto AP features are not supported.

Support for High Latency Networks — When discussing network speed, bandwidth and latency are two elements

that affect network speed. Latency refers to delays typically encountered when process network data. A low latency

network connection is one that has small delay times, while a high latency network typically encounters long delays.

− When a wireless client attempts to connect and maintain a connection to a WLA with a WLC located in a high

latency network, the client association fails on the network. This may happen for two reasons:

− a)The wireless client waits for a response from the WLA. Because the WLA forwards the requests to the WLC,

the client may time out due to the large round trip delay between the WLA and WLC.

MP-522 WLA522

MP-632 WLA632

Former Trapeze Name Current Juniper Product Name


3 Version Compatibility Copyright © 2013, Juniper Networks, Inc.

− b)The WLC waits for a response from the client. Because the roundtrip delay is large, the WLC may time out

before the response is returned to the client.

− To resolve this issue, a new feature, high latency mode, allows you to configure attributes that can mitigate the

association problems on a high latency network.

Enhanced Statistics and Counters for Mobility Domains — Mobility Domain configurations depend on sending

fast keepalive messages between the cluster seed and secondary seed as well as the seed and each of the MoDo

members. Fast keepalives are UDP packets with source and destination ports of 8821 which is the same port as the

TCP port number for the mobility domain TCP connections.

WLA Network Resiliency Roaming History Enhancements — When the network is configured for the network

resiliency feature, WLAs boot up on the network and then send the WLC request that is sent to the seed. The seed

selects a Primary Access Manager (PAM) and a Secondary Access Manager (SAM) for a booting WLA. Over a period

of time, the WLA can move to different WLCs on the network for various reasons, including the following:

− Connectivity - losing contact with the PAM or SAM, and if the WLA loses both, the WLA reboots.

− Configuration - changing the Mobility Domain affinity attribute can trigger the WLA to move to a preferred

controller. Changing the data path encryption (DPE) attribute can also trigger the WLA to move to another

controller.

− Load balancing - when member WLCs are removed or added to the network, the seed may move WLAs to other

active member WLCs.

− The seed keeps track of all WLAs active on the MoDo. The data includes the PAM, SAM, WLA IP address, and

other information that is shared with the secondary seed.

Multicast to Unicast Traffic Conversion - Media applications require reliable support for media transmissions on the

wireless network. Applications and products such as security and surveillance use "TV-like" video distribution on the

wireless network and require reliable support for quality content delivery.

Multicast transmission is unreliable due to the absence of feedback mechanism in the IEEE 8002.11 MAC protocol.

Broadcast can be undesirable in some situations such as wireless phones in sleep mode may wake up when a

broadcast packet is received.

This feature uses the multicast to unicast conversion of video content and performs additional optimizations such as

prioritization of video traffic, bandwidth reservation, and load optimization on the WLA to ensure reliable delivery of

video content.

Configurable IP Address for Sending SNMP Traps — Currently, the SNMP configuration on a network uses the

WLC IP address to send SNMP traps. In some implementations, it may be desirable to send SNMP traps from a

different IPv4 address.

Version Compatibility

RingMaster

This version of Mobility System Software (MSS) is intended for use with RingMaster Version 7.7 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 7.7. If your WLC is

running an older MSS version, you can use the upgrade path to upgrade the WLC to 7.7.

Table 1: Software Requirements for Upgrade to MSS Version 7.7

Product Minimum MSS Version Required Upgrade Path

WLC200 5.x 5.0.15.2 -> 6.0.7.2 ->7.0.x.x->7.1.x.x -> 7.3.x.x > 7.5.x.x > 7.6.x.x

WLC2 5.x 5.0.15.2 -> 6.0.7.2 ->7.0.x.x->7.1.x.x -> 7.3.x.x > 7.5.x.x > 7.6.x.x



Upgrading to MSS Version 7.7

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 7.7, return to this section.

Preparing the MX for the Upgrade

WLC8 5.x 5.0.15.2> 6.0.7.2 ->7.0.x.x->7.1.x.x -> 7.3.x.x > 7.5.x.x > 7.6.x.x

WLC800R 7.3.x 7.3.xx> 7.5.xx>7.6.xx

WLC880R 7.5.xx 7.5.xx>7.6.xx

WLC2800R 7.0.3.6 7.0.x.x->7.1.x.x -> 7.3.x.x > 7.5.x.x > 7.6.x.x

Software versions on the Juniper Support Site

When you go to the Software downloads page at http://www.juniper.net/support/products/mss/#sw 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.

Warning: This release of MSS 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 7.7 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 7.7.

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 7.7. Failure to do so

may result in lost configuration data.

Informational Note: MSS 7.7 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.

Table 1: Software Requirements for Upgrade to MSS Version 7.7 (continued)

Product Minimum MSS Version Required Upgrade Path



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 6 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

1. Back up the WLC, using the backup system command.

2. Copy the new system image onto a TFTP server.

For example, log into http://www.juniper.net/support/downloads/ 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://10.1.1.107/MX077021.800 boot1:MX077021.800

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 1.

4. Set the boot partition to the one with the upgrade image for the next restart.

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

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 7.7 are not supported.

Caution: Create a backup of your WLC files before you upgrade the WLC.

Juniper Networks recommends that you make a backup 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.

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.


6 Installing Upgrade Activation Keys on an WLC Copyright © 2013, Juniper Networks, Inc.

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.

WLC800# save configsuccess: configuration saved.WLC800# backup system tftp:/10.1.1.107/sysa_baksuccess: sent 28263 bytes in 0.324 seconds [ 87231 bytes/sec]WLC800# copy tftp://10.1.1.107/MX077021.800 boot1:MX077021.800........................................................................................................................................................................................................success: received 10266629 bytes in 92.427seconds [ 111078 bytes/sec]WLC800# set boot partition boot1success: Boot partition set to boot1:MX077021.800 (7.7.0.2).WLC800# show bootConfigured boot version: 7.7.0.2Configured boot image: boot1:MX075421.800Configured boot configuration: file:configurationBackup boot configuration: file:backup.cfgBooted version: 7.7.0.2Booted image: boot1:MX077021.800Booted configuration: file:configurationProduct model: WLCWLC800# 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:

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.

Table 2: Licensing and Upgrade Increments for the WLC Models

WLC Model Base WLA Support Maximum WLA Support Upgrade Increment

WLC800R/880R 16 128/256 16 or 32

WLC200 32 192 32

WLC2800 64 512 64


7 Installing Upgrade Activation Keys on an WLC Copyright © 2013, Juniper Networks, Inc.

Feature licensing is supported on WLC platforms as show in Table 3.

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.

Table 3: WLC Feature Licensing Matrix

WLC Model Advance Voice Module

High Availability

Module Mesh/Bridging Module

Spectrum Analysis

(WLA522, WLA532, and

WLA321)

WLC2 Supported Supported Up to 4 WLAs

(16 WLAs in Cluster mode)

Supported


(48 in Cluster mode)

Supported

WLC200 Supported Supported Up to 192WLAs


Supported

WLC800R Supported Supported Up to 128 WLAs

(512 WLAs in Cluster mode)

Supported

WLC880R Supported Supported Up to 256 WLAs

(2048 in Cluster Mode)

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.

WLC200 - supports four radios on simultaneous WLAs in spectral graphing mode.

WLC800R, WLC880R, and WLC2800 - 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 any WLC with a WLA capable of running Spectrum Analysis.


8 System Parameter Support Copyright © 2013, Juniper Networks, Inc.

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 versionIn the following example, the WLC serial number is 1234567890:

WLC800> show version

Mobility System Software, Version: 7.7.0.2 REL Copyright (c) 2002 - 2012 Juniper Networks, Inc. All rights reserved.

Build Information: (build#0) REL_7_7_0_branch 2012-03-02 14:21:00Model: WLC800RHardware Mainboard: version 24 ; revision 3 ; FPGA version 24 PoE board: version 1 ; FPGA version 6Serial number 1234567890Flash: 7.3.0.2.0.0.49 - md0aKernel: 3.0.0#112: Wed Aug 2 10:26:32 PDT 2009BootLoader: 7.7 / 7.6.1

3. Use a Web browser to access the Juniper Networks license server at the following URL:

https://www.juniper.net/lcrs/license.do

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-F20Esuccess: license accepted

5. Verify installation of the new license by typing the following command:

WLC800# show licenses

Feature : 96 additional MPsSupport for the additional WLAs begins immediately. You do not need to restart the WLC to place the upgrade into effect.

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)



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



Includes directly attached WLAs and Distributed WLAs. Inactive

configurations are backups.

Minimum link speed between WLCs in a Mobility

Domain

128 Kbps

Minimum link speed between an WLC and WLA in

a Mobility Domain

128 Kbps and 95ms round trip latency - this value is different if the

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: 512

Table 5: Network Parameters


Forwarding database entries WLC2800: 32768

WLC800R/WLC880R: 32768

WLC200: 8192

WLC8: 8192

WLC2: 8192

Statically configured VLANs WLC2800: 512 configured

WLC800R/WLC880R: 256 configured

WLC200: 128 configured



Spanning trees (STP/PVST+ instances) 64

Table 4: Mobility System Parameters (continued)




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

Table 6: Management Parameters


Maximum instances of RingMaster simultaneously

managing a network

32

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

Table 5: Network Parameters (continued)


Copyright © 2013, Juniper Networks, Inc. Known Behaviors and Issues 11


Known Behaviors and Issues

No known issues in this version of Mobility System Software.

Issues Resolved Since 7.7.4

Traffic becomes unstable after enabling per user bandwidth limit in the QoS profile on the wireless LAN controllers.

[PR852638]

After upgrade and a configuration core was generated, at times the clients cannot connect to any of the SSIDs.

[PR861550]

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


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.

Active AAA sessions (or clients trying to establish

active connections) per WLC

WLC2800: 12800

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

Table 6: Management Parameters (continued)



12 Issues Resolved Since MSS 7.7.3.2 Copyright © 2013, Juniper Networks, Inc.

WLC crashes with a Netsys core file upon receipt of a corrupted or malformed WLA management frame. [PR876488]

The cluster on the primary seed crashed when the xml test command <GET><DAP-TABLE/></GET> was issued.

[PR877704]

Issues Resolved Since MSS 7.7.3.2

Some WLAs rebooted on the network and displayed error messages in the system log file. [PR884299]

A portal ACL mapped to a WLA performing local switching did not work correctly if more than 32 ACEs were

configured. [PR877168]

The location policy VLAN did not override the service profile VLAN on the Web portal. [PR875916]

A WLC2800 with MSS 7.7.3.3 became unresponsive on the network. [PR875348, 876488]

Web-portal sessions would not display the initial login page to clients. [PR873790]

A cluster configuration displayed error messages that were incorrect about the status of the configuration.

[PR870475]

When performing cluster synchronization, the cluster members remained in “sync” status and were unaccessible.

[PR868222]

Clients could not connect to any SSID until the WLC was rebooted. [PR861550]

When blacklist configuration changes were made, the primary seed in a cluster was unreachable for a period of time.

[PR854887]

A specific build of MSS caused WLAs to stop responding on the wireless network. [PR857801]

HTTPS caused error messages in the system log file. [PR849588]

A WLC880R with MSS 7.7.2.3 became unresponsive on the network. [PR847973]

High traffic load on the MP-82 caused the MP to stop sending network traffic. [PR834832]

Excessive retransmits were causing the four-way handshake authentication to fail on the wireless network.

[PR824160]

iPads were unable to connect to a specific SSID. [PR816489]


The show rfdetect data output did not display any information. [PR845430]

MSS erroneously reported a RADIUS server status as down when it was active on the network. [PR840184]

An SSID was incorrectly identified as “suspect” instead of “rogue”. [PR839329]

Wired authentication stopped working on a WLC. [PR839020]

Some Intel clients experienced packet loss when connected to 802.11n. [PR838592]

The Web Portal login page did not display after 1000 active sessions on the WLC. [PR836631]

A WLA rebooted after 4 hours when WAN outage was configured for 6 hours. [PR836505]

MSS detected radar signals on a Mesh AP when there were none. [PR829528]

The EAP process failed on a WLC880. [PR829526]

Traffic was not forwarded on a WLC to WLC tunnel in a Mobility Domain. [PR819819]

WLAs were incorrectly identified as Rogue APs on the network. [PR814321]

When a cluster configuration was synchronizing members, some members had to reboot before joining. [PR813478]

Copyright © 2013, Juniper Networks, Inc. Issues Resolved Since MSS 7.7.1.6 13



External Web portal redirect failed and the WLC was unresponsive.[PR810429]

A high number of failures were reported for HTTP sessions during rate testing. [PR808480]

Intra-session roaming did not work on a WLC. [PR808475]

WLA322 did not detect FCC Type 1 radar when configured for CAC. [PR787171]

There was high CPU utilization for the http process after upgrading to MSS Version 7.7.1.6. [PR785391]

Unicast traffic was stuck in the unicast station queue. [781461]

A WLC was falsely reporting spoofed BSSIDs. [750926]

Clients did not roam correctly in a mesh WLA to mesh WLA configuration. [PR750687]

A RADIUS server was incorrectly reported as down by the WLC. [PR724279]

When connected to the WLA532, the Intel 5100 Client appeared to send traffic over the network, but no data was

actually sent. [PR702722]


RADIUS and LDAP VSAs changed on WLCs due to rebranding from Trapeze Networks to Juniper Networks.

(PR698842)

SNMP queries on 'trpzApStatApStatusApState' or 'trpzApStatApStatusMacApState' on an WLC acting as a Secondary

Access Manager (SAM) for a WLA in a cluster configuration returned the value '0' for that WLA. [PR673913]

Some 802.11n clients experienced delays or dropped high priority traffic if frame aggregation was enabled.

[PR687433]

If you changed the number of an WLA configured for local switching, the WLA was removed from the configuration.

[PR656505]

Documentation Errata

In the section "Support for Extended Certificate Chains" in the MSS Config Guide it says "MSS now supports

Certificate Chains with up to 6 intermediate Certificate Authorities (CAs)". This is incorrect. MSS supports 9

intermediate certificates. [PR837503]

Documents

Release Notes for Mobility System Software Version 7.7.4