Release Notes for Cisco Wireless Controllers and Lightweight Access Points for Cisco Wireless Release 8.2.100.0

---

Table 1 Revision History

Modification Date	Modification Details
January 29, 2018	Features Not Supported on Cisco Virtual WLCs – Modified information about FlexConnect central switching.
October 16, 2017	Features Not Supported on Cisco Aironet 1830 and 1850 APs – Added SIP snooping with FlexConnect in local switching mode
October 10, 2017	Features Not Supported on Cisco Virtual WLCs – Added Wired Guest and FlexConnect central switching.
November 22, 2016	Features Not Supported on Cisco 2504 WLC – Added: EoGRE Features Not Supported on Cisco Virtual WLCs – Added: EoGRE (Supported in only local switching mode)
September 27, 2016	What’s new in this Release – Added: Removal of Support for Rx SOP from Mesh Backhaul
May 17, 2016	L3 Interfaces for Tunneling Protocols – Added note on feature tunnel support. Upgrading to Cisco WLC Software Release 8.2.100.0 – Added this statement: “If you upgrade from Release 8.0.110.0 to a later release, the config redundancy mobilitymac mac-addr command's setting is removed. You must manually reconfigure the mobility MAC address after the upgrade.”
April 22, 2016	Features Not Supported on Cisco Virtual WLCs – Added Lync SDN.
March 21, 2016	Features Not Supported on Cisco 2504 WLC – Added Application Visibility and Control (AVC) for FlexConnect centrally switched access points to the list of not supported features.
March 16, 2016	What’s New in this Release – Added a Note on Release 8.2 related interface restrictions
March 8, 2016	Resolved Caveats – Added CSCuw03323 to the Resolved Caveats list.
March 4, 2016	Upgrading to Cisco WLC Software Release 8.2.100.0 – Documented CSCux75436 kernel route issue.
March 3, 2016	Mobility Express Features – Added information about Cisco CMX support.
March 2, 2016	Upgrading to Cisco WLC Software Release 8.2.100.0 – Added a statement that Cisco Aironet 3600 Series APs cannot recognize the reload command.
February 21, 2016	2.4-GHz Mesh – Rephrased the statements made in this section.
February 18, 2016	Features Not Supported on Cisco Aironet 1830 and 1850 APs – Added Telnet to the list of unsupported features

Supported Cisco Wireless Controller Platforms

The following Cisco WLC platforms are supported in this release:

• Cisco 2500 Series Wireless Controllers (Cisco 2504 Wireless Controller)
• Cisco 5500 Series Wireless Controllers (5508 and 5520 Wireless Controllers)
• Cisco Flex 7500 Series Wireless Controllers (Cisco Flex 7510 Wireless Controller)
• Cisco 8500 Series Wireless Controllers (8510 and 8540 Wireless Controllers)
• Cisco Virtual Wireless Controllers on the Cisco Services-Ready Engine (Cisco SRE) or the Cisco Wireless LAN Controller Module for Cisco Integrated Services Routers G2 (UCS-E)

---

Note Kernel-based virtual machine (KVM) is supported in Cisco Wireless Release 8.1 and later releases.

After KVM is deployed, we recommend that you do not downgrade to a Cisco Wireless release that is earlier than Release 8.1.

• Cisco Wireless Controllers for High Availability for Cisco 2504 WLC, Cisco 5508 WLC, Cisco 5520 WLC, Cisco Wireless Services Module 2 (Cisco WiSM2), Cisco Flex 7510 WLC, Cisco 8510 WLC, and Cisco 8540 WLC.

---

Note AP Stateful switchover (SSO) is not supported on Cisco 2504 WLCs.

• Cisco WiSM2 for Catalyst 6500 Series Switches
• Cisco Mobility Express Solution

For information about features that are not supported on the Cisco WLC platforms, see “Features Not Supported on Cisco WLC Platforms” section.

Supported Access Point Platforms

The following access point platforms are supported in this release:

• Cisco Aironet 1040 Series Access Points
• Cisco Aironet 1140 Series Access Points
• Cisco Aironet 1260 Series Access Points
• Cisco Aironet 1600 Series Access Points
• Cisco Aironet 1700 Series Access Points
• Cisco Aironet 1830 Series Access Points
• Cisco Aironet 1850 Series Access Points
• Cisco Aironet 2600 Series Access Points
• Cisco Aironet 2700 Series Access Points
• Cisco Aironet 3500 Series Access Points
• Cisco Aironet 3600 Series Access Points
• Cisco Aironet 3700 Series Access Points
• Cisco Aironet 600 Series OfficeExtend Access Points
• Cisco Aironet 700 Series Access Points
• Cisco Aironet 700W Series Access Points
• Cisco AP802 Integrated Access Point
• Cisco AP803 Integrated Access Point
• Cisco ASA 5506W-AP702
• Cisco Aironet 1530 Series Access Points
• Cisco Aironet 1550 Series Access Points
• Cisco Aironet 1570 Series Access Points
• Cisco Industrial Wireless 3700 Series Access Points

---

Note The Cisco 1040 Series, 1140 Series, and 1260 Series access points have feature parity with Cisco Wireless Release 8.0. Features introduced in Cisco Wireless Release 8.1 and later are not supported on these access points.

For information about features that are not supported on some access point platforms, see Features Not Supported on Access Point Platforms.

---

Note Cisco AP802 is an integrated access point on the Cisco 800 Series Integrated Services Routers (ISRs). For more information about the stock-keeping units (SKUs) for the AP802s and the Cisco ISRs, see the following data sheets:

• AP860:

http://www.cisco.com/c/en/us/products/collateral/routers/800-series-routers/data_sheet_c78_461543.html

• AP880:

http://www.cisco.com/c/en/us/products/collateral/routers/887-integrated-services-router-isr/data_sheet_c78_459542.html

http://www.cisco.com/c/en/us/products/collateral/routers/800-series-routers/data_sheet_c78-613481.html

http://www.cisco.com/c/en/us/products/collateral/routers/880-3g-integrated-services-router-isr/data_sheet_c78_498096.html

http://www.cisco.com/c/en/us/products/collateral/routers/880g-integrated-services-router-isr/data_sheet_c78-682548.html

• AP890:

http://www.cisco.com/c/en/us/products/collateral/routers/800-series-routers/data_sheet_c78-519930.html

Before you use a Cisco AP802 series lightweight access point with Cisco Wireless Release 8.2.100.0, you must upgrade the software in the Cisco 880 Series ISRs to Cisco IOS 15.1(4)M or later releases.

Unsupported Cisco Wireless Controller Platforms

The following Cisco Wireless Controller platforms are not supported:

• Cisco 4400 Series Wireless LAN Controller
• Cisco 2100 Series Wireless LAN Controller
• Cisco Catalyst 3750G Integrated Wireless LAN Controller
• Cisco Wireless Controller software for Cisco SRE Internal Services Module (ISM) 300, Cisco SRE Service Module (SM) 700, Cisco SRE Service Module (SM) 710, Cisco SRE Service Module (SM) 900, and Cisco SRE Service Module (SM) 910.
• Cisco Catalyst 6500 Series and 7600 Series WiSM
• Cisco Wireless LAN Controller Module (NM/NME)

---

---

Cisco Smart Software Licensing

