ZoneFlex R500 Intermittent Client Disconnects

  • 2
  • Question
  • Updated 1 month ago
  • Answered
I'm sure this has been a topic of discussion  but I can't seem to pinpoint an actual fix or root cause. I have 2 R500 AP's running standalone and running firmware version 100.0.0.0.127. Mesh recovery has been disabled. One is manually set for channel 6 and the other for channel 11. I am getting no interference on those channels from any neighboring AP's. The closest one strong enough to cause interference is set to channel 1. The devices are not rebooting as they have been up for over 40 days. The client disconnects occur daily.

One of my issues in trying to troubleshoot this is that the logs are literally filled with the following error message that I believe is unrelated to my current issue.

Cannot notify kernel for DeleteAP (65535) event, -- Address family not supported by protocol (124)

I see a few 802.11 Deauth reason codes or 8 which should be normal when roaming between the 2 AP's. This is most likely peoples phones/tablets. The clients that are disconnecting are laptops and do not roam between the AP's.

Any insight is much appreciated!

-Doug
Photo of Doug Sutherland

Doug Sutherland

  • 6 Posts
  • 0 Reply Likes

Posted 3 years ago

  • 2
Photo of Andrea Coppini

Andrea Coppini, Employee

  • 67 Posts
  • 31 Reply Likes
Doug, what is the client device? Make/model/os version?
Photo of Sean

Sean

  • 349 Posts
  • 92 Reply Likes
If you have Base 100 on the AP's they do not offer roaming i.e. 802.11r/k as they are not aware of each other.

To fix this issue you'll need to use Unleashed

Note: You can enable smart-roam and set the value of the roam to cater for your network:

https://support.ruckuswireless.com/answers/000002277

I personally would recommend that you try Unleashed:

http://docs.ruckuswireless.com/unleashed/200.1.9.12/

Bye the way, is this Doug Sutherland that used to be at NbW?

If so Happy New Year Doug, if not Happy New Year anyway :)
(Edited)
Photo of Doug Sutherland

Doug Sutherland

  • 6 Posts
  • 0 Reply Likes

Andrea - the Dell laptops are all Windows based - Win7 or higher. Did not have any issues with old Linksys wireless router. We just expanded the office so I bought the 2 Ruckus AP's for coverage.

Sean - the R500 Ethernet ports are running at 1G - I can roam between the AP wit no problems. It is the laptops sitting in an office not moving that drops connectivity intermittently. I'm sure the tablet I roam with would drop too if I walked around long enough. Point being - I don't thinks it's associated with roaming. The radio on both AP's have the same SSID.

I'm not the same Doug that was at NbW - but Happy new Year to you too!! :)

Photo of Doug Sutherland

Doug Sutherland

  • 6 Posts
  • 0 Reply Likes

Goal right now is to remedy whatever is causing this error so I can clear my logs.

"Cannot notify kernel for DeleteAP (65535) event, -- Address family not supported by protocol (124)"


Photo of Sean

Sean

  • 349 Posts
  • 92 Reply Likes
Can you download the support file from the AP and got to the bottom and let us see whats going on as opposed to a single as that may help.
Photo of Doug Sutherland

Doug Sutherland

  • 6 Posts
  • 0 Reply Likes
Can't do that until tonight Sean but I'll take a look - does the support file have diag info at the bottom?
Photo of Doug Sutherland

Doug Sutherland

  • 6 Posts
  • 0 Reply Likes

Ok  the end of the support file is a tail of the log. I'm just trying to find the remedy for the below message as it is literally filling up the log making it difficult to see the messages that matter.

"Cannot notify kernel for DeleteAP (65535) event, -- Address family not supported by protocol (124)"

I have not tried to upgrade to the latest code yet. I have seen threads saying that v 9 is more stable. I assume these kernel events are more firmware related vs a setting being wrong somewhere.

Photo of Michael Brado

Michael Brado, Official Rep

  • 2570 Posts
  • 351 Reply Likes
I came across an article today, refering to an ER-2390 about R500 model (only) AP random reboots, fixed in latest 100.1.0.0.432 standalone image.
https://support.ruckuswireless.com/software/838-standalone-ap-software-100-1-0-0-432-indoor-aps
Photo of Doug Sutherland

Doug Sutherland

  • 6 Posts
  • 0 Reply Likes
Thanks Michael - my AP's are not rebooting at all. They have an uptime of over 40 days which is about when I installed them. I'm really trying to get rid of the kernel error listed above - any ideas?
Photo of Sean

Sean

  • 349 Posts
  • 92 Reply Likes
What is the timing between the clients connecting and them being disconnented.

This may be related to session inactivity settings.
Photo of LToled

LToled

  • 1 Post
  • 1 Reply Like
In the Stand-alone firmware 100.1.0.0.432, go to Administration - Management and Disable Controller Discovery Agent (LWAPP). This is the DeleteAP (65535) error you are seeing in the log.
Photo of Kaj Bjorlin

Kaj Bjorlin

  • 6 Posts
  • 1 Reply Like
I have the same problem with one of my two R380 Unleashed. It dies (like it reboots) once every other hour or similar and the wifi is clearly unavailable in the area that it covers when it's down. It usually stays rebooting for up to 10 minutes.... Super annoying! It's not the client disconnecting it's the AP that "dies"...
Photo of Kaj Bjorlin

Kaj Bjorlin

  • 6 Posts
  • 1 Reply Like
Well, I have now upgraded both R310 Unleashed to the latest firmware. One of them says disconnected in the web interface, however I don't think it is (the lights show me a different story). Sigh.
Photo of Kaj Bjorlin

Kaj Bjorlin

  • 6 Posts
  • 1 Reply Like
Ok so now I realized it says the disconnected has an older firmware. But when I click to upgrade it only brings up the already upgraded AP. My only option is to do "local upload" to it and I do. Then it says "when the other AP comes online there is an update button to push but that never appears...
Photo of Kaj Bjorlin

Kaj Bjorlin

  • 6 Posts
  • 1 Reply Like
Well, it never came online so I pressed "removed" it. Now I have to figure out how to add it back in.
Photo of Kaj Bjorlin

Kaj Bjorlin

  • 6 Posts
  • 1 Reply Like
Ok, so I factory reset the non-working AP using a paper-clip for 6+ seconds and then put it back hardwired on the LAN. That made it upgrade the firmware itself it seems and hopefully will come back online in the mesh.
Photo of Kaj Bjorlin

Kaj Bjorlin

  • 6 Posts
  • 1 Reply Like
Yes after a bunch of different statuses like Provisioning and Disconnected the second AP came online in the Mesh fine. Thanks! :)