Примечания к выпуску для Cisco Cisco 4402 Wireless LAN Controller
15
Release Notes for Cisco Wireless LAN Controllers and Mesh Access Points for Release 4.1.190.5
OL-31336-01
Caveats
Caveats
This section lists open, resolved and closed caveats in Release 4.1.190.5.
Open Caveats
The following caveats are open (unresolved) in this release:
•
CSCsj48044—In some cases, public safety information might not display accurately in Cisco WCS.
Workaround: Query the information using the controller GUI or CLI, where applicable.
•
CSCsj48049—The Custom options for the TX Power Level Assignment parameter (Configure >
Access Point > Radio) in Cisco WCS do no reflect the correct dBm values; however, the correct
values are resident in the software.
Access Point > Radio) in Cisco WCS do no reflect the correct dBm values; however, the correct
values are resident in the software.
Workaround: Select the Tx Power Level Assignment based on the values 1 (high) to 5 (low) and
ignore the dBm values associated with those numbers.
ignore the dBm values associated with those numbers.
•
CSCsj67716—When AP1520 and AP1510 are operating in the same network, public safety channels
for the AP1510 might display (show mesh neigh summary Cisco_AP) the public safety channel
values of 190 or 196 rather than 20 and 26, if the AP1510 is operating with a release earlier than
4.1.181.0. Channels 20 and 26 were adopted for public safety transmissions in release 4.1.181.0.
Previous releases use channels 190 and 196 for public safety transmission.
for the AP1510 might display (show mesh neigh summary Cisco_AP) the public safety channel
values of 190 or 196 rather than 20 and 26, if the AP1510 is operating with a release earlier than
4.1.181.0. Channels 20 and 26 were adopted for public safety transmissions in release 4.1.181.0.
Previous releases use channels 190 and 196 for public safety transmission.
Workaround: None. This is a display issue only. It is not service affecting.
•
CSCsj73871—The config mesh linkdata AP_Name command which provides link test data is not
supported on the AP1520.
supported on the AP1520.
Workaround: None.
•
CSCsj77654—The current packet error rate (PER) displayed in Cisco WCS reflects a cumulative
value for control and data packets rather than distinct values.
value for control and data packets rather than distinct values.
Workaround: None.
•
CSCsj95524–In some cases, a higher than expected number of parent exclusion events might be
generated during an extended join period for an AP1520.
generated during an extended join period for an AP1520.
Workaround: Verify that the Bridge Group Name (BGN) for the AP1520 joining the network is
properly configured to limit the number of potential parents.
properly configured to limit the number of potential parents.
•
CSCsk07157–When operating as a MAP, the AP1520 generally prefers to select a parent that shares
the same bridge group name (BGN), rather than a wired interface (uplink) to the controller. This
approach is different from the AP1510 which always places a higher priority on selecting a parent
with a wired connection.
the same bridge group name (BGN), rather than a wired interface (uplink) to the controller. This
approach is different from the AP1510 which always places a higher priority on selecting a parent
with a wired connection.
Additionally, when an AP1520 connects to a parent with a default (null) BGN, the AP1520 disables
the Ethernet Bridging feature to prevent a potential bridge loop. This behavior also differs from that
of the AP1510.
the Ethernet Bridging feature to prevent a potential bridge loop. This behavior also differs from that
of the AP1510.
Workaround: Configure a bridge group name for the AP1520 and verify that its parent is on the
same bridge group to allow Ethernet Bridging.
same bridge group to allow Ethernet Bridging.
•
CSCsk07319–The txpkts rate for the neighboring mesh node always displays a value of 5000 in the
text of the show mesh adjacency all command for the AP1520.
text of the show mesh adjacency all command for the AP1520.
Workaround: None.