Cisco Cisco 2106 Wireless LAN Controller
48
Release Notes for Cisco Wireless LAN Controllers and Lightweight Access Points for Release 4.2.207.0
OL-31336-01
Caveats
•
CSCsy98796—The controller web authentication Login Success page does not show the logical
DNS name for the virtual interface when configured.
DNS name for the virtual interface when configured.
Workaround: Use the raw IP address link provided by the Success page for the logout.html call if
needed.
needed.
•
CSCsz03162—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.
are able to successfully associate to an access point but cannot pass traffic.
Workaround: 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.
as channel 14 in Japan) that allow associations from 802.11b client devices.
•
CSCsz09498—When client devices trigger the auto-immune code on a controller, it can be difficult
to determine how exactly the client device violated the auto-immune rules.
to determine how exactly the client device violated the auto-immune rules.
Workaround: None.
•
CSCsz25704—The VLAN and IP values are sometimes swapped in DHCP-4-INVALID_VLANID_
ARP system messages.
ARP system messages.
Workaround: None.
•
CSCsz50249—Access points in local mode, connected to a controller running software release
4.2.130.0 or later, sometimes send 802.11g extended supported rate information elements,
regardless of the supported rates on the client. The access point sends the information elements only
when 802.11g is enabled on the network. However, hybrid-REAP access points never send 802.11g
extended supported rate information elements. To be consistent with access points in local mode,
they should.
4.2.130.0 or later, sometimes send 802.11g extended supported rate information elements,
regardless of the supported rates on the client. The access point sends the information elements only
when 802.11g is enabled on the network. However, hybrid-REAP access points never send 802.11g
extended supported rate information elements. To be consistent with access points in local mode,
they should.
Workaround: None.
•
CSCsz62198—Third-party certificates for web authentication are installed but sometimes indicate
that they are locally generated.
that they are locally generated.
Workaround: None.
•
CSCta01626—The controller produces rogue syslog messages, but rogue entries are not populated
into the tables.
into the tables.
Workaround: None.
•
CSCta07301—When you use the default NTP polling interval of 86400 seconds, the controller’s
clock might drift 2 seconds or more from the actual time. This behavior can cause problems for
location.
clock might drift 2 seconds or more from the actual time. This behavior can cause problems for
location.
Workaround: Use the config time ntp interval 3600 CLI command to set the NTP polling interval
to the minimum value of 3600 seconds.
to the minimum value of 3600 seconds.
Resolved Caveats
These caveats are resolved in controller software release 4.2.207.0.
•
CSCsl34068—A guest user client is not restricted to the bandwidth configured for the guest role.
•
CSCsm19182—When an 802.11n radio is operating on channels 52 through 140, the channel width
is configured for 40 MHz, and a radar event is detected, it is possible for the radio interface to
become disabled instead of moving to another channel. This problem occurs when the access point
is operating in the vicinity of radar operations or under extreme traffic conditions (when a false radar
detection might occur).
is configured for 40 MHz, and a radar event is detected, it is possible for the radio interface to
become disabled instead of moving to another channel. This problem occurs when the access point
is operating in the vicinity of radar operations or under extreme traffic conditions (when a false radar
detection might occur).