I have 4 AP 2 indoor (eap660) and 2 outdoor (eap610,eap225)
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Sorry for picking AP200 mine is not on the list.
So I have Omada TP-Link SDN Four AP 2 indoor (eap660 v1.0 1.1.1) and
2 outdoor (eap610 v1.0 - FW:1.1.3, eap225 v3.0 - FW:5.1.0)
and all connected as a MESH network.
And some indoor clients are connecting to the outdoor AP even though the
AP indoor is closer to the client. This confuses me. Is this normal?
It also seems clients may be bouncing between APs which causes issues
when trying to view cameras or interact with them.
Maybe the APs are too close to each other? I am not sure how far apart
they should be.
Sorry for the compounded issues. In the Omada controller web GUI, I also
see % utilized high on the 2.4 sides with a large gold (interference) bar.
Any assistance is appreciated.
The only way to see if an AP is too close to another is via RSSI or DB readings. Ideally you want to be standing under AP1 and see AP2 at around -65db, that allows a good margin of error. If its -50, then its too strong, -75 then too weak.. 65ish is the magic number.
Also remember if manually settings channels to swop them around to avoid interference, dont have 2x APs close on channel 11 unless you need to. Roaming will happily work from all channels. Look to do something like this if possible keeping the same channel APs as far apart as possible
Other option is just let the controller choose the channels and power, its generally good at it and sometimes the best idea. Your neighbours and airspace will change daily, let the controller adjust to fix this.
Under Settings > WiFi there is a tool called AI WLAN, schedule this to run daily and let it scan at say 3am.. it will change the channels as needed, find it works for me.
That orange bit is contention / noise. Could be the other APs or just interference. Sadly in 2.4ghz its not going to get much better, its a pretty saturated frequency so try to use band steering to move as many as possible to the 5ghz.
If you have clients jumping AP a lot and want stop this you have two options really.
1. use the new lock to AP feature to stop that client roaming
2. disable AI Roaming, that will reduce the proactive roaming its doing.. but could also affect the load balancing overall. Its a test and see scenario.
In terms to where it is connecting (what AP). This isnt hard and fast the closest one is best, say im right beside AP1 and its -50db (good signal) with AP2 nearby at -60. Obviously AP1 is the better choice, that is until you consider that AP1 has 6 other clients at this time, AP2 is idle. The slight loss in signal strength and speed will be greatly compensated by the un-contested access to AP2, therefore its the better option overall. AI Roaming will make this decision for you and attempt to load balance things
The only way to see if an AP is too close to another is via RSSI or DB readings. Ideally you want to be standing under AP1 and see AP2 at around -65db, that allows a good margin of error. If its -50, then its too strong, -75 then too weak.. 65ish is the magic number.
Also remember if manually settings channels to swop them around to avoid interference, dont have 2x APs close on channel 11 unless you need to. Roaming will happily work from all channels. Look to do something like this if possible keeping the same channel APs as far apart as possible
Other option is just let the controller choose the channels and power, its generally good at it and sometimes the best idea. Your neighbours and airspace will change daily, let the controller adjust to fix this.
Under Settings > WiFi there is a tool called AI WLAN, schedule this to run daily and let it scan at say 3am.. it will change the channels as needed, find it works for me.
That orange bit is contention / noise. Could be the other APs or just interference. Sadly in 2.4ghz its not going to get much better, its a pretty saturated frequency so try to use band steering to move as many as possible to the 5ghz.
If you have clients jumping AP a lot and want stop this you have two options really.
1. use the new lock to AP feature to stop that client roaming
2. disable AI Roaming, that will reduce the proactive roaming its doing.. but could also affect the load balancing overall. Its a test and see scenario.
In terms to where it is connecting (what AP). This isnt hard and fast the closest one is best, say im right beside AP1 and its -50db (good signal) with AP2 nearby at -60. Obviously AP1 is the better choice, that is until you consider that AP1 has 6 other clients at this time, AP2 is idle. The slight loss in signal strength and speed will be greatly compensated by the un-contested access to AP2, therefore its the better option overall. AI Roaming will make this decision for you and attempt to load balance things
@Philbert
OK, excellent all 4 APs are in the 60's now.
I did enable Load balancing on the 1 wired AP and the other eap660 (playroom).
I do see each AP is on a different channel on 2.4Gz.
I have 1 AP that is wired the other 3 are wireless and linked to the wired AP
