Something similar has occured to me and it's giving me a big headache. In a nutshell the culprit is the DHCPRELEASE message generated by a client when it disassociates from an accesspoint or the client shuts down. When this happens the DHCP on the BBSM removes the lease causing the client to get a different IP next time it associates to the network. The problem is that this may happen in a shorter time than the porthop delay causing a stale session for that user. Is there a solution to this problem from Cisco?
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...