EAP650 mesh nodes roaming clients no connection (until EAP restarted)
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.EAP650 mesh nodes roaming clients no connection (until EAP restarted)
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
I have a few omada APs installed and managed by a controller running in docker (latest version) on a ubuntu system:
-
3 x 650 (#1 wired, #1 wireless meshed to #1 ~-68dBm and #3 meshed to #2 ~-55dBm) - all latest FW
-
1 x 650-Wall (wired) - latest FW
Since installing #3 i have had a lot of problems with clients not roaming properly, in particular to the two APs that are wirelessly connected to the wired AP. It seems that any client will connect if near a wired AP, but if they then roam to a meshed one they lose connection (and cannot reconnect).
I have tried:
-
Set to WPA/WPA2 only
-
Disable 6GHz
-
Disable 5GHz
-
All power outputs set to low
-
Resetting the APs and reprovisioning them to the controller
The only way I can get the network to function as expected is by restarting #2 (either physically or via GUI), but even then it falls over after approx 12 hour depending on usage. I currently have a scheduled overnight restart of #2, resulting in everything working until about the evening when it fails.
It appears that clients will roam to #3, but there is then no onwards connectivity to #2 and therefore wider network/WAN. Connected to #3 AP when the system has failed allows me to ping other clients on the AP, but not #2 AP or any WAN address.
thanks for any help/ideas.
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
Happy the advice helped :)
Sounds like you can safely fix your 5.8G radios at 40Mhz and enjoy life now. Honestly, there's not many applications where you'd even notice the difference between 70 and 100 Mbps.
The transmit power question has a few more nuances to it, mostly around how much external inteference from other wifi systems there is, as well as how close your own APs are to each other. My go-to analogy is standing in a large room, how loud do you have to speak to be heard if the room is a) full of many people all having a multitude of conversations b) sparsely populated by a few groups having quiet conversations in the corners?
Because the meshing uses the 5.8G radios, reducing their power levels reduces the amount of signal available and makes it more susceptible to competing noise. A lot of this can be mitigated with judicious channel selection, but some people have no choice with their APs but to 'shout as loud as possible' in order to 'drown out' the local competition.
- Copy Link
- Report Inappropriate Content
On the min RSSI question, again very subjective based on your location. You will need to actually measure the AP power in your desired 'transition' zones...and you may find surprises...ie expected signal strengths are different than what you would have expected...RF is a funny creature.
- Copy Link
- Report Inappropriate Content
Thanks so much for all the information! RSSI is indeed very subjective - I have moved one of the APs about 5cm and now got a -65dBm link between them.
I have left the 5GHz on 20Mhz wide, but unfortunately still have the same issue as previous with roaming clients not working when they roam to the Bureau after a while.
Does the RSSI threshold have any impact on meshed APs, i.e. will it disconnect other APs with lower signal?
EDIT - just realised whilst I'd set the wired AP to HIGH I hadn't realised the recieving AP Tx power could be independently set and still had it on Low! Now corrected, mesh signal is 57dBm and we'll see how it goes...
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 1250
Replies: 14
Voters 0
No one has voted for it yet.