Skip to main content

6 Messages

 • 

130 Points

Thu, Jan 7, 2016 2:19 AM

Answered

ZoneFlex R500 Intermittent Client Disconnects

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

Responses

74 Messages

 • 

1.6K Points

5 years ago

Doug, what is the client device? Make/model/os version?

333 Messages

 • 

5.1K Points

5 years ago

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 :)

6 Messages

 • 

130 Points

5 years ago

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!! :)

6 Messages

 • 

130 Points

5 years ago

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)"


333 Messages

 • 

5.1K Points

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.

6 Messages

 • 

130 Points

Can't do that until tonight Sean but I'll take a look - does the support file have diag info at the bottom?

6 Messages

 • 

130 Points

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.

Brand User

Former Employee

 • 

2.6K Messages

 • 

44.8K Points

5 years ago

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

6 Messages

 • 

130 Points

5 years ago

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?

333 Messages

 • 

5.1K Points

What is the timing between the clients connecting and them being disconnented.

This may be related to session inactivity settings.

1 Message

 • 

80 Points

4 years ago

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.

11 Messages

 • 

204 Points

2 years ago

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"...
Brand User

Former Employee

 • 

2.6K Messages

 • 

44.8K Points

You must have R310 model APs running Unleashed (R300 wasn't supported)?  Are you running the latest Unleashed release?
(check online upgrade), or download FW here:
https://support.ruckuswireless.com/software/1817-ruckus-unleashed-ap-200-6-10-1-312-ga-refresh2-soft...
hoping that you might see improved performance. 
I have not heard of APs just "dying" unless they rebooted, which could be seen in logs.

11 Messages

 • 

204 Points

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.

11 Messages

 • 

204 Points

Help...

11 Messages

 • 

204 Points

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

11 Messages

 • 

204 Points

Well, it never came online so I pressed "removed" it. Now I have to figure out how to add it back in.