Home | Skip to Content | Skip to Search | Skip to Navigation | Skip to Footer |
Worldwide [change] |Register |About Cisco
Guest

Hierarchical Navigation

Cisco 4400 Series Wireless LAN Controllers

Release Notes for Cisco Wireless LAN Controllers and Lightweight Access Points for Release 4.1.181.0

Downloads

Table Of Contents

Release Notes for Cisco Wireless LAN Controllers and Lightweight Access Points for Release 4.1.181.0

Contents

Cisco Unified Wireless Network Solution Components

Special Notice for Mesh Networks

Controller Requirements

Software Release Information

Finding the Software Release

Upgrading to a New Software Release

Special Rules for Upgrading to Controller Software Release 4.1.181.0

New and Changed Information

RRM Features and Changed Information

New DCA CLI Commands

RRM Changes

Mesh Features and Changed Information

Mesh Multicast for Video

AP1510 Interoperability with Cisco 3200 MAR in Public-Safety Networks

Transmit Power Levels for 1500 Series Access Points

LED Verification on 1500 Series Access Points

Mesh Changes

Installation Notes

Warnings

Safety Information

FCC Safety Compliance Statement

Safety Precautions

Installation Instructions

Important Notes

802.11n

Disabling Radio Bands

MAC Filtering for WGB Wired Clients

CKIP Not Supported with Dynamic WEP

UNII-2 Channels Disabled on New 1000 Series Access Points for United States, Canada, and Philippines

FCC DFS Support on AP1130s

Access Point Radios Are Not Enabled After Upgrading to 4.1.181.0

Setting the Retransmit Timeout Value for TACACS+ Servers

Configuring an Access Point's PreStandard Power Setting

Using CCKM with CB21AG Client Adapters

DHCP Option 60 and 1500 Series Access Points

AP1000 and Radar Detection

Controller Functions that Require a Reboot

Multicast Queue Depth

2106 Controller LEDs

Resetting the Configuration on 2006 Controllers

Rate-Limiting on the Controller

Pings Supported on the Controller

Pinging from a Network Device to a Controller Dynamic Interface

IPSec Not Supported

4400 Series Controllers Do Not Forward Subnet Broadcasts through Guest Tunnel

Re-enable Broadcast after Upgrading to Release 4.0.206.0

Service Modules Supported in the Catalyst 6500 Series Switch

Connecting 1100 and 1300 Series Access Points

Controllers Must Run Release 3.2.116.21 or Later to Support -P Regulatory Domain

Preventing Clients from Accessing the Management Network on a Controller

Voice Wireless LAN Configuration

Conducting a Radio Site Survey for Mesh Deployments

Operating Mesh Networks through Switches and Routers

Cisco 7920 Wireless IP Phone Support

Changing the IOS LWAPP Access Point Password

Exclusion List (Blacklist) Client Feature

RADIUS Servers and the Management VLAN

Cisco 1000 Series Access Points and WMM

Cisco Aironet 1030 Remote Edge Lightweight Access Points and WPA2-PSK

Lightweight Access Point Connection Limitations

RADIUS Servers

Management Usernames and Local Netuser Names

802.1x and Microsoft Wireless Configuration Manager

Using the Backup Image

Home Page Retains Web Authentication Login with IE 5.x

Rogue Location Discovery Protocol (RLDP)

Ad-Hoc Rogue Containment

Changing the Default Values of SNMP Community Strings

Changing the Default Values for SNMP v3 Users

Features Not Supported on 2000 and 2100 Series Controllers

Some Clients See Only 64 Access Point MAC Addresses (BSSIDs) at a Time

2006 Image Not Supported for 3504 Controllers

Running a 3504 Image on a 2000 Series Controller

Upgrading External Web Authentication

Caveats

Open Caveats

Resolved Caveats

Closed Caveats

If You Need More Information

Troubleshooting

Documentation Updates

Omissions

Related Documentation

Obtaining Documentation, Support, and Security Guidelines


Release Notes for Cisco Wireless LAN Controllers and Lightweight Access Points for Release 4.1.181.0

July 23, 2007

These release notes describe open and resolved caveats for software release 4.1.181.0 for Cisco 2000, 2100, and 4400 Series Wireless LAN Controllers; Cisco Wireless Services Modules (WiSM); Cisco Wireless LAN Controller Network Modules; Catalyst 3750G Integrated Wireless LAN Controller Switches; Cisco 3201 Wireless Mobile Interface Cards (WMICs); and Cisco Aironet 1000, 1100, 1130, 1200, 1240, 1300, and 1500 (1505 and 1510) Series Lightweight Access Points, which comprise part of the Cisco Unified Wireless Network (UWN) Solution.

Note Unless otherwise noted, all of the Cisco wireless LAN controllers are hereafter referred to as controllers, and all of the Cisco lightweight access points are hereafter referred to as access points.

Contents

These release notes contain the following sections.

•Cisco Unified Wireless Network Solution Components

•Controller Requirements

•Software Release Information

•New and Changed Information

•Installation Notes

•Important Notes

•Caveats

•Troubleshooting

•Documentation Updates

•Related Documentation

•Obtaining Documentation, Support, and Security Guidelines

Cisco Unified Wireless Network Solution Components

The following components are part of the Cisco UWN Solution and are compatible in this release:

•Software release 4.1.181.0 for all Cisco controllers and lightweight access points

•Cisco autonomous to lightweight mode upgrade tool release 2.01

•Cisco Wireless Control System (WCS) software release 4.1.91.0

•Cisco Wireless Control System (WCS) Navigator 1.0.91.0

