Link to home
Start Free TrialLog in
Avatar of matedwards
matedwardsFlag for United Kingdom of Great Britain and Northern Ireland

asked on

Ruckus Zoneflex 7982 multiple SSIDs disconnects

We have some stand alone Ruckus Zoneflex 7982 APs (ie there is no controller).

We introduced 2 SSIDs on 2 different VLANS.
At first all seemed to work fine but we've noticed some mobile clients, especially Macbooks, disconnect after a few minutes.
If the wireless NIC is turned off and on again on the Macbook they reconnect for another 5 minutes and then the problem happens again.
On the Ruckus APs, I have increased the Beacon Interval time from 100ms to 400ms as is advised on most wireless systems when using multiple SSIDs.

Are there any other settings I need to change?

Many thanks in advanced.
Avatar of Craig Beck
Craig Beck
Flag of United Kingdom of Great Britain and Northern Ireland image

I've never heard that increasing the beacon interval to 400ms is recommended.

Have you performed a wireless survey?
What version of firmware is on it? And have you looked at the Inactivty Timeout? If so, try to set that to something on the order of 500 minutes (some versions of hardware maxed this out at 10, which got fixed eventually, meaning that you may need to update the firmware if yours currently maxes out at 10).

Here's an article from Ruckus even acknowledging that they had messed up at a point in time: https://forums.ruckuswireless.com/ruckuswireless/topics/disabling-client-inactivity-timeout

Additionally, also do a survey as Craig Beck has recommended.
Avatar of matedwards

ASKER

Thanks Craig.. I haven't done a wireless survey as I'm just a sys-admin with no specialist equipment.

This sonicwall wireless configuration video explains increasing the Beacon Interval (7min:25sec). I've also read similar in the Cisco Wifund course.

https://www.youtube.com/watch?v=c9jPTJYrgRo

Many thanks for your help.
Thanks masnrock, I will check firmware first thing. Although, users have said they are surfing the net when the Macbook disconnects.

Many thanks for your help
With respect, I design Cisco-based enterprise networks and use their design guides regularly.  I've never seen 400ms specifically mentioned anywhere.  

You should always leave the beacon period alone (100ms on Cisco kit) unless there's a good reason to change it, and consider the DTIM value too if you do. If you don't get this right it can be catastrophic to wireless connectivity.
Apologies Craig, looks like I've got mixed up with the Guard Interval (800/400ns).

Why does Sonicwall advise a Beacon Interval of 400 for multiple SSIDs? Some other message boards suggest reducing or increasing depending on your environment.

Could you suggest some 'common' settings for a campus of 8 WAPS with 100 roaming clients?

Would trying to get all clients into the 5GHz band help? A quick look with NetSpot shows many 2.4GHz networks nearby that must be interfering with ours.
 
Masnrock.. the firmware version is 9.6.1.0.15. So I think the time out is, as you suggested, 500min.

Again thanks for the help...
Our other campuses are all sonicwall/sonicpoint wireless and they won't allow a beacon Interval of less than 200 for multiple SSIDs.!!

I'm getting more confused.??
SOLUTION
Avatar of masnrock
masnrock
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Yep, couldn't agree more Masnrock.

The Sonicwall/point system just doesn't seem up to the job unless it's WPA2 only.

I will check timeout settings.

Many thanks again
ASKER CERTIFIED SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
I took the beacon interval back down to 100. I also had one SSID broadcast solely in the 5Ghz band and the other SSID solely in the 2.4GHz band. Without a controller I tried to manually separate the networks as best as I could. Stability appears to be much better.

Again, thanks for the help.