Cisco started the initiative of simplifying customer license management by building a Cisco Smart Software Manager portal. It helps the customers understand what licenses they have purchased and what licenses they are using. Various other Cisco products are already Smart Enabled and with the introduction of this release Cisco Smart Software Licensing will now be available on the following platforms:

• Cisco 5520 WLC (AIR-CT5520-K9)
• Cisco 8540 WLC (AIR-CT8540-K9)
• Cisco vWLC (L-AIR-CTVM-5-K9)

For more information, see the following:

• Cisco Smart Software Licensing Overview
• Cisco Smart Software Licensing section in the Cisco Wireless Controller Configuration Guide.

Increased AP and Client Scale for Cisco Virtual Wireless Controller

The capacity of Cisco Virtual Wireless Controllers (vWLCs) is increased with the introduction of a Large Scale vWLC.

Two new SKUs with two types of scaling configurations are available. During installation or upgrade, you can choose between Small Scale vWLC and Large Scale vWLC.

This table lists the two types of Cisco vWLCs, their requirements and capacity:

Access Point Provisioning using Plug-n-Play (PnP)

The Access Point Provisioning using Plug-n-Play (AP PnP) solution provides staging parameters to an AP before it is associated with a Cisco WLC. Using this staging configuration, the AP gets the run-time configuration when it associates with a Cisco WLC. PnP is supported only on AP recovery images and is activated only for the zero-day deployment. PnP can no longer be initiated after the AP associates with a Cisco WLC for the first time.

The following AP scenario is supported:

• On-premise redirection—Customers hosting the PnP server in their network

The AP PnP solution is supported on the following APs:

• Cisco 702i AP
• Cisco 702W Series APs
• Cisco Aironet 1600 Series APs
• Cisco Aironet 1700 Series APs
• Cisco Aironet 2600 Series APs
• Cisco Aironet 2700 Series APs
• Cisco Aironet 3600 Series APs
• Cisco Aironet 3700 Series APs

NetFlow Export 2.0

The following are the template enhancements in NetFlow Version 9:

• New features can be added to NetFlow quickly, without breaking existing implementations.
• NetFlow is future-proofed against new or developing protocols, because NetFlow Version 9 can be adapted to provide support for those protocols.
• NetFlow Version 9 is the IETF standard mechanism for information export.
• Third-party business partners who produce applications that provide collector or display services for NetFlow are not required to recompile their applications each time a new NetFlow feature is added.

For more information, see the Configuring NetFlow section in the Cisco Wireless Controller Configuration Guide.

AVC Enhancements

In Release 8.2, the following features are available on Cisco WLCs:

• Protocol Pack 14.0
• NBAR Engine Release 3.16(23)

Features

• NBAR2 Engine Version 23 is tightly coupled with Cisco Wireless Release 8.2 and aligns with Protocol Pack 14.0.
• Faster upgrade and downgrade process—Downgrading from Release 8.2 to Release 8.1 changes the protocol pack to the previously installed protocol pack version, which is Protocol Pack 11.0.
• Traffic is classified instantly upon Cisco WLC bootup.
• Support for 1536 applications.

---

Note Newer protocol packs are tied with Network-Based Application Recognition (NBAR) Engine Version 14 and later. Protocol packs that are earlier than Version 14 do not work with the new engine.

For more information, see the Release Notes for NBAR2 Protocol Pack 14.0.0 for Cisco Wireless Controllers.

Bonjour Gateway with Googlecast Support

Googlecast Service that uses the service key, _googlecast._tcp.local, is supported on the existing implementation of Bonjour gateway on Cisco WLC.

Enhanced wIPS Support for Hyperlocation Module with Advanced Security

wIPS support for the 40 MHz to 80 MHz range using Hyperlocation module is introduced. This feature detects alarms in the 40 MHz to 80 MHz range (if RRM channel scanning is selected) and provides information to Cisco Prime Infrastructure (PI). Channel width information is derived from the packet data rate and sent to the wIPS module, which stores channel width per alarm. Using the show capwap am alarm alarm-id command, you can view the channel width in which the attack has occurred.

The wIPS alarm report contains the channel width of the attack and device capability (802.11a/b/g/n/ac). No wIPS-specific configuration is required to enable this feature. The only prerequisite is that RRM scanning must be enabled for this feature to work as expected.

Cisco Air Time Fairness: Client Fair Sharing

In Release 8.2, Cisco Air Time Fairness can be enforced on clients that are associated with an SSID/WLAN. This ensures that all clients within an SSID/WLAN are treated equally based on their utilization of the radio air time. This feature is useful in scenarios where one or a few clients could use the total air time available for an SSID/WLAN, thereby depriving Wi-Fi experience for other clients associated with the same SSID/WLAN.

For more information, see the Cisco Air Time Fairness section in the Cisco Wireless Controller Configuration Guide.

Cisco WLAN Express Enhancements

• New best practices added in Release 8.2. For details, see the “Complete List of Best Practices in Release 8.2” section.
• You have the option to ignore a recommended best practice by clicking the Ignore button. The Ignore button is visible (only for some best practices) when you click the + icon to select a recommended best practice. These best practices are added to the ignored list.
• The best practices information displayed when you click the Learn More button is integrated with the Cisco WLC software. The Learn More button is visible (only for some best practices) when you click the + icon to select a recommended best practice. Previously, this document was accessible on Cisco.com.
• Updates have been made to the Main Dashboard with the addition of new dashlets. For more information, see the Cisco Wireless Controller Online Help.

Complete List of Best Practices in Release 8.2

---

Note The best practices introduced in Release 8.2 are listed below in bold.

• Infrastructure

– AVC Visibility

– Band Select

– Controller High Availability

– Disable Aironet IE

– Disable Internal DHCP

– Disable Management over Wireless

– Fast SSID

– HTTPS for Management

– Load Balancing

– Load Balancing Window

– Local Profiling

– mDNS Gateway

– Multicast Forwarding

– Multicast Mobility

– Multicast VLAN

– NTP

– Tagged Management VLAN

– Virtual Gateway IP

– WLAN not on Management VLAN

• Security

– 802.1X on AP

– CPU ACLs

– Client Exclusion

– Legacy IDS

– Local Management Password Policies

– Min Rogue RSSI Threshold

– Peer to Peer

– Rogue Policies

– SSH/Telnet Access

– User Login Policies

– WLAN with 802.1X

– WLAN with WPA2 and AES Policy

• RF Management

– Auto Coverage Hole Detection

– Auto Dynamic Channel Assignment

– Auto Transmit Power Control

– Best Channel Width

– CleanAir Detection

– Client Band Select

– DCA Cisco AP Load

– Event Driven RRM

– High SSID Counts

– Wi-Fi Interference

---

Note The 40-MHz Channel Width best practice is not available in Release 8.2.

2.4-GHz Mesh

Mesh functionality in 2.4 GHz is supported on all APs that support Mesh.

In addition, while both 2.4 GHz and 5 GHz can be used outdoor across the globe, in Israel, only 2.4 GHz can be used outdoor. Therefore, a new regulatory domain, –I, and country code, IO, is introduced to support the use of 2.4 GHz as outdoor mesh backhaul on Cisco Aironet 1530 and 1570 APs.

