The Intelligent Capture feature provides support to have a direct communication link between Cisco DNA Center and access points (APs), so each of the APs can communicate with Cisco DNA Center directly. Using this channel, the Cisco DNA Center can receive packet capture data, AP and client statistics, and spectrum data.

For more information about configuring Intelligent Capture feature, see the applicable Cisco DNA Center Assurance User Guide at

For more information about configuring the Cisco 1800s Sensor, see the applicable Cisco Digital Network Architecture Center User Guide, Release 1.2.5 at:

• https://www.cisco.com/c/en/us/td/docs/cloud-systems-management/network-automation-and-management/dna-center/1-2-5/user_guide/b_dnac_ug_1_2_5/b_dnac_ug_1_2_4_chapter_0110.html#task_fh1_phw_scb

• https://www.cisco.com/c/en/us/td/docs/cloud-systems-management/network-automation-and-management/dna-center/1-2-5/user_guide/b_dnac_ug_1_2_5/b_dnac_ug_1_2_4_chapter_01011.html#task_tm5_njw_scb

In this release, this feature is enhanced to support FlexConnect mode Local Switching-based IPSK P2P blocking.

In this release, this feature is enhanced to function with L2+L3 enabled WLANs. This enhancement can be enabled only with dot1x+Webauth security setup.

In this release, Inter-Release Controller Mobility (IRCM) with Cisco Catalyst 9800 Series Wireless Controllers is supported.

For more information about IRCM, see the Cisco Catalyst 9800 Wireless Controller-Aireos IRCM Deployment Guide at:

The Cisco Wave 2 APs as Workgroup Bridges feature is in Early Field Trial state.

Note	This feature is not yet officially supported and there will be no assistance from Cisco's Technical Assistance Center.

• Legacy clients that require RC4 or 3DES encryption types are not supported in Local EAP authentication.

• If you downgrade from Release 8.8.x to Release 8.7, FlexConnect IPv6 ACLs are shown to be in their FlexConnect group.

• If you have an AVC profile with default-class setting and you downgrade from Release 8.8.x to an earlier release, the default-class setting is still present in the controller, although the earlier releases do not support this setting.

• If you want to downgrade from Release 8.8.x to Release 8.6.101.0 and if you have Wave 2 APs in Flex+Bridge mode, ensure that these APs are changed to Bridge mode before you perform the downgrade; else, the APs will have incorrect configuration after the downgrade process.

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

• After downloading the new software to the Cisco APs, it is possible that a Cisco AP may get stuck in an upgrading image state. In such a scenario, it might be necessary to forcefully reboot the controller to download a new controller software image or to reboot the controller after the download of the new controller software image. You can forcefully reboot the controller by entering the reset system forced command.

• It is not possible to download some of the older configurations from the controller because of the Multicast and IP address validations. See the "Restrictions on Configuring Multicast Mode" section in the Cisco Wireless Controller Configuration Guide for detailed information about platform support for global multicast and multicast mode.

• When a client sends an HTTP request, the controller intercepts it for redirection to the login page. If the HTTP GET request that is intercepted by the controller is longer than 2000 bytes, the controller drops the packet. Track the Caveat ID CSCuy81133 for a possible enhancement to address this restriction.

• When downgrading from one release to an earlier release, you might lose the configuration from your current release. The workaround is to reload the previous controller configuration files that are saved in the backup server, or to reconfigure the controller.

• When you upgrade controller to an intermediate release, wait until all the APs that are associated with the controller are upgraded to the intermediate release before you install the latest controller software. In large networks, it can take some time to download the software on each AP.

• You can upgrade to a new release of the controller software or downgrade to an earlier release even if FIPS is enabled.

• When you upgrade to the latest software release, the software on the APs associated with the controller is also automatically upgraded. When an AP is loading software, each of its LEDs blinks in succession.

• Controllers support standard SNMP MIB files. MIBs can be downloaded from the software download page on Cisco.com.

• The controller software that is factory-installed on your controller and is automatically downloaded to the APs after a release upgrade and whenever an AP joins a controller. We recommend that you install the latest software version available for maximum operational benefit.

• Ensure that you have a TFTP, HTTP, 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 controller software image. Some TFTP servers that support files of this size are tftpd32 and the TFTP server within Cisco Prime Infrastructure. If you attempt to download the controller software image and your TFTP server does not support files of this size, the following error message appears:

    TFTP failure while storing in flash

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

• The controller 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, from the Boot Options menu, choose Option 2: Run Backup Image to boot from the backup image. Then, upgrade with a known working image and reboot controller.

• 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}

  The following are the details of the command:

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

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

• Do not power down controller or any AP during the upgrade process. If you do this, the software image might get corrupted. Upgrading controller with a large number of APs can take as long as 30 minutes, depending on the size of your network. However, with the increased number of concurrent AP upgrades supported, the upgrade time should be significantly reduced. The APs must remain powered, and controller must not be reset during this time.

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

  • Enable or disable LAG.

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

  • Add a new license or modify an existing license .

    Note	Reboot is not required if you are using Right-to-Use licenses.

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

• From Release 8.3 or a later release, ensure that the configuration file that you back up does not contain the < or > special characters. If either of the special characters is present, the download of the backed up configuration file fails.

• Cisco WLAN Express Setup Over-the-Air Provisioning

• Mobility controller functionality in converged access mode

• VPN Termination (such as IPsec and L2TP)

• Internal DHCP Server

• Mobility controller functionality in converged access mode

• VPN termination (such as IPsec and L2TP)

• Fragmented pings on any interface

• Cisco Umbrella

• Software-defined access

• Domain-based ACLs

• Internal DHCP server

• Cisco TrustSec

• Access points in local mode

• Mobility or Guest Anchor role

• Wired Guest

• Multicast

  Note	FlexConnect locally switched multicast traffic is bridged transparently for both wired and wireless on the same VLAN. FlexConnect APs 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.

• Central switching on Microsoft Hyper-V deployments

• AP and Client SSO in High Availability

• PMIPv6

• Datagram Transport Layer Security (DTLS)

• EoGRE (Supported only in local switching mode)

• Workgroup bridges

• Client downstream rate limiting for central switching

• SHA2 certificates

• Cisco WLC integration with Lync SDN API

• Cisco OfficeExtend Access Points

For detailed information about feature support on Cisco Aironet Wave 2 APs, see:

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

• 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

• AP join priority (Mesh APs have a fixed priority)

• Location-based services

• Dynamic Mesh backhaul data rate.

  Note	We recommend that you keep the Bridge data rate of the AP as auto.

• Background scanning

• Noise-tolerant fast convergence

• MAC Authentication FlexConnect Local Authentication

• Noise-tolerant fast convergence

• Static WEP