Skip to main content

36 Messages

 • 

810 Points

Thu, Dec 14, 2017 1:50 AM

Answered

AP firmware 3.6.0.0.709 High Connection Errors

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.  

Responses

14 Messages

 • 

224 Points

3 years ago

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.

90 Messages

 • 

1.8K Points

3 years ago

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.. 

26 Messages

 • 

430 Points

3 years ago

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...

116 Messages

 • 

2.3K Points

3 years ago

We are seeing the same behavior. Should I downgrade to 3.5 or wait until Ruckus fixes this and apply the next version?

127 Messages

 • 

2.4K Points

3 years ago

I am seeing he same type of stats. User experience seems good but the stats are a bit concerning.

178 Messages

 • 

2.9K Points

3 years ago

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.

127 Messages

 • 

2.4K Points

3 years ago

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.

178 Messages

 • 

2.9K Points

If you go to the AP and then down to Event tab - type in "authenticat" in the search, are there alerts/errors present?

127 Messages

 • 

2.4K Points

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

178 Messages

 • 

2.9K Points

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.

127 Messages

 • 

2.4K Points

Thanks! Are you seeing errored events on your case? 

178 Messages

 • 

2.9K Points

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?

178 Messages

 • 

2.9K Points

3 years ago

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

1 Message

 • 

60 Points

3 years ago

Hi Are there any news in this case? I have the same issue after upgrading last week.

178 Messages

 • 

2.9K Points

3 years ago

No news as of yet, as there hasn't been an update to the original 3.6.0.0.510 release version chain. I suppose the question would be if this fix will be implemented into the next point release or not.

4 Messages

 • 

122 Points

3 years ago

i ve a lot of connection failures also with 3.5.1.0.1026
i  don't have any autentications errors, i don't understand what could be the issues. 
Tech support told me that is ok, and it s normal... (i don't think).
i tried different configuration but the result was always teh same.

1 Message

 • 

60 Points

3 years ago

Same thing here. any news on this case ? 

4 Messages

 • 

122 Points

3 years ago

wow! nice that somebody else is facing these problems! :D

116 Messages

 • 

2.3K Points

3 years ago

Any word on when the next level of firmware will be released to fix this issue?

1 Message

 • 

62 Points

3 years ago

I had this with R710 APs, on 3.5.1 after migrating them from ZD 9.13. After a couple of hours of head scratching, checking everything was working and looking for an issue. I rebooted the APs and all the errors cleared. *shrugs*