Removal of Support for Rx SOP from Mesh Backhaul

From Cisco Wireless Release 8.2, the Rx SOP feature in bridge mode is not supported in the mesh backhaul 5-GHz interface to improve backhaul stability.

Pre-Shared Key Provisioning Support for Mesh Networks

Support is added for the pre-shared key (PSK) functionality that can be provisioned from Cisco WLC and can help make a controlled mesh deployment and enhance mesh access point (MAP) security beyond the currently used default cisco PSK.

With this new feature, MAPs, which are not preset yet with a valid PSK can connect to Cisco WLC using the default cisco PSK, during the provisioning window controlled by the Administrator. However, it will then receive a new PSK from the Cisco WLC, and from that point on, will only be able to connect with that PSK, and no longer with the default passphrase cisco.

---

Dynamic Management User Login via AAA Server

Management users who are logged in when external servers are not available must reauthenticate when the external RADIUS servers are available. Failing to do so will lead to termination of the user session to prevent potential operational and security risks. When RADIUS servers are not available, management users are authenticated locally. After the RADIUS servers are back online, management users are prompted to log in again within a specific timeframe.

For more information, see the Setting up TACACS+ section in the Cisco Wireless Controller Configuration Guide.

Test AAA Command for RADIUS

To troubleshoot AAA RADIUS interactions for WLAN authentication, test aaa commands are introduced:

• Test AAA RADIUS interactions for WLAN authentication by entering this command:

test aaa radius username username password password wlan-id wlan-id [ apgroup apgroupname server-index server-index ]

The test command sends an access request the RADIUS server for client authentication. Access request exchange takes place between Cisco WLC and the AAA server, and the registered RADIUS callback handles the response.

The response includes authentication status, number of retries, and RADIUS attributes.

• View the RADIUS response to test the RADIUS request by entering this command:

test aaa show radius

For more information, see the Troubleshooting AAA RADIUS Interactions for WLAN Authentication section in the Cisco Wireless Controller Configuration Guide.

Custom HTTP Port for Profiling

WLC can now send HTTP user agent information to ISE for devices that use custom port (not only port 80).

L3 Interfaces for Tunneling Protocols

Prior to Release 8.2, the management IP address was used as the tunnel endpoint. Release 8.2 has allowed the specification of any L3 dynamic interface as a tunnel endpoint, other than the management interface, if need be.

---

Note This feature currently supports EoGRE and PMIPv6 types of tunnels for mobility tunnel termination.

Cisco 5520, 8510, and 8540 WLC Updates

• Out-of-Band Management Support—Prior to Cisco Wireless Release 8.2, we recommended that you do not use the service port for continuous SNMP polling and management functions, except when the management interface of the Cisco WLC is unreachable. In Cisco Wireless Release 8.2, this restriction is removed.

In Release 8.2, the following are supported on the Cisco 5520, 8510, and 8540 WLCs:

– SNMP polling v2 and v3

– Syslog messaging towards external server

– Any form of file transfer, including FTP, TFTP, and SFTP, to/from external server

– HTTP and HTTPS access to Cisco WLC

– SSH and Telnet

• Local EAP is supported
• Wired Guest Access is supported

Support for Wi-Fi Certified Passpoint Release 2.0

In order to support Passpoint Release 2.0 certification, the technical specification of HotSpot 2.0 Release 2 has been implemented, which allows an end user, upon reaching a Passpoint 2.0 WLAN, to sign up online, on the fly, to that WLAN, in the case where no previously known or preferred WLANs were available to allow secure connection.

This is made possible by adding configuration capability to a Cisco WLC to allow clients to connect to an Online Sign-Up (OSU) server and obtain WPA2-Enterprise credentials to perform their subsequent authentication with the secure Passpoint 2.0 WLAN.

For more information, see the Configuring Mobile Concierge chapter in the Cisco Wireless Controller Configuration Guide.

Bonjour Gateway on Cisco 2504 WLC

Limited Bonjour gateway is supported on Cisco 2504 WLC with support for up to 200 instance services.

Increased Channel and Tx Power Support for Various Countries

To maximize the amount of channels supported and transmit power that is specified in the wireless regulations, the following changes are made in the regulatory domains:

1.–S APs will work with the lower Tx power; –N will continue to use the higher power

Platforms Supported

• Indoor

– Cisco Aironet 3700 Series Access Points

– Cisco Aironet 2700 Series Access Points

– Cisco Aironet 1830 and 1850 Access Points

---

Note The 1830 and 1850 APs already support the domain change for Thailand and Vietnam. In Release 8.2, the APs support the domain change for Macau.

– Cisco Aironet 1700 Series Access Points

– Cisco Aironet 700i and 700w Access Points

• Outdoor

– Cisco Aironet 1570 Series Access Points

– Cisco Aironet 1530 Series Access Points

Universal PIDs Supported

• Indoor

– Cisco Aironet 3700 Series Access Points

– Cisco Aironet 2700 Series Access Points

– Cisco Aironet 1830 and 1850 Access Points

---

Note Supports Macau changes from –C to –S domain.

– Cisco Aironet 700i and 700w Access Points

• Outdoor

– Cisco Aironet 1530 Series Access Points

Legacy APs

• Changes made in Cisco WLC to support –S domain for Hong Kong, Macau, Thailand, and Vietnam.
• Changes made in Cisco WLC to support –I domain for Algeria
• Previously supported domains can continue to associate with Cisco WLC and be supported in addition to the new domain APs.

Upgrade and Downgrade Scenarios

• When you upgrade to Release 8.2, the regular SKU APs will continue to associate with the Cisco WLC and be operational with both the radios.
• If a Cisco WLC is downgraded from Release 8.2, the indoor APs deployed in Hong Kong, Thailand, Vietnam, and Macau with –S domain and APs deployed in Algeria with –I domain will continue to associate with Cisco WLCs. However, the 802.11a radio will not be operational.

Increased Country Code Support

In Release 8.2, you can configure up to 110 country codes per Cisco WLC. Prior to Release 8.2, you could configure up to 20 country codes per Cisco WLC.

Security Update

Support for Transport Layer Security (TLS) v1.2 is added in Release 8.2.

The following are supported for web authentication and WebAdmin based on the configuration:

• TLSv1.2
• TLSv1.0
• SSLv3
• SSLv2

---

Note DTLSv1.2 for CAPWAP is not supported.

QoS Mapping

The QoS Mapping feature maintains the QoS policies in situations where appropriate QoS markings that match the application type are not marked by clients or applications. The administrator maps the differentiated services code point (DSCP) to user-priority values in a Cisco WLC, which in turn provides better experience to users while using certain applications, such as voice or video applications.

For more information, see the Configuring QoS Mapping section in the Cisco Wireless Controller Configuration Guide.

Cisco Industrial Wireless 3702 Access Point Updates

• Flexible Antenna Port Support—The Cisco IW 3702 AP model with external antennas can operate in the 2.4-GHz and 5.0-GHz band in one of two antenna band modes.

In the single-band mode:

– the 5-GHz radio uses antenna ports C and D, each with a single band antenna

– the 2.4-GHz radio uses antenna ports A and B, each with a single band antenna

In the dual-band mode, four dual-band antennas are used and both the radios share these antennas.

• Daisy chaining is supported (support introduced in Release 8.1.111.0)

