Cisco Cisco 2106 Wireless LAN Controller
26
Release Notes for Cisco Wireless LAN Controllers and Lightweight Access Points for Release 4.2.205.0
OL-31336-01
Caveats
•
CSCsg04831—There are not enough debugs to determine the packet flow in the controller for guest
access.
access.
Workaround: Use a wireless sniffer trace.
•
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.
•
CSCsg39910—The 1000 series access points should support direct Telnet to the controller CLI.
Workaround: None.
•
CSCsg39928—The 1000 series access points should support direct Secure Shell (SSH) to the
controller CLI.
controller CLI.
Workaround: None.
•
CSCsg45938—Devshell commands do not work on SSH or Telnet sessions.
Workaround: Enter the devshell commands in a console session.
•
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.
•
CSCsg66040—After a software upgrade, controllers might experience intermittent access to the
management interface through HTTPS.
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.
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.
Login with the relevant credentials and reconfigure the virtual interface with this CLI command:
config interface address virtual 1.1.1.1
c.
Reboot the controller and make sure the Secure Web service shows up as OK.
d.
Generate a certificate using this CLI command:
config certificate generate webauth
e.
Click Yes when prompted and wait a few minutes for the certificate to generate.
f.
Reboot the controller.
•
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.