text:
Table Of Contents
Release Notes for Cisco Wireless LAN Controllers and Lightweight Access Points for Release 126.96.36.199
Cisco Unified Wireless Network Solution Components
Special Rules for Upgrading to Controller Software Release 126.96.36.199
Software Release Support for Access Points
Interoperability With Other Clients
Special Rules for Upgrading to Controller Software 184.108.40.206 in Mesh Networks
Upgrading to a New Software Release
FCC Safety Compliance Statement
Using the Cisco 5500 Series Controller USB Console Port
Important Notes for Controllers and Nonmesh Access Points
Upgrading to 188.8.131.52 or 220.127.116.11 Can Disrupt DHCP Service When Using Controller's Internal DHCP Feature
Additive Licenses Available for 5500 Series Controllers
One-Time Password (OTP) Support
RADIUS Called-station-id and Calling-station-id Attributes
Using Access Points in Sniffer Mode
Inter-Release Controller Mobility
RLDP Limitations in This Release
802.11g Controller and 802.11b Clients
CAPWAP Problems with Firewalls and ACLs
Messages Appearing Upon Controller Bootup
Cisco 1250 Series Access Points and Cisco 7920 IP Phones
Crash Files for 1250 Series Access Points
Configuration File Stored in XML
Access Points Send Multicast and Management Frames at Highest Basic Rate
802.11a Channels 120, 124, and 128 Disabled
Impact of External Antenna Gain on Transmit Power
Supporting Oversized Access Point Images
MAC Filtering for WGB Wired Clients
CKIP Not Supported with Dynamic WEP
Setting the Date and Time on the Controller
Synchronizing the Controller and Location Appliance
FCC DFS Support on 1130 Series Access Points
Inaccurate Transmit Power Display
Setting the Retransmit Timeout Value for TACACS+ Servers
Configuring an Access Point's Prestandard Power Setting
Controller Functions that Require a Reboot
Rate-Limiting on the Controller
Pings Supported to the Management Interface of the Controller
Pinging from a Network Device to a Controller Dynamic Interface
4400 Series Controllers Do Not Forward Subnet Broadcasts through the Guest Tunnel
Connecting 1100 and 1300 Series Access Points
Preventing Clients from Accessing the Management Network on a Controller
Voice Wireless LAN Configuration
Enabling/Disabling Band Selection and Client Load Balancing
Changing the IOS LWAPP Access Point Password
Exclusion List (Blacklist) Client Feature
RADIUS Servers and the Management VLAN
Management Usernames and Local Netuser Names
Home Page Retains Web Authentication Login with IE 5.x
Changing the Default Values of SNMP Community Strings
Changing the Default Values for SNMP v3 Users
DirectStream Feature Is Not Supported With WGB
Controller does not Support Transmitting Jumbo Frames
Features Not Supported on 2100 Series Controllers
Features Not Supported on 5500 Series Controllers
Some Clients See Only 64 Access Point MAC Addresses (BSSIDs) at a Time
2106 Image Not Supported for 3504 Controllers
Running a 3504 Image on a 2106 Series Controller
Upgrading External Web Authentication
Switch Port and Controller Port
Issues With mac-address CLI for Unified and Autonomous Access Points
Obtaining Documentation and Submitting a Service Request
Release Notes for Cisco Wireless LAN Controllers and Lightweight Access Points for Release 18.104.22.168
April 2011
The 188.8.131.52 release is a maintenance release that contains only bug fixes. This release does not contain any new major feature or support any new platforms. This release should not be confused with the 7.0 MR1 release, which will happen in April or May, 2011.
These release notes describe open and resolved caveats for release 184.108.40.206 for Cisco 2100, 4400, and 5500 Series Wireless LAN Controllers; Cisco Wireless Services Modules (WiSMs); Cisco Wireless LAN Controller Network Modules; Catalyst 3750G Integrated Wireless LAN Controller Switches; Cisco 3201 Wireless Mobile Interface Cards (WMICs); Cisco Aironet 1100, 1130, 1200, 1230AG, 1240, 1250, 1300, AP3500, AP1260, AP 1040, and AP801 Series Lightweight Access Points; Cisco Aironet 1130AG, 1240AG, 1522, and 1524 Mesh 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 referred to as controllers, and all of the Cisco lightweight access points are referred to as access points.
These release notes contain the following sections.
•Cisco Unified Wireless Network Solution Components
•Upgrading to a New Software Release
•Using the Cisco 5500 Series Controller USB Console Port
•Important Notes for Controllers and Nonmesh Access Points
•Obtaining Documentation and Submitting a Service Request
Cisco Unified Wireless Network Solution Components
The following components are part of the Cisco UWN Solution and are compatible in this release:
•Software release 188.8.131.52 for all Cisco controllers and lightweight access points
•Cisco autonomous to lightweight mode upgrade tool release 3.0
•Cisco Wireless Control System (WCS) software release 7.0.164
•Cisco WCS Navigator 220.127.116.11
•Location appliance software release 22.214.171.124
•Mobility services engine software release 18.104.22.168 and Context Aware Software
Note Client and tag licenses are required in order to retrieve contextual (such as location) information within the Context Aware Software. See the Release Notes for Cisco 3350 Mobility Services Engine for Software Release 6.0 for more information.
•Cisco 3350, 3310 Mobility Services Engines
•Cisco 2100 Series Wireless LAN Controllers
•Cisco 4400 Series Wireless LAN Controllers
•Cisco 5500 Series Wireless LAN Controllers
•Cisco Wireless Services Module (WiSM) for Cisco Catalyst 6500 Series Switches and Cisco 7600 Series Routers
•Cisco Wireless LAN Controller Network Module for Cisco Integrated Services Routers
Note The 18.104.22.168 release does not support the NM-AIR-WLC6 platform. The NME-AIR-WLC platform is supported.
•Catalyst 3750G Wireless LAN Controller Switches
•Cisco 3201 Wireless Mobile Interface Card (WMIC)
•Cisco Aironet 1130AG, 1240AG, 1522, and 1524 Mesh Access Points
Note This release does not support Cisco Aironet 600, 1261 (single radio), 1505, 1510, 1550 access points.
•Cisco Aironet 1100, 1130, 1200, 1230AG, 1240, 1250, AP1260, 1300, AP3500, AP 1040 and AP801 Series Lightweight Access Points
Note Controller software release 184.108.40.206 or later is not compatible with Cisco Aironet 1000 series access points.
Note The AP801 is an integrated access point on the Cisco 800 Series Integrated Services Routers (ISRs).
Note The 801 access point (the access point embedded in the 88xW ISR), the 1250 series access point, and the 1140 series access point have a hardware limitation where beacons can only be output at intervals that are multiples of 17 milliseconds. When these APs are configured for a 100-millisecond beacon interval, they transmit beacons every 102 milliseconds. Similarly, when the beacon interval is configured for 20 milliseconds, these APs transmit beacons every 17 milliseconds.
Note Only Cisco Aironet 1200 Series Access Points that contain 802.11g (AIR-MP21G) or second-generation 802.11a radios (AIR-RM21A or AIR-RM22A) are supported for use with controller software releases. The AIR-RM20A radio, which was included in early 1200 series access point models, is not supported. To see the type of radio module installed in your access point, enter this command on the access point: show controller dot11radio n, where n is the number of the radio (0 or 1).
Controller Requirements
The controller GUI requires the following operating system and web browser:
•Windows XP SP1 (or later) or Windows 2000 SP4 (or later)
•Internet Explorer 6.0 SP1 (or later) or Mozilla Firefox 126.96.36.199 (or later)
Note Internet Explorer 6.0 SP1 (or later) and Mozilla Firefox 18.104.22.168 (or later) are the only browsers supported for using the controller GUI and web authentication.
MIB Files
Cisco controllers support standard SNMP Management Information Base (MIB) files. MIBs can be downloaded from the Software Center on Cisco.com. Only one MIB is posted per major release (184.108.40.206, 6.0, 5.2, 5.1, and so on). If an updated MIB becomes available, the previous version is removed from the Software Center and replaced by the new version.
New Features
The following are the two new commands introduced in this release.
•To add flexibility for CCKM max timestamp validation, use the
config wlan security wpa akm cckm timestamp-tolerance <tolerance> command.
where the value for time-stamp tolerance is from 1000 to 5000 msecs and the default tolerance is 1000 msecs.
•To enable the WGB VLAN client feature, use the config wgb vlan {enable | disable} command.
Software Release Information
The 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, you should 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 184.108.40.206 or later, and the Supervisor 720 12.2(18)SXF5 (Cisco IOS Software Modularity) supports the Cisco WiSM software release 126.96.36.199 (with Cisco IOS Software Modularity).
Note To use the Cisco WiSM in the Cisco 7609 and 7613 Series Routers, the routers must be running Cisco IOS Release 12.2(18)SXF5 or later.
Note The Cisco Wireless LAN Controller Network Module is supported on Cisco 28/37/38xx Series Integrated Services Routers running Cisco IOS Release 12.4(11)T2, 12.4(11)T3, and 12.5.
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, 12.2(35)SE or later, 12.2(37)SE or later, 12.2(44)SE or later, or 12.2(46)SE or later. The following Cisco IOS Releases and any variants are not supported: 12.2(25)SEC, 12.2(25)SED, 12.2(25)SEE, 12.2(25)SEF, and 12.2(25)SEG. All Catalyst 3750 software feature sets (IP Base, IP Service, and Advanced IP Services) are supported for use with the controller.
Note You can use the 2112 and 2125 controllers only with software release 188.8.131.52 or later.
Finding the Software Release
To find the software release running on your controller, click Monitor and look at the Software Version field under Controller Summary on the controller GUI, or enter show sysinfo on the controller CLI.
Special Rules for Upgrading to Controller Software Release 18.104.22.168
Before upgrading your controller to software release 22.214.171.124, you must comply with the following rules:
•Before you download a software image or an ER.aes file to a 2100 series controller or a controller network module, use the show memory statistics CLI command to see the current amount of free memory. If the controller has less than 90 MB of free memory, you need to reboot it before downloading the file.
•Before you use an AP801 series lightweight access point with controller software release 188.8.131.52, you must upgrade the software in the Cisco 860 and 880 Series Integrated Services Routers (ISRs) to Cisco IOS 12.4(22)T and the software in the Cisco 890 Series Integrated Services Router to Cisco IOS 12.4(22)YB.
•Make sure you have a TFTP or FTP server available for the software upgrade. Keep these guidelines in mind when setting up a TFTP or FTP server:
–Controller software release 220.127.116.11 is larger 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 tftpd and the TFTP server within the WCS. If you attempt to download the 126.96.36.199 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 service port, the TFTP or FTP server must be on the same subnet as the service port because the service port is not routable, or you must create static routes on the controller.
–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.
–A third-party TFTP or FTP server cannot run on the same computer as WCS because the WCS built-in TFTP or FTP server and the third-party TFTP or FTP server require the same communication port.
•The AP-count evaluation licenses for the 7.0 and the 6.0 releases are different. If you downgrade from a 7.0 release to a 6.0 release, you must activate the AP-count evaluation license of the 6.0 release after you downgrade. Similarly, if you upgrade from a 6.0 release to a 7.0 release, you must activate the AP-count evaluation license of the 7.0 release after you upgrade. If you do not activate the AP-count license, then the AP-count is shown as 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 18.104.22.168. Table 1 shows the upgrade path that you must follow before downloading software release 220.127.116.11.
Table 1 Upgrade Path to Controller Software Release 220.127.116.11
Current Software Release Upgrade Path to 18.104.22.168 Software
126.96.36.199 or later 3.2 release
Upgrade to 220.127.116.11 or later 4.0 release, then upgrade to 188.8.131.52, before upgrading to 126.96.36.199.
220.127.116.11 or later 4.0 release
Upgrade to 22.214.171.124 before upgrading to 126.96.36.199.
188.8.131.52 or later 4.1 release
Upgrade to 22.214.171.124 before upgrading to 22.214.171.124.
Upgrade to 220.127.116.11M and then to 188.8.131.52 before upgrading to 188.8.131.52.
184.108.40.206M or 126.96.36.199M
Upgrade to 22.214.171.124 before upgrading to 188.8.131.52.
126.96.36.199 or earlier 4.2 release
Upgrade to 220.127.116.11 before upgrading to 220.127.116.11.
126.96.36.199 or later 4.2 release
You can upgrade directly to 184.108.40.206.
188.8.131.52 or later 4.2 release
You can upgrade directly to 188.8.131.52.
18.104.22.168 or later 5.0 release
You can upgrade directly to 188.8.131.52.
22.214.171.124 or later 5.1 release
Upgrade to a 5.2 or a 6.0 release and then upgrade to 184.108.40.206.
220.127.116.11 or later 5.2 release
You can upgrade directly to 126.96.36.199.
22.214.171.124 or later 6.0 release
You can upgrade directly to 220.127.116.11.
220.127.116.11 or later 6.0 release
You can upgrade directly to 18.104.22.168.
You can upgrade directly to 126.96.36.199.
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 22.214.171.124 software. In large networks, it can take some time to download the software on each access point.
•We recommend that you install the Cisco Unified Wireless Network Controller Boot Software 18.104.22.168 ER.aes file on all controller platforms. This file resolves CSCsm03461 and is necessary in order for you to view the version information for ER.aes files in the output of the show sysinfo CLI command. If you do not install this ER.aes file, your controller does not obtain the fix for this defect, and "N/A" appears in the Emergency Image Version field in the output of this command.
Note You cannot install the Cisco Unified Wireless Network Controller Boot Software 188.8.131.52 ER.aes file on Cisco 5500 Series Controller platform.
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 (126.96.36.199 ER.aes) ensures that the boot software 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.
Software Release Support for Access Points
Table 2 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.
Table 2 Software Support for Access Points
Access Points First Support Last Support
1000 Series
Airespace AS1200
1040 Series
1100 Series
1220 Series
1230 Series
1240 Series
1250 Series
1260 Series
1300 Series
1400 Series
Standalone Only
3500 Series
1500 Mesh Series
1520 Mesh Series
-A and N: 126.96.36.199 or 5.2 or later1
All other reg. domains: 22.214.171.124M or 5.2 or later1
-A and N: 220.127.116.11 or 5.2 or later1
All other reg. domains: 126.96.36.199M or 5.2 or later1
-A and N: 184.108.40.206 or 5.2 or later1
All other reg. domains: 188.8.131.52M or 5.2 or later1
18.104.22.168 or later.
-A, C and N: 6.0 or later
All other reg. domains: 188.8.131.52 or later.
-A: 184.108.40.206M or 5.2 or later1
1 These access points are supported in the separate 4.1.19x.x mesh software release or with release 5.2 or later releases. These access points are not supported in the 4.2, 5.0, or 5.1 Releases.
Interoperability With Other Clients
This section describes the interoperability of the version of controller software with other client devices.
Table 3 describes the configuration used for testing the clients.
Table 3 Test Bed Configuration for Interoperability
Hardware/Software Parameter Hardware/Software Configuration Type
Cisco 4400 Series Controller and Cisco 5500 Series Controller
Access points
1131, 1142, 1242, 1252, AP 3500e and AP3500i
802.11a, 802.11g, 802.11n2, 802.11n5
Open, WEP, PSK (WPA and WPA2), 802.1X (WPA-TKIP and WPA2-AES) (LEAP, PEAP, EAP-FAST, EAP-TLS)
Type of tests
Connectivity, traffic, and roaming between two access points
Table 4 lists the versions of the clients. The traffic tests included data or voice. The clients included laptops, handheld devices, phones, and printers.
Table 4 Client Type
Client Type and Name Version Laptop
Intel 3945/4965
126.96.36.199 or 18.104.22.168
Intel 5100/5300/6200/6300
Dell 1395/1397/Broadcom 4312HMG(L)
XP/Vista: 22.214.171.124 Win7: 184.108.40.206
Dell 1505/1510/Broadcom 4321MCAG/4322HM
Dell 1520/Broadcom 43224HMS
Atheros HB92/HB97
Atheros HB95
MacBook Pro (Broadcom)
Handheld Devices
Falcon 4200/WinCE 4.2
Intermec CK31/WinCE 4.2:
Intermec CN3/Windows Mobile 5.0
Psion 7535/WinCE 5.0
Psion WAP/WinCE 5.0
Symbol 8846/Pocket PC 4.20
Symbol MC70 /Windows Mobile 5.0
Symbol MC9060/Pocket PC 4.2
Symbol MC9090/WinCE 5.0
Phones and Printers
Ascom i75
Nokia e61
Spectralink 8030
Spectralink e340/PTE110
Spectralink i640/PTX110
Vocera B1000A
Vocera B2000
Zebra QL320
Monarch 9855
Cisco 7921G
Cisco 7925G
Special Rules for Upgrading to Controller Software 18.104.22.168 in Mesh Networks
Caution Before upgrading your controller to software release 18.104.22.168 in a mesh network, you must comply with the following rules.
Upgrade Compatibility Matrix
Table 5 outlines the upgrade compatibility of controller mesh and nonmesh releases and indicates the intermediate software releases required as part of the upgrade path.
Software Upgrade Notes
The software upgrade notes are as follows:
•You can upgrade from 220.127.116.11M and 126.96.36.199M to 22.214.171.124 without any configuration file loss. See Table 5 for the available upgrade paths.
Note If you downgrade to a mesh release, you must then reconfigure the controller. We recommend that you save the configuration from the mesh release before upgrading to release 126.96.36.199 for the first time. Then, you can reapply the configuration if you need to downgrade.
•You cannot downgrade from controller software release 126.96.36.199 to a mesh release (for example, 220.127.116.11, 22.214.171.124M, or 4.1.192.xM) without losing your configuration settings.
•Configuration files are in the binary state immediately after upgrade from a mesh release to controller software release 22.214.171.124. After a reset, the XML configuration file is selected.
•Do not edit XML files.
•Any field with an invalid value is filtered out and set to default by the XML validation engine. Validation occurs during bootup.
•If you upgrade the controller from software release 4.1.191.xM to 4.1.192.xM and then to software release 126.96.36.199, the controller might reboot without a crash file. To work around this problem, manually reset the controller without saving the configuration after you upgrade the controller to software release 188.8.131.52. Also, make sure to check the RRM configuration settings after the reset to verify that they are correct (CSCsv50357).
•If you upgrade the controller from software release 4.1.191.xM to 4.1.192.xM and then to software release 220.127.116.11, the controller might reboot without a crash file. To work around this problem, manually reset the controller without saving the configuration after you upgrade the controller to software release 18.104.22.168. Also, make sure to check the RRM configuration settings after the reset to verify that they are correct (CSCsv50357).
Table 5 Upgrade Compatibility Matrix for Controller Mesh and Nonmesh Releases from 22.214.171.124 release and above
Upgrade to 18.104.22.168 188.8.131.52
Upgrade from
1 You can upgrade directly from software release 18.104.22.168 to 22.214.171.124M; however, upgrading to 220.127.116.11M before upgrading to 184.108.40.206M is highly recommended.
2 Customers who require dynamic frequency selection (DFS) functionality should not use this release. This release does not provide DFS functionality fixes found in release 22.214.171.124. Additionally, this release is not supported in ETSI-compliant countries or Singapore.
3 Release 22.214.171.124 provides fixes for DFS on 1510 series access points. This functionality is needed only in countries where DFS rules apply.
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. Up to 10 access points can be concurrently upgraded from the controller.
Note The 5500 series controllers can download the 22.214.171.124 software to 500 access points simultaneously.
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 18.104.22.168 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.
Note In controller software release 5.2 or later, the WLAN override feature has been removed from both the controller GUI and CLI. If your controller is configured for WLAN override and you upgrade to controller software release 18.104.22.168, the controller deletes the WLAN configuration and broadcasts all WLANs. You can specify that only certain WLANs be transmitted by configuring access point groups. Each access point advertises only the enabled WLANs that belong to its access point group.
Note If a WiSM controller is heavily loaded with access points and clients and is running heavy traffic, a software upgrade sometimes causes an Ethernet receive-path lockup and the hardware watchdog sometimes trips. You might need to reset the controller to return to normal operation.
Note Do not install the 220.127.116.11 controller software file and the 126.96.36.199 ER.aes boot software file at the same time. Install one file and reboot the controller; then install the other file and reboot the controller.
Note When upgrading from 220.127.116.11 to 220.127.116.11 release, access points with names that contain spaces will lose their configured name after the space. For example, if an access point was named "APTestName 12", after upgrade, when the access point rejoins the controller, the name is truncated to "APTestName".
Note If the SSID is associated with a dynamic interface, then the DHCP Option 82 that you configure must be enabled on the dynamic interface. Otherwise, the upgrade may not occur as expected.
To upgrade the controller software using the controller GUI, follow these steps.
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. Otherwise, you must manually reconfigure the controller.
Step 2 Follow these steps to obtain the 184.108.40.206 controller software and the Cisco Unified Wireless Network Controller Boot Software 22.214.171.124 ER.aes file from the Software Center on Cisco.com:
a. Click this URL to go to the Software Center:
b. Click Wireless Software.
c. Click Wireless LAN Controllers.
d. Click Standalone Controllers or Integrated Controllers and Controller Modules.
e. Click a controller series.
f. If necessary, click a controller model.
g. If you chose Standalone Controllers in Step d., click Wireless LAN Controller Software.
h. If you chose Cisco Catalyst 6500 Series/7600 Series Wireless Services Module (WiSM) in Step e., click Wireless Services Modules (WiSM) Software.
i. 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.
j. Click a software release number.
k. Click the filename (filename.aes).
l. Click Download.
m. Read Cisco's End User Software License Agreement and then click Agree.
n. Save the file to your hard drive.
o. Repeat steps a. through n. to download the remaining file (either the 220.127.116.11 controller software or the Cisco Unified Wireless Network Controller Boot Software 184.108.40.206 ER.aes file).
Step 3 Copy the controller software file (filename.aes) and the Cisco Unified Wireless Network Controller Boot Software 22.214.171.124 ER.aes file to the default directory on your TFTP or FTP server.
Step 4 Disable the controller 802.11a and 802.11b/g networks.
Step 5 Disable any WLANs on the controller.
Step 6 Click 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 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 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 into the FTP server.
b. In the Server Login Password text box, enter the password to log into 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 Step 6 to Step 17 to install the remaining file (either the 22.214.171.124 controller software or the Cisco Unified Wireless Network Controller Boot Software 184.108.40.206 ER.aes file).
Step 19 Reenable the WLANs.
Step 20 For Cisco WiSMs, reenable the controller port channel on the Catalyst switch.
Step 21 Reenable your 802.11a and 802.11b/g networks.
Step 22 If desired, reload your latest configuration file to the controller.
Step 23 To verify that the 220.127.116.11 controller software is installed on your controller, click Monitor on the controller GUI and look at the Software Version field under Controller Summary.
Step 24 To verify that the Cisco Unified Wireless Network Controller Boot Software 22.214.171.124 ER.aes file is installed on your controller, enter the show sysinfo command on the controller CLI and look at the Emergency Image Version field.
Note If you do not install the 220.127.116.11 ER.aes file, the Emergency Image Version field shows "N/A."
Installation Notes
This section contains important information to keep in mind when installing controllers and access points.
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 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.
Using the Cisco 5500 Series Controller USB Console Port
The USB console port on the 5500 series controllers connects directly to the USB connector of a PC using a USB Type A-to-5-pin mini Type B cable.
Note The 4-pin mini Type B connector is easily confused with the 5-pin mini Type B connector. They are not compatible. Only the 5-pin mini Type B connector can be used.
For operation with Microsoft Windows, the Cisco Windows USB console driver must be installed on any PC connected to the console port. With this driver, you can plug and unplug the USB cable into and from the console port without affecting Windows HyperTerminal operations.
Note Only one console port can be active at a time. When a cable is plugged into the USB console port, the RJ-45 port becomes inactive. Conversely, when the USB cable is removed from the USB port, the RJ-45 port becomes active.
USB Console OS Compatibility
•Microsoft Windows 2000, XP, Vista (Cisco Windows USB console driver required)
•Apple Mac OS X 10.5.2 (no driver required)
•Linux (no driver required)
To install the Cisco Windows USB console driver, follow these steps:
Step 1 Follow these steps to download the USB_Console.inf driver file:
a. Click this URL to go to the Software Center:
b. Click Wireless LAN Controllers.
c. Click Standalone Controllers.
d. Click Cisco 5500 Series Wireless LAN Controllers.
e. Click Cisco 5508 Wireless LAN Controller.
f. Choose the USB driver file.
g. Save the file to your hard drive.
Step 2 Connect the Type A connector to a USB port on your PC.
Step 3 Connect the mini Type B connector to the USB console port on the controller.
Step 4 When prompted for a driver, browse to the USB_Console.inf file on your PC. Follow the prompts to install the USB driver.
Note Some systems might also require an additional system file. You can download the Usbser.sys file from this URL:
The USB driver is mapped to COM port 6. Some terminal emulation programs do not recognize a port higher than COM 4. If necessary, change the Cisco USB systems management console COM port to an unused port of COM 4 or lower. To do so, follow these steps:
Step 1 From your Windows desktop, right-click My Computer and choose Manage.
Step 2 From the list on the left side, choose Device Manager.
Step 3 From the device list on the right side, double-click Ports (COM & LPT).
Step 4 Right-click Cisco USB System Management Console 0108 and choose Properties.
Step 5 Click the Port Settings tab and click the Advanced button.
Step 6 From the COM Port Number drop-down list, choose an unused COM port of 4 or lower.
Step 7 Click OK to save and then close the Advanced Settings dialog box.
Step 8 Click OK to save and then close the Communications Port Properties dialog box.
Important Notes for Controllers and Nonmesh Access Points
This section describes important information about controllers and nonmesh lightweight access points.
Upgrading to 184.108.40.206 or 188.8.131.52 Can Disrupt DHCP Service When Using Controller's Internal DHCP Feature
Upgrading to controller release 22.214.171.124 or 188.8.131.52 can cause client devices to fail to complete DHCP. To work around this problem, use an external DHCP server, such as a router or a Layer-3 switch. This defect is described in CSCth68708, which is visible in the Bug Toolkit on Cisco.com at this URL:
Additive Licenses Available for 5500 Series Controllers
You can now purchase licenses to support additional access points on 5500 series controllers. The new additive licenses (for 25, 50, or 100 access points) can be upgraded from all license tiers (12, 25, 50, 100, and 250 access points). The additive licenses are supported through both rehosting and RMAs.
One-Time Password (OTP) Support
One Time Passwords (OTP) are supported on the Wireless Lan Controller (WLC) using TACACS and RADIUS. In this configuration, the controller acts as a transparent passthrough device. The controller forwards all client requests to the TACACS/RADIUS server without inspecting the client behavior. When using OTP, the client must only establish a single connection to the controller to function properly. The controller currently does not have any intelligence or checks to correct a client that is trying to establish multiple connections.
RADIUS Called-station-id and Calling-station-id Attributes
In software releases prior to 6.0, the controller sends uppercase alphabetic characters in the MAC address. In software release 6.0 or later, the controller sends lowercase alphabetic characters in the MAC address for the RADIUS called-station-id and calling-station-id attributes. If you enabled these attributes for 802.1X authentication in previous releases and upgrade to software release 6.0, client authentication fails. Therefore, you must change the MAC addresses to lowercase characters on the RADIUS server before upgrading to software release 6.0.
Access Point Groups
You can create up to 50 access point groups for 2100 series controllers and controller network modules and up to 300 access point groups for 4400 series controllers, 500 AP Groups on 5500 Series Controllers, and 192 access point groups for the Cisco WiSM, and the 3750G wireless LAN controller switch.
Using Access Points in Sniffer Mode
You must disable IP-MAC address binding in order to use an access point in sniffer mode if the access point is joined to a 5500 series controller, a 2100 series controller, or a controller network module running software release 6.0. To disable IP-MAC address binding, enter this command using the controller CLI: config network ip-mac-binding disable.
WLAN 1 must be enabled in order to use an access point in sniffer mode if the access point is joined to a 5500 series controller, a 2100 series controller, or a controller network module running software release 6.0. If WLAN 1 is disabled, the access point cannot send packets.
Inter-Release Controller Mobility
When controllers in the mobility list are running different software releases (such as 5.0, 5.1, 5.2, and 6.0), Layer 2 or Layer 3 client roaming is not supported between GD to ED. It is supported only between controllers running the same and GD release such as 6.0 and 4.2.
Guest tunneling works only between controllers running the same software release or between controllers running software release 4.2 and controllers running any later software release (for example, 4.2 to 5.0, 4.2 to 5.1, 4.2 to 5.2, or 4.2 to 6.0). Guest tunneling does not work among controllers running other combinations of software.
RLDP Limitations in This Release
Rogue Location Discovery Protocol (RLDP) is a controller feature that detects the presence of rogue access points that are connected to your wired network. In this software release, RLDP operates with these limitations:
•RLDP detects rogue access points that are configured for open authentication.
•RLDP detects rogue access points that use a broadcast BSSID (that is, the access point broadcasts its SSID in beacons).
•RLDP detects only rogue access points that are on the same network. In other words, if an access list in the network prevents the sending of RLDP traffic from the rogue access point to the controller, RLDP does not work.
•RLDP does not work on 5-GHz dynamic frequency selection (DFS) channels. However, this works when the managed access point is a monitor mode AP on a DFS channel.
Internal DHCP Server
When clients use the controller's internal DHCP server, IP addresses are not preserved across reboots. As a result, multiple clients can be assigned with the same IP address. To resolve any IP address conflicts, clients must release their existing IP address and request a new one.
Bootloader Menu
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 series controllers are different than for other controller platforms.
Bootloader Menu for 5500 Series Controllers
Boot Options
Please choose an option from below:
1. Run primary image
2. Run backup image
3. Change active boot image
4. Clear Configuration
5. Format FLASH Drive
6. Manually update images
Please enter your choice:
Bootloader Menu for Other Controller Platforms
Boot Options
Please choose an option from below:
1. Run primary image
2. Run backup image
3. Manually update images
4. Change active boot image
5. Clear Configuration
Please enter your choice:
Enter 1 to run the current software, enter 2 to run the previous software, or enter 4 (on a 5500 series controller) or 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 Refer to the Installation Guide or Quick Start Guide for your controller for more details on running the bootup script and power-on self-test.
Fragmented Pings
Cisco 5500 series controllers do not support fragmented pings on any interface. Similarly, Cisco 4400 series controllers, the Cisco WiSM, and the Catalyst 3750G Integrated Wireless LAN Controller Switch do not support fragmented pings on the AP-manager interface.
802.11g Controller and 802.11b Clients
When a controller is configured to allow only 802.11g traffic, 802.11b client devices are able to successfully associate to an access point but cannot pass traffic. When you configure the controller for 802.11g traffic only, disable any channels (such as channel 14 in Japan) that allow associations from 802.11b client devices.
CAPWAP Problems with Firewalls and ACLs
If you have a firewall or access control list (ACL) between the controller and its access points that allows LWAPP traffic, before upgrading to software release 5.2 or later and CAPWAP, you should allow CAPWAP traffic from the access points to the controller by opening the following destination ports:
The access points use a random UDP source port to reach these destination ports on the controller. In controller software release 5.2, LWAPP was removed and replaced by CAPWAP, but if you have a new out-of-the-box access point, it could try to use LWAPP to contact the controller before downloading the CAPWAP image from the controller. Once the access point downloads the CAPWAP image from the controller, it uses only CAPWAP to communicate with the controller.
Note After 60 seconds of trying to join a controller with CAPWAP, the access point falls back to using LWAPP. If it cannot find a controller using LWAPP within 60 seconds, it tries again to join a controller using CAPWAP. The access point repeats this cycle of switching from CAPWAP to LWAPP and back again every 60 seconds until it joins a controller.
Note An access point with the LWAPP recovery image (an access point converted from autonomous mode or an out-of-the-box access point) uses only LWAPP to try to join a controller before downloading the CAPWAP image from the controller.
Messages Appearing Upon Controller Bootup
Several messages might flood the message logs when the controller boots up. These messages appear because of a failure to read or delete several different configuration files. These are low-severity messages that can safely be ignored. They do not affect controller functionality. These are some examples:Mar 18 16:05:56.753 osapi_file.c:274 OSAPI-5-FILE_DEL_FAILED: Failed to delete the file : sshpmInitParms.cfg. file removal failed.-Process: Name:fp_main_task, Id:11ca7618Mar 18 16:05:56.753 osapi_file.c:274 OSAPI-5-FILE_DEL_FAILED: Failed to delete the file : bcastInitParms.cfg. file removal failed.-Process: Name:fp_main_task, Id:11ca7618
Web Authentication Redirects
The controller supports web authentication redirects only to HTTP (HTTP over TCP) servers. It does not support web authentication redirects to HTTPS (HTTP over SSL) servers.
Note For 5500 series controllers, 2100 series controllers, and controller network modules, you must configure a preauthentication access control list (ACL) on the WLAN for the external web server and then choose this ACL as the WLAN preauthentication ACL under Security Policies > Web Policy on the WLANs > Edit page.
Cisco 1250 Series Access Points and Cisco 7920 IP Phones
Cisco 1250 series access points are not supported for use with the Cisco 7920 IP phone. They can, however, be used with the Cisco 7921 and 7925 IP phones.
Crash Files for 1250 Series Access Points
The 1250 series access points may contain a bootloader older than version 12.4(10b)JA. Units with old bootloaders do not generate a crash log when a crash occurs. The crash log is disabled so that a crash does not corrupt the flash file system. Units with bootloader versions 12.4(10b)JA or later generate a crash log if the access point is associated to a controller running software release 184.108.40.206 or later.
New 1250 series access points shipped from the factory contain new bootloader images, which fix the flash file system after it is corrupted during a crash (without losing files). This new bootloader automatically sets a new CRASH_LOG environment variable to "yes," which enables a crash log to be generated following a crash but only on controllers running software release 184.108.40.206 or later. Therefore, no user configuration is needed to enable a crash log on new 1250 series access points shipped from the factory.
These examples show the output from the CLI commands (in bold) that you use to check the bootloader version on lightweight and autonomous 1250 series access points:
Commands entered on the controller CLI:
debug ap enable AP001b.d513.1754
debug ap command "show version | include BOOTLDR" AP001b.d513.1754Thu Apr 23 09:31:38 2009: AP001b.d513.1754: BOOTLDR: C1250 Boot Loader(C1250-BOOT-M) Version 12.4(10b)JA, RELEASE SOFTWARE (fc1)
Command entered on the access point CLI:
show version | include BOOTLDRBOOTLDR: C1250 Boot Loader (C1250-BOOT-M) Version 12.4(10b)JA, RELEASE SOFTWARE (fc1)
Configuration File Stored in XML
In controller software release 188.8.131.52 and later, the controller's bootup configuration file is stored in an Extensible Markup Language (XML) format rather than in binary format. When you upgrade a controller to 188.8.131.52 or a later software release, the binary configuration file is migrated and converted to XML.
Note You cannot download a binary configuration file onto a controller running software release 126.96.36.199. Also, do not attempt to make changes to the configuration file. If you do so and then download the file to a controller, the controller displays a cyclic redundancy checksum (CRC) error while it is rebooting and returns the configuration parameters to their default values.
Note You cannot modify the configuration files for 2000, 4000, and 4100 series controllers. The ability to modify configuration files is available in controller software release 5.2 or later, and these controllers support only earlier software releases (up to the 4.2 release for 2000 series controllers and up to the 3.2 release for 4000 and 4100 series controllers).
LWAPP Mode Changes
When you upgrade to controller software release 188.8.131.52 or later, the LWAPP mode changes to Layer 3 if it was previously configured for Layer 2.
If you downgrade from controller software release 184.108.40.206, 188.8.131.52, 18.104.22.168, 188.8.131.52, 188.8.131.52, 22.214.171.124, or 22.214.171.124 to 22.214.171.124 or an earlier release, the LWAPP mode changes from Layer 3 to Layer 2. Access points might not join the controller, and you must manually reset the controller to Layer 3 to resolve this issue.
Access Points Send Multicast and Management Frames at Highest Basic Rate
Access points running recent Cisco IOS versions transmit multicast frames at the highest configured basic rate and management frames at lowest basic mandatory rates, which can cause reliability problems. Access points running LWAPP or autonomous Cisco IOS should transmit multicast and management frames at the lowest configured basic rate. Such behavior is necessary to provide good coverage at the cell's edge, especially for unacknowledged multicast transmissions where multicast wireless transmissions may fail to be received.
Because multicast frames are not retransmitted at the MAC layer, clients at the edge of the cell may fail to receive them successfully. If reliable reception is a goal, then multicast frames should be transmitted at a low data rate. If support for high data rate multicast frames is required, then it may be useful to shrink the cell size and disable all lower data rates.
Depending on your specific requirements, you can take the following action:
•If you need to transmit multicast data with the greatest reliability and if there is no need for great multicast bandwidth, then configure a single basic rate, one that is low enough to reach the edges of the wireless cells.
•If you need to transmit multicast data at a certain data rate in order to achieve a certain throughput, then configure that rate as the highest basic rate. You can also set a lower basic rate for coverage of nonmulticast clients.
Disabling Radio Bands
The controller disables the radio bands that are not permitted by the configured country of operation (CSCsi48220).
802.11a Channels 120, 124, and 128 Disabled
802.11a channels 120, 124, and 128 are disabled to achieve compliance with draft EN 301 893 version 1.5.1 on the following -E regulatory domain products: AP1131AG, AP1242AG, and AP1252AG.
Impact of External Antenna Gain on Transmit Power
In controller software release 4.2 or later, external antenna gain is factored into the maximum transmit power of the access point. Therefore, when you upgrade from an earlier software release to 4.2 or later, you might see a decrease in transmit power output.
Note The Transmit Power level can range between -10 dBM to 30 dBM.
Supporting Oversized Access Point Images
Controller software release 4.2 or later allows you to upgrade to an oversized access point image by deleting the recovery image to create sufficient space. This feature affects only access points with 8 MB of flash (the 1100, 1200, and 1310 series access points). All newer access points have a larger flash size than 8 MB.
Note As of August 2007, there are no oversized access point images, but as new features are added, the access point image size will continue to grow.
The recovery image provides a backup image that can be used if an access point power-cycles during an image upgrade. The best way to avoid the need for access point recovery is to prevent an access point from power-cycling during a system upgrade. If a power-cycle occurs during an upgrade to an oversized access point image, you can recover the access point using the TFTP recovery procedure.
To recover the access point using the TFTP recovery procedure, follow these steps:
Step 1 Download the required recovery image from Cisco.com (c1100-rcvk9w8-mx, c1200-rcvk9w8-mx, or c1310-rcvk9w8-mx) and install it in the root directory of your TFTP server.
Step 2 Connect the TFTP server to the same subnet as the target access point and power-cycle the access point. The access point boots from the TFTP image and then joins the controller to download the oversized access point image and complete the upgrade procedure.
Step 3 After the access point has been recovered, you may remove the TFTP server.
Multicast Queue Depth
The multicast queue depth is 512 packets on all controller platforms. However, the following message might appear on 2106 controllers: "Rx 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 2106.
This message appears when too many multicast messages are sent to the CPU. In controller software releases prior to 5.1, multicast, CDP, and ARP packets share the same queue. However, in software releases 5.1 and later, these packets are separated into different queues. There are currently no controller commands that can be entered to determine if the multicast receive queue is full. When the queue is full, some packets are randomly discarded.
MAC Filtering for WGB Wired Clients
Controller software release 126.96.36.199 or later 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 18.104.22.168 or later, 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. We recommend that you use either dynamic WEP without CKIP (which is less secure) or WPA/WPA2 with TKIP or AES (which are more secure).
Setting the Date and Time on the Controller
Cisco Aironet lightweight access points do not connect to the 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.
Synchronizing the Controller and Location Appliance
For controller software release 4.2 or later, if a location appliance (release 3.1 or later) is installed on your network, the time zone must be set on the controller to ensure proper synchronization between the two systems. Also, we highly recommend that the time be set for networks that do not have location appliances. Refer to Chapter 4 of the Cisco Wireless LAN Controller Configuration Guide, Release 7.0, for instructions for setting the time and date on the controller.
Note The time zone can be different for the controller and the location appliance, but the time zone delta must be configured accordingly, based on Greenwich Mean Time (GMT).
FCC DFS Support on 1130 Series Access Points
Federal Communications Commission (FCC) dynamic frequency selection (DFS) is supported only on 1130 series access points 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. 1130 series access points with FCC DFS support have an FCC ID LDK102054E sticker. 1130 series access points without FCC DFS support have an LDK102054 (no E suffix) sticker. 1130 series access points that are operating in the United States, Canada, or the Philippines; have an FCC ID E sticker; and are running the 126.96.36.199 software release or later can use channels 100 through 140 in the UNII-2 band.
Inaccurate Transmit Power Display
After you change the position of the 802.11a radio antenna for a lightweight 1200 or 1230 series access point, the power setting is not updated in the controller GUI and CLI. Regardless of the user display, the internal data is updated, and the transmit power output is changed accordingly. To see the correct transmit power display values, reboot the access point after changing the antenna's position. (CSCsf02280)
Setting the Retransmit Timeout Value for TACACS+ Servers
We recommend 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:
•2600, 2610, 2611, 2621, 2650, 2651
•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.
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:
•Enable or disable link aggregation (LAG)
•Enable a feature that is dependent on certificates (such as HTTPS and web authentication)
•Add new or modify existing SNMP v3 users
•Install a license, change the license feature set, or change the priority of an AP-count evaluation license on a 5500 series controller
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.
Rate-Limiting on the Controller
Rate-limiting is applicable to all traffic destined to the CPU from either direction (wireless or wired). We recommend 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, we recommend that you reapply the config advanced rate enable command after testing is complete.
Pings Supported to the Management Interface of the Controller
Controller software release 188.8.131.52 or later 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.
GLBP Support
This version of Controller software release 220.127.116.11 is compatible with the Gateway Load Balancing Protocol (GLBP).
4400 Series Controllers Do Not Forward Subnet Broadcasts through the 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.
Connecting 1100 and 1300 Series Access Points
You must install software release 220.127.116.11 or later on the controller before connecting 1100 and 1300 series access points to the controller.
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.
Enabling/Disabling Band Selection and Client Load Balancing
It is not possible to enable or disable band selection and client load balancing globally through the controller GUI or CLI. You can, however, enable or disable band selection and client load balancing for a particular WLAN. Band selection and client load balancing is enabled globally by default.
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 mgmtuser add 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.
RADIUS Servers
This product has been tested with CiscoSecure ACS 4.2 and later and works with any RFC-compliant RADIUS server.
Management Usernames and Local Netuser Names
Management usernames and local netuser names must be unique because they are stored in the same database. That is, you cannot assign the same name to a management user and a local netuser.
Using the Backup Image
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.
Home Page Retains Web Authentication Login with IE 5.x
Because of a caching problem in the Internet Explorer 5.x browser, the home page retains the web authentication login. To correct this problem, clear the history or upgrade your workstation to Internet Explorer 6.x.
Ad-Hoc Rogue Containment
Client card implementations may mitigate the effectiveness of ad-hoc containment.
Changing the Default Values of SNMP Community Strings
The controller has commonly known default values of "public" and "private" for the read-only and read-write SNMP community strings. Using these standard values presents a security risk. Therefore, Cisco strongly advises that you change these values. Refer to the Cisco Wireless LAN Controller Configuration Guide, Release 7.0, for configuration instructions.
Changing the Default Values for SNMP v3 Users
The controller uses a default value of "default" for the username, authentication password, and privacy password for SNMP v3 users. Using these standard values presents a security risk. Therefore, Cisco strongly advises that you change these values. Refer to the Cisco Wireless LAN Controller Configuration Guide, Release 7.0, for configuration instructions.
Note SNMP v3 is time sensitive. Make sure that you have configured the correct time and time zone on your controller.
DirectStream Feature Is Not Supported With WGB
The DirectStream feature from the controller does not work for clients behind workgroup bridges and the stream is denied. This feature is not supported in 7.0 release.
Controller does not Support Transmitting Jumbo Frames
The controller does not support transmitting jumbo frames. To avoid having the WLC transmit CAPWAP packets to the AP that necessitates fragmentation and reassembly, reduces the MTU/MSS on the client side. For example, the TCP MSS Adjust feature can be leveraged here.
Features Not Supported on 2100 Series Controllers
This hardware feature is not supported on 2100 series controllers:
•Service port (separate out-of-band management 10/100-Mbps Ethernet interface)
These software features are not supported on 2100 series controllers:
•VPN termination (such as IPsec and L2TP)
•VPN passthrough option
Note You can replicate this functionality on a 2100 series controller by creating an open WLAN using an ACL.
•Termination of guest controller tunnels (origination of guest controller tunnels is supported)
•External web authentication web server list
•Spanning Tree Protocol (STP)
•Port mirroring
•QoS per-user bandwidth contracts
•IPv6 pass-through
•Link aggregation (LAG)
•Multicast-unicast mode
Features Not Supported on 5500 Series Controllers
These software features are not supported on 5500 series controllers:
•Static AP-manager interface
Note For 5500 series controllers, you are not required 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.
•Asymmetric mobility tunneling
•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.
•Configuration of 802.3 bridging, AppleTalk, and Point-to-Point Protocol over Ethernet (PPPoE)
Note The 5500 series controllers bridge these packets by default. If desired, you can use ACLs to block the bridging of these protocols.
Some Clients See Only 64 Access Point MAC Addresses (BSSIDs) at a Time
In a crowded RF environment, clients may not be able to detect the desired SSID because of internal table limitations. Sometimes disabling and then enabling the client interface forces a rescan. Your RF environment needs to be controlled. Cisco UWN rogue access point detection and containment can help you to enforce RF policies in your buildings and campuses.
2106 Image Not Supported for 3504 Controllers
The 2106 controller image is supported for use with only 2100 series controllers. Do not install the 2106 image on a 3504 controller. Otherwise, errors may occur. Install only the 3504 image on a 3504 controller.
Running a 3504 Image on a 2106 Series Controller
It is possible to run a 3504 controller image on a 2106 series controller, but Cisco Aironet 1130, 1200, and 1240 series access points will not be able to connect to the controller.
Upgrading External Web Authentication
When upgrading a controller from operating system release 2.0 or 22.214.171.124 to release 18.104.22.168 or later, update the external web authentication configuration as follows:
1. For 5500 series controllers, 2100 series controllers, and controller network modules, you must configure a preauthentication access control list (ACL) on the WLAN for the external web server and then choose this ACL as the WLAN preauthentication ACL under Security Policies > Web Policy on the WLANs > Edit page.
2. For 4400 series controllers and the Cisco WiSM, instead of using a preauthentication ACL, the network manager must configure the external web server IP address using this command:
config custom-web ext-webserver add index IP-address
Note IP-address is the address of any web server that performs external web authentication.
3. The network manager must use the new login_template shown here:
Note Make sure to format the script to avoid any extra characters or spaces before using the web authentication template.
<html><head><meta http-equiv="Pragma" content="no-cache"> <meta HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1"> <title>Web Authentication</title> <script>function submitAction(){var link = document.location.href;var searchString = "redirect=";var equalIndex = link.indexOf(searchString);var redirectUrl = "";var urlStr = "";if(equalIndex > 0) {equalIndex += searchString.length;urlStr = link.substring(equalIndex);if(urlStr.length > 0){redirectUrl += urlStr;if(redirectUrl.length > 255)redirectUrl = redirectUrl.substring(0,255);document.forms[0].redirect_url.value = redirectUrl;}}document.forms[0].buttonClicked.value = 4;document.forms[0].submit();}function loadAction(){var url = window.location.href;var args = new Object();var query = location.search.substring(1);var pairs = query.split("&");for(var i=0;i<pairs.length;i++){var pos = pairs[i].indexOf('=');if(pos == -1) continue;var argname = pairs[i].substring(0,pos);var value = pairs[i].substring(pos+1);args[argname] = unescape(value);}//alert( "AP MAC Address is " + args.ap_mac);//alert( "The Switch URL is " + args.switch_url);document.forms[0].action = args.switch_url;// This is the status code returned from webauth login action// Any value of status code from 1 to 5 is error condition and user// should be shown error as below or modify the message as it suits// the customerif(args.statusCode == 1){alert("You are already logged in. No further action is required on your part.");}else if(args.statusCode == 2){alert("You are not configured to authenticate against web portal. No further action is required on your part.");}else if(args.statusCode == 3){alert("The username specified cannot be used at this time. Perhaps the user is already logged into the system?");}else if(args.statusCode == 4){alert("Wrong username and password. Please try again.");}else if(args.statusCode == 5){alert("The User Name and Password combination you have entered is invalid. Please try again.");}}</script></head><body topmargin="50" marginheight="50" onload="loadAction();"> <form method="post"> <input TYPE="hidden" NAME="buttonClicked" SIZE="16" MAXLENGTH="15" value="0"> <input TYPE="hidden" NAME="redirect_url" SIZE="255" MAXLENGTH="255" VALUE=""> <input TYPE="hidden" NAME="err_flag" SIZE="16" MAXLENGTH="15" value="0"><div align="center"><table border="0" cellspacing="0" cellpadding="0"> <tr> <td> </td></tr><tr align="center"> <td colspan="2"><font size="10" color="#336699">Web Authentication</font></td></tr><tr align="center"><td colspan="2"> User Name <input type="TEXT" name="username" SIZE="25" MAXLENGTH="63" VALUE=""> </td> </tr> <tr align="center" > <td colspan="2"> Password <input type="Password" name="password" SIZE="25" MAXLENGTH="24"> </td> </tr><tr align="center"><td colspan="2"><input type="button" name="Submit" value="Submit" class="button" onclick="submitAction();"> </td> </tr> </table> </div></form></body></html>
Switch Port and Controller Port
When the port status on the controller changes, the switch status does not get changed. This is a known issue. For example, when the controller port goes down, the switch port is still in administrable state. This has been resolved in Cisco 5500 Series Controllers.
Issues With mac-address CLI for Unified and Autonomous Access Points
The unified and autonomous access point do not support the mac-address command for the wireless interfaces. When invoked, the command executes, but can cause the access point to fail.
Default A-MPDU settings
By default, Aggregated MAC Protocol Data Unit (A-MPDU) is enabled for priority level 0, 4 and 5 and the rest are disabled. In releases prior to 6.0 release, only priority 0 was enabled by default. The video performance is enhanced when priorities 4 and 5 are enabled for A-MPDU aggregation.
The following sections lists Open Caveats and Resolved Caveats for Cisco controllers and lightweight access points for version 18.104.22.168. 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 may be standardized.
•Spelling errors and typos may be corrected.
Note If you are a registered cisco.com user, view Bug Toolkit on cisco.com at the following website:
To become a registered cisco.com user, go to the following website:
Open Caveats
For open caveats, refer to the Release Notes for Cisco Wirless LAN Controllers and Lightweight Access Points for Release 126.96.36.199.
Resolved Caveats
Table 6 lists caveats resolved in controller software release 126.96.36.199.
Table 6 Resolved Caveats
ID Numbers Caveat Title
The default group for ap-groups does not contain all SSIDs
There are several inconsistencies of MAC address on WLC
Web-Auth: Web page takes a long time to display under a heavy load
Controller crashes at sshpmMainTask under high web-auth load conditions
AP1230 Malloc failure with tracebacks
After a bad UN is used, the LDAP server does not functional for 15 minutes
WiSM is unreachable outside of Catalyst 6500 Series Switch
The WLC 5500 DP CRASH: Hardware is deadlocked when all Packet Buffers are in use
Wrong BSSID in reassoc resp during intra-wlc roaming if CAC/CCKM fails
The WLC stops responding to network
LAG fail-over does not work on CT5508
Access Points acknowledges on incorrect phone
Crash accessing 0xfefefefc while logging
MFP - Invalid MIC error due to held beacons on the radio
Clients with a Static IP address may get stuck in DHCP_REQD state
Clients are unable to get a DHCP offer from WLC internal DHCP scope
Increase the maximum IGMP timeout from 5 minutes to 2 hours
WLC kernel hang up followed by flash issue and the WLC does not reboot
Intermittent webauth page with HREAP local switching
Switch CAM table is not updated after L2 roam
WLC 5508 drops TCP and UDP packets
CT4404 crashes when changing global ap username and password.
CT5508 crashes when trying to shut the data ports one by one
AP radio resets when moving between WLCs with different mobility names
WLC crashes while executing the debug hreap aaa event command
Passive clients are unable to pass traffic on 5500 while working on 4400 Series Controllers
WLC 5500 sees low throughput for small packet size frames
MAC based debugging is not working for WLC 5500
With 1G load to CP IP addr crash occurs with heartbeat loss
WLC is not releasing the BIND for the 1st LDAP and the next user fails auth
WLC with Web-auth users may go unreachable or fails to redirect the client
WLC dataplane core fails to respond due to memory corruption
Fragemented mcast pkts get dropped ( MCAST Packet Corruption)
Radius accounting stop packets are sent to the wrong AAA server
5508: WLC is forwarding traffic on incorrect VLAN in AP-group setup
Crash when stress testing CSCth68708
11r IE should be removed from open auth reassociation response
WLC5508 does not allow RIPv2 updates through
WLC5500 crash with certain multicast-unicast traffic
Enhancement: add flexibility for CCKM max timestamp validation
Anchor GW failover breaks guest client traffic
WLC 4402 (SW 126.96.36.199) crash with "Out of Memory" and "mwar_exit.crash"
Memory leak sshpm, on sshencode. line 252
WGB VLAN client support control
Clients are mapped to the native VLAN of the h-reap AP switchport trunk
1250 AP cannot negotiate PoE through CDP with dot1x enabled on the port
AP 1131 stops responding to Polycom phone
AP may crash during rate shift operation
Radio may stop transmitting for several seconds due to MSDU packet load
11n APs stop transmitting and receiving with spike in noise/interference
Hreap Central Switching TCP Performance Better Than Local Switching
Bad client issue with mix 11a/n video clients.
Multicast traffic stops after fast roaming - incorrect AP client count
Controller GUI shows incorrect channel assignment for client access
Native VLAN configuration is not consistent in HREAP
Association fails on H-REAP AP when client changes SSID
Wrong power unit was used on AIR-AP1231G-A-K9 and AIR-AP1220-IOS-UPGRD.
Multicast packets stuck on radio forever, after WLAN changes
3500 series AP crash - process capwap client - memory error
Unified APs removing clients on maximum retries.
AP error due to process_execute; unexpected exception to CPUvector
C1130 core dump: Radio command cmd 21 (FF50,0,0) status 7F17
AP crashes in disc_tx_unqueue function under heavy load
AP stops send/ack for 20-500ms to new Polycom phone
unified ap not clearing capwap mn state correctly
Duration field change for AP3500
AP violating block ack agreement causes the client to drop frames
WLC is leaking unencrypted frames for WGB clients
If You Need More Information
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:
(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.)
For the most up-to-date, detailed troubleshooting information, refer to the Cisco TAC website at
Click Product Support > Wireless. Then choose your product and Troubleshooting to find information on the problem you are experiencing.
Documentation Updates
This section lists updates to user documentation that has not yet been added to either printed or online documents.
The Package Contents section in the Quick Start Guide: Cisco 4400 Series Wireless LAN Controllers should be updated to include this item, which is included with the 4400 series controller:
•DB-9-to-DB-9 null modem cable
Related Documentation
For additional information on the Cisco controllers and lightweight access points, refer to 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 Control System Configuration Guide
You can access these documents from this link:
Obtaining Documentation and Submitting a Service Request
For information on obtaining documentation, submitting a service request, and gathering additional information, see the monthly What's New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation, at:
Subscribe to the What's New in Cisco Product Documentation as a Really Simple Syndication (RSS) feed and set content to be delivered directly to your desktop using a reader application. The RSS feeds are a free service and Cisco currently supports RSS Version 2.0.
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: www.cisco.com/go/trademarks. Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1110R)