•Location appliance software release 3.0.42.0

•Cisco 2700 Series Location Appliances

•Cisco 2000 Series Wireless LAN Controllers

•Cisco 2100 Series Wireless LAN Controllers

•Cisco 4400 Series Wireless LAN Controllers

•Cisco Wireless Services Module (WiSM) for Cisco Catalyst 6500 Series Switches

•Cisco Wireless LAN Controller Network Module for Cisco Integrated Services Routers

•Catalyst 3750G Wireless LAN Controller Switches

•Cisco 3201 Wireless Mobile Interface Card (WMIC)

•Cisco Aironet 1000, 1100, 1130, 1200, 1240, 1300, and 1500 (1505 and 1510) Series Lightweight Access Points

Special Notice for Mesh Networks

Note Controller software release 4.1.181.0 does not support the new Cisco Aironet 1520 Series Mesh Access Point. If you intend to use this new access point, you must run controller software release 4.1.19x.y, which supports only mesh access points. If your network contains 1520 mesh access points and Cisco non-mesh access points (such as 1240 series access points), you need to manage your 1520 mesh access points with one controller and your non-mesh access points with a second controller. If you have 1505 and/or 1510 mesh access points, you should connect them to the same controller as the 1520 mesh access points.

Note Cisco WCS software release 4.1.91.0 manages controllers running software release 4.1.181.0 or 4.1.19x.y. You do not need a separate instance of WCS to manage each controller.

Controller Requirements

The controller graphical user interface (GUI) requires the following operating system and web browser:

•Windows XP SP1 or higher or Windows 2000 SP4 or higher

•Internet Explorer 6.0 SP1 or higher

Note Internet Explorer 6.0 SP1 or higher is the only browser supported for accessing the controller GUI and for using web authentication.

Software Release Information

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. As new releases become available for the controllers and their access points, consider upgrading.

Note The Cisco WiSM requires software release SWISMK9-32 or later. The Supervisor 720 12.2(18)SXF2 supports the Cisco WiSM software release 3.2.78.4 or later, and the Supervisor 720 12.2(18)SXF5 (Cisco IOS Software Modularity) supports the Cisco WiSM software release 4.0.155.5 (with Cisco IOS Software Modularity).

Note The Cisco WiSM is only supported on Cisco 7609 and 7613 Series Routers running Cisco IOS Release 12.2(18)SXF9 or later.

Note The Cisco Wireless LAN Controller Network Module-Enhanced (WLCM-E) is supported on Cisco 28/37/38xx Series Integrated Services Routers running Cisco IOS Release 12.4(11)T2 or later.

Note To use the controller in the Catalyst 3750G Wireless LAN Controller Switch, the switch must be running Cisco IOS Release 12.2.25.FZ or 12.2(25)SEE.

Finding the Software Release

To find the software release running on your controller, look on the Monitor > Summary page of the controller GUI or enter show sysinfo on the controller command line interface (CLI).

Upgrading to a New Software Release

When you upgrade the controller's software, the software on the controller's associated access points is also automatically upgraded. When an access point is loading software, each of its LEDs blinks in succession.

Caution Do not power down the controller or any access point during this 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 in software release 4.0.206.0 and later, the upgrade time should be significantly reduced. The access points must remain powered, and the controller must not be reset during this time.

Special Rules for Upgrading to Controller Software Release 4.1.181.0

Caution Before upgrading your controller to software release 4.1.181.0, you must comply with the following rules.

•Controller software release 4.1.181.0 is greater than 32 MB; therefore, you must make sure that your TFTP server supports files that are larger than 32 MB. Some TFTP servers that support files of this size are tftpd32 and the TFTP server within the WCS. If you attempt to download the 4.1.181.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 your controller is running software release 3.2.195.10 (or a later 3.2 release) or 4.0.206.0 (or a later 4.0 release), you can upgrade your controller directly to software release 4.1.181.0. If your controller is running an earlier 3.2 or 4.0 release, you must upgrade your controller to an intermediate release prior to upgrading to 4.1.181.0. Table 1 shows the upgrade path that you must follow before downloading software release 4.1.181.0.

Table 1 Upgrade Path to Controller Software Release 4.1.181.0

Current Software Release
Upgrade Path to 4.1.181.0 Software

3.2.78.0

Upgrade to 4.0.206.0 (or a later 4.0 release) before upgrading to 4.1.181.0.

3.2.116.21

3.2.150.10

3.2.171.6

3.2.193.5

If your controller is configured with the new J3 country code, upgrade to 3.2.195.10 (or a later 3.2 release). If your controller is not configured for the new J3 country code, you can upgrade to 3.2.195.10 (or a later 3.2 release) or to 4.0.206.0 (or a later 4.0 release).

3.2.195.10 or later 3.2 release

You can upgrade directly to 4.1.181.0.

4.0.155.5

Upgrade to 4.0.206.0 (or a later 4.0 release) before upgrading to 4.1.181.0.

4.0.179.11

4.0.206.0 or later 4.0 release

You can upgrade directly to 4.1.181.0.

4.1.171.0

You can upgrade directly to 4.1.181.0.


Note When you upgrade the controller to an intermediate software release, wait until all of the access points joined to the controller are upgraded to the intermediate release before you install the 4.1.181.0 software. In large networks, it can take some time to download the software on each access point.

•Cisco recommends that you also install the Cisco Unified Wireless Network Controller Boot Software 4.1.181.0 ER.aes file on the 2106 controller. This file resolves bootloader defects and is necessary to ensure proper operation of the controller. The ER.aes file is required for only the 2106 controller.

