Cisco Cisco 2106 Wireless LAN Controller

<td colspan="2"><input type="button" name="Submit" value="Submit" class="button" 

onclick="submitAction();"> </td> </tr> </table> </div>

</form>

</body>

</html>

This section lists 

 and 

 for Cisco controllers and lightweight access 

points.

These caveats are open in controller software release 4.2.176.0.

CSCsb77595—When logging out from Telnet/SSH sessions, the session always prompts the user to 
save changes, even when no changes have been made. 

Workaround: Ignore the prompt and exit as usual.

CSCsd54928—The CPU ACL is unable to block LWAPP packets that are destined for the IP address 
of the dynamic interface.

Workaround: None.

CSCsd84706—Containment information for ad-hoc rogue access points is not shown on the 
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.

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.

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.

Workaround: Clear the configuration on the controller. Then reconfigure the controller and perform 
the redundancy test.

CSCsg04831—There are not enough debugs to determine the packet flow in the controller for guest 
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.

Workaround: None.