Manualshelf

Release Notes

ManualsBrandsCisco ManualsWLAN access pointsCisco 2106 Wireless LAN Controller
12345678910
Americas Headquarters:
Cisco Systems, Inc., 170 West Tasman Drive, San Jose, CA 95134-1706 USA
Release Notes for Cisco Wireless LAN
Controllers and Lightweight Access Points for
Release 4.2.176.0
November 21, 2008
These release notes describe open and resolved caveats for software release 4.2.176.0 for Cisco 2000,
2100, and 4400 Series Wireless LAN Controllers; Cisco Wireless Services Modules (WiSM); Cisco
Wireless LAN Controller Network Modules; Catalyst 3750G Integrated Wireless LAN Controller
Switches; Cisco 3201 Wireless Mobile Interface Cards (WMICs); and Cisco Aironet 1000, 1100, 1130,
1200, 1230AG, 1240, 1250, and 1300 Series Lightweight Access Points, which comprise part of the
Cisco Unified Wireless Network (UWN) Solution.
Note Unless otherwise noted, all of the Cisco wireless LAN controllers are hereafter referred to as controllers,
and all of the Cisco lightweight access points are hereafter referred to as access points.
Contents
These release notes contain the following sections.
• Cisco Unified Wireless Network Solution Components, page 2
• Controller Requirements, page 3
• Software Release Information, page 3
• Installation Notes, page 7
• Installation Notes, page 7
• Important Notes, page 10
• Caveats, page 23
• Troubleshooting, page 42
• Documentation Updates, page 42

Summary of content (44 pages)