Note The ER.aes files are independent from the controller software files. You can run any controller software file with any ER.aes file. However, installing the latest boot software file (4.1.181.0 ER.aes) ensures that the bootloader modifications in all of the previous and current boot software ER.aes files are installed.

Caution If you require a downgrade from one release to another, you may 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.

Follow these steps to upgrade the controller software using the controller GUI.

Step 1 Upload your controller configuration files to a server to back them up.

Note Cisco highly recommends that you back up your controller's configuration files prior to upgrading the controller software. Otherwise, you must manually reconfigure the controller.

Step 2 Disable the controller 802.11a and 802.11b/g networks.

Step 3 Disable any WLANs on the controller.

Step 4 Follow these steps to obtain the 4.1.181.0 controller software and the Cisco Unified Wireless Network Controller Boot Software 4.1.181.0 ER.aes file from the Software Center on Cisco.com:

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

http://www.cisco.com/public/sw-center/sw-wireless.shtml

b. Click Wireless Software.

c. Click Wireless LAN Controllers.

d. Click Standalone Controllers, Wireless Integrated Routers, or Wireless Integrated Switches.

e. Click the name of a controller.

f. Click Wireless LAN Controller Software.

g. Click a controller software release.

h. Click the filename (filename.aes).

i. Click Download.

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. to k. to download the remaining file (either the 4.1.181.0 controller software or the Cisco Unified Wireless Network Controller Boot Software 4.1.181.0 ER.aes file).

Step 5 Copy the controller software file (filename.aes) and the Cisco Unified Wireless Network Controller Boot Software 4.1.181.0 ER.aes file to the default directory on your TFTP server.

Step 6 Click Commands > Download File to open the Download File to Controller page.

Step 7 From the File Type drop-down box, choose Code.

Step 8 In the IP Address field, enter the IP address of the TFTP server.

Step 9 The default values of 10 retries and 6 seconds for the Maximum Retries and Timeout fields should work fine 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 field and the amount of time (in seconds) that the TFTP server attempts to download the software in the Timeout field.

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

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

Step 12 Click Download to download the software to the controller. A message appears indicating the status of the download.

Step 13 Repeat Step 6 to Step 12 to install the remaining file (either the 4.1.181.0 controller software or the Cisco Unified Wireless Network Controller Boot Software 4.1.181.0 ER.aes file).

Step 14 After the download is complete, click Reboot.

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

Step 16 Click OK to confirm your decision to reboot the controller.

Step 17 After the controller reboots, re-enable the WLANs.

Step 18 Re-enable your 802.11a and 802.11b/g networks.

Step 19 If desired, reload your latest configuration file to the controller.

Step 20 To verify that the 4.1.181.0 controller software is installed on your controller, click Monitor on the controller GUI and look at the Software Version field under Controller Summary.

Note You cannot verify the boot software version on the 2106 controller. The Bootloader Version field remains at 4.0.190.0 for the 2106 controller, so you cannot tell which ER.aes file is installed.

New and Changed Information

The following new features and changed information are included in controller software release 4.1.181.0.

RRM Features and Changed Information

These radio resource management (RRM) features have been added to controller software release 4.1.181.0.

New DCA CLI Commands

These new CLI commands have been added to configure the dynamic channel allocation (DCA) algorithm:

•To control the DCA sensitivity with respect to changes in the environment, enter this command:

config advanced {802.11a | 802.11b} channel dca sensitivity {low | medium | high}

The DCA algorithm determines whether to make a channel change based on how much better a new channel would be for the radio with the worst DCA metric in the radio band. The DCA metric is comprised of noise, interference, channel load, and overlapping neighbors (other radios on the same channel). Previously, a channel change would occur if another channel was 5 dBm better than the current channel of the radio with the worst DCA metric. This new command allows you to control how sensitive the DCA algorithm is to environmental changes, such as signal, load, noise, and interference, when determining whether to change channels. Table 2 shows the three available DCA sensitivity levels.

Table 2 DCA Sensitivity Levels

DCA Sensitivity Level
Description
2.4-GHz DCA Sensitivity Threshold (dB)
5-GHz DCA Sensitivity Threshold (dB)

High

High sensitivity to
environmental changes

5

5

Medium (default)

Moderate sensitivity to
environmental changes

15

20

Low

Low sensitivity to
environmental changes

30

35


For example, if the radio with the worst DCA metric in the 2.4-GHz band has a metric of -60 dBm on its current channel and the DCA algorithm finds that the metric would be -80 dBm on another channel (which is an improvement of 20 dBm), the DCA algorithm would change the channel if the DCA sensitivity is set to high or medium. It would not change the channel if the sensitivity is set to low.

•To define the time when DCA starts, enter this command:

config advanced {802.11a | 802.11b} channel dca anchor-time hour

where hour is an hour in the day from 0 to 23 (12:00 a.m. to 11:00 p.m.).

•Previously, the DCA algorithm ran every 10 minutes. To now define how often DCA runs, enter this command:

config advanced {802.11a | 802.11b} channel dca interval value

where value is 0, 1, 2, 3, 4, 6, 8, 12, or 24. 0 equals 10 minutes and is the default value. The rest of the values represent hours. So if you specify a value of 8, DCA would run every 8 hours.

For example, if you specify an anchor time of 0 and a DCA interval of 12, the DCA algorithm would run at 12:00 a.m. and 12:00 p.m. every day.

Note You can view the configured DCA sensitivity, anchor-time, and interval on the 802.11a (or 802.11b/g) Global Parameters > Auto RF page on the controller GUI. However, you can configure these values only from the controller CLI.