---

Table 4 Software Support for Access Points

Access Points		First Support	Last Support
700 Series	AIR-CAP702I-x-K9	7.5.102.0	—
	AIR-CAP702I-xK910	7.5.102.0	—
700W Series	AIR-CAP702Wx-K9	7.6.120.0	—
	AIR-CAP702W-xK910	7.6.120.0	—
1000 Series	AIR-AP1010	3.0.100.0	4.2.209.0
	AIR-AP1020	3.0.100.0	4.2.209.0
	AIR-AP1030	3.0.100.0	4.2.209.0
	Airespace AS1200	—	4.0
	AIR-LAP1041N	7.0.98.0	—
	AIR-LAP1042N	7.0.98.0	—
1100 Series	AIR-LAP1121	4.0.155.0	7.0.x
1130 Series	AIR-LAP1131	3.1.59.24	8.0.x
1140 Series	AIR-LAP1141N	5.2.157.0	—
	AIR-LAP1142N	5.2.157.0	—
1220 Series	AIR-AP1220A	3.1.59.24	7.0.x
	AIR-AP1220B	3.1.59.24	7.0.x
1230 Series	AIR-AP1230A	3.1.59.24	7.0.x
	AIR-AP1230B	3.1.59.24	7.0.x
	AIR-LAP1231G	3.1.59.24	7.0.x
	AIR-LAP1232AG	3.1.59.24	7.0.x
1240 Series	AIR-LAP1242G	3.1.59.24	8.0.x
	AIR-LAP1242AG	3.1.59.24	8.0.x
1250 Series	AIR-LAP1250	4.2.61.0	8.0.x
	AIR-LAP1252G	4.2.61.0	8.0.x
	AIR-LAP1252AG	4.2.61.0	8.0.x
1260 Series	AIR-LAP1261N	7.0.116.0	—
	AIR-LAP1262N	7.0.98.0	—
1300 Series	AIR-BR1310G	4.0.155.0	7.0.x
1400 Series	Standalone Only	—	—
1600 Series	AIR-CAP1602I-x-K9	7.4.100.0	—
	AIR-CAP1602I-xK910	7.4.100.0	—
	AIR-SAP1602I-x-K9	7.4.100.0	—
	AIR-SAP1602I-xK9-5	7.4.100.0	—
	AIR-CAP1602E-x-K9	7.4.100.0	—
	AIR-SAP1602E-xK9-5	7.4.100.0	—
1700 Series	AIR-CAP1702I-x-K9	8.0.100.0	—
	AIR-CAP1702I-xK910	8.0.100.0	—
1830 Series	AIR-AP1832I-UXK9	8.1.120.0	—
	AIR-AP1832I-x-K9	8.1.120.0	—
1850 Series	AIR-AP1852I-UXK9	8.1.111.0	—
	AIR-AP1852I-UXK910	8.1.111.0	—
	AIR-AP1852I-UXK9C	8.1.111.0	—
	AIRAP1852I-UXK910C	8.1.111.0	—
	AIR-AP1852E-UXK9	8.1.111.0	—
	AIR-AP1852E-UXK910	8.1.111.0	—
	AIR-AP1852E-UXK9C	8.1.111.0	—
	AIRAP1852E-UXK910C	8.1.111.0	—
	AIR-AP1852E-x-K9	8.1.111.0	—
	AIR-AP1852E-x-K9C	8.1.111.0	—
	AIR-AP1852I-x-K9	8.1.111.0	—
	AIR-AP1852I-x-K9C	8.1.111.0	—
AP801	—	5.1.151.0	8.0.x
AP802	—	7.0.98.0	—
AP802H	—	7.3.101.0	—
AP803	—	8.1.120.0	—
ASA5506W-AP702	—	8.1.120.0	—
2600 Series	AIR-CAP2602I-x-K9	7.2.110.0	—
	AIR-CAP2602I-xK910	7.2.110.0	—
	AIR-SAP2602I-x-K9	7.2.110.0	—
	AIR-SAP2602I-x-K95	7.2.110.0	—
	AIR-CAP2602E-x-K9	7.2.110.0	—
	AIR-CAP2602E-xK910	7.2.110.0	—
	AIR-SAP2602E-x-K9	7.2.110.0	—
	AIR-SAP2602E-x-K95	7.2.110.0	—
2700 Series	AIR-CAP2702I-x-K9	7.6.120.0	—
	AIR-CAP2702I-xK910	7.6.120.0	—
	AIR-CAP2702E-x-K9	7.6.120.0	—
	AIR-CAP2702E-xK910	7.6.120.0	—
	AIR-AP2702I-UXK9	8.0.110.0	—
3500 Series	AIR-CAP3501E	7.0.98.0	—
	AIR-CAP3501I	7.0.98.0	—
	AIR-CAP3502E	7.0.98.0	—
	AIR-CAP3502I	7.0.98.0	—
	AIR-CAP3502P	7.0.116.0	—
3600 Series2	AIR-CAP3602I-x-K9	7.1.91.0	—
	AIR-CAP3602I-xK910	7.1.91.0	—
	AIR-CAP3602E-x-K9	7.1.91.0	—
	AIR-CAP3602E-xK910	7.1.91.0	—
	USC5101-AI-AIR-K9	7.6	—
3700 Series	AIR-CAP3702I	7.6	—
	AIR-CAP3702E	7.6	—
	AIR-CAP3702P	7.6	—
600 Series	AIR-OEAP602I	7.0.116.0	—
1500 Mesh Series	AIR-LAP-150	3.1.59.24	4.2.207.54M
	AIR-LAP-1510	3.1.59.24	4.2.207.54M
1520 Mesh Series	AIR-LAP1522AG	-A and N: 4.1.190.1 or 5.2 or later3	8.0.x
		All other reg. domains: 4.1.191.24M or 5.2 or later1	8.0.x
	AIR-LAP1522HZ	-A and N: 4.1.190.1 or 5.2 or later1	8.0.x
		All other reg. domains: 4.1.191.24M or 5.2 or later1	8.0.x
	AIR-LAP1522PC	-A and N: 4.1.190.1 or 5.2 or later1	8.0.x
		All other reg. domains: 4.1.191.24M or 5.2 or later1	8.0.x
	AIR-LAP1522CM	7.0.116.0 or later.	8.0.x
	AIR-LAP1524SB	-A, C and N: 6.0 or later	8.0.x
		All other reg. domains: 7.0.116.0 or later.	8.0.x
	AIR-LAP1524PS	-A: 4.1.192.22M or 5.2 or later1	8.0.x
1530	AIR-CAP1532I-x-K9	7.6	—
	AIR-CAP1532E-x-K9	7.6	—
1550	AIR-CAP1552C-x-K9	7.0.116.0	—
	AIR-CAP1552E-x-K9	7.0.116.0	—
	AIR-CAP1552H-x-K9	7.0.116.0	—
	AIR-CAP1552I-x-K9	7.0.116.0	—
	AIR-CAP1552EU-x-K9	7.3.101.0	—
	AIR-CAP1552CU-x-K9	7.3.101.0	—
	AIR-CAP1552WU-x-K9	8.0.100.0	—
1552S	AIR-CAP1552SA-x-K9	7.0.220.0	—
	AIR-CAP1552SD-x-K9	7.0.220.0	—
