Troubleshooting an Omada AP That Goes Offline Abnormally
EAP680 HD , EAP245( V3 V3.6 V4 V4.6 ) , EAP683 , EAP673-Extender , EAP230-Wall , EAP680 , EAP113-Outdoor , EAP215-Bridge KIT , Festa F65 , EAP115( V4 V4.20 V4.6 V5 ) , EAP235 , EAP650-Outdoor , EAP610 HD , EAP653 UR , EAP660 HD , EAP625-Outdoor HD , EAP670-Outdoor , EAP673 , EAP110( V4 V5 ) , EAP670 , EAP115-Bridge , EAP235-Wall , Festa F61-Outdoor , EAP225( V3 V3.6 V4 V4.6 V4.80 V5 ) , EAP215-Bridge , EAP610-Outdoor , EAP115-Wall , EAP610GP-Desktop , EAP683 UR , EAP225-Wall , EAP655-WE-AC , EAP211-Bridge , EAP225-Outdoor , EAP223 , EAP783 , EAP265 HD , EAP115-Bridge KIT , EAP620 HD , EAP613 , EAP615-WE , EAP610 , EAP653 , EAP211-Bridge KIT , EAP655-Wall , EAP615-Wall , EAP655-WE , EAP773 , EAP772 , EAP650 , EAP683 LR , EAP770 , Festa F52-Outdoor , EAP690E HD , EAP615GP-Wall , EAP723 , Festa F52 , EAP623-Outdoor HD , EAP650-Wall , EAP110-Outdoor( V3 V3.6 V3.8 )
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
This article introduces how to troubleshoot the issues of Omada AP devices going offline abnormally.
- Omada AP
- Omada Controller (Software Controller/Hardware Controller/CBC, V5.9 and above)
When AP devices go offline (displayed as DISCONNECTED on the Controller), you can refer to the troubleshooting steps in this article.
Here are the troubleshooting steps for Wired AP and Mesh AP, respectively.
Step 1. Check the LED status of the AP.
- If the LED is off, it indicates that the AP's power supply is abnormal. If a DC power supply powers the AP, check whether the power plug is fully inserted or the power cord is damaged. If PoE powers the AP, check the power sourcing equipment (PSE) and the specifications and length of the Ethernet cable.
- If the LED flashes slowly (e.g., every 5 seconds), it indicates an abnormal connection among the AP, the Controller, and the Gateway. In this case, check whether the Ethernet cable is properly connected and the Controller is correctly configured.
Step 2. Check the AP's IP address to see whether it was changed before it went offline.
- If the AP obtains a static IP address, ensure it is in the same network segment as the Controller’s.
- If the AP obtains a dynamic IP address, go to the DHCP server to check whether the AP has obtained the IP address.
Step 3. Check whether the LAN IP address of the PC where the Controller runs and the IP address of the AP are in the same subnet. If not, check whether Management VLAN has been enabled before the AP goes offline.
- If Management VLAN is enabled, ensure the corresponding VLAN tunnel has been set in the network. Meanwhile, it is also recommended that Option 138 or Option 43 be configured on the DHCP Server based on actual needs.
- If Management VLAN is disabled, check whether the VLAN settings have been modified on the corresponding ports of the DHCP Server. This may lead to a change in the LAN IP address of the PC where the Controller runs. In this case, configure the IP settings to make sure the LAN IP address of the PC and the IP address of the AP are in the same network segment. Then, the controller will be able to manage the AP again.
Step 4. Check whether an IP address conflict occurs in the network. If so, remove the devices with the IP address conflict to see if the offline AP can resume the connection.
Step 5. Check whether the connection between the AP and the Controller is normal. If not, check the Ethernet cable connection.
Step 6. Check whether there are a large number of multicast and broadcast messages in the network that cause abnormal communication between the Controller and the AP and cause the AP to go offline.
Step 7. Check whether the firewall is enabled on the PC where the Controller runs. If it is, abnormal communication between the Controller and the AP may occur.
Step 8. If the AP is an Omada Pro model, check whether the license has expired.
Step 1. Check the LED status of the Mesh AP. If the LED is off, it indicates that the power supply for the Mesh AP is abnormal.
- If a DC power supply powers the AP, check whether the power plug is fully inserted or the power cord is damaged.
- If PoE powers the AP, check the power sourcing equipment (PSE) and the specifications and length of the Ethernet cable.
Step 2. Check whether the Mesh AP supports the same channel of the 5 GHz band as the one set for the Root AP.
Step 3. Ensure that Mesh, Auto Failover, and Full-Sector DFS are all enabled.
Step 4. Check for obstacles that may cause severe signal attenuation, resulting in the Mesh AP going offline.
Step 5. Check whether the transmission power of the Root AP is too low, causing the Mesh AP to go offline.
Step 6. Check the Mesh AP's IP address to see whether it has been changed before it goes offline.
Step 7. Check whether the Management VLAN was enabled before the Mesh AP went offline. If so, ensure the corresponding VLAN tunnel has been set in the network. Meanwhile, it is also recommended that Option 138 or Option 43 be configured on the DHCP Server based on actual needs.
Step 8. Check whether you have ever logged into the standalone Web GUI of the Mesh AP before it was adopted by the Controller. If you have, this may cause the AP to be unable to become Isolated and be discovered and managed by the Controller. In this case, reset the AP to factory defaults and just keep it powered on without any settings.
This article presents the troubleshooting methods to deal with the abnormal connection issues of Wired and Mesh APs. If your AP goes offline unexpectedly, follow the steps above for troubleshooting.
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