Примечания к выпуску для Cisco Cisco 2106 Wireless LAN Controller
27
Release Notes for Cisco Wireless LAN Controllers and Lightweight Access Points for Release 4.2.112.0
OL-31336-01
Caveats
•
CSCse06206—The controller sends a DEL notification when the IKE lifetime expires, but it does
not send the notice to the client.
not send the notice to the client.
Workaround: None.
•
CSCse87087—A controller with link aggregation (LAG) enabled fails Ethernet link redundancy.
This problem occurs when the controller uses an Ethernet copper gigabit interface converter (GBIC)
instead of a fiber GBIC and one of two Ethernet cables is pulled out of the GBIC.
This problem occurs when the controller uses an Ethernet copper gigabit interface converter (GBIC)
instead of a fiber GBIC and one of two Ethernet cables is pulled out of the GBIC.
Workaround: Clear the configuration on the controller. Then reconfigure the controller and perform
the redundancy test.
the redundancy test.
•
CSCsf29783—The Cisco WiSM reboots after experiencing a failure with the reaperWatcher
mmMfpTask.
mmMfpTask.
Workaround: None.
•
CSCsg04831—There are not enough debugs to determine the packet flow in the controller for guest
access.
access.
Workaround: Use a wireless sniffer trace.
•
CSCsg22062—“LWAPP RM Measure process” traceback messages might appear for access points
converted to lightweight mode after you upgrade the controller from software release 4.0.179.11 to
4.0.219.0.
converted to lightweight mode after you upgrade the controller from software release 4.0.179.11 to
4.0.219.0.
Workaround: None.
•
CSCsg48089—If you lose your controller password and have not backed up the configuration, the
recovery mechanism is to revert to the factory default settings.
recovery mechanism is to revert to the factory default settings.
Workaround: None.
•
CSCsg59235—The controller CLI lacks commands for debugging activity at the IP, ICMP, TCP,
UDP, TELNET, SSH, and HTTP layers.
UDP, TELNET, SSH, and HTTP layers.
Workaround: Use an external packet capture device to collect packets to and from the controller.
Send these packets to the Technical Assistance Center (TAC) for analysis.
Send these packets to the Technical Assistance Center (TAC) for analysis.
•
CSCsg66040—Controllers running software release 4.0.179.11 sometimes fail to respond to
communication through HTTPS.
communication through HTTPS.
Workaround: Upgrade the controller software.
•
CSCsg68046—The complete reason for a TFTP download failure needs to appear on the controller
GUI. If the controller cannot find the software file on the TFTP server during a software upgrade, it
reports that the transfer failed rather than that the file is not present.
GUI. If the controller cannot find the software file on the TFTP server during a software upgrade, it
reports that the transfer failed rather than that the file is not present.
Workaround: Make sure that the file and filename are entirely correct before upgrading, or upgrade
using the CLI to receive a more accurate reason for the failure. Further details are available if you
use the debug transfer all enable command prior to upgrade.
using the CLI to receive a more accurate reason for the failure. Further details are available if you
use the debug transfer all enable command prior to upgrade.
•
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.
•
CSCsg82429—The controller and its access points have no way to be configured with an IP MTU
value. As a result, they normally transmit full-sized (1500B) IP packets to or from wireless clients
as outer IP packets of size 1566B (due to the LWAPP header overhead). These packets are usually
fragmented between the controller and access point. Also, in some network topologies, the fixed
1500B IP MTU used by the controller may cause problems when talking to other IP endpoints (such
as a WCS.)
value. As a result, they normally transmit full-sized (1500B) IP packets to or from wireless clients
as outer IP packets of size 1566B (due to the LWAPP header overhead). These packets are usually
fragmented between the controller and access point. Also, in some network topologies, the fixed
1500B IP MTU used by the controller may cause problems when talking to other IP endpoints (such
as a WCS.)