Note When the controller reboots, the DCA algorithm runs every 10 minutes for the first 100 minutes, regardless of how the anchor-time and interval parameters are configured. This initial startup phase enables the DCA algorithm to converge to a reliable channel before the scheduled operation occurs. After the first 100 minutes, the DCA algorithm runs at only the scheduled times.

•To enable debugging for the DCA algorithm's channel change, enter this command:

debug airewave-director channel

This command provides the previous channel, the 802.11 interference energy (both the previous and current values in dBm), the noise energy (both the previous and current values in dBm), and the reason why the channel was changed. Possible reasons include:

–0 = Other (could occur as a result of a manual channel change or for other reasons)

–1 = Signal (could occur if another access point moved on and off the radio's current channel)

–2 = Noise

–4 = 802.11 interference

–6 = Noise and 802.11 interference

Note You can see the reason why the DCA algorithm changed channels by clicking Monitor and then View All under Most Recent Traps on the controller GUI. The trap provides the MAC address of the radio that changed channels, the previous channel and the new channel, the reason why the change occurred, the energy before and after the change, the noise before and after the change, and the interference before and after the change.

RRM Changes

These changes in RRM functionality have been added to controller software release 4.1.181.0.

•The default value for the transmit power control threshold has been changed from -65 dBm to -70 dBm.

•The default setting for aggressive load-balancing has been changed to disabled, and the default value for the clients parameter in the config load-balancing window clients CLI command has been changed to 5.

Mesh Features and Changed Information

These mesh features have been added to controller software release 4.1.181.0.

Mesh Multicast for Video

You can use the controller CLI to configure three mesh multicast modes to manage video camera broadcasts. When enabled, these modes reduce unnecessary multicast transmissions within the mesh network and conserve backhaul bandwidth.

Mesh multicast modes determine how bridging-enabled access points [mesh access points (MAPs) and root access points (RAPs)] send multicasts among Ethernet LANs within a mesh network. Mesh multicast modes manage non-LWAPP multicast traffic only. LWAPP multicast traffic is governed by a different mechanism.

The three mesh multicast modes are:

•Regular mode—Data is multicast across the entire mesh network and all its segments by bridging-enabled RAPs and MAPs. This is the default mode.

•In mode—Multicast packets received from the Ethernet by a MAP are forwarded to the RAP's Ethernet network. No additional forwarding occurs, which ensures that non-LWAPP multicasts received by the RAP are not sent back to the MAP Ethernet networks within the mesh network (their point of origin), and MAP-to-MAP multicasts do not occur because they are filtered out.

•In-out mode—The RAP and MAP both multicast but in a different manner:

–If multicast packets are received at a MAP over Ethernet, they are sent to the RAP; however, they are not sent to other MAP Ethernets, and the MAP-to-MAP packets are filtered out of the multicast.

–If multicast packets are received at a RAP over Ethernet, they are sent to all the MAPs and their respective Ethernet networks. When the in-out mode is in operation, it is important to properly partition your network to ensure that a multicast sent by one RAP is not received by another RAP on the same Ethernet segment and then sent back into the network.

Note If 802.11b clients need to receive LWAPP multicasts, then multicast must be enabled globally on the controller as well as on the mesh network (using the config network multicast global enable CLI command). If multicast does not need to extend to 802.11b clients beyond the mesh network, the global multicast parameter should be disabled (using the config network multicast global disable CLI command).

To enable multicast mode on a mesh network, enter this command:

config mesh multicast {regular | in | in-out}

AP1510 Interoperability with Cisco 3200 MAR in Public-Safety Networks

You can configure the Cisco AP1510 to interoperate with the Cisco 3200 Series Wireless Mobile Access Router (MAR) on the public-safety channel (4.9 GHz) to integrate data collected from in-vehicle deployments such as police cars into the overall wireless infrastructure. Follow these guidelines for the AP1510 and Cisco 3200 MAR to interoperate on the public-safety network:

•The Cisco 3200 MAR must run Cisco IOS Software Release 12.3(2)JK3, and the AP1510 must run controller software release 4.1.181.0.

•Client access must be enabled on the backhaul to use the 4.9-GHz band for client traffic.

•Public safety must be enabled globally on all MAPs in the mesh network.

•When using the CLI, the 802.11a radio must be disabled before configuring channels and then re-enabled.

•The channel number assignment on the AP1510 and Cisco 3200 MAR radio interfaces must match.

–Channels 20 (4950 MHz) and 26 (4980 MHz) are used for client access. This configuration change is made on the controller. No changes are made to the access point configuration.

–Channel assignments are made only to the RAP. Updates to the MAP are propagated by the RAP.

–To ensure backward compatibility with controller software releases 4.0 and 4.1.171.0, channels 190 and 196 are still used for the backhaul and client access.

Using the GUI to Enable AP1510 Association with the Cisco 3200 MAR

Follow these steps to enable the AP1510 to associate with the Cisco 3200 MAR using the GUI.

Step 1 Click Wireless > Mesh to access the Mesh page.

Step 2 Check the Backhaul Client Access check box to allow wireless client association over the 802.11a radio and click Apply.

Step 3 When you are prompted to allow a reboot of all mesh access points in order to enable backhaul client access, click OK.

Step 4 On the controller CLI, enter this command to enable public-safety:

config mesh public-safety enable all

Step 5 On the controller GUI, click Wireless > Access Points > Radios > 802.11a/n. The 802.11a/n Radios page appears.

Step 6 Hover your cursor over the blue drop-down arrow for the desired RAP and choose Configure. The 802.11a/n Cisco APs > Configure page appears.

Step 7 Under RF Backhaul Channel Assignment, choose Custom for the Assignment Method and either channel 20 or 26 from the Custom drop-down menu.

Step 8 Click Apply to commit your changes.

Step 9 Click Save Configuration to save your changes.

Using the CLI to Enable AP1510 Association with the Cisco 3200 MAR

Follow these steps to enable the AP1510 to associate with the Cisco 3200 MAR using the CLI.

Step 1 To enable client access mode on the AP1510, enter this command:

config mesh client-access enable

Step 2 To enable public safety on a global basis, enter this command:

config mesh public-safety enable all

Step 3 To choose the public-safety channels, enter these commands:

config 802.11a disable Cisco_RAP

config 802.11a channel ap Cisco_RAP {20 | 26}

config 802.11a enable Cisco_RAP

Step 4 To save your changes, enter this command:

save config

Step 5 To verify your configuration, enter these commands:

show mesh public-safety

show mesh client-access

show ap config 802.11a summary

Transmit Power Levels for 1500 Series Access Points

In controller software release 4.1.181.0, power levels for the AP1505 and AP1510 are reported as either Tx Power Level 1 or Tx Power Level 2. Previously, only a maximum transmission power (Max Tx Power) was reported.

•Tx Power Level 1 = The maximum power level that exists across all of the data rates

•Tx Power Level 2 = Tx Power Level 1 minus 3 dBm

Note The CLI command summary displays the dBm value for power levels 1 and 2, but this reading is not available on the controller GUI.

Using the GUI to View Transmit Power Levels for 1500 Series Access Points

Follow these steps to view transmit power levels for an AP1505 or AP1510 using the GUI.

Step 1 Click Wireless > Access Points > Radios > 802.11a/n or 802.11b/g/n to access the 802.11a/n (or 802.11b/g/n) Radios page.

Step 2 Hover your cursor over the blue drop-down arrow for the desired access point and choose Detail. The 802.11a/n (or 802.11b/g/n) AP Interfaces > Details page appears (see Figure 1).

Figure 1 802.11a/n AP Interfaces > Details Page

This page shows the current transmit power level under the "Tx Power" section.

Using the CLI to View Transmit Power Levels for 1500 Series Access Points

To view transmit power levels for an AP1505 or AP1510 using the CLI, enter these commands:

show ap config 802.11a Cisco_AP

show ap config 802.11b Cisco_AP

Note The show ap config 802.11a Cisco_AP command is not applicable to the AP1505 because it has only one radio, the 802.11b/g/n.

Information similar to the following appears: 

show ap config 802.11a mesh-RAP-45

Tx Power 

      Num Of Supported Power Levels ............. 2

      Tx Power Level 1 .......................... 26 dBm

      Tx Power Level 2 .......................... 23 dBm

      Tx Power Configuration .................... CUSTOMIZED

Current Tx Power Level .................... 2 

show ap config 802.11b mesh-RAP-45

Tx Power 

      Num Of Supported Power Levels ............. 2

      Tx Power Level 1 .......................... 24 dBm

      Tx Power Level 2 .......................... 21 dBm

      Tx Power Configuration .................... AUTOMATIC

Current Tx Power Level .................... 1

LED Verification on 1500 Series Access Points

You can attach an LED indicator to the Power over Ethernet (PoE) connector of AC-powered Cisco Aironet 1505 and 1510 Access Points to verify that power is on. A steady green color indicates that the access point is receiving power and that LWAPP is connected and ready to serve clients. You might notice a blinking green light between the initial and final steady green light as the LED confirms LWAPP connectivity.

Note 1500 series access points with a serial number of WCN10160121 or greater support the use of the LED indicator.

Note Do not install the LED indicator if the access point has an Ethernet connection to the network.

For details on installing the LED indicator, refer to the Cisco Aironet Series 1500 Access Point LED Indicator Installation Instructions at this URL:
http://www.cisco.com/en/US/products/ps6548/tsd_products_support_series_home.html

Mesh Changes

These changes in mesh functionality have been added to controller software release 4.1.181.0.

•The ability to enable or disable the MAC filter list has been removed from both the controller GUI and CLI.

•Because controller software release 4.1 does not support an external AAA server for mesh access points, local authentication and RADIUS server support should always be enabled. Therefore, the following CLI commands are no longer supported:

config mesh local-auth disable

config mesh radius-server

•The show mesh env {summary | Cisco_AP} CLI command now provides battery details, including charge, power, serial number, temperature, version, and voltage. Here is a sample output: 

AP Name    : ap:60:6b:30

AP Model   : OAP1500

AP Role    : MeshAP


Temperature: 33 C, 91 F

Heater     : OFF

Ethernet   : UP


Battery S/W version   : 01.02a


Battery Serial Number : 0638F9500006

WARNING: Replace battery

Battery Input Voltage : 120.0 V

Battery Output Voltage:  55.1 V

Battery Output Power  : 12.2 W

Battery Voltage       :  52.5 V

Battery Temperature   : 23 C 73 F

Battery Charge        : 100.000 %

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.

Warning Only trained and qualified personnel should be allowed to install, replace, or service this equipment.

Warning Do not locate any antenna near overhead power lines or other electric light or power circuits, or where it can come into contact with such circuits. When installing antennas, take extreme care not to come in contact with such circuits, as they may cause serious injury or death. For proper installation and grounding of the antenna, refer to national and local codes (e.g. U.S.: NFPA70, National Electrical Code, Article 810, in Canada: Canadian Electrical Code, Section 54).

Warning This product relies on the building's installation for short-circuit (overcurrent) protection. Ensure that the protective device is rated not greater than: 120 VAC, 15A U.S. (240vac, 10A International)

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.

Warning Read the installation instructions before you connect the system to its power source.

Warning Do not work on the system or connect or disconnect cables during periods of lightning activity.

Warning Do not operate your wireless network near unshielded blasting caps or in an explosive environment unless the device has been modified to be especially qualified for such use.

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.

Warning This unit is intended for installation in restricted areas. A restricted access area can be accessed only through the use of a special tool, lock and key, or other means of security.

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

Each year hundreds of people are killed or injured when attempting to install an antenna. In many of these cases, the victim was aware of the danger of electrocution but did not take adequate steps to avoid the hazard.

For your safety, and to help you achieve a good installation, read and follow these safety precautions. They may 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:

a. Do not use a metal ladder.

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

Refer to 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 professionally installed.

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.

Important Notes

This section describes important information about the controllers and access points.

802.11n

802.11n radios are not supported for use with controller software release 4.1.181.0. In this release, disregard any 802.11n-related parameters that appear on the controller GUI pages and any 802.11n-related controller CLI commands.

Disabling Radio Bands

The controller disables the radio bands that are not permitted by the configured country of operation (CSCsi48220).

MAC Filtering for WGB Wired Clients

Controller software release 4.1.178.0 enables you to configure a MAC-filtering IP address for a workgroup bridge (WGB) wired client to allow passive WGB wired clients, such as terminal servers or printers with static IP addresses, to be added and remain in the controller's client table while the WGB is associated to a controller in the mobility group. This feature, activated by the config macfilter ipaddress MAC_address IP_address CLI command, can be used with any passive device that does not initiate any traffic but waits for another device to start communication.

This feature allows the controller to learn the IP address of a passive WGB wired client when the WGB sends an IAPP message to the controller that contains only the WGB wired client's MAC address. Upon receiving this message from the WGB, the controller checks the local MAC filter list (or the anchor controller's MAC filter list if the WGB has roamed) for the client's MAC address. If an entry is found and it contains an IP address for the client, the controller adds the client to the controller's client table.

