DescriptionIssues with clients connecting to WEP profile with the AP300/OAP180.
ScopeKB ARTICLE TYPE:
Troubleshooting
RELATED PRODUCTS: MC3000, AP300, OAP180,
AP201
RELATED SOFTWARE VERSIONS:
3.6
KEYWORDS: WEP, ESS, AP, security
profile
SolutionSTEPS TAKEN FOR
TROUBLESHOOTING:
1:
Verify the controller's running-configuration; check the security
profiles which are mapped to those
APs.
2: Check the
static WEP key index given to all the ESS profiles configured with the
WEP encryption.
3:
Configures the index position of a static WEP key. Specify one of the
four possible static WEP keys that can be configured by the user station
key management program.
GUI:
Go
to "Configuration" tab >> Click on "Security"
>> Select the respective "Security profile" click on
"Settings" button >> Change the "Static WEP Key Index"
value that range from 1 to 4. Make sure that each ESS profile uses a
unique key index of 1 through 4.
CLI:
MeruController1# configure
terminal
MeruController1(config)# security-profile
<profile
name>
MeruController1(config-security)#
static-wep key-index <position ranging from 1 to
4>
RESOLUTION:
Verify the configuration of the ESS profiles that the
clients have issues with. Alter the Static WEP Key Index value of all
the ESS profiles that uses the WEP encryption to a unique key index
value of 1 through 4. For example, you can configure up to 4 WEP
profiles, as long each uses a unique key index of 1 through
4.
ROOT
CAUSE:
Using more
than one security profile in which WEP is configured with the same key
index on an AP300/OAP180 is not supported. Configuring 2 different
profiles, both using the same index number, is not allowed. The key
index feature provides interoperability if the user program can
configure four key settings.
