Frequent wireless disconnections occurring since upgrade to 10.21.01.0065

[Steve_Ballantyn]

I apologize for the redundant question. It seems like "clients disconnecting" is a common topic. But I am starting a new one, because it seems that every situation is different.

I have a C5210 and a bunch of 3825i AP's all over my hospital. Just before Christmas I upgraded to the latest firmware, 10.21.01.0065. Since then I am getting complaints from users (across the board) that they are frequently getting dropped from WiFi. After it happens they are easily able to reconnect and all is well. But it's driving them mad as they will be in mid-sentence documenting in their various applications and then it sort of freezes up and KAPOW! Connection lost!

There is nothing newer to upgrade to. And I suppose I could downgrade to see if the problems goes away. But I would rather seek out the source of the problem and fix it. Especially if it's just something wacky in my configuration.

I plan on putting in a call and opening a ticket on Monday morning with support. But in the meantime - does anyone have any ideas for me? I use Netsight and Purview, and I have all of these logs and diagnostic data at my disposal, but I am not really sure where to start. I suppose the first question is - does anyone else have this issue with this firmware?

[Ronald_Dvorak]

notepad row# 7174 - what is the reason code - it's not on the screenshot

[Ronald_Dvorak]

What does the controller GUI > logs > station events ....show for that MAC in that timeframe ?

[Steve_Ballantyn]

My users provided me some feedback today. Here is the first instance of a "disconnect" that a user reported to me, from the ap.log. The blue highlight is the MAC of the station that dropped.

I have submitted this to support. But in the mean time - does this look like useful information to anyone?

[Jeremy_Gibbs]

I am too having some issues with this also. Please post any updates you find here, as this will be very useful to many people! My radio settings are almost the same as Ronald Ds. Using 12 and 24 for the MBR.. 12 in less dense and 24 in most dense areas.

One thing I have noticed, sometimes band-steering tries to force users who don't have an 5 Ghz to 5 Ghz by constantly rejecting their association requests. I have seen this in the new version of code, especially with XBOX 360 consoles. I won't even see the MAC in NetSight until I turn off BS... If you do a tail -f /tmp/log/ap.log | grep -i "mac address of client" you can see the logs for band-steering trying to force a non capable 2.4 client to 5 Ghz

[Steve_Ballantyn]

Laura, if the new2day password didn't work, it's because the AP is successfully pulling a config from the controller, and your controller is dictating the password.

You can set/change that password in the web GUI under AP tab > Global Settings (on the left) > Registration. Check the "SSH Access" password. Mine appears to be blank --- which is odd, because I know I have set a password and use it all the time.