Note Unlike the existing MAC filtering feature for wireless clients, you are not required to enable MAC filtering on the WLAN for WGB wired clients.

Note WGB wired clients using MAC filtering do not need to obtain an IP address through DHCP to be added to the controller's client table.

CKIP Not Supported with Dynamic WEP

In controller software release 4.1.181.0, CKIP is supported for use only with static WEP. It is not supported for use with dynamic WEP. Therefore, a wireless client that is configured to use CKIP with dynamic WEP is unable to associate to a wireless LAN that is configured for CKIP. Cisco recommends that you use either dynamic WEP without CKIP (which is less secure) or WPA/WPA2 with TKIP or AES (which are more secure).

UNII-2 Channels Disabled on New 1000 Series Access Points for United States, Canada, and Philippines

New Cisco 1000 series lightweight access points for the United States, Canada, and the Philippines do not support the UNII-2 band (5.25 to 5.35 GHz). These models are labeled AP10x0-B, where "B" represents a new regulatory domain that replaces the previous "A" domain.

FCC DFS Support on AP1130s

Federal Communications Commission (FCC) dynamic frequency selection (DFS) is supported only on AP1130s in the United States, Canada, and the Philippines that have a new FCC ID. Access points use DFS to detect radar signals such as military and weather sources and then switch channels to avoid interfering with them. AP1130s with FCC DFS support have an FCC ID LDK102054E sticker. AP1130s without FCC DFS support have an LDK102054 (no E suffix) sticker. AP1130s that are operating in the United States, Canada, or the Philippines; have an FCC ID E sticker; and are running the 4.1.171.0 software release or greater can use channels 100 through 140 in the UNII-2 band.

