@pgemme wrote:
Thanks guys, thanks Colin.
We were good in 6.4.2.8, not sure we ever ran 6.4.2.4 but the symptom Colin posted looks spot on. Scheduling an upgrade with change control now. I always prefer going forward.
pgemme,
Please open a case with TAC. There are a number of things to check to ensure that you end up on the correct version of code and we are addressing what you perceive:
1. If you are running 6.4.2.9 through 6.4.2.10 AND
2. You see an access point not allowing users to attach and you run this command and get this response:
show ap remote debug anul-sta-entries ap-name <name of ap>
Module AP STM is busy. Please try later
AND
3. It is one of these AP models:
4. The message at the beginning of this post *could* be a symptom, but all of these other things must be happening as well.
It is best you open a TAC case to ensure this is your issue. It is also possible you have an unknown issue, or a different issue, but just reading symptoms on a post does not ensure that is your problem...is why you should open a TAC case.