AP firmware 3.6.0.0.709 High Connection Errors

  • 3
  • Question
  • Updated 1 month ago
I have upgraded my Vsz to 3.6.0.0.510 and upgraded the APs to 3.6.0.0.709.  After the upgrade i noticed that almost every AP had a high percentage of connection errors.  I let it go for several days and thought i still had a lot of clients connected so it must be working.  In the events I see a lot of Force DHCP disconnects.  I did not make any changes to that but did double check the settings.  Some wlans were not enabled and some set to anywhere from 5-15 seconds.  Downgraded the firmware to 3.5.1.0.1026 and the connection errors went away.  Has anyone seen this and have any ideas why i am seeing this.  
Photo of Paul McGuire

Paul McGuire

  • 2 Posts
  • 0 Reply Likes

Posted 1 month ago

  • 3
Photo of Aleksandar Radivojsa

Aleksandar Radivojsa

  • 10 Posts
  • 0 Reply Likes
Have the same problem and have opened case on Ruckus Support system. If I will get solution to solve this, I will post it here.
Photo of Jakob Peterhänsel

Jakob Peterhänsel

  • 66 Posts
  • 22 Reply Likes
Well.. not many alarms on it, but if I show the Connection Failures on the AP list, it looks like this:

Site One:


Site Two:


Not sure what to think of that.. 
Photo of Jamie Walmsley

Jamie Walmsley

  • 22 Posts
  • 3 Reply Likes
Personally id stick with 3.5. Looking at 3.6 known bugs and issues in my opinion its not release ready. We were recently advised by Ruckus NOT to upgrade to 3.6 and to stick with 3.5...
Photo of David Henderson

David Henderson

  • 92 Posts
  • 13 Reply Likes
We are seeing the same behavior. Should I downgrade to 3.5 or wait until Ruckus fixes this and apply the next version?
Photo of Diego Garcia del Rio

Diego Garcia del Rio

  • 5 Posts
  • 0 Reply Likes
I am seeing he same type of stats. User experience seems good but the stats are a bit concerning.
Photo of EightOhTwoEleven

EightOhTwoEleven

  • 12 Posts
  • 1 Reply Like
We also see the same, before 3.6 only a few (VHD areas) APs showed anthing above 2% -- now almost all have 70%+. Definitely a bug.
Photo of Diego Garcia del Rio

Diego Garcia del Rio

  • 5 Posts
  • 0 Reply Likes
Wonder if its a stats/counting error or real connection troubles. The user experience seems to be fine so far, but this was a brand new deployment starting on 3.6 so I don't have a reference point.
Photo of EightOhTwoEleven

EightOhTwoEleven

  • 12 Posts
  • 1 Reply Like
If you go to the AP and then down to Event tab - type in "authenticat" in the search, are there alerts/errors present?
Photo of Diego Garcia del Rio

Diego Garcia del Rio

  • 5 Posts
  • 0 Reply Likes
No authentication or connection errors on the event log. In fact, the main network is not even protected (its just an open network). I will look at stats per SSID
Photo of EightOhTwoEleven

EightOhTwoEleven

  • 12 Posts
  • 1 Reply Like
Then it sounds like it's a stats/counting error, especially if no events in the log are present. Again, for those of us who ran the 3.5.1 for a while - and then switched, without any other changes, these errors popped up.
Photo of Diego Garcia del Rio

Diego Garcia del Rio

  • 5 Posts
  • 0 Reply Likes
Thanks! Are you seeing errored events on your case? 
Photo of EightOhTwoEleven

EightOhTwoEleven

  • 12 Posts
  • 1 Reply Like
Yes we are, but I believe that's because we enabled the DoS protection and they are having wrong log in attempts. What do you expect when you attempt to login to the network as Bob?
Photo of EightOhTwoEleven

EightOhTwoEleven

  • 12 Posts
  • 1 Reply Like
Spoke with support and they said this is a known problem, and is being worked on. Here are the details:

SCG-75069

R3.6: AP KPI Connection failures: Connection failures AP flagging mechanism needs to enhance