Cisco Cisco Aironet 1310 Access Point Bridge Notas de publicación

Descargar
Página de 22
 
15
Release Notes for Cisco Aironet Access Points and Bridges for Cisco IOS Release 12.4(10b)JA
OL-14517-01
  Caveats
Non-Cisco Aironet Clients Sometimes Fail 802.1x Authentication
Some non-Cisco Aironet client adapters do not perform 802.1x authentication to the access point unless 
you configure Open authentication with EAP. To allow both Cisco Aironet clients using LEAP and 
non-Cisco Aironet clients using LEAP to associate using the same SSID, you might need to configure 
the SSID for both Network EAP authentication and Open authentication with EAP.
Pings and Link Tests Sometimes Fail to Clients with Both Wired and Wireless 
Network Connections
When you ping or run a link test from an access point to a client device installed in a PC running 
Microsoft Windows 2000, the ping or link test sometimes fails when the client has both wired and 
wireless connections to the LAN. Microsoft does not recommend this configuration. For more 
information, refer to Microsoft Knowledge Base article 157025 at this URL:
Layer 3 Mobility Not Supported on Repeaters and Workgroup Bridges
Repeater access points and workgroup bridges cannot associate to an SSID configured for Layer 3 
mobility. Layer 3 mobility is not supported on repeaters and workgroup bridges.
WLSM Required for Layer 3 Mobility
You must use a Wireless LAN Services Module (WLSM) as your WDS device in order to properly 
configure Layer 3 mobility. If you enable Layer 3 mobility for an SSID and your WDS device does not 
support Layer 3 mobility, client devices cannot associate using that SSID.
Caveats
This section lists 
 for access points and bridges in 
Cisco IOS Release 12.4(10b)JA.
Open Caveats
These caveats are open in Cisco IOS Release 12.4(10b)JA:
CSCsd99067—AVVID priority map incorrectly maps COS 5 to COS 7 within same VLAN.
The AVVID priority mapping in the CoS advanced parameters is incorrectly mapping the CoS value 
to 7 when making a call to a wired phone in same VLAN. This situation occurs in an 802.11g 
network running one 7921 and one access point.
Workaround—None.