Release Notes for Cisco Wireless LAN Controllers and Lightweight Access Points for Release 7.3.101.0
Available Languages
Table of Contents
Release Notes for Cisco Wireless LAN Controllers and Lightweight Access Points for Release 7.3.101.0
Cisco Unified Wireless Network Solution Components
Controller Platforms Not Supported
Software Release Support for Access Points
Upgrading to Controller Software Release 7.3.101.0
Upgrading to Controller Software Release 7.3.101.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.101.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.101.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
- Software Release Support for Access Points
- Upgrading to Controller Software Release 7.3.101.0
- Special Notes for Licensed Data Payload Encryption on Cisco Wireless LAN Controllers
- Interoperability With Other Clients in 7.3.101.0
- Features Not Supported on Controller Platforms
- Caveats
- Installation Notes
- Service and Support
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.101.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 new features in controllers introduced in the 7.3.101.0 controller software release. 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)JA
- Cisco Prime Infrastructure 1.2
- Mobility services engine software release 7.3.101.0 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, see the Release Notes for Cisco 3350 Mobility Services 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.101.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 these features, see the Cisco Wireless LAN Controller Configuration Guide.
- The virtual wireless LAN controller is software that can run on hardware that is compliant with an industry standard virtualization infrastructure. Virtual wireless LAN controllers provide flexibility for users to select the hardware based on their requirement.
We recommend that you have the following hardware to host a virtual controller:
– Cisco UCS R210-2121605W Rack Mount Server (2 RU)
– ISR G2 Services Ready Engine (SRE) using UCS Express
For more information, see http://www.cisco.com/c/en/us/support/wireless/virtual-wireless-controller/tsd-products-support-series-home.html
The virtual wireless LAN controller does not have a Manufacturer Installed Certificate (MIC). Therefore, APs cannot validate the virtual controller unless they are using a 7.3-based image such as the follows:
– 12.4(25e)JAL for 1130/1240 series APs
– 15.2(2)JA for 1250/1260/1140/2600/3500/3600 series APs
Follow either of the following two ways to resolve this:
– Install the abovementioned IOS images manually on the AP, join the APs to a hardware based controller using the 7.3 software release to download the image, and disable hash validation by entering the config certificate ssc hash validation disable command.
– Configure the virtual controller as a mobility member and include the hash value so that the APs can validate the virtual controller.
Note It is not possible to directly join an AP that has a 7.2 or older image of the controller with the virtual wireless LAN controller. You must first join the AP with a different controller model, say a 5500 or Flex 7500 series controller that is using the 7.3 software or later releases, and then join the AP with the virtual wireless LAN controller.
- Cisco 8500 Series Controllers are introduced with support for local mode, FlexConnect, and mesh modes. The Cisco 8500 Series Controllers support 6000 APs, 64,000 clients, 2000 FlexConnect groups, 6000 AP groups, 100 APs per FlexConnect group, and up to 4095 VLANs. A Cisco 8500 Series Controller can support up to 24,000 rogue APs and 32,000 rogue clients. For more information, see http://www.cisco.com/c/en/us/support/wireless/8500-series-wireless-controllers/tsd-products-support-series-home.html
- Increased scale for Cisco Flex 7500 Series Controllers to support 6000 APs, 64000 clients, 2000 FlexConnect groups, 6000 AP groups, 100 APs per FlexConnect group, and up to 4096 VLANs.
- The number of rogue APs and rogue clients that can be detected per platform is increased (see Table 1-1 ).
- This release extends the number of radio frequency identifiers (RFIDs) to be supported (see Table 1-2 ).
- The Cisco Aironet 2600 Series Access Points are supported. For more information, see http://www.cisco.com/c/en/us/products/wireless/aironet-2600-series/index.html
- High availability (HA) in controllers allows you to reduce the downtime of the wireless networks, due to the failover of controllers. In this release, a 1:1 (Active:Standby-Hot) AP stateful switchover (AP SSO) is supported. In an HA architecture, one controller is configured as the primary controller and another controller as the secondary controller.
After you enable HA, the primary and secondary controllers are rebooted. During the boot process, the primary controller role is negotiated as active and the secondary controller as standby-hot. After a switchover, the secondary controller becomes the active controller and the primary controller becomes the standby-hot controller. After subsequent switchovers, the roles are interchanged between the primary and the secondary controllers. The reason for switchovers could be due to manual trigger or a controller or network failure.
Note Internal DHCP is not supported.
– Split tunneling allows the traffic sent by a client to be classified based on the packet contents. The matching packets are locally switched and the rest of the traffic is centrally switched. The traffic that is sent by the client that matches the IP address of the device present in the local site can be classified as locally switched traffic and the rest of the traffic as centrally switched.
This feature is supported on the AP1040, AP1140, AP1260, AP2600, AP3500, and AP3600 access points.
– Support to configure Network Address Translation (NAT) and Port Address Translation (PAT) on FlexConnect locally switched WLANs is added. You must enable Central DHCP Processing to enable NAT and PAT.
This feature is supported on the AP1040, AP1140, AP1260, AP2600, AP3500, and AP3600 access points.
– Support for the Point to Point Protocol (PPP) and the Point to Point Protocol over Ethernet (PPPoE) is added for APs in FlexConnect mode. You must configure PPPoE submode when the AP is in FlexConnect mode.
This feature is supported on the AP1040, AP1140, AP1260, AP2600, AP3500, and AP3600 access points.
– This release extends WGB/uWGB support to FlexConnect APs for locally switched WLANs.
WGB is supported on all FlexConnect APs: AP1040, AP1130, AP1140, AP1240, AP1250, AP1260, AP1520, AP2600, AP3500, AP3600, AP801, and AP802.
– This release extends support for 802.11u in FlexConnect mode.
– 802.11r Fast Transition is now supported on FlexConnect APs in central and locally switched WLANs.
– VLAN-based local and central switching is supported. When a AAA server returns a VLAN configured for a client, the VLAN is configured on the local IEEE 802.1Q link, the AP bridges the traffic locally. If the VLAN is not configured on the AP uplink, the AP tunnels the traffic back to the controller. The controller bridges the traffic into the corresponding VLAN from where the traffic is transported toward the next routing instance for further processing.
- Table 1-3 lists the 802.11r L2 and L3 roaming rates that are supported in this release on the 5500 and WiSM2 controllers:
- This release extends support for HotSpot 2.0 specifications, where APs in mesh mode and APs in FlexConnect mode in locally switched WLANs are also supported.
- IPv6 address support is added for rogue client and wIPS alarms. Three new wIPS signatures are supported.
- This release extends support for IPv6 on Cisco Wireless Controller on Cisco Services-Ready Engine (SRE).
- Right to Use (RTU) licensing allows you to enable a desired AP license count on the controller after you accept the End User License Agreement (EULA). This process enables you to add AP counts on a controller without interacting with external tools.
RTU licensing is supported only on Cisco Flex 7500 Series and Cisco 8500 Series Wireless LAN Controllers.
– TSpec-based video calls including 802.11n clients.
– Facetime and Cius video call applications that use SIP unencrypted signaling.
- You can configure WLANs to do 802.1X authentication of clients if MAC authentication with static WEP fails. Clients are deauthenticated if they fail the 802.1X authentication. If MAC authentication is successful and clients send a request to start 802.1X authentication, clients have to pass the 802.1X authentication to be allowed to send data traffic. Otherwise, clients are deauthenticated. If clients choose not to have 802.1X authentication, they can be declared as authenticated if they pass MAC authentication.
- Proxy Mobile IPv6 is a network-based mobility management protocol that supports a mobile node by acting as the proxy for the mobile node in any IP mobility-related signaling. The mobility entities in the network track the movements of the mobile node and initiate the mobility signaling and set up the required routing state.
The main functional entities are the Local Mobility Anchor (LMA) and Mobile Access Gateway (MAG). The LMA maintains the reachability state of the mobile node and is the topological anchor point for the IP address of the mobile node. The MAG performs the mobility management on behalf of a mobile node. The MAG resides on the access link where the mobile node is anchored. The controller implements the MAG functionality.
Note PMIPv6 MAG functionality is supported only on Cisco 5500 Series Controllers, Cisco 8500 Series Controllers, and Cisco WiSM2.
Note In this release, the Cisco 8500 Series Controllers can support a maximum of 40,000 PMIPv6 clients out of the 64,000 clients that are supported.
config ipv6 { enable | disable }
- You can upload the output of the show run-config command onto an FTP server by entering this command:
transfer upload datatype run-config
- Support for detection and forwarding of the first HTTP packet with a user-agent attribute from a client per session to profile the client, where the controller acts as a collector, is added in this release.
- To resolve issues such as voice and security on wireless networks, you might need to dump packets from the AP for analysis while the AP continues to operate normally. The packets can be dumped onto an FTP server. This process of dumping packets for analysis is called Packet Capture. Use the controller to start or stop packet capture for clients. You can choose the type of packets that need to be captured using the controller.
- In this release, RF profiles incorporate new configurations, which are specially targeted at high-density and stadium environments. These new configurations are as follows:
– Stadium vision configurations
– Out-of-the-box AP configurations
– Load balancing configurations
– Coverage hole mitigation configurations
- VLAN tagging on Ethernet interfaces is supported. You can configure VLAN tagging on the Ethernet interface either directly from the AP console or through the controller and Cisco Prime Infrastructure. You must save the configuration in flash and all CAPWAP packets use the VLAN tag as configured with all the locally switched traffic, which is not mapped to a VLAN. When enabled, the CAPWAP packets from the AP are forwarded through the trunk VLAN. If it fails, the AP falls back to the untagged mode.
- DHCP Option 82 enhancement—You can also specify the name and the SSID of the access point to the DHCP Option 82 payload.
- RADIUS CallStationID enhancement—You can also specify the name and the SSID of the access point to determine the RADIUS CallStationID.
- The bandwidth contract feature is enhanced so that rate limits can be defined on both upstream and downstream traffic. Rate limits can be defined per SSID and/or specified as a maximum rate limit for all clients. These rate limits can be individually configured. This feature is supported on AP1140, AP1040, AP3500, AP3600, AP1250, and AP1260. In centrally switched WLANs, the downstream traffic is rate limited by the controller and the upstream is rate limited by the APs. In local switched WLANs, both upstream and downstream are traffic are rate limited by the APs.
- RADIUS source interface is aware of the AP group, which allows sourcing the RADIUS packets from the interface assigned to the AP group. To allow partitioning of a network into different subnets, AP groups can be used to provide site-specific VLANs, where each VLAN has its own IP subnet that can be identified. For all client associations to the site-specific VLAN on the AP, all RADIUS interactions must be sourced from the IP address of that site-specific VLAN, which maps an AP group to a site-specific VLAN and maps the VLAN to a unique IP subnet.
- Increased RADIUS servers per WLAN from 3 to 6.
- Added SNMP support to swap controller images (primary and standby).
- AP searches and renaming of APs are based on serial numbers.
- Usernames are displayed in client summaries.
- This release is compliant with the Federal Information Processing Standard (FIPS) 140-2 standard for wireless controllers and APs.
- This release introduces two new AP1552 models:
- AP802H, a newer version of AP802 is supported. For more information, see http://www.cisco.com/c/en/us/products/collateral/routers/800-series-routers/qa_c67-678460.html
- Support is added to the following features on the AP1552 models to match the ones with the indoor APs:
– Local, FlexConnect, Monitor, Rogue Detector, and Sniffer modes
– Datagram Transport Layer Security (DTLS)
Note Support is added for DTLS data plane encryption for the AP1552s in Local and FlexConnect mode.
- Mesh outdoor access points support local mode. In this mode, the AP can handle clients on its assigned channel or while monitoring all channels on the band over a 180-second period. During this time, the AP listens on each channel for 50 milliseconds for rogue client beacons, noise floor measurements, interference, and IDS events. The AP also scans for CleanAir interference on the channel.
- The operating frequency in the 5-GHz band for the 1550 series access points has been increased from 5.850 GHz to 5.875 GHz.
- A new country domain has been added for India. The –D domain supports the 20-MHz channels, which are 169 (5.845 GHz) and 173 (5.865 GHz), and the 40-MHz channel pair, which is 169/173 (5.855 GHz).
- You can activate CleanAir Advisor when you enable CleanAir on a backhaul radio. CleanAir Advisor generates Air Quality Index (AQI) and Interfere Detection Reports (IDRs), but the reports are displayed only in the controller. No action is taken through Event Driven RRM (ED-RRM).
- You can order AP1552E/EU with an Ethernet Passive Optical Network (EPON) SFP as an add-on. The EPON SFP provides Gigabit data rates. EPON SFP is not an orderable feature on the AP1552. You must order it separately and install it.
Software Release Support for Access Points
Table 1-4 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 later1 |
|||
Upgrading to Controller Software Release 7.3.101.0
Guidelines and Limitations
- The 7.3.101.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 new features in controllers introduced in the 7.3.101.0 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.101.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.101.0. Table 1-5 shows the upgrade path that you must follow before downloading software release 7.3.101.0.
- 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.101.0 from an earlier release, you must also upgrade to Cisco Prime Infrastructure 1.2 and MSE 7.3.101.0.
- 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 Microsoft Internet Explorer 6.0 SP1 (or a later release) or Mozilla Firefox 2.0.0.11 (or a later release).
- 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 for Release 1.7.0.0-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_1_7_0_0.html
- 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.101.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.101.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.”
– 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.101.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.101.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.101.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.101.0 controller software:
a. Click this URL to go to the Software Center:
https://software.cisco.com/download/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.101.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.101.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.101.0” section.
Interoperability With Other Clients in 7.3.101.0
This section describes the interoperability of the version of controller software with other client devices.
Table 1-6 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 1-7 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
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
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
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.101.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:
https://tools.cisco.com/IDREG/guestRegistration.do?locale=en_US
Open Caveats
Table 1-8 lists the open caveats in the 7.3.101.0 controller software release.
Resolved Caveats
Table 1-9 lists the caveats that are resolved in the 7.3.101.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 Guide
- Cisco Wireless LAN Controller Command Reference
- Cisco Wireless LAN Controller System Message Guide
Obtaining Documentation and Submitting a Service Request
For information on obtaining documentation, using the Cisco Bug Search Tool (BST), submitting a service request, and gathering additional information, see What’s New in Cisco Product Documentation at: http://www.cisco.com/c/en/us/td/docs/general/whatsnew/whatsnew.html
Subscribe to What’s New in Cisco Product Documentation, which lists all new and revised Cisco technical documentation, as an RSS feed and deliver content directly to your desktop using a reader application. The RSS feeds are a free service.
Feedback