Примечания к выпуску для Cisco Cisco 2000 Series Wireless LAN Controller
![Cisco](https://files.manualsbrain.com/attachments/7380d0050044647c30f5c24bbbf5d0c0b6d9bb84/common/fit/150/50/faa183d287233c52228cfea3dbc2a127fe780f60564fcb0955d9c3d1cd23/brand_logo.png)
7
Release Notes for Cisco Wireless LAN Controller and Cisco Lightweight Access Point for Release 3.1.105.0
OL-7431-03
Important Notes
•
The Dynamic Transmit Power Control (DTPC) information element (IE) must be enabled. The
DTPC information element is a beacon and probe information element that allows the Cisco
lightweight access point to broadcast information on its transmit power. The Cisco Wireless IP
Phone 7920 uses this information to automatically adjust its transmit power to the same level as the
Cisco lightweight access point to which it is associated. In this manner, both devices are transmitting
at the same level.
DTPC information element is a beacon and probe information element that allows the Cisco
lightweight access point to broadcast information on its transmit power. The Cisco Wireless IP
Phone 7920 uses this information to automatically adjust its transmit power to the same level as the
Cisco lightweight access point to which it is associated. In this manner, both devices are transmitting
at the same level.
•
The 7920 phones and the Wireless LAN Controllers do not currently use compatible fast roaming
mechanisms. The phone uses CCKM while the Wireless LAN Controllers use Proactive Key
Caching (PKC). To minimize roaming latency, static WEP is the recommended security mechanism.
mechanisms. The phone uses CCKM while the Wireless LAN Controllers use Proactive Key
Caching (PKC). To minimize roaming latency, static WEP is the recommended security mechanism.
•
When configuring WEP, there is a difference in nomenclature the Wireless LAN Controller and the
7920 phone. Configure the Wireless LAN Controller for 104 bits when using 128-bit WEP for the
7920.
7920 phone. Configure the Wireless LAN Controller for 104 bits when using 128-bit WEP for the
7920.
The Upgrade Process
When a Wireless LAN Controller is upgraded, the code on the associated Cisco lightweight access points
is also automatically upgraded. When a Cisco lightweight access point is loading code, each of its lights
blinks in succession.
is also automatically upgraded. When a Cisco lightweight access point is loading code, each of its lights
blinks in succession.
Caution
Do not power down the Wireless LAN Controller or any Cisco lightweight access point during this
process, or you can corrupt the software release!
process, or you can corrupt the software release!
Upgrading a Wireless LAN Controller with a large number of Cisco lightweight access points can take
as long as 30 minutes. The Cisco lightweight access points must remain powered and the Wireless LAN
Controller must not be reset during this time.
as long as 30 minutes. The Cisco lightweight access points must remain powered and the Wireless LAN
Controller must not be reset during this time.
Cisco recommends the following sequence when performing an upgrade:
1.
Upload your Wireless LAN Controller configuration files to a server to back them up.
2.
Turn off the Wireless LAN Controller 802.11a and 802.11b networks.
3.
Upgrade your Wireless LAN Controller.
4.
Re-enable your 802.11a and 802.11b networks.
Note
Wireless LAN Controllers can be upgraded from one operating system release to another. However,
should you require a downgrade from one release to another, you may be unable to use the higher release
configuration (CSCsb79383). The workaround is to reload the previous Wireless LAN Controller
configuration files saved on the backup server or to reconfigure the Wireless LAN Controller.
should you require a downgrade from one release to another, you may be unable to use the higher release
configuration (CSCsb79383). The workaround is to reload the previous Wireless LAN Controller
configuration files saved on the backup server or to reconfigure the Wireless LAN Controller.
Exclusion List (Blacklist) Client Feature
If a client is not able to connect, and the security policy for the WLAN and/or client is correct, the client
has probably been disabled. From the Web user interface, Monitor page under client summary, you can
see the client’s status. If they are disabled you can just do a “Remove” operation and the disable is
cleared for that client. The client automatically comes back and, if necessary, reattempts authentication.
Automatic disabling happens as a result of too many failed authentications. Clients disabled due to failed
authorization do not show up on the permanent disable display. This display is only for those MACs that
are set as permanently disabled by the administrator.
has probably been disabled. From the Web user interface, Monitor page under client summary, you can
see the client’s status. If they are disabled you can just do a “Remove” operation and the disable is
cleared for that client. The client automatically comes back and, if necessary, reattempts authentication.
Automatic disabling happens as a result of too many failed authentications. Clients disabled due to failed
authorization do not show up on the permanent disable display. This display is only for those MACs that
are set as permanently disabled by the administrator.