Access Point Radios Are Not Enabled After Upgrading to 4.1.181.0

After you upgrade the controller in the Catalyst 3750G Wireless LAN Controller Switch to software release 4.1.181.0, the access point radios are not enabled. This issue occurs because the switch is not correctly recognizing the access points through CDP and not enabling sufficient inline power for the radios. To work around this issue, uncheck the CDP State check box on the AP Configuration > CDP Template page on the controller GUI or enter config ap cdp disable all on the controller CLI.

Setting the Retransmit Timeout Value for TACACS+ Servers

Cisco recommends that the retransmit timeout value for TACACS+ authentication, authorization, and accounting servers be increased if you experience repeated reauthentication attempts or the controller falls back to the backup server when the primary server is active and reachable. The default retransmit timeout value is 2 seconds and can be increased to a maximum of 30 seconds.

Configuring an Access Point's PreStandard Power Setting

An access point can be powered by a Cisco prestandard 15-watt switch with Power over Ethernet (PoE) by entering this command:

config ap power pre-standard {enable | disable} {all | Cisco_AP}

A Cisco prestandard 15-watt switch does not support intelligent power management (IPM) but does have sufficient power for a standard access point. The following Cisco prestandard 15-watt switches are available:

•AIR-WLC2106-K9

•WS-C3550, WS-C3560, WS-C3750

•C1880

•2600, 2610, 2611, 2621, 2650, 2651

•2610XM, 2611XM, 2621XM, 2650XM, 2651XM, 2691

•2811, 2821, 2851

•3631-telco, 3620, 3640, 3660

•3725, 3745

•3825, 3845

