Cisco Cisco 2106 Wireless LAN Controller Release Notes
30
Release Notes for Cisco Wireless LAN Controllers and Lightweight Access Points for Release 4.1.181.0
OL-31336-01
Caveats
•
CSCsf02280—If you change the position of the antenna on an autonomous AP1200 converted to
lightweight mode, the power setting does not change.
lightweight mode, the power setting does not change.
Workaround: None.
•
CSCsf99924—In controller software releases 3.2.183.0 and later, you cannot configure the
controller to automatically adjust its local time for daylight saving time (DST). This feature was
available in earlier software releases, but it did not correctly adjust the time in the Southern
Hemisphere and did not respond to the daylight saving time changes for the United States in 2007.
controller to automatically adjust its local time for daylight saving time (DST). This feature was
available in earlier software releases, but it did not correctly adjust the time in the Southern
Hemisphere and did not respond to the daylight saving time changes for the United States in 2007.
Workaround: Follow these steps to work around this issue:
a.
Configure the controller for Greenwich mean time (GMT), with no time-zone offset.
b.
During standard time, run with the standard offset.
c.
When DST goes into effect, manually configure the controller for the correct local time.
For example, if your controller is in the U.S. Eastern time-zone, then before March 11, 2007,
your offset is –5. When DST takes effect, enter this CLI command: config time timezone -4.
your offset is –5. When DST takes effect, enter this CLI command: config time timezone -4.
•
CSCsg22915—Multicast packets from mobile clients with the access point group multicast address
are not dropped at the controller when multicast mode is set to mcast.
are not dropped at the controller when multicast mode is set to mcast.
Workaround: Make sure the multicast stream address and the access point group multicast address
are different.
are different.
•
CSCsg32646—If link aggregation (LAG) is enabled on the controller and the port channel is
configured on the infrastructure switch, the controller displays only a single entry for its neighbor
when you enter the sh cdp neighbor CLI command. When you enter the same command on the
switch, it displays two entries for the controller for two different ports that are part of LAG. The
controller should display two entries when the command is entered on the controller because the
switch sends the CDP message from two different ports that are part of the port channel.
configured on the infrastructure switch, the controller displays only a single entry for its neighbor
when you enter the sh cdp neighbor CLI command. When you enter the same command on the
switch, it displays two entries for the controller for two different ports that are part of LAG. The
controller should display two entries when the command is entered on the controller because the
switch sends the CDP message from two different ports that are part of the port channel.
Workaround: None.
•
CSCsg35690—The SNMP client troubleshooting buffer wraparound does not work in cases where
the number of messages exceed 2,000.
the number of messages exceed 2,000.
Workaround: Delete the client from the watchlist and then re-add it to the watchlist for the messages.
•
CSCsg48056—In certain cases, disabling the DHCP proxy causes a mesh access point to be
perceived as a client instead of an access point. Because the access point does not satisfy the
“Associated” state for a client, the DHCP server refuses to hand out an IP address to the access point.
perceived as a client instead of an access point. Because the access point does not satisfy the
“Associated” state for a client, the DHCP server refuses to hand out an IP address to the access point.
Workaround: Do not disable the DHCP proxy for mesh access points. Use this command to enable
DHCP proxy: config dhcp proxy enable.
DHCP proxy: config dhcp proxy enable.
•
CSCsg60778—When background scanning is enabled, it may cause temporary backhaul congestion,
which can result in voice packet loss and jittery voice traffic.
which can result in voice packet loss and jittery voice traffic.
Workaround: Turning off background scanning can alleviate this problem to some extent. However,
if the packet loss and the jittery voice traffic are due to RF issues, then changing the RAP to a
different channel may help.
if the packet loss and the jittery voice traffic are due to RF issues, then changing the RAP to a
different channel may help.
•
CSCsg74578—If you change a controller's management IP address, it is not sent to the access point
unless the access point is reset. As a result, multicasting does not work until the change is made on
the access point.
unless the access point is reset. As a result, multicasting does not work until the change is made on
the access point.
Workaround: None.
•
CSCsg76946—Cisco 3201 WMIC data throughput may be affected when using TKIP encryption.
Workaround: Use AES encryption or 802.1x dynamic keys.