text:
Mapping Identity
Mapping Identity, an exhibition of works by 11 international artists co-curated by Visiting Associate Professor Carol Solomon and Haverford senior Janet Yoon, will run in the College's Cantor Fitzgerald Gallery March 19-April 30, 2010. An opening lecture will be held March 19, 4 p.m. in Sharpless Auditorium followed by a reception at the Gallery.
The exhibit will open with a lecture by the renowned Ghanaian philosopher and Princeton professor Kwame Anthony Appiah entitled "Cosmopolitanism," Friday, March 19 at 4 p.m. in Sharpless Auditorium of the Koshland Integrated Natural Sciences Center, immediately followed by a reception in the Gallery at 5:30 p.m.
About the Exhibit:
Mapping Identity explores aspects of contemporary cultural identity and the effects of displacement, exile, transnationalism, hybridity, cosmopolitanism, and the state of the in-between, described by the curators as "that liminal space which characterizes the unmoored condition experienced by an increasing number of people in our transient world."
Paintings, prints, photographs, videos and sculpture by the following artists will be included: Fariba Alam (American/Bangladeshi), Zoulikha Bouabdellah (French/Algerian), María Magdalena Campos-Pons (Cuban/Nigerian/American), Lalla Essaydi (Moroccan/American), Gonkar Gyatso (Tibetan/British), Mona Hatoum (British/Palestinian), Glenn Kaino (American/Japanese), Daniel Kojo Schrade (German/Ghanaian), Zineb Sedira (French/Algerian), Shahzia Sikander (Pakistani/American), and Do-Ho Suh (Korean).
The exhibition takes place in conjunction with Professor Solomon's Haverford course "Art and Cultural Identity", which is being taught this spring.
Related Events:
- A Conversation with Tibetan Artist Gonkar Gyatso, followed by an International Food Fair Reception Tuesday, March 23 at 4:30 p.m. in the Cantor Fitzgerald Gallery.
- Gallery Talks by exhibition curator Janet Yoon '10 Sunday, March 21 at 2 p.m. and Tuesday, April 13 at 4 p.m.
- Gallery Talks by students in Art and Cultural Identity Wednesday, April 14 and Wednesday, April 21 at 2 p.m.
Support for the exhibition and related programs has been generously provided by the John B. Hurford '60 Humanities Center, the Center for Peace and Global Citizenship, Haverford President Steve Emerson, the Paul J. R. Desjardins Colloquium Fund, the Distinguished Visitors Program, the Margaret Gest Program, and the Office of Multicultural Affairs. Funding for artist talk supported by the John B. Hurford '60 Humanities Center's grant from the Leaves of Grass Foundation.
Visit the Mapping Identity Blog >
Overseen by the John B. Hurford '60 Humanities Center and located in Whitehead Campus Center, the Cantor Fitzgerald Gallery is open Monday-Friday 11 a.m.-5 p.m., Saturdays and Sundays 12-5 p.m., and Wednesdays until 8 p.m. For more information, contact Matthew Seamus Callinan, Campus Exhibitions Coordinator, at (610) 896-1287 or firstname.lastname@example.com.

