Release Notes for Cisco Wireless LAN Controllers and Lightweight Access Points for Release 7.3.112.0
Available Languages
Table of Contents
Release Notes for Cisco Wireless LAN Controllers and Lightweight Access Points for Release 7.3.112.0
Cisco Unified Wireless Network Solution Components
Controller Platforms Not Supported
Hierarchical Mobility (New Mobility)
Configuring Hierarchical Mobility (GUI)
Configuring Hierarchical Mobility (CLI)
Compatibility Matrix with Mobility Network Elements
Compatibility Matrix with Cisco 5760 Wireless LAN Controller and Cisco Catalyst 3850 Switch
Compatibility Matrix without Cisco 5760 Wireless LAN Controller and Cisco Catalyst 3850 Switch
Software Release Support for Access Points
Upgrading to Controller Software Release 7.3.112.0
Upgrading to Controller Software Release 7.3.112.0 (GUI)
Special Notes for Licensed Data Payload Encryption on Cisco Wireless LAN Controllers
Downloading and Installing a DTLS License for an LDPE Controller
Upgrading from an LDPE to a Non-LDPE Controller
Interoperability With Other Clients in 7.3.112.0
Features Not Supported on Controller Platforms
Features Not Supported on Cisco 2500 Series Controllers
Features Not Supported on WiSM2 and Cisco 5500 Series Controllers
Features Not Supported on Cisco Flex 7500 Controllers
Features Not Supported on Cisco 8500 Controllers
Features Not Supported on Cisco Wireless Controller on Cisco Services-Ready Engine
Features Not Supported on Cisco Virtual Wireless LAN Controllers
Features Not Supported on Mesh Networks
FCC Safety Compliance Statement
Obtaining Documentation and Submitting a Service Request
Release Notes for Cisco Wireless LAN Controllers and Lightweight Access Points for Release 7.3.112.0
These release notes describe what is new in this release, instructions to upgrade to this release, and open and resolved caveats for this release.
Note
Unless otherwise noted, all of the Cisco Wireless LAN controllers are referred to as controllers, and all of the Cisco lightweight access points are referred to as access points.
Contents
These release notes contain the following sections:
- Cisco Unified Wireless Network Solution Components
- What’s New in This Release
- Compatibility Matrix
- Software Release Support for Access Points
- Upgrading to Controller Software Release 7.3.112.0
- Special Notes for Licensed Data Payload Encryption on Cisco Wireless LAN Controllers
- Interoperability With Other Clients in 7.3.112.0
- Features Not Supported on Controller Platforms
- Caveats
- Installation Notes
- Service and Support
- Obtaining Documentation and Submitting a Service Request
Cisco Unified Wireless Network Solution Components
The following components are part of the Cisco UWN Solution and are compatible in this release:
Note For more information on the compatibility of wireless software components across releases, see the Cisco Wireless Solutions Software Compatibility Matrix.
Note The 7.3.112.0 controller software release is not compatible with Cisco Prime Network Control System (NCS) 1.1.1.24. Cisco Prime Infrastructure 1.2 is required to support the controller features introduced in the 7.3.x controller software releases. Cisco Prime Infrastructure 1.2 is the subsequent version of Cisco Prime Network Control System (NCS) 1.1.1.24.
- Cisco IOS Release 15.2(2) JA1.
- Cisco Prime Infrastructure 1.2.
- Mobility Services Engine software release 7.3 and context-aware software
Note Client and tag licenses are required to get contextual (such as location) information within the context-aware software. For more information, s ee the Release Notes for Cisco 3350 Mobility Servi ces Engine for Software Release 7.3.
- Cisco 3350, 3310, 3355 Mobility Services Engine, Virtual Appliance
- Cisco 2500 Series Wireless LAN Controllers
- Cisco 5500 Series Wireless LAN Controllers
- Cisco Flex 7500 Series Wireless LAN Controllers
- Cisco 8500 Series Wireless LAN Controllers
- Cisco Virtual Wireless LAN Controllers
- Cisco Wireless Controllers for high availability (HA controllers) for 5500 series, WiSM2, Flex 7500 series, and 8500 series controllers
- Cisco Wireless Services Module 2 (WiSM2) for Catalyst 6500 Series switches
- Cisco Wireless Controller on Cisco Services-Ready Engine (SRE) (WLCM2) running on ISM 300, SM 700, SM 710, SM 900, and SM 910
- Cisco Aironet 1550 (1552) Series outdoor 802.11n mesh access points; Cisco Aironet 1520 (1522, 1524) series outdoor mesh access points
- Cisco 1040, 1130, 1140, 1240, 1250, 1260, 2600, 3500, 3500p, 3600, Cisco 600 Series OfficeExtend Access Points, AP801, and AP802
The AP801 and AP802 are integrated access points on the Cisco 800 Series Integrated Services Routers (ISRs). For more information about the stock-keeping units (SKUs) for the access points and the ISRs, see the following data sheets:
– http://www.cisco.com/c/en/us/products/collateral/routers/800-series-routers/data_sheet_c78_461543.html
– 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
http://www.cisco.com/c/en/us/products/collateral/routers/800-series-routers/data_sheet_c78-519930.html
Note The AP802 is an integrated access point on the Next Generation Cisco 880 Series ISRs.
Note Before you use an AP802 series lightweight access point with controller software release 7.3.112.0, you must upgrade the software in the Next Generation Cisco 880 Series ISRs to Cisco IOS 151-4.M or later releases.
What’s New in This Release
This section provides a brief description of what is new in this release. For more information about instructions on how to configure controller features, see the Cisco Wireless LAN Controller Configuration Guide.
Hierarchical Mobility (New Mobility)
Hierarchical Mobility is referred to as New Mobility in the controller configuration. The release enables the controller to be compatible with Converged Access controllers with Wireless Control Module (WCM) like Cisco Catalyst 3850 switch and Cisco 5760 Wireless LAN Controller.
The Cisco 5500 Series Wireless LAN Controller, Cisco WiSM2, or the Cisco 5760 Wireless LAN Controller functions as a Mobility Controller (MC) with the Cisco Catalyst 3850 switch. The MC is part of a hierarchical architecture that consists of a Mobility Agent (MA), and a Mobility Oracle (MO).
A group of 3850 catalyst switch MAs can form a switch peer group (SPG). The internal MA of 5500, WISM2, and 5760 controllers form an independent SPG. The MC, MA, and MO can be in a single 5500, WISM2, or 5760 controller. Each MC forms a subdomain that can have multiple SPGs. Cisco 5500 Series Wireless LAN Controller, Cisco WiSM2, or the Cisco 5760 Wireless LAN Controller are MA/MC, by default. However, Cisco Catalyst 3850 switch can function both as MA/MC or MA only. The keepalives between MC and MO are not DTLS encrypted. Figure 1 shows the architecture of hierarchical mobility (also known as New Mobility). For more information, see Compatibility Matrix with Mobility Network Elements. By default, hierarchical mobility is disabled. For seamless mobility, the controller should either use hierarchical mobility or old mobility (flat mobility). Interoperability between the two types of mobility is not supported. High availability for Mobility Oracle is not supported in this release.
Note Hierarchical Mobility is supported only on Cisco 5500 Series Wireless LAN Controllers and Cisco WiSM2.
Figure 1 Architecture of Hierarchical Mobility
This section describes how to configure hierarchical mobility through either the GUI or the CLI:
Configuring Hierarchical Mobility (GUI)
Step 1 Choose CONTROLLER > Mobility Management > Mobility Configuration to enable and configure hierarchical mobility on the controller.
Step 2 Configure the following fields for hierarchical mobility:
Step 4 Choose CONTROLLER > Mobility Management > Switch Peer Group to add or remove members to the switch peer group.
This page lists all the switch peer groups and their details like bridge domain ID, multicast IP address, and status of the multicast mode. Click the name of the switch peer group to navigate to the Edit page and update the parameters, if required.
Step 5 Choose CONTROLLER > Mobility Management > Mobility Controller to view all the mobility controllers and their details like IP address, MAC address, client count, and link status.
Step 6 Choose CONTROLLER > Mobility Management > Mobility Clients to view all the mobility clients and their parameters.
Configuring Hierarchical Mobility (CLI)
Step 1 Enable or disable hierarchical mobility on the controller by entering this command:
config mobility new-architecture { enable | disable }
When you enable or disable hierarchical mobility, you must save the config and reboot the controller.
Step 2 Enable the Mobility Oracle (MO), or configure an external MO by entering this command:
config mobility oracle { enable | disable | ip ip_address }
ip_address is the IP address of the Mobility Oracle. The Mobility Oracle maintains the client database under one complete mobility domain. It consists of a station database, an interface to the Mobility Controller, and an NTP server. There can be only one MO in the entire mobility domain.
Step 3 Create, or delete switch peer groups (SPG) by entering this command:
config mobility switchPeerGroup { create | delete } peer-group-name
peer-group-name s the name of the switch peer group.
Step 4 Configure the MAC address of the member switch for compatibility between the flat and hierarchical (old and new) mobility by entering this command:
config mobility group member add ip_address {[ group-name ] | mac-address | [ public-ip-address ]}
ip_address is the IP address of the member.
group-name is the member switch group name, if it is different from the default group name.
mac-address is the MAC address of the member switch.
Step 5 Add, remove members, configure bridge domain ID, and multicast address of the switch peer group by entering this command:
config mobility switchPeerGroup { bridge-domain-id peer-group-name bridge_domain_id | member { add | delete } ip_address peer-group-name [ public_ip_address ] | multicast-address peer-group-name multicast_IP_address }
peer-group-name is the name of the SPG. bridge_domain_id is the bridge domain ID of the SPG.
ip_address is the IP address of switch peer group member.
public_ip_address is the public IP address of the switch peer group member.
Step 6 View the details of the mobility controllers according to the Mobility Oracle by entering this command:
Step 7 View the summary and details of the Mobility Oracle client database by entering this command:
show mobility oracle client { summary | detail }
Step 8 Verify the mobility statistics by entering this command:
Step 9 Verify the mobility configuration by entering this command:
Step 10 Save your changes by entering this command:
Step 11 Enable or disable debugging of mobility packets by entering this command:
debug mobility packet { enable | disable }
Step 12 Enable or disable debugging of the Mobility Oracle events and errors by entering this command:
debug mobility oracle {events | errors} { enable | disable }
Compatibility Matrix
This section consists of the following compatibility matrix:
- Compatibility Matrix with Mobility Network Elements
- Compatibility Matrix with Cisco 5760 Wireless LAN Controller and Cisco Catalyst 3850 Switch
- Compatibility Matrix without Cisco 5760 Wireless LAN Controller and Cisco Catalyst 3850 Switch
Compatibility Matrix with Mobility Network Elements
Table 3 lists the compatibility matrix with Mobility Network Elements: Mobility Controller (MC), Mobility Agent (MA), and Mobility Oracle (MO).
Yes1 (external) |
||||
Compatibility Matrix with Cisco 5760 Wireless LAN Controller and Cisco Catalyst 3850 Switch
For a seamless mobility between Cisco 5760 Wireless LAN Controller or Cisco Catalyst 3850 switch, and Cisco 5508 Wireless LAN and WiSM2 controllers, following are the prerequisites:
- Upgrade 5508 and WiSM2 to 7.3.112.0.
- Enable hierarchical mobility on 5508 and WiSM2. When you enable hierarchical mobility, the controller reboots.
Table 4 lists the software compatibility matrix with Cisco 5760 Wireless LAN Controller and Cisco Catalyst 3850 switch.
1.3.0.202 |
Compatibility Matrix without Cisco 5760 Wireless LAN Controller and Cisco Catalyst 3850 Switch
Table 5 lists the software compatibility matrix without Cisco 5760 Wireless LAN Controller and Cisco Catalyst 3850 switch.
Software Release Support for Access Points
Table 6 lists the controller software releases that support specific Cisco access points. The First Support column lists the earliest controller software release that supports the access point. For access points that are not supported in ongoing releases, the Last Support column lists the last release that supports the access point.
| Note The Cisco 3600 Access Point was introduced in 7.1.91.0. If your network deployment uses Cisco 3600 Access Points with release 7.1.91.0, we highly recommend that you upgrade to 7.2.103.0 or a later release. |
|||
-A and N: 4.1.190.1 or 5.2 or later3 |
|||
Upgrading to Controller Software Release 7.3.112.0
Guidelines and Limitations
- The 7.3.112.0 controller software release is not compatible with Cisco Prime Network Control System (NCS) 1.1.1.24. Cisco Prime Infrastructure 1.2 is required to support the controller features introduced in the 7.3.x controller software release. Cisco Prime Infrastructure 1.2 is the subsequent version of Cisco Prime Network Control System (NCS) 1.1.1.24.
- If you require a downgrade from one release to another, you might lose the configuration from your current release. The workaround is to reload the previous controller configuration files saved on the backup server or to reconfigure the controller.
- It is not possible to directly upgrade to the 7.3.112.0 release from a release that is older than 7.0.98.0.
- You can upgrade or downgrade the controller software only between certain releases. In some instances, you must first install an intermediate release prior to upgrading to software release 7.3.112.0. Table 7 shows the upgrade path that you must follow before downloading software release 7.3.112.0.
- When you downgrade the controller from 7.3.112.0 to a software release that does not support hierarchical mobility (new mobility) like 7.3.101.0, 7.2, 7.0, or earlier releases (all releases prior to 7.3.112.0), the controller automatically transits to flat mobility (old mobility). This is due to the difference in mobility architecture and noninteroperability between flat mobility (EOIP tunnels) and hierarchical mobility(CAPWAP tunnels).
- When you upgrade the controller to an intermediate software release, you must wait until all of the access points 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 access point.
- If you upgrade to the controller software release 7.3.112.0 from an earlier release, you must also upgrade to Cisco Prime Infrastructure 1.2 and MSE 7.3.
- You can upgrade to a new release of the controller software or downgrade to an older 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 controller is also automatically upgraded. When an access point is loading software, each of its LEDs blinks in succession.
- We recommend that you access the controller GUI using any of the following browsers:
– Microsoft Internet Explorer 6.0 SP1 (or a later release)
– Mozilla Firefox 2.0.0.11 (or a later release)
– Safari 5.1.5 (or a later release)
– Chrome 24.0.1312.52 m (or a later release)
– Android 4.0.4 (or a later release) built-in browser
- Cisco controllers support standard SNMP Management Information Base (MIB) files. MIBs can be downloaded from the Software Center on Cisco.com.
- The controller software is factory installed on your controller and automatically downloaded to the access points after a release upgrade and whenever an access point joins a controller. We recommend that you install the latest software version available for maximum operational benefit.
- We recommend that you install Wireless LAN Controller Field Upgrade Software (FUS) for Release 1.7.0.0-FUS first, 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_1_7_0_0.html. Upgrade the controller image after you upgrade the FUS, as the controller reboots during the upgrade.
- Ensure that you have a TFTP or FTP server available for the software upgrade. Follow these guidelines when setting up a TFTP or FTP server:
– Ensure that your TFTP server supports files that are larger than the size of the controller software release 7.3.112.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 7.3.112.0 controller software and your TFTP server does not support files of this size, the following error message appears: “TFTP failure while storing in flash.”
For large files, you can use a tftpd32 server. For more information, see the software informer website.
– If you are upgrading through the distribution system network port, the TFTP or FTP server can be on the same or a different subnet because the distribution system port is routable.
- When you plug a controller into an AC power source, the bootup script and power-on self-test run to initialize the system. During this time, you can press Esc to display the bootloader Boot Options Menu. The menu options for the 5500 differ from the menu options for the other controller platforms.
Bootloader Menu for 5500 Series Controllers:
Bootloader Menu for Other Controller Platforms:
Enter 1 to run the current software, enter 2 to run the previous software, enter 4 (on a 5500 series controller), or enter 5 (on another controller platform) to run the current software and set the controller 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 for your controller for more details on running the bootup script and power-on self-test.
- 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, be sure to 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 controller.
- Control which address(es) are sent in CAPWAP discovery responses when NAT is enabled on the Management Interface using the following command:
config network ap-discovery nat-ip-only { enable | disable }
– enable — Enables use of NAT IP only in a discovery response. This is the default. Use this command if all APs are outside of 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 of the NAT gateway; for example, Local Mode and OfficeExtend APs are on the same controller.
Note To avoid stranding 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 } tag. For the 7.2.103.0 and later releases, if you tag 802.1p packets, the tagging has impact only on 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 controller and the AP (main site and the branch). For more information about the FlexConnect AP upgrade feature, see the Cisco Wireless LAN Controller Configuration Guide.
Note Predownloading a 7.3.112.0 version on a Cisco Aironet 1240 access point is not supported when upgrading from a previous controller release. If predownloading is attempted to a Cisco Aironet 1240 access point, an AP disconnect will occur momentarily.
- Do not power down the controller or any access point during the upgrade process; otherwise, you might corrupt the software image. Upgrading a controller 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 controller must not be reset during this time.
- If you want to downgrade from the 7.3.112.0 release to a 6.0 or an older release, do either of the following:
– Delete all WLANs that are mapped to interface groups and create new ones.
– Ensure that all WLANs are mapped to interfaces rather than interface groups.
- After you perform these functions on the controller, you must reboot the controller 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 for a license
– Install vendor device certificate
– Install Web Authentication certificate
– Changes to management or virtual interface
- Ensure that you apply the calibration fix for AP1260 and AP3500 models (see the resolved caveat CSCty68030). This addresses a manufacturing calibration issue on the AP1260 and AP3500 models (VID V01). For more information, see https://supportforums.cisco.com/document/105346/calibration-fix-1260-3500-series-aps-csctu24972-cscty68030.
Upgrading to Controller Software Release 7.3.112.0 (GUI)
Step 1 Upload your controller configuration files to a server to back them up.
Note We highly recommend that you back up your controller’s configuration files prior to upgrading the controller software.
Step 2 Follow these steps to obtain the 7.3.112.0 controller 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 available:
– Integrated Controllers and Controller Modules
d. Depending on your controller platform, click one of the above options.
e. Click the controller model number or name. The Download Software page is displayed.
f. Click a controller software release. The software releases are labeled as follows to help you determine which release to download:
- 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.
g. Click a software release number.
h. Click the filename ( filename.aes).
j. Read Cisco’s End User Software License Agreement and then click Agree.
k. Save the file to your hard drive.
l. Repeat steps a. through k. to download the remaining file.
Step 3 Copy the controller software file ( filename.aes) to the default directory on your TFTP or FTP server.
Step 4 (Optional) Disable the controller 802.11a/n and 802.11b/g/n networks.
Note For busy networks, controllers on high utilization, or small controller platforms, we recommend that you disable the 802.11a/n and 802.11b/g/n networks as a precautionary measure.
Step 5 Disable any WLANs on the controller.
Step 6 Choose Commands > Download File to open the Download File to Controller page.
Step 7 From the File Type drop-down list, choose Code.
Step 8 From the Transfer Mode drop-down list, choose TFTP or FTP.
Step 9 In the IP Address text box, enter the IP address of the TFTP or FTP server.
Step 10 If you are using a TFTP server, the default values 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) that the TFTP server attempts to download the software in the Timeout text box.
Step 11 In the File Path text box, enter the directory path of the software.
Step 12 In the File Name text box, enter the name of the software file ( filename.aes).
Step 13 If you are using an FTP server, follow these steps:
a. In the Server Login Username text box, enter the username to log on to the FTP server.
b. In the Server Login Password text box, enter the password 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 14 Click Download to download the software to the controller. A message appears indicating the status of the download.
Step 15 After the download is complete, click Reboot.
Step 16 If prompted to save your changes, click Save and Reboot.
Step 17 Click OK to confirm your decision to reboot the controller.
Step 18 After the controller reboots, repeat Choose Commands > Download File to open the Download File to Controller page. to Click OK to confirm your decision to reboot the controller. to install the remaining file.
Step 20 For Cisco WiSM2 on the Catalyst switch, check the port channel and reenable the port channel if necessary.
Step 21 If you have disabled the 802.11a/n and 802.11b/g/n networks in (Optional) Disable the controller 802.11a/n and 802.11b/g/n networks., reenable them.
Step 22 To verify that the 7.3.112.0 controller software is installed on your controller, click Monitor on the controller GUI and look at the Software Version field under Controller Summary.
Special Notes for Licensed Data Payload Encryption on
Cisco Wireless LAN Controllers
Datagram Transport Layer Security (DTLS) is required for all Cisco 600 Series OfficeExtend Access Point deployments to encrypt data plane traffic between the APs and the controller. You can purchase Cisco Wireless LAN Controllers with either DTLS that is enabled (non-LDPE) or disabled (LDPE). If DTLS is disabled, you must install a DTLS license to enable DTLS encryption. The DTLS license is available for download on Cisco.com.
Important Note for Customers in Russia
If you plan to install a Cisco Wireless LAN Controller in Russia, you must get a Paper PAK, and not download the license from Cisco.com. The DTLS Paper PAK license is for customers who purchase a controller with DTLS that is disabled due to import restrictions but have authorization from local regulators to add DTLS support after the initial purchase. Consult your local government regulations to ensure that DTLS encryption is permitted.
Note Paper PAKs and electronic licenses available are outlined in the respective controller datasheets.
Downloading and Installing a DTLS License for an LDPE Controller
Step 1 Download the Cisco DTLS license.
a. Go to the Cisco Software Center at this URL:
https://tools.cisco.com/SWIFT/LicensingUI/Home
b. On the Product License Registration page, choose Get New > IPS, Crypto, Other Licenses.
c. Under Wireless, choose Cisco Wireless Controllers (2500/5500/7500/8500/WiSM2) DTLS License.
d. Complete the remaining steps 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. You can install the license either by using the controller web GUI interface or the CLI:
Management > Software Activation > Commands > Action : Install License
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 Controller
Step 1 Download the non-LDPE software release:
a. Go to the Cisco Software Center at this URL:
http://www.cisco.com/cisco/software/navigator.html?mdfid=282585015&i=rm
b. Choose the controller model from the right selection box.
c. Click Wireless LAN Controller Software.
d. From 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
g. Read Cisco’s End User Software License Agreement and then click Agree.
h. Save the file to your hard drive.
Step 2 Copy the controller software file ( filename.aes) to the default directory on your TFTP or FTP server.
Step 3 Upgrade the controller with this version by following the instructions from Copy the controller software file (filename.aes) to the default directory on your TFTP or FTP server. through To verify that the 7.3.112.0 controller software is installed on your controller, click Monitor on the controller GUI and look at the Software Version field under Controller Summary. detailed in the “Upgrading to Controller Software Release 7.3.112.0” section.
Interoperability With Other Clients in 7.3.112.0
This section describes the interoperability of the version of controller software with other client devices.
Table 8 describes the configuration used for testing the clients.
Open, WEP, PSK (WPA and WPA2), 802.1X (WPA-TKIP and WPA2-AES) (LEAP, PEAP, EAP-FAST, EAP-TLS) |
|
Connectivity, traffic, and roaming between two access points |
Table 9 lists the client types on which the tests were conducted. The clients included laptops, handheld devices, phones, and printers.
Features Not Supported on Controller Platforms
This section lists the features that are not supported in the following platforms:
- Features Not Supported on Cisco 2500 Series Controllers
- Features Not Supported on WiSM2 and Cisco 5500 Series Controllers
- Features Not Supported on Cisco Flex 7500 Controllers
- Features Not Supported on Cisco 8500 Controllers
- Features Not Supported on Cisco Wireless Controller on Cisco Services-Ready Engine
- Features Not Supported on Cisco Virtual Wireless LAN Controllers
- Features Not Supported on Mesh Networks
Features Not Supported on Cisco 2500 Series Controllers
- Wired guest access
- Cisco 2500 Series Controller cannot be configured as a guest anchor controller. However, it can be configured as a foreign controller to tunnel guest traffic to a guest anchor controller in a DMZ.
- Bandwidth contract
- Service port
- AppleTalk Bridging
- LAG
- Right to Use licensing
- Multicast-to-unicast
- High Availability
- PMIPv6
- Hierarchical Mobility
Note The features that are not supported on Cisco WiSM2 and Cisco 5500 Series Controllers are also not supported on Cisco 2500 Series Controllers.
Note Directly connected APs are supported only in Local mode.
Features Not Supported on WiSM2 and Cisco 5500 Series Controllers
- Spanning Tree Protocol (STP)
- Port mirroring
- Layer 2 access control list (ACL) support
- VPN termination (such as IPsec and L2TP)
- VPN passthrough option
Note You can replicate this functionality on a 5500 series controller by creating an open WLAN using an ACL.
Features Not Supported on Cisco Flex 7500 Controllers
Note For Cisco 7500 Series controllers, it is not necessary to configure an AP-manager interface. The management interface acts like an AP-manager interface by default, and the access points can join on this interface.
Note IPv6 client bridging and Router Advertisement Guard are supported.
Note An AP associated with the controller in local mode should be converted to FlexConnect mode or Monitor mode, either manually or by enabling the autoconvert feature. On the Flex 7500 controller CLI, enable the autoconvert feature by entering the config ap autoconvert enable command.
Features Not Supported on Cisco 8500 Controllers
- LAG
- Cisco 8500 Series Controller cannot be configured as a guest anchor controller. However, it can be configured as a foreign controller to tunnel guest traffic to a guest anchor controller in a DMZ.
- TrustSec SXP
- Local authentication (controller acting as authentication server)
- Internal DHCP server
- Wired guest access
- Data DTLS for locally switched clients
- Hierarchical Mobility
Features Not Supported on Cisco Wireless Controller on Cisco Services-Ready Engine
- Wired guest access
- Cisco Wireless Controller on Cisco Services-Ready Engine (SRE) cannot be configured as a guest anchor controller. However, it can be configured as a foreign controller to tunnel guest traffic to a guest anchor controller in a DMZ.
- Bandwidth contract
- Access points in direct connect mode
- Service port support
- AppleTalk Bridging
- LAG
- Hierarchical Mobility
Features Not Supported on Cisco Virtual Wireless LAN Controllers
- Data DTLS
- Cisco 600 Series OfficeExtend Access Points
- Wireless rate limiting (bandwidth contract)
- Internal DHCP server
- TrustSec SXP
- Access points in local mode
- Mobility/guest anchor
- Multicast-unicast mode
- IPv6
- PMIPv6
- WGB
- VideoStream
- High Availability
- Outdoor mesh access points
Note Outdoor APs such as AP1552 are supported in FlexConnect mode are supported if the APs are not used in a mesh deployment.
Features Not Supported on Mesh Networks
- Multicountry support
- Load-based 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
Caveats
The following sections lists Open Caveats and Resolved Caveats for Cisco controllers and lightweight access points for version 7.3.112.0. For your convenience in locating caveats in Cisco’s Bug Toolkit, the caveat titles listed in this section are drawn directly from the Bug Toolkit database. These caveat titles are not intended to be read as complete sentences because the title field length is limited. In the caveat titles, some truncation of wording or punctuation might be necessary to provide the most complete and concise description. The only modifications made to these titles are as follows:
- Commands are in boldface type.
- Product names and acronyms might be standardized.
- Spelling errors and typos might be corrected.
Note If you are a registered cisco.com user, view Bug Toolkit on cisco.com at the following website:
https://tools.cisco.com/bugsearch/
To become a registered cisco.com user, go to the following website:
http://tools.cisco.com/RPF/register/register.do
Open Caveats
Table 10 lists the open caveats in the 7.3.112.0 controller software release.
Resolved Caveats
Table 11 lists the caveats that are resolved in the 7.3.112.0 controller software release.
Installation Notes
This section contains important information to keep in mind when installing controllers and access points:
Warnings
Warning This warning means danger. You are in a situation that could cause bodily injury. Before you work on any equipment, be aware of the hazards involved with electrical circuitry and be familiar with standard practices for preventing accidents. Use the statement number provided at the end of each warning to locate its translation in the translated safety warnings that accompanied this device. Statement 1071
Warning Only trained and qualified personnel should be allowed to install, replace, or service this equipment. Statement 1030
Warning Do not locate the antenna near overhead power lines or other electric light or power circuits, or where it can come into contact with such circuits. When installing the antenna, take extreme care not to come into contact with such circuits, as they may cause serious injury or death. For proper installation and grounding of the antenna, please refer to national and local codes (e.g. U.S.: NFPA 70, National Electrical Code, Article 810, Canada: Canadian Electrical Code, Section 54). Statement 280
Warning This product relies on the building’s installation for short-circuit (overcurrent) protection. Ensure that a fuse or circuit breaker no larger than 120 VAC, 15A U.S. (240 VAC, 10A international) is used on the phase conductors (all current-carrying conductors). Statement 13
Warning This equipment must be grounded. Never defeat the ground conductor or operate the equipment in the absence of a suitably installed ground connector. Contact the appropriate electrical inspection authority or an electrician if you are uncertain that suitable grounding is available. Statement 1024
Warning Read the installation instructions before you connect the system to its power source. Statement 10
Warning Do not work on the system or connect or disconnect any cables (Ethernet, cable, or power) during periods of lightning activity. The possibility of serious physical injury exists if lightning should strike and travel through those cables. In addition, the equipment could be damaged by the higher levels of static electricity present in the atmosphere. Statement 276
Warning Do not operate the unit near unshielded blasting caps or in an explosive environment unless the device has been modified to be especially qualified for such use. Statement 364
Warning In order to comply with radio frequency (RF) exposure limits, the antennas for this product should be positioned no less than 6.56 ft. (2 m) from your body or nearby persons. Statement 339
Warning This unit is intended for installation in restricted access areas. A restricted access area can be accessed only through the use of a special tool, lock and key, or other means of security. Statement 1017
Safety Information
Follow the guidelines in this section to ensure proper operation and safe use of the controllers and access points.
FCC Safety Compliance Statement
FCC Compliance with its action in ET Docket 96-8, has adopted a safety standard for human exposure to RF electromagnetic energy emitted by FCC-certified equipment. When used with approved Cisco Aironet antennas, Cisco Aironet products meet the uncontrolled environmental limits found in OET-65 and ANSI C95.1, 1991. Proper operation of this radio device according to the instructions in this publication results in user exposure substantially below the FCC recommended limits.
Safety Precautions
For your safety, and to help you achieve a good installation, read and follow these safety precautions. They might save your life!
1. If you are installing an antenna for the first time, for your own safety as well as others, seek professional assistance. Your Cisco sales representative can explain which mounting method to use for the size and type of antenna you are about to install.
2. Select your installation site with safety as well as performance in mind. Electric power lines and phone lines look alike. For your safety, assume that any overhead line can kill you.
3. Call your electric power company. Tell them your plans and ask them to come look at your proposed installation. This is a small inconvenience considering your life is at stake.
4. Plan your installation carefully and completely before you begin. Successfully raising a mast or tower is largely a matter of coordination. Each person should be assigned to a specific task and should know what to do and when to do it. One person should be in charge of the operation to issue instructions and watch for signs of trouble.
5. When installing an antenna, remember:
b. Do not work on a wet or windy day.
c. Do dress properly—shoes with rubber soles and heels, rubber gloves, long-sleeved shirt or jacket.
6. If the assembly starts to drop, get away from it and let it fall. Remember that the antenna, mast, cable, and metal guy wires are all excellent conductors of electrical current. Even the slightest touch of any of these parts to a power line completes an electrical path through the antenna and the installer: you!
7. If any part of an antenna system should come in contact with a power line, do not touch it or try to remove it yourself. Call your local power company. They will remove it safely.
8. If an accident should occur with the power lines, call for qualified emergency help immediately.
Installation Instructions
See the appropriate quick start guide or hardware installation guide for instructions on installing controllers and access points.
Note To meet regulatory restrictions, all external antenna configurations must be installed by experts.
Personnel installing the controllers and access points must understand wireless techniques and grounding methods. Access points with internal antennas can be installed by an experienced IT professional.
The controller must be installed by a network administrator or qualified IT professional, and the proper country code must be selected. Following installation, access to the controller should be password protected by the installer to maintain compliance with regulatory requirements and ensure proper unit functionality.
Service and Support
Information About Caveats
If you need information about a specific caveat that does not appear in these release notes, you can use the Cisco Bug Toolkit to find caveats of any severity. Click this URL to browse to the Bug Toolkit:
https://tools.cisco.com/bugsearch/
(If you request a defect that cannot be displayed, the defect number might not exist, the defect might not yet have a customer-visible description, or the defect might be marked Cisco Confidential.)
Troubleshooting
For the most up-to-date, detailed troubleshooting information, see the Cisco TAC website at this URL:
http://www.cisco.com/c/en/us/support/index.html
Click Product Support > Wireless. Then choose your product and Troubleshooting to find information on the problem you are experiencing.
Related Documentation
For additional information about the Cisco controllers and lightweight access points, see these documents:
- The quick start guide or installation guide for your particular controller or access point
- Cisco Wireless LAN Controller Configuration Guides
- Cisco Wireless LAN Controller Command References
- Cisco Wireless LAN Controller System Message Guide
You can access these documents at this URL: http://www.cisco.com/c/en/us/products/wireless/index.html.
Obtaining Documentation and Submitting a Service Request
For information on obtaining documentation, submitting a service request, and gathering additional information, see the monthly What’s New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation:
http://www.cisco.com/c/en/us/td/docs/general/whatsnew/whatsnew.html
Subscribe to the What’s New in Cisco Product Documentation as an RSS feed and set content to be delivered directly to your desktop using a reader application. The RSS feeds are a free service. Cisco currently supports RSS Version 2.0.
Feedback