Realy slow and unstable TX/RX Rates
Hello to all.
I have an Installation (big house) with a lot of clients (IoT)
All the APs are EAP615wall and EAP610Outdoor. Router ER605. Switch, SG2428P. All of them with the latest firmware. Running a virtualized Controller, also the latest version.
Now, the problem is that suddenly, the TX and RX went crazy
All connections ara really slow and stable. Any idea why? can anybody help me?
BR
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
Hi @artucast
there could be several reasons of the crazy RX, TX rate:
**1. Network Congestion** - **Increased Traffic**: With a large number of IoT clients, there might be a sudden spike in network traffic. For example, if many IoT devices start sending data simultaneously, such as security cameras uploading high - resolution footage, or a batch of smart sensors sending out readings due to an environmental trigger.
**2. Wireless Interference** - **External Interference**: There could be external sources of interference affecting the wireless signals of your EAP615wall and EAP610Outdoor access points. This could be from neighboring Wi - Fi networks, microwave ovens, cordless phones, or other electronic devices operating in the 2.4GHz or 5GHz bands. -
**Internal Interference**: In a large house installation, the access points themselves might be interfering with each other. If they are placed too close together or on overlapping channels, it can lead to signal degradation and erratic TX and RX rates.
**Suggested Solution**: Use a Wi - Fi analyzer tool to identify the channels used by neighboring networks and your own access points. Try to re - configure the channels of your access points to less congested ones. Also, ensure that the access points are placed at an appropriate distance from each other to minimize interference.
For more details, please refer to this article:
- Copy Link
- Report Inappropriate Content
Hi @artucast
there could be several reasons of the crazy RX, TX rate:
**1. Network Congestion** - **Increased Traffic**: With a large number of IoT clients, there might be a sudden spike in network traffic. For example, if many IoT devices start sending data simultaneously, such as security cameras uploading high - resolution footage, or a batch of smart sensors sending out readings due to an environmental trigger.
**2. Wireless Interference** - **External Interference**: There could be external sources of interference affecting the wireless signals of your EAP615wall and EAP610Outdoor access points. This could be from neighboring Wi - Fi networks, microwave ovens, cordless phones, or other electronic devices operating in the 2.4GHz or 5GHz bands. -
**Internal Interference**: In a large house installation, the access points themselves might be interfering with each other. If they are placed too close together or on overlapping channels, it can lead to signal degradation and erratic TX and RX rates.
**Suggested Solution**: Use a Wi - Fi analyzer tool to identify the channels used by neighboring networks and your own access points. Try to re - configure the channels of your access points to less congested ones. Also, ensure that the access points are placed at an appropriate distance from each other to minimize interference.
For more details, please refer to this article:
- Copy Link
- Report Inappropriate Content
Thanks for your help.
Could it be that the EAP615Wall is not suitable for this application? Maybe the EAP650wall is better?
Now, each EAP615wall is servicing between 10 and 20 clients, but they are all low-traffic, except for one TV and a few phones.
I ran the WLAN optimization process a few times, and now it shows 87%
Can I config something to prioritize the "important" clients?
Thanks
- Copy Link
- Report Inappropriate Content
Hi @artucast
Regarding to the wireless performance, there is no big difference between EAP615-wall and EAP650-wall.
If you also have Omada SDN gateway, you can consider configure QoS:
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 104
Replies: 3
Voters 0
No one has voted for it yet.