The enable version of this command is required for full functionality when the access point is powered by a Cisco prestandard 15-watt switch. It is safe to use if the access point is powered by either an IPM switch or a power injector or if the access point is not using one of the 15-watt switches listed above.

You might need this command if your radio operational status is "Down" when you expect it to be "Up." Enter the show msglog command to look for this error message, which indicates a PoE problem: 

Apr 13 09:08:24.986 spam_lrad.c:2262 LWAPP-3-MSGTAG041: AP 00:14:f1:af:f3:40 is unable to 
verify sufficient in-line power. Radio slot 0 disabled.

Using CCKM with CB21AG Client Adapters

Cisco Aironet CB21AG client adapters support only this CCKM configuration setting: WPA + TKIP + authentication key management CCKM.

DHCP Option 60 and 1500 Series Access Points

The VCI string for DHCP option 60 on 1500 series access point changes to Cisco AP c1500 after the access points are upgraded to controller software release 4.1.181.0.

AP1000 and Radar Detection

The AP1000 performs radar detection on channels that do not require it (such as channel 36). If the access point detects radar on these channels, the controller captures it in log messages.

Controller Functions that Require a Reboot

After you perform these functions on the controller, you must reboot the controller in order for them to take effect:

•Switch between Layer 2 and Layer 3 LWAPP mode

•Enable or disable link aggregation (LAG)

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

•Enable or disable the mobility protocol port using this CLI command:

config mobility secure-mode {enable | disable}

Multicast Queue Depth

The multicast queue depth is 512 packets on all controller platforms. However, the following message might appear on 2006 controllers: "CPU Receive Multicast Queue is full on Controller." This message does not appear on 4400 series controllers because the 4400 NPU filters ARP packets while all forwarding (multicast or otherwise) and multicast replication are done in the software on the 2006.

2106 Controller LEDs

The 2106 controller's Status LED and AP LED do not flash amber when software is being uploaded to the controller or downloaded to an access point, respectively.

Note Some versions of the Cisco 2106 Wireless LAN Controller Quick Start Guide might incorrectly state that these LEDs flash amber during a software upload or download.

Resetting the Configuration on 2006 Controllers

If you wish to reset the configuration to factory defaults on a 2006 controller, perform one of the following:

•From the controller GUI, click Commands > Reset to Factory Default > Reset.

•From the controller CLI (after system bootup and login), enter clear config. Then after the configuration has been cleared, enter reset system without saving the current configuration.

•From the controller console (after system bootup), enter Recover-Config from the User Name prompt.

Caution Do not attempt to reset the controller's configuration by choosing Option 5, Clear Config, from the boot menu.

Rate-Limiting on the Controller

Rate-limiting is applicable to all traffic destined to the CPU from either direction (wireless or wired). Cisco recommends that you always run the controller with the default config advanced rate enable command in effect in order to rate-limit traffic to the controller and protect against denial-of-service (DoS) attacks. You can use the config advanced rate disable command to stop rate-limiting of Internet Control Message Protocol (ICMP) echo responses for testing purposes. However, Cisco recommends that you reapply the config advanced rate enable command after testing is complete.

Pings Supported on the Controller

Controller software release 4.1.181.0 is designed to support ICMP pings to the management interface either from a wireless client or a wired host. ICMP pings to other interfaces configured on the controller are not supported.

Pinging from a Network Device to a Controller Dynamic Interface

Pinging from a network device to a controller dynamic interface may not work in some configurations. When pinging does operate successfully, the controller places Internet Control Message Protocol (ICMP) traffic in a low-priority queue, and the reply to ping is on best effort. Pinging does not pose a security threat to the network. The controller rate limits any traffic to the CPU, and flooding the controller is prevented. Clients on the WLAN associated with the interface pass traffic normally.

IPSec Not Supported

Software release 4.1.181.0 does not allow you to choose IPSec as a Layer 3 Security option. None and VPN Passthrough are the only available options. If you upgrade to this release from a previous release that supported IPSec as a Layer 3 Security option, any WLANs that are configured for this feature become disabled. If you want to configure IPSec, you must use a version of controller software prior to 3.2.

4400 Series Controllers Do Not Forward Subnet Broadcasts through Guest Tunnel

As designed, 4400 series controllers do not forward IP subnet broadcasts from the wired network to wireless clients across the EoIP guest tunnel.

Re-enable Broadcast after Upgrading to Release 4.0.206.0

In software releases 4.0.179.0 and earlier, broadcast and multicast forwarding were both controlled with a single global flag that enabled multicast. Beginning with software release 4.0.206.0, these functions were broken into separate configuration flags: one that controls broadcast and one that controls non-broadcast multicast. If you have multicast enabled in software releases 4.0.179.0 and earlier, the broadcast flag is left disabled after upgrading to software release 4.0.206.0. As a result, some applications that rely on broadcast do not work after the upgrade.

After you upgrade to software release 4.0.206.0, use this CLI command to re-enable broadcast:

config network broadcast enable

When re-enabled, broadcast uses the multicast mode configured on the controller.

Service Modules Supported in the Catalyst 6500 Series Switch

The Catalyst 6500 Series Switch chassis can support up to five Cisco WiSMs without any other service module installed. If one or more service modules are installed, the chassis can support up to a maximum of four service modules (WiSMs included).

Connecting 1100 and 1300 Series Access Points

You must install software release 4.0.179.8 or later on the controller before connecting 1100 and 1300 series access points to the controller.

Controllers Must Run Release 3.2.116.21 or Later to Support -P Regulatory Domain

To support access points configured for use in Japan, you must upgrade the controller software to release 3.2.116.21 or later. Earlier releases do not support access points configured for use in Japan (regulatory domain -P).

