Примечания к выпуску для Cisco Cisco 4402 Wireless LAN Controller
![Cisco](https://files.manualsbrain.com/attachments/7380d0050044647c30f5c24bbbf5d0c0b6d9bb84/common/fit/150/50/faa183d287233c52228cfea3dbc2a127fe780f60564fcb0955d9c3d1cd23/brand_logo.png)
R E V I E W D R A F T — C I S C O C O N F I D E N T I A L
15
Release Notes for Cisco Wireless LAN Controllers and Lightweight Access Points for Release 3.2.210.0
OL-xxxxx-xx
Important Notes
•
QoS per-user bandwidth contracts
•
IPv6 pass-through
Some Clients See Only 64 Access Point MAC Addresses (BSSIDs) at a Time
In a crowded RF environment, clients may not be able to detect the desired SSID because of internal
table limitations. Sometimes disabling and then enabling the client interface forces a rescan. Your RF
environment needs to be controlled. Cisco UWN rogue access point detection and containment can help
you to enforce RF policies in your buildings and campuses.
table limitations. Sometimes disabling and then enabling the client interface forces a rescan. Your RF
environment needs to be controlled. Cisco UWN rogue access point detection and containment can help
you to enforce RF policies in your buildings and campuses.
Pinging from Any Network Device to a Dynamic Interface IP Address Is Not
Supported
Supported
Clients on the WLAN associated with the interface pass traffic normally.
2006 Image Not Supported for 3504 Controllers
The 2006 controller image is supported for use with only 2000 series controllers. Do not install the 2006
image on a 3504 controller. Otherwise, errors may occur. Install only the 3504 image on a 3504
controller.
image on a 3504 controller. Otherwise, errors may occur. Install only the 3504 image on a 3504
controller.
Running a 3504 Image on a 2000 Series Controller
It is possible to run a 3504 controller image on a 2000 series controller, but Cisco Aironet 1130, 1200,
and 1240 series access points will not be able to connect to the controller.
and 1240 series access points will not be able to connect to the controller.
Cisco Lightweight Access Points Fail to Join Cisco Controllers
When a Cisco lightweight access point is connected to a terminal server port and reboots because of a
join failure or timeout, this sequence repeats until the access point returns to the boot prompt and remains
there. This condition occurs when there is no telnet session to the access point’s console port and when
the controller is not responding to the access point’s join response.
join failure or timeout, this sequence repeats until the access point returns to the boot prompt and remains
there. This condition occurs when there is no telnet session to the access point’s console port and when
the controller is not responding to the access point’s join response.
Workaround: Disconnect the access point’s console port from the terminal server. Reprogram the
controller to have it respond to the access point’s join request. Power cycle the access point to force a
restart.
controller to have it respond to the access point’s join request. Power cycle the access point to force a
restart.