Release Notes

32
Release Notes for Cisco Wireless LAN Controllers and Lightweight Access Points for Release 4.2.176.0
OL-31336-01
Caveats
• CSCsm40903—Additional information is needed for the following message: “claspam_lrad.c:1626
LWAPP-6-PORTMAP_ERR: Failed to obtain multicast port map for interface 4, using default index
(50).”
Workaround: None.
• CSCsm40906—The following message appears on the 2106 controller when multicast is disabled:
“claspam_lrad.c:1626 LWAPP-6-PORTMAP_ERR: Failed to obtain multicast port map for interface
4, using default index (50).” No multicast messages should appear when multicast is disabled.
Workaround: None.
• CSCsm65043—1240 series access points might stop accepting new clients. In this case, the show
controller d1 command shows the following:
Beacon Flags: 0; Beacons are disabled; Probes are disabled
Workaround: Reboot the access point.
• CSCsm71573—When the following message appears, it fills up the entire message log:
mm_listen.c:5078 MM-3-INVALID_PKT_RECVD: Received an invalid packet from 10.0.x.x.
Source member:0.0.0.0. source member unknown.
Workaround: None.
• CSCsm79901—Wired clients attached to a workgroup bridge (WGB) are retaining the previous IP
address after the WGB obtains a new IP address. As a result, the wired client stops sending traffic
to the infrastructure network.
Workaround: Release and renew the DHCP IP address manually on the WGB wired client.
• CSCsm80423—The controller cannot block Layer2 multicast traffic.
Workaround: None.
• CSCsm82725—Clients are able to connect to the Internet without authenticating when using web
authentication and port 53 on a proxy server.
Workaround: None.
• CSCsm82984—When a controller and an access point are brought up with factory default settings,
you can Telnet to the access point (even though the show ap config general Cisco_AP CLI
command shows the Telnet feature as disabled). Also, once Telnet and SSH are enabled, they are not
disabled after you clear the controller’s configuration (even though the output of the show command
indicates that they have been disabled).
Workaround: None.
• CSCsm84952—When you configure wired and wireless guest WLANs on two controllers, a wired
guest user obtains an IP address but does not always receive the web authentication page or cannot
login properly. Additionally, a reattempt by the wired client might result in obtaining an IP address
from the other controller, causing the client to appear to have been handed an IP address from each
controller.
Workaround: Disable the wired guest WLAN on one of the controllers and enable it as needed.
Using an external DHCP server might resolve this issue as well.
• CSCsm89253—The controller should log a message if it sends “Telnet is not allowed on this port”
to Telnet clients.
Workaround: None.
• CSCsm94702—When the controller is configured through the service port, the VLAN ID and port
information do not appear in the output of the show int summary CLI command.