An answer to your question is not as simple as you might think.
LEAP does not require a static WEP key to be set on the client, and there is no reason to run WEP and LEAP authentication at the same time unless:
-you are migrating your network from open/shared authentication, used a WEP key at one time and are migrating users over to LEAP one at a time.
In the above case, you would technically be running LEAP and WEP on the same access point, but users would only be authenticated by one or the other. Users will not be authenticated by LEAP and static WEP at the same time.
I did this during our migration to LEAP from open/WEP based authentication and it worked beautifully. Once LEAP was up and running, users no longer had to use static WEP keys on the client side.
Also, the awesome thing about LEAP is that it uses dynamic WEP keys which are session specific, but that is another paragraph or two. Just got to cisco.com and search for "dynamic wep".
Transferring Crash file from standby:
Login to the Active WLC in HA.
(Cisco Controller) >transfer upload datatype crash
(Cisco Controller) >transfer upload filename <Desired filename>
(Cisco Controller) >transfer up...
This is the start of a display filter cross reference between Wireshark and OmniPeek.
The 1st installment is a table of advanced filters. More filters will be added as time allows.
It is a living doc, so check back for changes every so often
Please feel ...
I have created a Powershell script to automatically add a Wireless Guest User on Cisco WLCs. (tested on 2500 Series)
The script should be completely self explanatory.
Powershell SNMP Module (Install-Module -Name SNMP)
SNMP Write Access to...