subset: commoncrawl


text:
One of the most popular foods in the world is pizza, and restaurants (like my favourite Lorentto WoodFire Pizza on Bondi Road) that service this great food find financial success. However, when it comes to serving this delicious food, there are two ways that pizza can be cooked, and those two ways are either in regular pizza ovens or a wood fire pizza ovens. People who find out that pizza has different cooking methods may wonder just why people would want to use a pizza oven that relied on burning wood, and here is more information about the pros and cons of using a wood fire pizza oven.
Any food that is cooked with wood has a very unique taste, and some restaurants even specialize in the fact they have the majority of their dishes cooked in this way. The food cooked with the heat provided by wood has a smoky taste, and some food, like pizza, really comes out great cooked in this manner.
There is a safety issue, and there are some states that will not allow for restaurants to use wood fire pizza ovens anymore due to the concern of a wayward spark landing in the wrong place and causing a fire.
People are into eating a naturally as possible, and even go so far as to only eat food prepared in a certain way. The ovens that rely on wood chunks for heat use the fire from burning wood to cook the food, and that is just how some people like it because the wood is more natural than using electricity or gas.
The price of wood can be high, so restaurants that have wood fire pizza ovens have to buy a certain amount of wood in order to serve their customers. Buying wood every week can get quite expensive, which is going to eat into their profits, and they will have to charge more for those special wood fire cooked dishes.
Australians eat millions of pizzas every year, and one of the most popular ways to cook it is with a wood fire pizza oven. These special pizza ovens require large amounts of wood to be burned into order to generate the heat to cook food, and the food that is cooked this way can have a unique smoky taste that people really love. There are pros and cons to this kind of oven, and restaurants should weigh them both before deciding to buy an oven for their kitchen.
To lear more visit: http://chowhound.chow.com/topics/716758


