Cisco Cisco Aironet 1200 Access Point Notas de publicación
15
Release Notes for Cisco Aironet Access Points for Cisco IOS Release 12.3(8)JA2
OL-10768-01
Important Notes
Corrupt EAP Packet Sometimes Causes Error Message
During client authentication, the access point sometimes receives a corrupt EAP packet and displays this
error message:
error message:
Oct 1 09:00:51.642 R: %SYS-2-GETBUF: Bad getbuffer, bytes= 28165
-Process= "Dot11 Dot1x process", ipl= 0, pid= 32
-Traceback= A2F98 3C441C 3C7184 3C604C 3C5E14 3C5430 124DDC
You can ignore these messages.
When Cipher Is TKIP Only, Key Management Must Be Enabled
When you configure TKIP-only cipher encryption (not TKIP + WEP 128 or TKIP + WEP 40) on any
radio interface or VLAN, every SSID on that radio or VLAN must be set to use WPA or CCKM key
management. If you configure TKIP on a radio or VLAN but you do not configure key management on
the SSIDs, client authentication fails on the SSIDs.
radio interface or VLAN, every SSID on that radio or VLAN must be set to use WPA or CCKM key
management. If you configure TKIP on a radio or VLAN but you do not configure key management on
the SSIDs, client authentication fails on the SSIDs.
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.
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
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:
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.
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.
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.