nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

AP firmware 3.6.0.0.709 High Connection Errors

unknown

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.

Find more posts tagged with

Accepted answers

All comments

unknown

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.

unknown

Well.. not many alarms on it, but if I show the Connection Failures on the AP list, it looks like this:

Site One:
Image_ images_messages_5f91c437135b77e2479c1b2b_224dbe3eddbed4a66afb112f8fb3c896_RackMultipart20171214112667144-5be1fd2d-7fb5-475e-8ffe-bd14fe67c744-80228751.png1513243069

Image_ images_messages_5f91c437135b77e2479c1b2b_224dbe3eddbed4a66afb112f8fb3c896_RackMultipart20171214112667144-5be1fd2d-7fb5-475e-8ffe-bd14fe67c744-80228751.png1513243069

Site Two:
Image_ images_messages_5f91c437135b77e2479c1b2b_fbcd7b23ebae12a5581531e1f92a0aef_RackMultipart20171214834051i8b-f03ee78b-3c83-48de-aef1-a3467261cc26-2096024891.png1513243096

Image_ images_messages_5f91c437135b77e2479c1b2b_fbcd7b23ebae12a5581531e1f92a0aef_RackMultipart20171214834051i8b-f03ee78b-3c83-48de-aef1-a3467261cc26-2096024891.png1513243096

Not sure what to think of that..

unknown

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

unknown

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

unknown

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

unknown

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.

unknown

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.

unknown

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

unknown

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

unknown

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.

unknown

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

unknown

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

unknown

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.

unknown

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.

Image_ images_messages_5f91c441135b77e2479ec196_94d553e872e156157ad3b35e3dd08901_RackMultipart201802081310631pd-d9fc6b7e-c62b-4900-97c1-10d0f3c197a1-637509637.png1518079298

Image_ images_messages_5f91c441135b77e2479ec196_94d553e872e156157ad3b35e3dd08901_RackMultipart201802081310631pd-d9fc6b7e-c62b-4900-97c1-10d0f3c197a1-637509637.png1518079298

unknown

Same thing here. any news on this case ?

unknown

wow! nice that somebody else is facing these problems! 😄

unknown

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

unknown

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*

unknown

This has not been fixed with the latest SmartZone 3.6.1.0.227 (MR1) patch.

eizens_putnins

I upgraded today to 3.6.1. and can confirm -- bug is still there. But at least users are not affected...

klaus_heidelber

I have the same here. And in the troubelshooting section I can see the devices have many 802.11 Authentication Request/Response packets. Connection seems to take longer than on previous code.

klaus_heidelber

Running on latest 3.6.1.0.227 code

unknown

Agreed, noticed the same. Hopefully they can get this resolved with next release.

unknown

From 3.5 to 3.6, health metric is more detailed and seperated.

I think metric is calculated by authentication and association in 3.5.
Otherwise, In 3.6, metric is calcualted by more factor such as association, authentication, dhcp, eap.

If in 3.6 percent of failed dhcp packet is increase, metric would be more higher than 3.5's

If it is a bit fixed, the metric will be great to check health.

Regards.

unknown

Anyone has an idea if this has been fixed in the lates OS ?

peter_riederer_

in the current Version 5.0 there are no issues anymore

klaus_heidelber

Did you see the many 802.11 Authentication Request/Response packets before? Is this fixed, too?