text:
Robert Gibbs was White House Press Secretary from President Obama's inauguration until February 2011. Gibbs held the position of Communications Director for Obama's presidential campaign until becoming Senior Strategist for Communications and Message during the general election.
Gibbs, a native of Auburn, Alabama and a graduate of North Carolina State University, began working with President-elect Obama in April 2004 serving as Communications Director for his United States Senate race and later as his Senate Communications Director. Earlier in his career, Gibbs served as Communications Director for Senator Fritz Hollings and worked on Senator Debbie Stabenow's 2000 Senate campaign. He also served as press secretary for the Democratic Senatorial Campaign Committee and worked for Senator John Kerry's presidential campaign. Gibbs lives in Alexandria, Virginia with his wife, Mary Catherine, and their five-year-old son, Ethan.
This weekend, experts from the Office of the U.S. Trade Representative are in Seattle, Washington, hammering out the legal language for the landmark trade agreement President Obama announced earlier this month: improvements on the US-Korea trade deal that make the pact better for American workers and businesses, particularly in our recovering auto sector.
White House Press Secretary Robert Gibbs on the ongoing efforts in response to the severe weather and flooding in Tennessee and across the Southeast.
Press Secretary Robert Gibbs provides another update on the response to the BP spill in the Gulf of Mexico.
Press Secretary Robert Gibbs discusses the coordinated response to the BP Oil Spill. [Uppdated.]
Declaraciones del Presidente sobre el terremoto en Chile.
The President made the following statement on the earthquake in Chile and preparations for a possible tsunami that could reach American shores later today. (Includes links to more information and resources.)
A brief post from White House Press Secretary Robert Gibbs.
Assistant to the President and Deputy National Security Advisor for Strategic Communications and Speechwriting