1570	AIR-AP1572EAC-x-K9	8.0.110.0	—
	AIR-AP1572ICy4-x-K9	8.0.110.0	—
	AIR-AP1572ECy-x-K9	8.0.110.0	—
IW3700	IW3702-2E-UXK9	8.0.120.0	—
	IW3702-4E-UXK9	8.0.120.0	—

Release Types

 

5.AssureWave is a Cisco program that focuses on satisfying customer quality requirements in key industry segments in the mobility space. This program links and expands on product testing conducted within development engineering, regression testing, and system test groups within Cisco. The AssureWave program has established partnerships with major device and application vendors to help ensure broader interoperability with our new release. The AssureWave certification marks the successful completion of extensive wireless LAN controller and access point testing in real-world use cases with a variety of mobile client devices applicable in a specific industry.

Software Release Recommendations

 

For detailed release recommendations, see the software release bulletin:

http://www.cisco.com/c/en/us/products/collateral/wireless/8500-series-wireless-controllers/bulletin-c25-730741.html

For more information about the Cisco Wireless solution compatibility matrix, see http://www.cisco.com/c/en/us/td/docs/wireless/compatibility/matrix/compatibility-matrix.html.

Guidelines and Limitations

• After upgrading to Release 8.2, the Cisco WLC might lose all IPv4 connectivity. The Cisco WLC can no longer service incoming SSH/Web sessions and is unable to ping other IPv4 stations. However, the default router is able to ping the Cisco WLC’s management interface.

Every 10 seconds, a message similar to the following is sent to the msglog:

This occurs in the following conditions:

a. LAG is not configured.

b. The management interface is untagged and is mapped to one physical port.

c. When an untagged dynamic interface is added and mapped to port 2, the default route for the management interface is lost.

The workaround is to configure all interfaces with VLANs.

You can track this issue via CSCux75436.

• Effective with Release 8.2.100.0, you cannot download some of the older configurations from the Cisco WLC because of the Multicast and IP address validations introduced in this release. The platform support for global multicast and multicast mode are listed in the following table.

 

 

• In Release 8.2, the reload command is not recognized by Cisco Aironet 3600 Series APs. The workaround is to use the debug capwap console cli command.
• Cisco WLC Release 7.3.112.0, which is configured for new mobility, might revert to old mobility after upgrading to Release 7.6, even though Release 7.6 supports new mobility. This issue occurs when new mobility, which is compatible with the Cisco 5760 Wireless LAN Controller and the Cisco Catalyst 3850 Series Switch, are in use. However, old mobility is not affected.

The workaround is as follows:

a. Enter the following commands:

b. After the reboot, press Esc on the console, and use the boot menu to select Release 7.6.

c. After booting on Release 7.6, set back the primary boot, and save the configuration by entering the following command:

config boot primary

---

Note The epings are not available in the Cisco 5500 Series WLC when New Mobility is enabled.

---

Note If you downgrade from a Cisco WLC release that supports new mobility to a Cisco WLC release that does not support new mobility, for example, Cisco Wireless Release 7.6 to Release 7.3.x and you download the 7.6 configuration file with new mobility in enabled state, the release that does not support new mobility will have the new mobility feature in enabled state.

• If you downgrade from Release 8.2.100.0 to a 7.x release, the trap configuration is lost and must be reconfigured.
• If you upgrade from Release 8.0.110.0 to a later release, the config redundancy mobilitymac mac-addr command's setting is removed. You must manually reconfigure the mobility MAC address after the upgrade.
• If you are upgrading from Release 8.0.140.0 or 8.0.15x.0 to a later release and also have the multiple country code feature configured, the feature configuration is corrupted after the upgrade. For more information, see CSCve41740.
• If you have ACL configurations in a Cisco WLC, and downgrade from a 7.4 or later release to a 7.3 or earlier release, you might experience XML errors on rebooting the Cisco WLC. However, these errors do not have any impact on any of the functionalities or configurations.
• If you are upgrading from a 7.4.x or earlier release to a release later than 7.4, the Called Station ID type information is mapped to the RADIUS Accounting Called Station ID type; which, by default, is set to apradio-mac-ssid. You can configure the RADIUS Authentication Called Station ID type information by using the config radius auth callStationIdType command.
• When FlexConnect APs (known as H-REAP APs in the 7.0.x releases) that are associated with a Cisco WLC that has all the 7.0.x software releases prior to Release 7.0.240.0, upgrade to Release 8.2.100.0, the APs lose the enabled VLAN support configuration. The VLAN mappings revert to the default values of the VLAN of the associated interface. The workaround is to upgrade from Release 7.0.240.0 and later 7.0.x releases to Release 8.2.100.0.

---

Note In case of FlexConnect VLAN mapping deployment, we recommend that the deployment be done using FlexConnect groups. This allows you to recover VLAN mapping after an AP rejoins the Cisco WLC without having to manually reassign the VLAN mappings.

• When a client sends an HTTP request, the Cisco WLC intercepts it for redirection to the login page. If the HTTP GET request that is intercepted by the Cisco WLC is longer than 2000 bytes, the Cisco WLC drops the packet. Track CSCuy81133 for a possible enhancement to address this restriction.
• We recommend that you install Release 1.9.0.0 of Cisco Wireless LAN Controller Field Upgrade Software (FUS), which is a special AES package that contains several system-related component upgrades. These include the bootloader, field recovery image, and FPGA/MCU firmware. Installing the FUS image requires special attention because it installs some critical firmware. The FUS image is independent of the runtime image. For more information, see http://www.cisco.com/c/en/us/td/docs/wireless/controller/release/notes/fus_rn_OL-31390-01.html.

---

Note The FUS image installation process reboots the Cisco WLC several times and reboots the runtime image. The entire process takes approximately 30 minutes. We recommend that you install the FUS image in a planned outage window.

---

Note If you are using a Cisco 2500 Series controller and you intend to use the Application Visibility and Control (AVC) and NetFlow protocol features, you must install Release 1.9.0.0 of Cisco Wireless LAN Controller FUS. This is not required if you are using other controller hardware models.

• After you upgrade to Release 7.4, networks that were not affected by the existing preauthentication access control lists might not work because the rules are now enforced. That is, networks with clients configured with static DNS servers might not work unless the static server is defined in the preauthentication ACL.
• On the Cisco Flex 7500 Series WLCs, if FIPS is enabled, the reduced boot options are displayed only after a bootloader upgrade.

---

Note Bootloader upgrade is not required if FIPS is disabled.

• If you have to downgrade from one release to another, you might lose the configuration from your current release. The workaround is to reload the previous Cisco WLC configuration files saved on the backup server, or to reconfigure the Cisco WLC.
• It is not possible to directly upgrade to Release 8.2.100.0 release from a release that is earlier than Release 7.0.98.0.
• You can upgrade or downgrade the Cisco WLC software only between certain releases. In some instances, you must first install an intermediate release prior to upgrading to Release 8.2.100.0. Table 8 shows the upgrade path that you must follow before downloading Release 8.2.100.0.

---

 

