Примечания к выпуску для Cisco Cisco 2000 Series Wireless LAN Controller
11
Release Notes for Cisco Wireless LAN Controller and Cisco Lightweight Access Point for Release 3.1.105.0
OL-7431-03
Important Notes
•
Spanning tree.
•
Port mirroring.
•
Cranite.
•
Fortress.
•
AppleTalk.
•
802.1p tagging.
•
QoS per user bandwidth contracts.
•
IPv6 pass-through.
Some Clients Can 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 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 enforce RF policies in your buildings and campuses.
Pinging from Any Network Device to a Dynamic Interface IP Address Not
Supported
Supported
Clients on the WLAN associated with the interface pass traffic normally.
Cisco 4400 Series Wireless LAN Controller Limitations
•
Data traffic that goes in Cisco 4400 Series Wireless LAN Controller port 1 or 2 and exits port 3 or
4 may experience a loss rate of less than 1%.
4 may experience a loss rate of less than 1%.
•
Heavy multicast traffic may cause the Cisco 4400 Series Wireless LAN Controller to lose
connection with Cisco lightweight access points.
connection with Cisco lightweight access points.
Cisco Lightweight Access Point Fails to Join Wireless LAN Controller
Cisco lightweight access point boots up IOS image and reboots due to join failure or timeout. This
sequence repeats forever until Cisco lightweight access point goes into boot prompt and stays there. This
condition occurs when the Cisco lightweight access point console is connected to a terminal server port,
when there is no telnet session to the Cisco lightweight access point console port, and when the Wireless
LAN Controller is not responding to the Cisco lightweight access point join response.
Workaround: Disconnect the Cisco lightweight access point console port from the terminal server.
Reprogram the Wireless LAN Controller to have it response to the Cisco lightweight access point join
request. Power cycle the Cisco lightweight access point to force restart.
sequence repeats forever until Cisco lightweight access point goes into boot prompt and stays there. This
condition occurs when the Cisco lightweight access point console is connected to a terminal server port,
when there is no telnet session to the Cisco lightweight access point console port, and when the Wireless
LAN Controller is not responding to the Cisco lightweight access point join response.
Workaround: Disconnect the Cisco lightweight access point console port from the terminal server.
Reprogram the Wireless LAN Controller to have it response to the Cisco lightweight access point join
request. Power cycle the Cisco lightweight access point to force restart.