TP-Link Omada AP Mesh Network Troubleshooting Guide
EAP683 UR , EAP653 UR , EAP660 HD , EAP225-Outdoor , EAP773 , EAP625-Outdoor HD , EAP245( V3 V3.6 V4 V4.6 ) , EAP783 , EAP772 , EAP650 , EAP265 HD , EAP115-Bridge KIT , EAP610 , EAP225( V3 V3.6 V4 V4.6 V4.80 V5 ) , EAP623-Outdoor HD , EAP610-Outdoor , EAP650-Outdoor , EAP211-Bridge KIT , EAP655-Wall
Recent updates may have expanded access to feature(s) discussed in this FAQ. Visit your product's support page, select the correct hardware version for your device and check either the Datasheet or the firmware section for the latest improvements added to your product.
Contents
Case 1: Fail to discover Mesh AP
Case 2: Unstable/disconnected Mesh AP
Case 3: Clients get slow speed with Mesh network
The article introduces various ways to troubleshoot an Omada AP Mesh Network.
- Omada Controller (Software Controller / Hardware Controller / CBC)
- Omada AP
This article applies to: Omada Mesh Devices
Mesh is used to establish a wireless network or expand a wired network through a wireless connection on the 5GHz and 6GHz radio bands. We can use Omada AP products to build mesh networks in indoor and outdoor areas.
Here are the instructions on how to set up mesh with different management methods:
Omada Controller: How to Build a Mesh Network via Omada EAP in Controller Mode
Omada APP: How to Configure your Omada EAP into a Mesh Network Using the Omada App
You might initially encounter difficulties setting up your mesh network or experience performance problems after configuration. To assist you, we've outlined some troubleshooting steps below. We'll cover two key areas:
Root AP: In a mesh topology, APs in the Omada Controller network are accessed via wired Ethernet.
Mesh AP: In a mesh network, APs are managed via wireless uplink
Case 1: Failure to discover the Mesh AP
Step 1. Log in to the Controller, go to Settings > Site > Wireless Features to confirm that Mesh and Auto Failover are enabled.
Step 2. Ensure the mesh AP is powered and isolated, with no wired connections to the gateway, switch, or other APs. Then, verify if the AP's LED is slowly flashing (4.2 seconds on, 0.8 seconds off).
Step 3. Make sure the mesh AP is within the coverage of the root AP, and try to place them in the same room for the first installation.
Step 4. If the Root AP's 5G band is configured to use a DFS channel, it's expected that the Mesh AP won't be discoverable in the 5GHz band during the Channel Availability Check (CAC) period.
Step 5. Confirm that the Root AP is working on a channel supported by the Mesh AP. It is recommended that the Root AP be deployed to band 1 first.
Step 6. Try changing another AP to the Root AP and discovering the Mesh AP again.
Step 7. Hard reset the APs and try again.
Case 2: Unstable/disconnected Mesh AP
Step 1. Perform a ping test on the computer where the Root AP is located. If the mesh AP cannot be pinged continuously, troubleshooting is recommended according to the steps in Case 1.
Step 2. An unstable mesh connection is likely if a Mesh AP is pingable but experiences high packet loss or latency. Determine the Mesh AP's hop count, as Omada APs support up to three hops. More hops can increase interference and connection issues. Consider reducing the hop count for better performance.
Step 3. Confirm whether the channel utilization of the band where the mesh is located is too high. If so, please adjust it to a bandwidth and channel with less interference.
Step 4. Modify the transmit power of the Root AP
Log in to the Controller, navigate to Devices > Config > Radios > Tx Power to adjust the transmit power to an appropriate level. Remember, higher transmit power can increase interference with neighboring APs. To improve connection stability, gradually decrease the transmit power until the issue is resolved.
Step 5. If the Mesh AP can automatically reconnect, check the signal strength on the Omada Controller. Please tap on the Mesh AP to view the signal quality between it and its parent access point.
Generally, a signal strength of -30dBm is excellent, -60dBm is normal, and -80dBm is weak. If the signal is weak, please relocate the Mesh AP closer to the Root AP or switch to a different uplink AP.
Step 6. If the disconnected AP won't get back online after all these steps, please forget it on the Controller or hard reset it and try to add it again.
Case 3: Clients get slow speed with Mesh network
Step 1. If the client connects to the Root AP and receives slow speed, please refer to the following steps:
- Connect a PC directly to the front router/ switch and check whether the wired speed is normal.
- Confirm if settings such as bandwidth control are set up on the router/switch.
- Confirm if the Rate Limit is configured and enabled on the AP.
- Change the Ethernet cable from AP to the front router/switch.
- Check the signal strength and the distance from the client to the AP during the speed test.
- Check for any obstacles between the AP and the client or if the speed is normal when the client is closer to the AP.
- Check whether there are multiple APs located near one another.
- Check if the channel utilization is high: Change the channel, channel width, and TX power, then test the speed again.
- Confirm if the Multicast-to-Unicast Conversion function is enabled.
- Ensure the AP’s firmware is the latest. Reset the AP and create a new SSID (or keep the default SSID) for the speed test.
Step 2. If the client connects to the Mesh AP and gets slow speed, please refer to the following steps:
NOTE: Because Mesh APs share wireless bandwidth with connected clients, their performance might be lower than that of those directly connected to the Root AP. This can result in slower speeds. The following factors could be contributing to this issue:
- Confirm at which hop the Mesh AP is located. The larger the number of hops, the greater the interference or loss of the mesh connection, which will also affect the speed test results. You can reduce the hops for a better user experience.
- Check the signal strength of the associated clients. If the RSSI associated with the client is less than -75dBm, it may result in a low negotiation rate. Check whether the client and the AP are too far apart and confirm whether there is any obstruction between them.
- Check whether there are multiple APs located in close proximity.
- Check if the channel utilization is high. Please change the channel/channel width/TX power, then test the speed again.
- Confirm if the Multicast-to-Unicast Conversion function is enabled.
- Make sure the AP’s firmware is the latest. Reset AP and create a new SSID (or keep the default SSID) for the speed test.
If the problem still exists after trying the above steps, please contact TP-Link technical support for further help.
To learn more about each function and configuration, please go to the Download Center to download the manual of your product.
Looking for More
Is this faq useful?
Your feedback helps improve this site.
What’s your concern with this article?
- Dissatisfied with product
- Too Complicated
- Confusing Title
- Does not apply to me
- Too Vague
- Other
We'd love to get your feedback, please let us know how we can improve this content.
Thank you
We appreciate your feedback.
Click here to contact TP-Link technical support.
TP-Link Community
Still need help? Search for answers, ask questions, and get help from TP-Link experts and other users around the world.
We have updated our Policies. Read Privacy Policy and Terms of Use here.
This website uses cookies to improve website navigation, analyze online activities and have the best possible user experience on our website. You can object to the use of cookies at any time. You can find more information in our privacy policy .
We have updated our Policies. Read Privacy Policy and Terms of Use here.
This website uses cookies to improve website navigation, analyze online activities and have the best possible user experience on our website. You can object to the use of cookies at any time. You can find more information in our privacy policy .
Basic Cookies
These cookies are necessary for the website to function and cannot be deactivated in your systems.
TP-Link
accepted_local_switcher, tp_privacy_base, tp_privacy_marketing, tp_smb-select-product_scence, tp_smb-select-product_scenceSimple, tp_smb-select-product_userChoice, tp_smb-select-product_userChoiceSimple, tp_smb-select-product_userInfo, tp_smb-select-product_userInfoSimple, tp_top-banner, tp_popup-bottom, tp_popup-center, tp_popup-right-middle, tp_popup-right-bottom, tp_productCategoryType
Livechat
__livechat, __lc2_cid, __lc2_cst, __lc_cid, __lc_cst, CASID
Youtube
id, VISITOR_INFO1_LIVE, LOGIN_INFO, SIDCC, SAPISID, APISID, SSID, SID, YSC, __Secure-1PSID, __Secure-1PAPISID, __Secure-1PSIDCC, __Secure-3PSID, __Secure-3PAPISID, __Secure-3PSIDCC, 1P_JAR, AEC, NID, OTZ
Analysis and Marketing Cookies
Analysis cookies enable us to analyze your activities on our website in order to improve and adapt the functionality of our website.
The marketing cookies can be set through our website by our advertising partners in order to create a profile of your interests and to show you relevant advertisements on other websites.
Google Analytics & Google Tag Manager
_gid, _ga_<container-id>, _ga, _gat_gtag_<container-id>
Google Ads & DoubleClick
test_cookie, _gcl_au
Meta Pixel
_fbp
Crazy Egg
cebsp_, _ce.s, _ce.clock_data, _ce.clock_event, cebs
Hotjar
OptanonConsent, _sctr, _cs_s, _hjFirstSeen, _hjAbsoluteSessionInProgress, _hjSessionUser_14, _fbp, ajs_anonymous_id, _hjSessionUser_<hotjar-id>, _uetsid, _schn, _uetvid, NEXT_LOCALE, _hjSession_14, _hjid, _cs_c, _scid, _hjAbsoluteSessionInProgress, _cs_id, _gcl_au, _ga, _gid, _hjIncludedInPageviewSample, _hjSession_<hotjar-id>, _hjIncludedInSessionSample_<hotjar-id>
lidc, AnalyticsSyncHistory, UserMatchHistory, bcookie, li_sugr, ln_or