• When you upgrade the Cisco WLC to an intermediate software release, you must wait until all of the access points that are associated with the Cisco WLC are upgraded to the intermediate release before you install the latest Cisco WLC software. In large networks, it can take some time to download the software on each access point.
• You can upgrade to a new release of the Cisco WLC software or downgrade to an earlier release even if Federal Information Processing Standard (FIPS) is enabled.
• When you upgrade to the latest software release, the software on the access points associated with the Cisco WLC is also automatically upgraded. When an access point is loading software, each of its LEDs blinks in succession.
• We recommend that you access the Cisco WLC GUI using Microsoft Internet Explorer 10 or a later version or Mozilla Firefox 32 or a later version.

---

Note Microsoft Internet Explorer 8 might fail to connect over HTTPS because of compatibility issues. In such cases, you can explicitly enable SSLv3 by entering the config network secureweb sslv3 enable command.

• Cisco WLCs support standard SNMP MIB files. MIBs can be downloaded from the Software Center on Cisco.com.
• The Cisco WLC software is factory installed on your Cisco WLC and is automatically downloaded to the access points after a release upgrade and whenever an access point joins a Cisco WLC. We recommend that you install the latest software version available for maximum operational benefit.
• Ensure that you have a TFTP, FTP, or SFTP server available for the software upgrade. Follow these guidelines when setting up a server:

– Ensure that your TFTP server supports files that are larger than the size of Cisco WLC software Release 8.2.100.0. Some TFTP servers that support files of this size are tftpd32 and the TFTP server within the Prime Infrastructure. If you attempt to download the 8.2.100.0 Cisco WLC software and your TFTP server does not support files of this size, the following error message appears:

– If you are upgrading through the distribution system network port, the TFTP or FTP server can be on the same subnet or a different subnet because the distribution system port is routable.

• When you plug a Cisco WLC into an AC power source, the bootup script and power-on self test is run to initialize the system. During this time, press Esc to display the bootloader Boot Options menu. The menu options for the Cisco 5500 Series WLC differ from the menu options for the other Cisco WLC platforms.

Bootloader menu for Cisco 5500 Series WLC:

Bootloader menu for other Cisco WLC platforms:

Enter 1 to run the current software, enter 2 to run the previous software, enter 4 (on Cisco 5500 Series WLC), or enter 5 (on Cisco WLC platforms other than 5500 series) to run the current software and set the Cisco WLC configuration to factory defaults. Do not choose the other options unless directed to do so.

---

Note See the Installation Guide or the Quick Start Guide pertaining to your Cisco WLC platform for more details on running the bootup script and power-on self test.

• The Cisco WLC bootloader stores a copy of the active primary image and the backup image. If the primary image becomes corrupted, you can use the bootloader to boot with the backup image.

With the backup image stored before rebooting, choose Option 2: Run Backup Image from the boot menu to boot from the backup image. Then, upgrade with a known working image and reboot the Cisco WLC.

• You can control the addresses that are sent in the Control and Provisioning of Wireless Access Points (CAPWAP) discovery responses when NAT is enabled on the Management Interface using the following command:

config network ap-discovery nat-ip-only { enable | disable }

Here:

– enable —Enables use of NAT IP only in a discovery response. This is the default. Use this command if all the APs are outside the NAT gateway.

– disable —Enables use of both NAT IP and non-NAT IP in a discovery response. Use this command if APs are on the inside and outside the NAT gateway, for example, Local Mode and OfficeExtend APs are on the same Cisco WLC.

---

Note To avoid stranding of APs, you must disable AP link latency (if enabled) before you use the disable option for the config network ap-discovery nat-ip-only command. To disable AP link latency, use the config ap link-latency disable all command.

• You can configure 802.1p tagging by using the config qos dot1p-tag { bronze | silver | gold | platinum } command. For Release 7.2.103.0 and later releases, if you tag 802.1p packets, the tagging has an impact on only wired packets. Wireless packets are impacted only by the maximum priority level set for QoS.
• You can reduce the network downtime using the following options:

– You can predownload the AP image.

– For FlexConnect access points, use the FlexConnect AP upgrade feature to reduce traffic between the Cisco WLC and the AP (main site and the branch). For more information about the FlexConnect AP upgrade feature, see the Cisco Wireless Controller Configuration Guide.

---

Note Predownloading Release 8.2.100.0 on a Cisco Aironet 1240 access point is not supported when upgrading from a previous Cisco WLC release. If predownloading is attempted on a Cisco Aironet 1240 access point, an AP disconnect will occur momentarily.

• Do not power down the Cisco WLC or any access point during the upgrade process; otherwise, you might corrupt the software image. Upgrading a Cisco WLC with a large number of access points can take as long as 30 minutes, depending on the size of your network. However, with the increased number of concurrent access point upgrades supported, the upgrade time should be significantly reduced. The access points must remain powered, and the Cisco WLC must not be reset during this time.
• To downgrade from Release 8.2.100.0 to Release 6.0 or an earlier release, perform either of these tasks:

– Delete all the WLANs that are mapped to interface groups, and create new ones.

– Ensure that all the WLANs are mapped to interfaces rather than interface groups.

• After you perform the following functions on the Cisco WLC, reboot the Cisco WLC for the changes to take effect:

– Enable or disable link aggregation (LAG)

– Enable a feature that is dependent on certificates (such as HTTPS and web authentication)

– Add a new license or modify an existing license

– Increase the priority of a license

– Enable HA

– Install the SSL certificate

– Configure the database size

– Install the vendor-device certificate

– Download the CA certificate

– Upload the configuration file

– Install the Web Authentication certificate

– Make changes to the management interface or the virtual interface

– Make changes to TCP MSS settings

Upgrading to Cisco WLC Software Release 8.2.100.0 (GUI)

---

Step 1 Upload your Cisco WLC configuration files to a server to back up the configuration files.

---

Note We highly recommend that you back up your Cisco WLC configuration files prior to upgrading the Cisco WLC software.

Step 2 Follow these steps to obtain Cisco Wireless Release 8.2.100.0 software:

a. Click this URL to go to the Software Center:

http://www.cisco.com/cisco/software/navigator.html

b. Choose Wireless from the center selection window.

c. Click Wireless LAN Controllers.

The following options are displayed. Depending on your Cisco WLC platform, select either of these options:

– Integrated Controllers and Controller Modules

– Standalone Controllers

d. Select the Cisco WLC model number or name.

The Download Software page is displayed.

e. The software releases are labeled as follows to help you determine which release to download. Click a Cisco WLC software release number:

• Early Deployment (ED) —These software releases provide new features and new hardware platform support as well as bug fixes.
• Maintenance Deployment (MD) —These software releases provide bug fixes and ongoing software maintenance.
• Deferred (DF) —These software releases have been deferred. We recommend that you migrate to an upgraded release.

f. Click the filename ( filename.aes).

g. Click Download.

h. Read the Cisco End User Software License Agreement and click Agree.

i. Save the file to your hard drive.

j. Repeat steps a. through i. to download the remaining file.

Step 3 Copy the Cisco WLC software file ( filename.aes) to the default directory on your TFTP, FTP, or SFTP server.

Step 4 (Optional) Disable the Cisco WLC 802.11a/n and 802.11b/g/n networks.

---

Note For busy networks, Cisco WLCs on high utilization, and small Cisco WLC platforms, we recommend that you disable the 802.11a/n and 802.11b/g/n networks as a precautionary measure.