Caveats This section lists Open Caveats and Resolved Caveats for Cisco controllers and lightweight access points. Open Caveats These caveats are open in controller software release 4.2.176.0. • CSCsb77595—When logging out from Telnet/SSH sessions, the session always prompts the user to save changes, even when no changes have been made.

  • PAGE 24

    Caveats • CSCsg66040—After a software upgrade, controllers might experience intermittent access to the management interface through HTTPS. Workaround: Follow these steps to workaround the issue: a. Make sure HTTPS is enabled on the controller’s management interface, reboot the controller from the CLI, and monitor the last service if error messages appear after the controller prompts you to enter a username and password to login. b.

  • PAGE 25

    Caveats Workaround: Configure a larger value for the controller database, such as 2048. • CSCsg95474—Lightweight access points do not queue disassociation messages, causing the Cisco 7921 phone to remain in a registering loop. This problem occurs when you change the data rate on the access point. Workaround: Power cycle the 7921 phone. • CSCsh11086—If you press Ctrl-S and Ctrl-Q to pause and restart the output of a command such as debug dot1x event enable, the controller reboots.

  • PAGE 26

    Caveats Workaround: Change the WLAN QoS profile on both the internal controller and the anchor controller to silver. • CSCsi72767—A script runs each time you generate a dependency file, which makes the build very slow. Workaround: None. • CSCsj03124—RLDP behavior is inconsistent when initiated from a Cisco 1250 series access point. Workaround: Use access points other than the 1250 when RLDP needs to be used.

  • PAGE 27

    Caveats • CSCsj61649—Whenever a log analysis report is generated on a CCXv5 client using WCS, the DHCP and AAA logs are swapped. Workaround: Use the controller CLI to view this information. • CSCsj67447—When you use the controller GUI to modify an existing (or newly created) guest LAN and you choose an ingress interface that is already in use, no error appears. The error that appears on the CLI should also appear on the GUI: “Ingress interface is in use by some other guest lan.” Workaround: None.

  • PAGE 28

    Caveats • CSCsk17001—When a guest LAN with a blank ingress interface name is added to the controller, the application fails with an SNMP exception message. Workaround: Use the controller CLI to configure a guest LAN. You might need to delete a previous guest LAN if it has a blank ingress interface configured on it and then recreate it. By default, the ingress interface is blank. • CSCsk22861—An MGID entry is not cleared from the access point when IGMP snooping is disabled. Workaround: None.

  • PAGE 29

    Caveats • CSCsk86536—The wrong error message appears when you change country channels with the 802.11a radio enabled. Workaround: None. • CSCsl01005—Sometimes bandwidth contracts do not take effect. If a user who has bandwidth restrictions logs in and logs out and then another user who does not have bandwidth restrictions logs in, the bandwidth restrictions are not removed immediately. Workaround: Reassociate the user between logout of the old user and login of the new user.

  • PAGE 30

    Caveats • CSCsl47720—The link test report for a CCX client generated using the controller GUI does not provide enough information. Workaround: Use the controller CLI. It always provides the correct link test report, except in cases of a CCX client connected to a hybrid-HREAP access point broadcasting a centrally switched WLAN. • CSCsl48639—An IP address can be configured on a dynamic interface on a controller when that IP address has already been assigned to another device on the network.

  • PAGE 31

    Caveats Workaround: Install the Cisco Unified Wireless Network Controller Boot Software 4.2.112.0 ER.aes file, which contains a new bootloader. A successful transfer and upgrade of the ER file indicates that the ER file has been updated properly. • CSCsm08623—If the config paging disabled CLI command is entered on the controller, the output of the show msglog command is periodically interrupted with the “Would you like to display the next 15 entries?” prompt. Workaround: None.

  • PAGE 32

    Caveats • CSCsm40903—Additional information is needed for the following message: “claspam_lrad.c:1626 LWAPP-6-PORTMAP_ERR: Failed to obtain multicast port map for interface 4, using default index (50).” Workaround: None. • CSCsm40906—The following message appears on the 2106 controller when multicast is disabled: “claspam_lrad.c:1626 LWAPP-6-PORTMAP_ERR: Failed to obtain multicast port map for interface 4, using default index (50).” No multicast messages should appear when multicast is disabled.

  • PAGE 33

    Caveats Workaround: None. • CSCsm95478—HT protection bits might incorrectly report the operating mode. Workaround: None. • CSCsm96105—The controller does not pass traffic to a client device with a MAC address beginning with 00:00:00:00. This issue occurs with both WGB and wireless clients. Workaround: None. • CSCsm98659—The clcCdpGlobalEnable SNMP variable cannot be set on the controller unless there is at least one access point present on the controller.

  • PAGE 34

    Caveats • CSCso66183—Symbol Vocollect devices might disassociate from Cisco 1240 series access points and display the following error message: "3/30/2008 04:42" Error " Mar 30 04:47:25.626 spam_api.c:816 WAPP-3-MAX_AID: Reached max limit (200) on the association ID for AP 00:1d:a1:90:11:10" "3/30/2008 04:42" Error " Mar 30 04:47:21.703 spam_api.c:816 WAPP-3-MAX_AID: Reached max limit (200) on the association ID for AP 00:1d:a1:90:11:10" Workaround: Manually power-cycle the access points.

  • PAGE 35

    Caveats Workaround: Use the controller CLI to edit the guest user’s parameters. • CSCsq22518—CCKM clients using WPA2 reauthenticate when moving between hybrid-REAP access points. Workaround: None. • CSCsq22827—The access point name sometimes disappears from the controller GUI and CLI. Workaround: None. • CSCsq23594—When a CCXv5 request is manually sent to a CCXv5 client, an emergency log message is written to the log and sent to any configured syslog servers. Workaround: None.

  • PAGE 36

    Caveats • CSCsq35590—If you change a 1240 series access point’s country of operation from Spain to the U.S., tracebacks might occur while the access point joins the controller. Workaround: None. • CSCsq37810—If you add a controller to WCS and later reboot the controller, WCS does not receive the trap for a cold start, which prevents it from pushing the configuration back to the controller. Workaround: Manually push the configuration from WCS.

  • PAGE 37

    Caveats • CSCsr44439—The web authentication page does not load on the browser when the client connects through a wired guest VLAN on a controller running software release 4.2.130.0. Workaround: None. • CSCsr45163—When IPv6 clients move from an access point group or VLAN to a new access point group or VLAN, they lose connectivity because all traffic is forwarded to the old VLAN. Workaround: Configure the clients with a static IPv6 address.

  • PAGE 38

    Caveats • CSCsr83307—A configuration file that is uploaded with an encryption key can be downloaded without the encryption key. Workaround: None. • CSCsr83671—The auto-RF feature on a Cisco WiSM or 4400 series controller sets 1130 and 1240 series access points to channel 36 for the 5-GHz band (802.11a). Workaround: Follow these steps to work around the issue: a. To change the sensitivity level, enter this command: config advanced 802.11a channel dca sensitivity high b.

  • PAGE 39

    Caveats • CSCsu07730—When you try to configure a network address for the AP-manager on a 4400 series controller, an “Invalid IP” error message sometimes appears. Workaround: None. • CSCsu11528—The 4400 series controllers might drop very large (usually greater than 6000 bytes) UDP and ping frames sourced from a wired node on the Ethernet and originating at 1-Gbps line rate. Workaround: Drop the line rate to 100 Mbps, decrease the size of UDP or ICMP frames, or use a different brand of wired client card.

  • PAGE 40

    Caveats • CSCsu52812—When the controller is in multicast-unicast mode, it sends unicast traffic to an access point before that access point has fully joined the controller. This behavior can be a serious problem when the access point is running a recovery image like 12.3(11)JX1, which does not drop LWAPP data packets. If the number of data packets sent to the access point before it receives the full image is large enough, the access point locks up and cannot join the controller.

  • PAGE 41

    Caveats • CSCsu84220—When Cisco 1131 and 1242 access points are joined to a controller running software release 4.2.130.0 and a WAN outage occurs, the access points come back up, but sometimes the radios do not. Workaround: Reboot the access points. • CSCsu84498—The transmit diversity for multicast-broadcast packets is not alternating on the 1240 series access point’s antenna ports. Workaround: None.

  • PAGE 42

    Troubleshooting • CSCsv34605—An access point using the Rogue Location Detection Protocol (RLDP) does not receive a DHCP address if the DHCP server is on an autonomous access point. As a result, RLDP does not detect if the rogue access point is on the wire. Workaround: None. Resolved Caveats These caveats are resolved in controller software release 4.2.176.0. • CSCsr67250—1250 series access points do not adjust their power levels correctly and always stay on Tx Power Level 1 or 2.

  • PAGE 43

    Related Documentation Related Documentation For additional information on the Cisco controllers and lightweight access points, refer to these documents: • The quick start 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 Click this link to browse to the Cisco Support and Documentation page: http://www.cisco.com/c/en/us/support/index.

  • PAGE 44

    Obtaining Documentation, Support, and Security Guidelines Release Notes for Cisco Wireless LAN Controllers and Lightweight Access Points for Release 4.2.176.