Cisco Cisco 2106 Wireless LAN Controller Notas de publicación
28
Release Notes for Cisco Wireless LAN Controllers and Mesh Access Points for Release 4.1.191.24M-Mesh
OL-31336-01
Caveats
•
CSCsl01069–In some circumstances, the mesh network would not form in optimal topologies and
MAPs would make unnecessary parent changes which would result in small outages in network
service (on the order of several seconds).
MAPs would make unnecessary parent changes which would result in small outages in network
service (on the order of several seconds).
•
CSCsl15370–A 1510 child MAP would fail to connect to the network during its security stage if it
was connecting to controllers whose names had different string lengths. The workaround was to use
the same string length for all controller names; and update each MAP with the relevant controller
name. Ensure that the modified name is reflected for the primary, secondary and tertiary controller
names.
was connecting to controllers whose names had different string lengths. The workaround was to use
the same string length for all controller names; and update each MAP with the relevant controller
name. Ensure that the modified name is reflected for the primary, secondary and tertiary controller
names.
•
CSCsl24573–In some cases, the MAC addresses of some mesh access points appeared in the
Excluded Client list of controllers. You could not remove (delete) the MAP entry from the Excluded
Client List. However, these MAPs were able to join the network by associating through a different
controller. The workaround was to reboot the controller to clear the client entries.
Excluded Client list of controllers. You could not remove (delete) the MAP entry from the Excluded
Client List. However, these MAPs were able to join the network by associating through a different
controller. The workaround was to reboot the controller to clear the client entries.
•
CSCsm16872, CSCsu52762–Viewing the access point detail window from the controller GUI
caused the GUI to freeze and the controller to reboot. No crash file was created.
caused the GUI to freeze and the controller to reboot. No crash file was created.
Closed Caveats
The following caveats represent those bugs that are closed and not actively being investigated but might
still represent active conditions in a product. Workarounds are provided.
still represent active conditions in a product. Workarounds are provided.
•
CSCsg60778–When background scanning is enabled, it may cause temporary backhaul congestion,
which might result in voice packet loss and jittery voice traffic.
which might result in voice packet loss and jittery voice traffic.
Workaround: Turning off background scanning can alleviate this problem to some extent.
However, if the packet loss and the jittery voice traffic are due to RF issues, then changing the RAP
to a different channel might help.
However, if the packet loss and the jittery voice traffic are due to RF issues, then changing the RAP
to a different channel might help.
•
CSCsi07934—Efficient multicast to 802.11 clients is not supported on mesh access
points.Therefore, you should not turn on multicast mode on the controller when it needs to service
mesh access points. If you do, the mesh access points may start disconnecting due to issues with
queue overflow at the MAPs. This issue applies to all controller commands starting with: config
network multicast
points.Therefore, you should not turn on multicast mode on the controller when it needs to service
mesh access points. If you do, the mesh access points may start disconnecting due to issues with
queue overflow at the MAPs. This issue applies to all controller commands starting with: config
network multicast
Workaround: If you need to turn on the controller multicast mode for non-mesh access points,
service mesh access points on a different controller than the one used for non-mesh access points.
service mesh access points on a different controller than the one used for non-mesh access points.
•
CSCsi67588, CSCsi74994–Bridge group names applied by Cisco WCS Access Point templates are
not updated in WCS windows because the controller initiates a reboot of the relevant mesh access
point before the information can be updated in Cisco WCS.
not updated in WCS windows because the controller initiates a reboot of the relevant mesh access
point before the information can be updated in Cisco WCS.
Workaround: At the Configure > Access Point window, select Audit from the Select a command
drop-down menu and click GO. at the Configure > Access Points to update the access point
information.
drop-down menu and click GO. at the Configure > Access Points to update the access point
information.
•
CSCsi74994–See description under CSCsi67588 above.
•
CSCsi83262–The back up battery for an AP1510 provides no warning when the AC source fails.
Workaround: Battery status warnings available in WCS and controller GUI and CLI.
•
CSCsi83272–After detaching and reattaching a probe to a backup battery on an AP 1510 the battery
status remains at a 0% charge reading for up to 30 minutes. This is in keeping with the design of the
battery. The battery estimates its charge on 30 minute cycles.
status remains at a 0% charge reading for up to 30 minutes. This is in keeping with the design of the
battery. The battery estimates its charge on 30 minute cycles.
Workaround: Keep probe attached to the battery for 30 minutes for accurate reading.