Step 5 Choose Commands > Download File to open the Download File to Controller page.

Step 6 From the File Type drop-down list, choose Code.

Step 7 From the Transfer Mode drop-down list, choose TFTP, FTP, or SFTP.

Step 8 In the IP Address text box, enter the IP address of the TFTP, FTP, or SFTP server.

Step 9 If you are using a TFTP server, the default value of 10 retries for the Maximum Retries text field, and 6 seconds for the Timeout text field should work correctly without any adjustment. However, you can change these values, if desired. To do so, enter the maximum number of times that the TFTP server attempts to download the software in the Maximum Retries text box and the amount of time (in seconds) for which the TFTP server attempts to download the software, in the Timeout text box.

Step 10 In the File Path text box, enter the directory path of the software.

Step 11 In the File Name text box, enter the name of the software file ( filename.aes).

Step 12 If you are using an FTP server, perform these steps:

a. In the Server Login Username text box, enter the username with which to log on to the FTP server.

b. In the Server Login Password text box, enter the password with which to log on to the FTP server.

c. In the Server Port Number text box, enter the port number on the FTP server through which the download occurs. The default value is 21.

Step 13 Click Download to download the software to the Cisco WLC.

A message appears indicating the status of the download.

Step 14 After the download is complete, click Reboot.

Step 15 If you are prompted to save your changes, click Save and Reboot.

Step 16 Click OK to confirm your decision to reboot the Cisco WLC.

Step 17 For Cisco WiSM2 on the Catalyst switch, check the port channel and re-enable the port channel if necessary.

Step 18 If you have disabled the 802.11a/n and 802.11b/g/n networks in (Optional) Disable the Cisco WLC 802.11a/n and 802.11b/g/n networks., re-enable them.

Step 19 To verify that the 8.2.100.0 Cisco WLC software is installed on your Cisco WLC, click Monitor on the Cisco WLC GUI and view the Software Version field under Controller Summary.

 

---

Downloading and Installing a DTLS License for an LDPE Cisco WLC

---

Step 1 To download the Cisco DTLS license:

a. Go to the Cisco Software Center at this URL:

https://tools.cisco.com/SWIFT/LicensingUI/Home

b. From the Product License Registration page from the Get Other Licenses drop-down list, click IPS, Crypto, Other....

c. In the Wireless section, click Cisco Wireless Controllers (2500/5500/7500/WiSM2) DTLS License and click Next.

d. Follow the on-screen instructions to generate the license file. The license file information will be sent to you in an e-mail.

Step 2 Copy the license file to your TFTP server.

Step 3 Install the DTLS license either by using the Cisco WLC web GUI interface or the CLI:

• To install the license using the WLC web GUI, choose:

Management > Software Activation > Commands > Action : Install License

• To install the license using the CLI, enter this command:

license install tftp ://ipaddress /path /extracted-file

After the installation of the DTLS license, reboot the system. Ensure that the DTLS license that is installed is active.

 

Upgrading from an LDPE to a Non-LDPE Cisco WLC

---

Step 1 Download the non-LDPE software release:

a. Go to the Cisco Software Center at:

http://www.cisco.com/cisco/software/navigator.html?mdfid=282585015&i=rm

b. Choose the Cisco WLC model.

c. Click Wireless LAN Controller Software.

d. In the left navigation pane, click the software release number for which you want to install the non-LDPE software.

e. Choose the non-LDPE software release: AIR-X-K9-X-X.X.aes

f. Click Download.

g. Read the Cisco End User Software License Agreement and then click Agree.

h. Save the file to your hard drive.

Step 2 Copy the Cisco WLC software file ( filename.aes) to the default directory on your TFTP server or FTP server.

Step 3 Upgrade the Cisco WLC with this version by performing Step 3 through Step 19 detailed in the “Upgrading to Cisco WLC Software Release 8.2.100.0” section.

 

Table 9 Test Bed Configuration for Interoperability

Hardware/Software Parameter	Hardware/Software Configuration Type
Release	8.2.100.0
Cisco WLC	Cisco 55xx Series Controller
Access points	3502, 3602, 1602, 2602, 1702, 2702, 3702, 702, 702W, 1852
Radio	802.11ac, 802.11a, 802.11g, 802.11n2, 802.11n5
Security	Open, WEP, PSK (WPA and WPA2), 802.1X (WPA-TKIP and WPA2-AES) (LEAP, PEAP, EAP-FAST, EAP-TLS)
RADIUS	ACS 4.2, ACS 5.2
Types of tests	Connectivity, traffic, and roaming between two access points

Table 10 Client Types

Client Type and Name	Version
Laptop
Intel 4965	v13.4
Intel 5100/5300	v14.3.2.1
Intel 6200	15.15.0.1
Intel 6300	15.16.0.2
Intel 6205	15.16.0.2
Intel 1000/1030	v14.3.0.6
Intel 7260	17.16.0.4
Intel 7265	17.16.0.4
Intel 3160	17.16.0.4
Broadcom 4360	6.30.163.2005
Linksys AE6000 (USB)	5.1.2.0
Netgear A6200 (USB)	6.30.145.30
Netgear A6210(USB)	5.1.18.0
D-Link DWA-182 (USB)	6.30.145.30
Engenius EUB 1200AC(USB)	1026.5.1118.2013
Asus AC56(USB)
Dell 1395/1397/Broadcom 4312HMG(L)	5.30.21.0
Dell 1501 (Broadcom BCM4313)	v5.60.48.35/v5.60.350.11
Dell 1505/1510/Broadcom 4321MCAG/4322HM	5.60.18.8
Dell 1515(Atheros)	8.0.0.239
Dell 1520/Broadcom 43224HMS	5.60.48.18
Dell 1530 (Broadcom BCM4359)	5.100.235.12
Dell 1540	6.30.223.215
Cisco CB21	1.3.0.532
Atheros HB92/HB97	8.0.0.320
Atheros HB95	7.7.0.358
MacBook Pro	OSX 10.11.1
MacBook Air old	OSX 10.11.1
MacBook Air new	OSX 10.11.1
Macbook Pro with Retina Display	OSX 10.11.1
Macbook New 2015	OSX 10.11.1
Tablets
Apple iPad2	iOS 9.1(13B143)
Apple iPad3	iOS 9.1(13B143)
Apple iPad mini with Retina display	iOS 9.1(13B143)
Apple iPad Air	iOS 9.1(13B143)
Apple iPad Air 2	iOS 9.1(13B143)
Samsung Galaxy Tab Pro SM-T320	Android 4.4.2
Samsung Galaxy Tab 10.1- 2014 SM-P600	Android 4.4.2
Samsung Galaxy Note 3 - SM-N900	Android 5.0
Microsoft Surface Pro 3	Windows 8.1 Driver: 15.68.3073.151
Microsoft Surface Pro 2	Windows 8.1 Driver: 14.69.24039.134
Google Nexus 9	Android 6.0
Google Nexus 7 2nd Gen	Android 5.0
Intermec CK70	Windows Mobile 6.5 / 2.01.06.0355
Intermec CN50	Windows Mobile 6.1 / 2.01.06.0333
Symbol MC5590	Windows Mobile 6.5 / 3.00.0.0.051R
Symbol MC75	Windows Mobile 6.5 / 3.00.2.0.006R
Phones and Printers
Cisco 7921G	1.4.5.3.LOADS
Cisco 7925G	1.4.5.3.LOADS
Cisco 8861	Sip88xx.10-2-1-16
Ascom i75	1.8.0
Spectralink 8030	119.081/131.030/132.030
Apple iPhone 4S	iOS 9.1(13B143)
Apple iPhone 5	iOS 9.1(13B143)
Apple iPhone 5s	iOS 9.1(13B143)
Apple iPhone 5c	iOS 9.1(13B143)
Apple iPhone 6	iOS 9.1(13B143)
Apple iPhone 6 Plus	iOS 9.1(13B143)
HTC One	Android 5.0
OnePlusOne	Android 4.3
Samsung Galaxy S4 T-I9500	Android 5.0.1
Sony Xperia Z Ultra	Android 4.4.2
Nokia Lumia 1520	Windows Phone 8.1
Google Nexus 5	Android 5.1
Nexus 6	Android 5.1.1
Samsung Galaxy S5-SM-G900A	Android 4.4.2
Huawei Ascend P7	Android 4.4.2
Samsung Galaxy S III	Android 4.3
SpectraLink 8450	3.0.2.6098/5.0.0.8774
Samsung Galaxy Nexus GTI9200	Android 4.4.2
Samsung Galaxy Mega SM900	Android 4.4.2
Samsung Galaxy S6	Android 5.1.1

