Cisco Cisco 2106 Wireless LAN Controller Release Notes
41
Release Notes for Cisco Wireless LAN Controllers and Lightweight Access Points for Release 4.2.130.0
OL-31336-01
Caveats
•
CSCsm50774—The controller might reboot due to a failure of the apfReceiveTask software
watchdog.
watchdog.
•
CSCsm52401—Sometimes one-way audio might suddenly occur.
•
CSCsm78567—Access points running software release 4.1 or 4.2 might reload or disconnect from
the network after a variable uptime due to a memory leak on CDP processing in the access point.
The time between access point reloads might depend on the CDP rate received by the access point.
the network after a variable uptime due to a memory leak on CDP processing in the access point.
The time between access point reloads might depend on the CDP rate received by the access point.
•
CSCsm80066—When a controller receives an ARP request with its own IP address as the source, it
stops responding to Telnet and GUI connections.
stops responding to Telnet and GUI connections.
•
CSCsm95615—A sequence ID difference exists between the 2100 and 4400 series controllers.
•
CSCsm95651—Multiple controllers running software release 4.1.185.0 might reboot
spontaneously, without generating a crash log.
spontaneously, without generating a crash log.
•
CSCsm96307—A controller might reboot unexpectedly following a period of high CPU utilization
charged to the SNMPtask. This condition triggers a Reaper timeout and a system reset.
charged to the SNMPtask. This condition triggers a Reaper timeout and a system reset.
•
CSCsm97315—While installing a web authentication certificate, the controller fails with an invalid
password error. This problem occurs only on controllers that have been upgraded from software
release 4.1.
password error. This problem occurs only on controllers that have been upgraded from software
release 4.1.
•
CSCsm99941—Controllers running software release 4.2 or 5.0 might reboot and create a crash log.
This behavior occurs frequently if rogue client and access point polling is enabled through WCS on
the Location Appliance. If the default polling interval for rogue clients and access points is used,
the controller might reboot every 10 minutes.
This behavior occurs frequently if rogue client and access point polling is enabled through WCS on
the Location Appliance. If the default polling interval for rogue clients and access points is used,
the controller might reboot every 10 minutes.
•
CSCso15640—The controllers in the Cisco WiSM might reboot due to a software failure of the
instruction located at 0x1036f2ac (debugPrintMessage2+288).
instruction located at 0x1036f2ac (debugPrintMessage2+288).
•
CSCso17455—Controllers sometimes reboot when SSH is enabled.
•
CSCso27775—The controller logs show several error messages on one line only (both on the CLI
and on the syslog server). The error message is truncated, so it does not reach the carriage return in
the end. This error message appears when several access points are trying to join a controller that is
already at full access point capacity.
and on the syslog server). The error message is truncated, so it does not reach the carriage return in
the end. This error message appears when several access points are trying to join a controller that is
already at full access point capacity.
•
CSCso27809—When a 1000 series access point is configured with a static IP address, domain name,
and DNS server, it still uses the DNS domain name obtained from a DHCP INFORM request,
ignoring the statically configured domain name. This behavior may break the discovery process
through the DNS mechanism because the DNS query can no longer match the configured name.
and DNS server, it still uses the DNS domain name obtained from a DHCP INFORM request,
ignoring the statically configured domain name. This behavior may break the discovery process
through the DNS mechanism because the DNS query can no longer match the configured name.
•
CSCso30745—When a packet fails the admission control test because the switch fabric cell buffers
corresponding to its stream are full, it is incorrectly forwarded to the CPU instead of being
discarded. This incorrect forwarding of many such packets could cause an overload of the CPU and
a Reaper reset.
corresponding to its stream are full, it is incorrectly forwarded to the CPU instead of being
discarded. This incorrect forwarding of many such packets could cause an overload of the CPU and
a Reaper reset.
•
CSCso36248—The LDAP username is limited to 24 characters in controller software release
4.2.112.0.
4.2.112.0.
•
CSCso40917—The FPGA link might stop working, causing the access points to disconnect from the
controller and preventing the controller from being managed by any port other than the service port.
The NPU Check Task or a similar task should monitor the status of the FPGA link.
controller and preventing the controller from being managed by any port other than the service port.
The NPU Check Task or a similar task should monitor the status of the FPGA link.
•
CSCso42187—A 1010 series access point reboots intermittently. The syslog displays the following
message: “Max retransmissions reached on AP. AP xx:xx:xx:xx:xx:xx associated. Last AP failure
was due to AP reset.”
message: “Max retransmissions reached on AP. AP xx:xx:xx:xx:xx:xx associated. Last AP failure
was due to AP reset.”
•
CSCso43852—A controller running software release 4.2.112.0 might reboot due to a software
failure of the apfReceiveTask at mmParsePayload.
failure of the apfReceiveTask at mmParsePayload.