text:
Report: Kimbo Slice vs. Roy Jones Jr PPV bout in Jamaica is in the works
Report: Kimbo Slice vs. Roy Jones Jr PPV bout in Jamaica is in the works - Mixed Martial Arts NewsIn what feels like an implausible scenario, a Jamaica based newspaper is reporting that a bout between boxing great Roy Jones Jr, and Kimbo Slice is in the works. The proposed bout is reported to be in Jamaica in December, and will be on Pay Per View in the United States.
They even gave Kimbo Slice (a nickname) another nickname - The Street Fighter. Kevin "Kimbo "The Streetfighter" Slice" Ferguson is a little awkward. In truth, technically Kimbo Slice in an AKA rather than a ring name, which makes it a little less absurd, but still, do not be shocked if the bout does not come to pass.
With local boxing slowly regaining its vibrancy, Giomax Entertainment company and Stewart's Auto Sales have combined in an effort to take the sport to another level with an exciting exhibition bout featuring the enigmatic veteran boxing star Roy 'Superman' Jones and streetfighter turned professional boxer, Kimbo 'The Streetfighter' Slice.
The fight, labelled 'Beauty and the Beast', will take place in Montego Bay in December, it was announced at a launch at the Spanish Court Hotel on Thursday evening.
Lawyer Lewis Hanna, who has been helping to tie up the deal, noted that this unique fight was organised as a part of Jamaica's 50th anniversary celebrations.
He noted that all the details for the fight are yet to be finalised, but he expects a conclusion soon.
Hanna said this was not a one-off fight and the promoters will be looking to stage other interesting fight cards on the island.
"We want to forge a relationship going forward and not just with one fight... so you can look forward to seeing more fights, whether it's Roy himself fighting or helping young men get opportunities. But the aspiration is to have a lot more fights, at least one a year in Jamaica," he said.
Hanna thinks the December fight will have a tremendous impact on the sport locally, and that Jones, one of the best boxers of the modern era, will thrill boxing fans.
Jones will face a daunting opponent in Kimbo Slice.
The 234-pound, six-footer Slice was a very popular streetfigher since 2003.
However, after some disappointments, the Bahamian-born slugger switched to professional boxing last year and has scored five consecutive wins, four by knockout.
Both fighters had an interest to fight each other for some time, but 'Superman' had said he wanted to wait until Slice gained experience and exposure in the sport.
Now the two have been contracted by Giomax and Stewart's Auto in what is expected to be a blockbuster pay-per-view event in America.
And although Jones acknowledged that his opponent was bigger and stronger than he was, he says his experience and know-how as a boxer will even things up.
"He's a big streetfighter with a lot of power, so early in the fight he can be very dangerous... but as the fight goes on, my mental experience should take over. But for the first five rounds he will be very deadly," Jones said at Thursday's event.