---

Features Not Supported on Cisco 2504 WLC

• Autoinstall
• Cisco WLC integration with Lync SDN API
• Application Visibility and Control (AVC) for FlexConnect local switched access points
• Application Visibility and Control (AVC) for FlexConnect centrally switched access points

---

Note However, AVC for local mode APs is supported.

• Bandwidth Contract
• Service Port
• AppleTalk Bridging
• Right-to-Use Licensing
• PMIPv6
• EoGRE
• AP Stateful Switchover (SSO) and client SSO
• Multicast-to-Unicast
• Cisco Smart Software Licensing

---

Note The features that are not supported on Cisco WiSM2 and Cisco 5508 WLC are not supported on Cisco 2504 WLCs too.

---

Note Directly connected APs are supported only in the local mode.

Features Not Supported on Cisco WiSM2 and Cisco 5508 WLC

• Spanning Tree Protocol (STP)
• Port Mirroring
• VPN Termination (such as IPsec and L2TP)
• VPN Passthrough Option

---

Note You can replicate this functionality on a Cisco 5500 Series WLC by creating an open WLAN using an ACL.

• Configuration of 802.3 bridging, AppleTalk, and Point-to-Point Protocol over Ethernet (PPPoE)
• Fragmented pings on any interface
• Right-to-Use Licensing
• Cisco 5508 WLC cannot function as mobility controller (MC). However, Cisco 5508 WLC can function as guest anchor in a New Mobility environment.
• Cisco Smart Software Licensing

Features Not Supported on Cisco Flex 7510 WLCs

• Static AP-manager interface

---

Note For Cisco Flex 7500 Series WLCs, it is not necessary to configure an AP-manager interface. The management interface acts as an AP-manager interface by default, and the access points can join on this interface.

• TrustSec SXP
• IPv6 and Dual Stack client visibility

---

Note IPv6 client bridging and Router Advertisement Guard are supported.

• Internal DHCP server
• Access points in local mode

---

Note An AP associated with the Cisco WLC in the local mode should be converted to the FlexConnect mode or monitor mode, either manually or by enabling the autoconvert feature. On the Cisco Flex 7500 WLC CLI, enable the autoconvert feature by entering the config ap autoconvert enable command.

• Mesh (use Flex + Bridge mode for mesh-enabled FlexConnect deployments)
• Spanning Tree Protocol (STP)
• Cisco Flex 7500 Series WLC cannot be configured as a guest anchor Cisco WLC. However, it can be configured as a foreign Cisco WLC to tunnel guest traffic to a guest anchor Cisco WLC in a DMZ.
• Multicast

---

Note FlexConnect local-switched multicast traffic is bridged transparently for both wired and wireless on the same VLAN. FlexConnect access points do not limit traffic based on Internet Group Management Protocol (IGMP) or MLD snooping.

• PMIPv6
• Cisco Smart Software Licensing

Features Not Supported on Cisco 5520, 8510, and 8540 WLCs

• Internal DHCP Server
• Mobility controller functionality in converged access mode

---

Note Cisco Smart Software Licensing is not supported on Cisco 8510 WLC.

Features Not Supported on Cisco Virtual WLCs

• Cisco Aironet 1850 and 1830 Series APs
• Internal DHCP server
• TrustSec SXP
• Access points in local mode
• Mobility/Guest Anchor
• Wired Guest
• Multicast

---

Note FlexConnect local-switched multicast traffic is bridged transparently for both wired and wireless on the same VLAN. FlexConnect access points do not limit traffic based on IGMP or MLD snooping.

• FlexConnect central switching in large-scale deployments

---

Note FlexConnect central switching is supported in only small-scale deployments, wherein the total traffic on Cisco WLC ports is not more than 500 Mbps.

FlexConnect local switching is supported.

• AP and Client SSO in High Availability
• PMIPv6
• EoGRE (Supported in only local switching mode)
• Workgroup Bridges
• Client downstream rate limiting for central switching
• SHA2 certificates
• Cisco WLC integration with Lync SDN API

Features Not Supported on Mesh Networks

• Load-based call admission control (CAC). Mesh networks support only bandwidth-based CAC or static CAC
• High availability (fast heartbeat and primary discovery join timer)
• AP acting as supplicant with EAP-FASTv1 and 802.1X authentication
• Access point join priority (mesh access points have a fixed priority)
• Location-based services

Features Not Supported on Cisco Aironet 1830 and 1850 APs

• Cisco Virtual Wireless Controller
• Mesh mode
• Flex mode
• Monitor mode
• Workgroup Bridge (WGB) mode
• Link aggregation (LAG)
• OfficeExtend mode
• Enhanced Local Mode (ELM)
• Integrated BLE
• Basic spectrum analysis
• USB-based Bluetooth Low Energy (BLE) device support
• Cisco CleanAir
• Cisco Wireless ClientLink 3.0
• Rogue Location Discovery Protocol (RLDP)
• Cisco Compatible eXtensions (CCX) Specification
• 802.1x supplicant for AP authentication on the wired port
• CKIP, CMIC, and LEAP with Dynamic WEP
• Static WEP key for TKIP or CKIP
• Dynamic Transmit Power Control (DTPC)
• Federal Information Processing Standard (FIPS) and Common Criteria
• 40-MHz Rogue detection
• Native IPv6
• Telnet
• SIP snooping with FlexConnect in local switching mode

---

Note For Cisco Aironet1850 Series AP technical specifications with details on currently supported features, see the Cisco Aironet 1850 Series Access Points Data Sheet.

Features Not Supported on Cisco Aironet 1550 APs (with 64-MB Memory)

• PPPoE
• PMIPv6

---

Note To see the amount of memory in a Cisco Aironet 1550 AP, enter the following command:

(Cisco Controller) >show mesh ap summary

Open Caveats

 

Resolved Caveats