Cisco Cisco 2000 Series Wireless LAN Controller Guia De Informação

Página de 17
A. The key lengths shown on the WLCs are actually the number of bits that are in the shared
secret and do not include the 24−bits of the Initialization Vector (IV). Many products, which
includes the Aironet products, call it a 128−bit WEP key. In reality it is a 104−bit key with
24−bit IV. The key size of 104−bit is what you must enable on the WLC for 128−bit WEP
encryption.
If you choose the 128−bit key size on the WLC, it is actually a 152−bit (128 + 24 IV) WEP
key encryption. Only Cisco 1000 Series LAPs (AP1010, AP1020, AP1030) support the use of
the WLC 128 bit WEP key setting.
Q. Why do I get the 
WEP key size of 128 bits is not supported
on 11xx, 12xx and 13xx model APs. Wlan will not be pushed
to these Access Points.
 error message when I try to configure WEP
on a WLC?
A. On a Wireless LAN Controller, when you choose Static WEP as the Layer 2 Security
method, you have these options or the WEP Key Size.
not set
♦ 
40 bits
♦ 
104 bits
♦ 
128 bits
♦ 
These key size values do not include the 24−bit Initialization Vector (IV), which is
concatenated with the WEP key. So, for a 64−bit WEP, you need to choose 40 bits as the
WEP key size. The controller adds the 24−bit IV to this in order to make a 64−bit WEP key.
Similarly, for a 128 bit WEP key, choose 104 bits.
Controllers also supports 152 bit WEP keys (128 bit + 24 bit IV). This configuration is not
supported on the 11xx, 12xx and 13xx model APs. So when you try to configure WEP with
144 bits, the controller gives a message that this WEP configuration is not pushed to 11xx,
12xx and 13xx model APs.
Q. Clients are not able to authenticate to a WLAN that is configured for
WPA2 and the controller displays the 
apf_80211.c:1923
APF−1−PROC_RSN_WARP_IE_FAILED: Could not process the RSN
and WARP IE's. station not using RSN (WPA2) on WLAN
requiring RSN.MobileStation:00:0c:f1:0c:51:22, SSID:<>
error message. Why do I receive this error?
A. This mostly occurs due to incompatibility on the client side. Try these steps in order to fix
this issue:
Check if the client is Wi−Fi certified for WPA2 and check the configuration of the
client for WPA2.
♦ 
Check the data sheet in order to see if the client Utility supports WPA2. Install any
patch released by the vendor to support WPA2. If you use Windows Utility, make
sure that you have installed the WPA2 patch from Microsoft in order to support
WPA2.
♦ 
Upgrade the client's Driver and Firmware.
♦ 
Turn off Aironet extensions on the WLAN.
♦