I've been having a problem for the past few weeks. Before upgrading our wireless infrastructure with the WLC we just used standalone 1242's. 802.11b devices would connect to an ssid using wpa-psk. Something has happened lately and these devices won't work anymore, laptops and other devices work with the same ssid just fine.
If I should send more info just let me know.
Hope you can help.
I am attatching a debug client log for one of these devices, the only errors I see are dhcp, but the clients have always been setup statically:
It is likely that you have a 'DHCP Required' rule in the WLAN settings. If you disable / remove this setting, the WLC will not required clients to get a DHCP IP Address before granting them access to the network.
Sometimes there are issues using static IP addresses on the client side. This can result in the client associating but not authenticating as the clients ARP entry never hits the controller and thus the client is never in the controllers client list. Use DHCP when necessary, 90 percent of tac calls at Airespace were a result of not using dhcp.
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...