text:
USM Campus Ventures
A Model for Innovation in Experiential Education
Campus Ventures is an innovative experiential education program for students of the University of Southern Maine, built on the premise that engaged learning is fundamental to career readiness and student success. The Campus Ventures project-based learning model engages students in relevant, real-world projects starting as early as their first year at USM, with several documented learning outcomes:
- Technical skill development
- Direct knowledge transfer from theoretical/academic to applied scenarios
- Leadership, teamwork, communication, and soft-skill development
- Project management and delivery
In three and half years, the program has consistently demonstrated repeatability, scalability, continuing success, and accolades from community partners. The program enjoys a thriving relationship with key external partners in Maine's technology & entrepreneurial communities.


text:
Chamber of Commerce discusses area's business future
When Tom Snell was chairman of the Sanford Area Chamber of Commerce's board of directors last year, he wanted it to focus on being four C-words: convener, challenger, communicator and cheerleader. As Brad Simpson takes over the top spot this year, he's looking to add a fifth word: competitor.
Simpson said at a dinner Thursday night that Lee County's resources — resources as varied water access, quality schools and human capital — give the county and its businesses the chance to become a competitor not just in the state or the South, but globally.
"But we must work together," Simpson said. "We cannot afford to continue pursuing divided agendas."
Simpson and Snell made their remarks at the Chamber's annual Membership Meeting and Fundraiser, which had a small yet lively crowd as CEOs clinked wine glasses with politicians and veterans compared the medals pinned to their tuxedos and swapped stories.
Several dozen people from the local business community — bankers, manufacturers, communications specialists, doctors and more — came out to support the Chamber, as did representatives of Lee County Schools and the governing bodies of Sanford, Broadway and Lee County. Sen. Ronald Rabin, who represents Harnett, Lee and parts of Johnston counties, was also in attendance.
The focus of Simpson's speech was on talks surrounding the merger of the Chamber and the Lee County Economic Development Corporation. He said that in the past, thanks to a number of public and private voices promoting businesses in Sanford and Lee County, the message had become muddled and the approach had become inefficient. But with increased collaboration between the groups — which is being actively encouraged by the Lee County Board of Commissioners — Simpson said the voice of business supporters in Lee County will become notably less fragmented.
Noting that individual businesses can't operate as they did five or 10 years ago because of the financial crisis, he said it's also time for business cheerleaders — to use one of Snell's terms — to reevaluate their methods. He said he welcomes input on how the local business community can be more competitive, how it can increase the quality of education and how it can continue to make Lee County a more attractive place for both businesses and people to move. But that can't be done entirely by the private sector, he said.
"This entity will have the weight of our business community behind it," Simpson said. "It must also have the weight and support of our governments. ... They must do their part."