Cisco Cisco 2106 Wireless LAN Controller
24
Release Notes for Cisco Wireless LAN Controllers and Lightweight Access Points for Release 4.2.173.0
OL-31336-01
Caveats
•
CSCsd84706—Containment information for ad-hoc rogue access points is not shown on the
controller GUI.
controller GUI.
Workaround: Use the controller CLI.
•
CSCsd95723—Some users might be confused when presented with the None and DHCP options for
configuring the service port interface in the initial controller setup wizard. These options are
available for a controller that has no configuration and the setup wizard is being used to configure it.
configuring the service port interface in the initial controller setup wizard. These options are
available for a controller that has no configuration and the setup wizard is being used to configure it.
Workaround: Users can interpret the None option as Static and a logical alternative to DHCP.
•
CSCse06202—When a controller’s IKE lifetime expires, a rekey is not offered.
Workaround: None.
•
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.
•
CSCsg04831—There are not enough debugs to determine the packet flow in the controller for guest
access.
access.
Workaround: Use a wireless sniffer trace.
•
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.