> TAC says I have to wait for a fix. I'm just surprised it's taking so long.
Well then TAC has misled you! The status of that bug is currently Unreproducible (and has been since 22nd July) which means TAC (and possibly also dev team) were not able to reproduce the issue in their lab and are not working on a fix for it at all.
If you want it fixed you're going to have to get back onto TAC to re-open that bug and talk them through how to repro it very carefully (many of the current TAC first level engineers require a lot of guidance and hand holding). We had one who managed to actually go backwards after 2 weeks on a case the other day. They completely misunderstood the issue and made a number of false and incorrect statements contradicting what we had already explained in great detail the day the case was opened, complete with debugs, logs and packet captures illustrating the problem and how to 100% reliably reproduce it. After we made a huge fuss (due to 2 weeks of time wasting rubbish which achieved nothing), an escalation engineer was engaged and the bug was reproduced in their lab within a day! Some of those engineers literally do not understand basic IP protocols or Cisco kit operation (let alone RFCs), so if you cannot get them to understand within a few days then escalation is essential. The more detailed debugs, logs and packet captures you can provide, the better. You need to provide incontrovertible evidence of the problem and a reliable method for reproducing it so there is no wiggle room for them to get out of fixing it.
Meanwhile your only option is to use the workaround - "Disable OKC and FT on the WLAN"