Preventing Clients from Accessing the Management Network on a Controller

To prevent or block a wired or wireless client from accessing the management network on a controller (from the wireless client dynamic interface or VLAN), the network administrator should ensure that there is no route through which to reach the controller from the dynamic interface or use a firewall between the client dynamic interface and the management network.

Voice Wireless LAN Configuration

Cisco recommends that aggressive load balancing always be turned off either through the controller GUI or CLI in any wireless network that is supporting voice, regardless of vendor. When aggressive load balancing is turned on, voice clients can hear an audible artifact when roaming, and the handset is refused at its first reassociation attempt.

Conducting a Radio Site Survey for Mesh Deployments

A radio site survey (temporary setup of mesh links) should be conducted prior to any physical installation of 1500 series mesh access points to verify that there is no interference to the radio signal path due to physical structures such as trees and buildings or equipment that may be transmitting on the same channel (co-channel interference).

For detailed information on conducting site surveys and other factors to consider when planning your network (data rate, distance between access points, interference, and so on), refer to the Cisco Aironet 1500 Series Wireless Mesh AP Version 5.0 Design Guide at http://www.cisco.com/en/US/products/ps6548/tsd_products_support_series_home.html

Operating Mesh Networks through Switches and Routers

In mesh networks that operate through switches and routers, network round-trip delays between access points and the controller must be less than 100 milliseconds (ms); otherwise, timing problems may occur during wireless client authentication. Also, network path outages of 60 seconds between access points and the controller may cause the access points to lose connectivity.

Cisco 7920 Wireless IP Phone Support

When using Cisco 7920 Wireless IP Phones with controllers, make sure that the phones and controllers are configured as follows:

•Aggressive load balancing must be disabled for each controller. Otherwise, the initial roam attempt by the phone may fail, causing a disruption in the audio path.

•The QoS Basis Service Set (QBSS) information element (IE) must be enabled. The QBSS IE enables the access points to communicate their channel usage to wireless devices. Because access points with high channel usage might not be able to handle real-time traffic effectively, the 7920 phone uses the QBSS value to determine if they should associate with another access point. Use the following commands to enable the QBSS IE:

–sh wlan summary

Note Use this command to determine the WLAN ID number of the WLAN to which you want to add QBSS support.

–config wlan disable wlan_id_number

–config wlan 7920-support ap-cac-limit enable wlan_id_number

–config wlan enable wlan_id_number

–sh wlan wlan_id_number

Note Use this command to verify that the WLAN is enabled and the Dot11-Phone Mode (7920) field is configured for compat mode.

–save config

•The Dynamic Transmit Power Control (DTPC) information element (IE) must be enabled using the config 802.11b dtpc enable command. The DTPC IE is a beacon and probe information element that allows the access point to broadcast information on its transmit power. The Cisco 7920 Wireless IP Phone uses this information to automatically adjust its transmit power to the same level as the access point to which it is associated. In this manner, both devices are transmitting at the same level.

•Both the 7920 phones and the controllers support Cisco Centralized Key Management (CCKM) fast roaming.

•When configuring WEP, there is a difference in nomenclature for the controller and the 7920 phone. Configure the controller for 104 bits when using 128-bit WEP for the 7920.

Changing the IOS LWAPP Access Point Password

Cisco IOS Lightweight Access Point Protocol (LWAPP) access points have a default password of Cisco, and the pre-stage configuration for LWAPP access points is disabled by default. To enable it, you must configure the access point with a new username and password when it joins the controller. Enter this command using the controller CLI to push a new username and password to the access point:

config ap username user_id password password {Cisco_AP | all}

•The Cisco_AP parameter configures the username and password on the specified access point.

•The all parameter configures the username and password on all the access points registered to the controller.

The password pushed from the controller is configured as "enable password" on the access point.

There are some cases where the pre-stage configuration for LWAPP access points is disabled and the access point displays the following error message when the CLI commands are applied:

"ERROR!!! Command is disabled."

For more information, refer to Upgrading Autonomous Cisco Aironet Access Points to Lightweight Mode.

Exclusion List (Blacklist) Client Feature

If a client is not able to connect to an access point, and the security policy for the WLAN and client are correct, the client has probably been disabled. In the controller GUI, you can view the client's status on the Monitor > Summary page under Client Summary. If the client is disabled, click Remove to clear the disabled state for that client. The client automatically comes back and, if necessary, reattempts authentication.

Automatic disabling happens as a result of too many failed authentications. Clients disabled due to failed authorization do not appear on the permanent disable display. This display is only for those MACs that are set as permanently disabled by the administrator.

RADIUS Servers and the Management VLAN

If a RADIUS server is on a directly connected subnet (with respect to the controller), then that subnet must be the management VLAN subnet.

Cisco 1000 Series Access Points and WMM

•In order to use Layer 2 LWAPP mode and WMM with a 1000 series access point, you must make sure that WMM is disabled.

•Clients cannot associate to an AP1030 in REAP mode if WMM is enabled on the WLAN. Disable WMM to allow the clients to associate.

Cisco Aironet 1030 Remote Edge Lightweight Access Points and WPA2-PSK

Cisco Aironet 1030 Remote Edge Lightweight Access Points do not support WPA2-PSK in REAP standalone mode.

Lightweight Access Point Connection Limitations

Cisco Aironet lightweight access points do not connect to the 4400 series controller if the date and time are not set properly. Set the current date and time on the controller before allowing the access points to connect to it.

RADIUS Servers

This product has been tested with CiscoSecure ACS 3.2 and later and works