Mesh Roaming Issues

  • 1
  • Question
  • Updated 3 years ago
We got a small'ish mesh running on 7762-s outdoor APs and a 1100 ZD. The roaming between APs takes about 30-40 seconds on average. This can't be normal, and I can't seem to correct it. Any advice/help please?
Photo of Christo Greeff

Christo Greeff

  • 7 Posts
  • 0 Reply Likes

Posted 3 years ago

  • 1
Photo of Keith - Pack Leader

Keith - Pack Leader

  • 860 Posts
  • 51 Reply Likes
Hi Christo - can you give us more details? What kind of client? How close are the AP's to one another? What version of ZoneFlex (er..Smart/OS) is running?

Are you really running a mesh? (where some of your AP's are only wirelessly connected to the ZD?) How many "hops" are in the mesh?
Photo of Primož Marinšek

Primož Marinšek, AlphaDog

  • 413 Posts
  • 48 Reply Likes
Do you mean that clients get disconnected and reconnect after 40s or are you just expecting them to change an AP at a particular point?
Photo of Christo Greeff

Christo Greeff

  • 7 Posts
  • 0 Reply Likes
Hi Keith

Herewith my answers, sorry for the late reply but was on the road.

Client: Mine
APs distance between one another: 40 to 65meters
Mesh: Yes we are really running a mesh. We've done a few installations in the past. There are two root APs and then another 4 APs. The other 4 APs all have 1 hop to their respective root AP. From the root APs there are CAT6 cables going to a PTP CPE that is connecting 500m away to a Sectorised Antennae. From the sectorised antennae it goes into a switch and breaks out to the internet/business servers, etc.
Smart OS: Unfortunately I am not on site anymore to login and confirm this

kind regards,
Christo
Photo of Keith - Pack Leader

Keith - Pack Leader

  • 860 Posts
  • 51 Reply Likes
Sorry - by client I mean device type. Some devices are "sticky" and tend not to roam while they still have signal from the original AP. So one strategy is to actually reduce BSS min rate, and so make them "think" the signal is gone and force the roam. Sometimes the client device hears the AP, but the AP can't hear the (much weaker) client and so it fails to roam and loses connectivity.
Photo of Primož Marinšek

Primož Marinšek, AlphaDog

  • 413 Posts
  • 48 Reply Likes
Are there a lot of other networks around the area? Maybe there are so many that the channel is busy and access to the medium takes to long. Are you experiencing this with all clients or just some?

Also explain please what you mean by "From the root APs there are CAT6 cables going to a PTP CPE that is connecting 500m away to a Sectorised Antennae". I'm not getting the last part of this sentence.

Maybe some "Airtime stats", "PHY Error Stats" and some info on stuck beacons on APs that the client roams from and roams to would probably be helpful.

Best way to get those would be via ZD WEB GUI under Monitor :: APs where you would click on the "System info" icon next to the APs in question. Maybe you can paste the "Airtime stats", "PHY Error Stats" and info on stuck beacons for "radio 0" here so we can look if it's something obvious, otherwise you will probably need to open a case, but don't do it just yet.
Photo of Christo Greeff

Christo Greeff

  • 7 Posts
  • 0 Reply Likes
Hi Keith

I think that is one way of doing it for sure and makes sense. However, by reducing power, we might lose a bit of coverage. The area is filled with small steele houses (about 50 of them) and so penetration is obviously an issue.

And then to answer Primoz.....hi....

No, it is in a newly developed area that is rural so no other network interference. We manage the network fully. To explain my sentence...

There is a centralized basestation. From the two root APs there is an additional CPE that connects via Cat6 to the Ruckus Root AP and wirelessly to the basestation.

There are no PHY error stats - zero currently.
Photo of Christo Greeff

Christo Greeff

  • 7 Posts
  • 0 Reply Likes
Hi Keith/Primoz,

But I reckon that it might be the devices themselves.....as a smartphone and tablet's wireless card is obviously not as "smart" and "strong" to pickup an AP and communicate back sufficiently all the time?
Photo of Primož Marinšek

Primož Marinšek, AlphaDog

  • 413 Posts
  • 48 Reply Likes
Yes, it's the clients choice to which AP (BSSID) it will connect, however Ruckus has a SmartRoam feature you can set to help with roaming. Read about how to set it up here https://support.ruckuswireless.com/an...

Keith suggested you use a higher minimum rate, not lower the transmit power. By doing that you hopefully make the client think of searching for a new AP faster so it doesn't hold on for deal life at speeds of 1Mbps, but rather at 5,5Mbps or even higher. It's available from FW 9.6 if I'm not mistaken.

Tell us FW version please? Are you tunnelling traffic to the ZD maybe? What kind of authentication are you using? What are you using on for wireless connection from CPE to the base station (WiFi, WiMax, 3G, Microlink,...)?
Photo of Christo Greeff

Christo Greeff

  • 7 Posts
  • 0 Reply Likes
Hi Primoz

Thanks for feedback once again. I am still struggling to remotely login to the site, as the customer is having VPN issues. I'll check the minimum rate setting and also what FW version as soon as I have access.

Authentication on all wireless is WPA2-AES. From CPE to basestation we are using a wireless PTP (WiFi) link.
Photo of Primož Marinšek

Primož Marinšek, AlphaDog

  • 413 Posts
  • 48 Reply Likes
Just some thoughts below.

Can you maybe disable encryption and check if the problem persists?

Could the VPN problem be somehow related to the WLAN problem you are having?

Another thing. Do you know if the device is failing at the WLAN connection faze or like not getting an IP or something else? Does it change anything if you configure a static IP on the device?

Does the device associate immediately if you have WiFi on it disabled and you enable it, or does it take that long even if not roaming?

Where is the ZD in this topology? Is it off-site or on site and where? Is there a big latency somewhere maybe?