Having a CCKM issue that is really annoying my customer. TKIP is configured with CCKM and is using LEAP for authentication. A WDS is setup and works great except for these issues. Clients attach and roam but 1-2 twice a day up to 6-8 times a day, clients authentication fails. The logs show "CCKM authentication fails" and the client drops. Moments later, the client associates correctly and everything resumes. All client adapters are at 220.127.116.11 while AP's are at 12.3.8 (not JA2). From the event logs, I pieced together that the client roams to a new AP, Deauthenticates from the existing AP, Reassociated to the new AP (CCKM Fast Roaming) then is Deauthenticated Reason: Previous authentication is no longer valid, and then finally reassociates to the new AP (the one roamed to) successfully with CCKM.
I have submitted a TAC case and they are giving me the obligatory, "check the network card duplex" answer and I need something firm. The application they are running will not tolerate drops at all. If this system isn't solid, the customer is fully ready to remove all the Cisco AP's and go with another company.
Transferring Crash file from standby: Login to the Active WLC in HA.
From CLI: (Cisco Controller) >transfer upload datatype crash (Cisco
Controller) >transfer upload filename (Cisco
Controller) >transfer upload mode tftp (Cisco Controller) >transfer
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 f...