javier_sanchez_7643553's profile

6 Messages

 • 

126 Points

Thu, Dec 31, 2015 5:15 PM

The Roaming not work, and users disconnect constantly even not move around.

I have a network with 16 AP (10 R500 and 6 R300) and a 1200 controller,2 SSID with WPA/AES and i need use a softphone but i have the next issue with some users:
All the Iphone ́s was disconnect constantly
An a Samsung Note 4 lost wifi signal and block the wifi networks when it moves of a R500 to a R300 (We need to turn on and off the airplane mode to resolve the issue)
More than 10 users with laptops HP and wireless card ralink rt3290 can not connect with the network (i upgrade the drivers and some laptops can connect now but the navigation on the net was terrible slow)
When i walk through the office and change of one AP to another and if i am in a call this ends, and the use of softphone it is very important in this project.

I hope anyone can help me.

Responses

Brand User

Former Employee

 • 

2.6K Messages

 • 

44.8K Points

6 y ago

I think you should go to Tech Support.

333 Messages

 • 

5.1K Points

6 y ago

If you are using 9.10 MR1and have force dhcp enabled you will have a roaming issues - this will be fixed in 9.10 MR2 and 9.12MR2

Solution is if you have force dhcp enabled is to disable this function to solve roaming issues.

6 Messages

 • 

126 Points

6 y ago

Thanks i will try it, and comment how work it.

Champion

 • 

202 Messages

 • 

3K Points

6 y ago

If "force dhcp" turns out not to be your problem, ask your support rep if the "smartroam" feature is appropriate for your location/application.

99 Messages

 • 

2K Points

6 y ago

Hi Javier,

First I would separate your problem into two different event, one is the client constantly disconnecting even when the client is not "roaming" and two, client stop working after a roam.

For the first issue, it's kind of hard to say if the client is truly not roaming, even stationary client can "roam" between APs under the correct, or better description is under the wrong condition. You should be able to review the controller log to see if the client is truly changing APs or not.  If it is not "roaming" and you are still "disconnecting", please verify if the client is still associated but just can not pass traffic.  I have seen a few case where this was the case where client's seem to loose IP connectivity for a while and was still associated to the AP.  If this is the case 9.12MR2, which should be released soon, should fix that.

For the second issue, Bill is probably correct, it's either a sticky client issue and the client is stuck on an inappropriate AP.  The only thing that I would suggest that is different is not to use Smartroam if you have Apple OS or iOS, as they have an automatic blacklist feature where too many kick via smartroam will trigger this feature and keep the client from connecting to the wlan again for sometime.  Depending on the AP density, I would use a higher BSS minrate to ensure that the client can not hear an AP's beacon when it's too far away, this way it will be the client decision to roam if it can't hear the AP's beacon at 12 Mbps for example.  You can use BSS min rate and Smartroam at the same time but it's generally not needed.

Without any more data to go on, I would suggest two things:
1. upgrade to 9.12MR2 as soon at it comes out
2. set the wlan BSS min rate to 12

Force DHCP should should not be needed/used, it was originally designed to keep people from statically configuring a client with the same IP as the Gateway or the controller causing network issue, it was not designed to help a client roam.

Sid

6 Messages

 • 

126 Points

6 y ago

Thanks for your help, i actually upgrade the system to 9.12 and works better, now i try with the Min rate and comment my results.

Kind regards

Champion

 • 

202 Messages

 • 

3K Points

6 y ago

'though this post recommends smartroam and smartroam may not be an appropriate solution for you, there may be other things about it that help...
https://forums.ruckuswireless.com/ruckuswireless/topics/best-practice-configs-for-a-high-density-dep...

6 Messages

 • 

160 Points

6 y ago

On the ZD models we noticed roaming will not work with WPA make sure you have security set to WPA2.

Champion

 • 

202 Messages

 • 

3K Points

6 y ago

John + Sean:

Sid is the best Ruckus support agent I know of.
He's suggesting bss-minrate (and avoiding smartroam) as the best solution for rapidly-roaming stationary clients and iOS devices that may "give up" after being repeatedly kicked.

Please let me know if the following summary is accurate:

Roaming issues:
John:Y   Sean:N    Bill:Y

smartroam
John:1   Sean:4    Bill:1/2

ofdm-only
John:N   Sean:Y    Bill:Y

bss-minrate
John:5.5 Sean:24   Bill:12/24

load-balancing
John:Y   Sean:17dB Bill:N

band-balancing
John:Y   Sean:0%   Bill:N


We all have smartroam configured but Sean is the only one not reporting roaming issues.
Sean also has the highest bss-minrate of "24" across the board.
(I'm showing configs for my outdoor public access areas, where I have a bss-minrate of "12" for the 2.4Ghz spectrum and "24" for the 5Ghz spectrum)
Sean's smartroam setting seems very aggressive at a roaming factor of "4".

I wonder if that aggressive roaming factor may be "saving" him from smartroam problems.
My understanding is that a smartroam "kick" will happen when the client is seen to cross the threshold from the "strong" side to the "weak" side of the roaming factor. With a roaming factor that high, a client might never roam to another AP (due to a kick) unless it's in a very high density of AP situation.

Following that rationale, maybe we should try a bss-minrate of "24" across the board?
I'm not sure I'd want to try that in areas w/ a lot of cinder-block, etc. but maybe in places where I'm not concerned about the AP density being too light to support it.

Opinions?

Champion

 • 

202 Messages

 • 

3K Points

6 y ago

John:

I would assume that Javier's environment includes areas of indoor coverage w/ "light" construction that's not very challenging to WiFi propogation, that his APs have good overlapping coverage, that there's no interference from competing WiFi or other devices, that his channel plan is "stable" (with APs not changing channels often) and that his iPhones (when in those areas) still "disconnect constantly".
Hopefully Javier can confirm all those things.

Do you think it's possible for Javier to adequately describe his environment's "unknown factors"?
or.. that his issue goes beyond what can be addressed in a forum like this?

I'm noticing that Javier is using beam-forming R500s and non-beam forming R300s.
(and having problems when physically roaming from R500s to R300s)
Personally, I would use the R500s and R300s in different areas, as opposed to using them close together in "unobstructed" areas.

If Javier puts all his R500s in one area and R300s in another:
It would be interesting to know if Javier still sees his iPhone problems in areas w/ R300s or only in areas w/ R500s.

Important Announcement