Cisco Cisco 2106 Wireless LAN Controller

Page de 58
 
32
Release Notes for Cisco Wireless LAN Controllers and Lightweight Access Points for Release 4.2.61.0
OL-31336-01
  Caveats
CSCsd52483—When you make changes in the bootloader of a 2006 controller or a Controller 
Network Module, the bootup process may halt, and the controller may stop responding. The 
controller also displays the "grub>" prompt on the console port. 
Workaround: Replace the controller.
CSCsd54928—The CPU ACL is unable to block LWAPP packets on the AP-manager interface.
Workaround: None.
CSCsd64081—Ethernet multicast mode is not passing multicast traffic on the 2006 controller.
Workaround: None.
CSCsd84706—Containment information for ad-hoc rogue access points is not shown on the 
controller GUI. 
Workaround: Use the controller CLI.
CSCsd86375—HiFn sessions are being added and deleted with the session handles set to 0.
Workaround: None.
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.
CSCse01881—The following message might randomly appear in the controller’s message logs: 
“[WARNING] dtl_arp.c 1656: Unable to delete ARP mapping.” 
Workaround: None.
CSCse11464—The Management Frame Protection Settings page on the controller GUI displays a 
maximum of 100 access points. 
Workaround: If there are more than 100 access points under MFP, use the controller CLI to view the 
list of access points.
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.
CSCsf26609—The “cLCdpAllApStatus” MIB variable with TruthValue always returns a value of 
false. This problem affects WCS operations.
Workaround: None.
CSCsf29783—The Cisco WiSM reboots after experiencing a failure with the reaperWatcher 
mmMfpTask.
Workaround: None.
CSCsg04831—There are not enough debugs to determine the packet flow in the controller for guest 
access.
Workaround: Use a wireless sniffer trace.
CSCsg05789—The controller should send all crash information to WCS, and WCS should forward 
that information to Cisco.com. 
Workaround: None.