Cisco Cisco 2106 Wireless LAN Controller Release Notes
![Cisco](https://files.manualsbrain.com/attachments/7380d0050044647c30f5c24bbbf5d0c0b6d9bb84/common/fit/150/50/faa183d287233c52228cfea3dbc2a127fe780f60564fcb0955d9c3d1cd23/brand_logo.png)
14
Release Notes for Cisco Wireless LAN Controllers and Lightweight Access Points for Release 4.2.61.0
OL-31336-01
New Features
•
Client reporting—This protocol is used by CCXv5 clients and the access point to exchange client
information. Client reports are collected automatically when the client associates. There are four
types of client reports:
information. Client reports are collected automatically when the client associates. There are four
types of client reports:
–
Client profile—Provides information about the configuration of the client.
–
Operating parameters—Provides the details of the client’s current operational modes.
–
Manufacturers’ information—Provides data about the wireless LAN client adapter in use.
–
Client capabilities—Provides information about the client’s capabilities.
•
Roaming and real-time diagnostics—You can use roaming and real-time logs and statistics to
solve system problems. The event log enables you to identify and track the behavior of a client
device. It provides a log of events and reports them to the access point. There are three categories
of event logs:
solve system problems. The event log enables you to identify and track the behavior of a client
device. It provides a log of events and reports them to the access point. There are three categories
of event logs:
–
Roaming log—Provides a historical view of the roaming events for a given client.
–
Robust Security Network Association (RSNA) log—Provides a historical view of the
authentication events for a given client.
authentication events for a given client.
–
Syslog—Provides internal system information from the client. For example, it may indicate
problems with 802.11 operation, system operation, and so on.
problems with 802.11 operation, system operation, and so on.
GUI Enhancements
•
Monitor and Controller Menus—The options on these menus have been rearranged.
•
All APs page— This page now shows the access point mode, and the layout has been changed to a
tabbed format.
tabbed format.
•
AP Policies page—You can now search for an access point in the authorization list by MAC address.
•
Clients page—You can filter clients so that only clients that meet certain criteria (such as MAC
address, access point name, WLAN profile, status, radio type, and/or WGB status) are displayed on
the Clients page.
address, access point name, WLAN profile, status, radio type, and/or WGB status) are displayed on
the Clients page.
•
Summary page—You can view the default mobility group under Controller Summary.
Access Point Additions and Changes
•
Cisco Aironet 1250 Series Access Point—All controllers now support the Cisco Aironet 1250
Series Access Point. This access point supports two (draft IEEE 802.11n version 2.0) radio modules:
a 2.4-GHz radio and a 5-GHz radio. You can configure the radios separately, using different settings
on each. For more information, refer to the Cisco Aironet 1250 Series Access Point Q&A at this
URL:
Series Access Point. This access point supports two (draft IEEE 802.11n version 2.0) radio modules:
a 2.4-GHz radio and a 5-GHz radio. You can configure the radios separately, using different settings
on each. For more information, refer to the Cisco Aironet 1250 Series Access Point Q&A at this
URL:
•
Support for 16 BSSIDs—All Cisco lightweight access points support 16 BSSIDs per radio and a
total of 16 wireless LANs per access point. In previous releases, they supported only 8 BSSIDs per
radio and a total of 8 wireless LANs per access point.
total of 16 wireless LANs per access point. In previous releases, they supported only 8 BSSIDs per
radio and a total of 8 wireless LANs per access point.
Other Changes
These additional changes are applicable to controller software release 4.2.61.0:
•
The PMK cache lifetime timer, which is used to trigger reauthentication with the client when
necessary, has been changed. It is now based on the timeout value received from the AAA server or
the WLAN session timeout setting rather than on the default PMK cache lifetime default value of
12 hours.
necessary, has been changed. It is now based on the timeout value received from the AAA server or
the WLAN session timeout setting rather than on the default PMK cache lifetime default value of
12 hours.