Примечания к выпуску для Cisco Cisco 2106 Wireless LAN Controller
33
Release Notes for Cisco Wireless LAN Controllers and Mesh Access Points for Release 4.1.192.22M
OL-16242-03
Caveats
•
CSCsl20845–It might take an extended period of time (an hour or more) for a change in attenuation
to cause the SNR for an existing AWPP neighbor entry to change accordingly. If an access point is
rebooted, the newly created AWPP neighbor entry has the expected SNR value immediately.
to cause the SNR for an existing AWPP neighbor entry to change accordingly. If an access point is
rebooted, the newly created AWPP neighbor entry has the expected SNR value immediately.
Workaround: None.
•
CSCsl63171–A controller might report a platinum QoS overflow condition to the message log even
when platinum QoS is not configured on any of the WLANs. The overflow condition is only reported
for 1510s.
when platinum QoS is not configured on any of the WLANs. The overflow condition is only reported
for 1510s.
Workaround: None.
•
CSCsm37109–If some cases, enabling the anti-stranding feature might cause the controller console
to be swamped with debug messages from a stranded access point and you are not able to access the
console prompt until the messages finish displaying. Messages disappear after 30 minutes when the
stranded mesh access point reloads.
to be swamped with debug messages from a stranded access point and you are not able to access the
console prompt until the messages finish displaying. Messages disappear after 30 minutes when the
stranded mesh access point reloads.
Workaround: None.
•
CSCsm44951–The show country channel command does not display the 4.9-GHz channel for the
1524 mesh access point although it is a supported. It only lists the 5-8-GHz channels.
1524 mesh access point although it is a supported. It only lists the 5-8-GHz channels.
Workaround: None. It is not service affecting. The 4.9-GHz channel is operating and the mesh
access point is able to join the controller.
access point is able to join the controller.
•
CSCsm49862–When a 802.11a network is disabled and a new mesh access point joins, the 802.11a
radio displays as UP or REG instead of the expected DOWN state because the 802.11a radio is not
shut off due to potential stranding issues. If a mesh access point joins before a 802.11a network is
disabled, the mesh access point displays as DOWN even though the 802.11a radio is actually UP. In
both cases, the mesh access points are not turned off.
radio displays as UP or REG instead of the expected DOWN state because the 802.11a radio is not
shut off due to potential stranding issues. If a mesh access point joins before a 802.11a network is
disabled, the mesh access point displays as DOWN even though the 802.11a radio is actually UP. In
both cases, the mesh access points are not turned off.
Workaround: None.
•
CSCsm62772–A controller running 4.1.190.5 or 4.1.191.24M software might crash unexpectedly
due to an SNMPTask.
due to an SNMPTask.
Workaround: None.
•
CSCsm73147– When a configured country code does not support the 5-GHz band (802.11a), an UP
condition for both the 2.4Ghz and 5Ghz radio of a 1510 mistakenly displays. As an unsupported
band, no data should display for the 5-GHz band and MAPs cannot join the RAP via that band.
condition for both the 2.4Ghz and 5Ghz radio of a 1510 mistakenly displays. As an unsupported
band, no data should display for the 5-GHz band and MAPs cannot join the RAP via that band.
Workaround: None.
•
CSCsm80803–When a wired client is connected to a workgroup bridge using WPAv1+TKIP (PSK),
it loses its association with a 1510.
it loses its association with a 1510.
Workaround: Configure WPAv2+AES.
•
CSCsm84194–A mesh access point might restart discovery while downloading an image. When this
occurs the mesh access point might require a number of retires before it successfully joins the
controller.
occurs the mesh access point might require a number of retires before it successfully joins the
controller.
Workaround: None. Recovery is automatic, mesh access point joins after retires without user
intervention.
intervention.
•
cscsm90114–In some cases, when RRM is enabled and a mesh access point radio goes off channel
frequently (every 30 to 60 seconds), clients are not being notified and the clients transmission queue
is not being reserved, so the client disconnects from the mesh access point.
frequently (every 30 to 60 seconds), clients are not being notified and the clients transmission queue
is not being reserved, so the client disconnects from the mesh access point.
Workaround: Increase the load and neighbor timers to 3600 seconds.
•
CSCsm90785–The WiSM only supports up to 300 mesh access points reliably.
Workaround: Do not allow more that 300 mesh access points to associate with a WiSM.