Typical SSH Commands for Omada AP Troubleshooting
EAP245( V3 V3.6 V4 V4.6 ) , EAP683 , EAP673-Extender , EAP230-Wall , EAP680 , EAP113-Outdoor , EAP215-Bridge KIT , 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 , 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 , EAP690E HD , EAP615GP-Wall , EAP723 , EAP623-Outdoor HD , EAP110-Outdoor , EAP650-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
Typical SSH Commands for Troubleshooting
This article introduces how to troubleshoot some common issues with Omada APs using SSH commands.
- Omada AP
- SSH Client
When client devices encounter wireless network issues while using Omada APs, such as low network throughput, poor signal quality, failure to obtain an IP address, or difficulty roaming between APs, try troubleshooting the wireless network through different methods. For example, relevant configuration settings on the Omada Controller or the Web UI of APs can be modified in standalone mode to ensure a normal network experience for clients. In some complex scenarios, tools like Wireshark can be used to capture communication packets between clients and APs or other network devices for troubleshooting. This article will introduce how to troubleshoot some common wireless network issues through SSH commands using the EAP650-Outdoor v1 as an example.
Note: The use of specific commands varies from model to model. Refer to the SSH Commands Guide for Omada AP to learn about all SSH commands supported by Omada APs.
Typical SSH Commands for Troubleshooting
- What can it be used for
Using this command, we can view the working information of all the AP’s wireless interfaces, including the working status, negotiation rate, wireless working mode, working frequency, Tx Power, etc.
- Example
When multiple SSIDs are created for the AP, and SSID Broadcast is enabled in Settings > Wireless Network > WLAN in the Controller’s Site view, but some client devices still cannot detect some of the SSIDs, it may be that the wireless interfaces corresponding to the SSIDs have not been fully established. In such cases, the iwconfig command can be used in the SSH client's terminal to view the relevant information about the interfaces. If the Bit Rate displays as 0 kb/s, as shown below, it indicates that the interface has not been fully established yet. This delay could be due to the slow propagation of configurations or the necessity for the 5G Radio to wait for the CAC (Channel Availability Check Time) before switching to a DFS channel. The CAC time varies for different DFS channels in different countries/regions, typically lasting up to 10 minutes.
- What can it be used for
The Omada AP comes with a built-in network performance-testing tool — iPerf, which can be used to test network bandwidth and quality, providing statistical information on network latency jitter, packet loss rate, etc. This tool can help us understand and evaluate the current wireless network's performance, identify network bottlenecks, and troubleshoot network issues.
- Example
When clients experience slow internet speeds, we can use this tool to locate network issues, especially within mesh networks. A typical topology is used as an example, as shown in the figure below. Use the iperf command to sequentially test the speed between Wireless client & Mesh AP2, Mesh AP2 & Mesh AP1, Mesh AP1 & Root AP, Root AP & Switch, and Switch & Router, so as to pinpoint the location of the issue accurately. Refer to the SSH Commands Guide for Omada AP for specific usage of this command.
Note: When using iPerf for speed testing, ensure that both endpoints of the test are running the same version. Currently, all Omada APs come with iPerf2 installed. Different subversions of iPerf2, such as v2.0.5 and v2.0.13, can be used together, but iPerf2 and iPerf3 are incompatible. Therefore, if one endpoint of the speed test is a wireless client and the other is an Omada AP, ensure that the client has iPerf2 installed. You can download the required version from iPerf - Download.
- What can it be used for
The restart command is used to reboot the device, which is equivalent to powering cycling it; the cliclientd reset command is used to reset the device to its factory settings, which is equivalent to pressing and holding the physical reset button.
- Example
In some cases, the device requires a reboot or reset due to anomalies or other reasons, but we cannot access its web interface, and the device is not easily accessible or installed nearby, such as when we are traveling or away from the location. For such cases, configure port-forwarding or take other measures on the router in advance to establish an SSH connection with the AP, and then manually enter the restart or cliclientd reset command to reboot or reset the device.
- What can it be used for
This command is used to view the statistical information of all wireless clients associated with the current AP. It provides more comprehensive and real-time information than what is displayed on the Web UI or Controller.
- Example
For medium—to large-scale networks with high traffic and a significant number of mobile clients, as clients roam between APs frequently, the statistical information on the Controller's Client page may experience a delay before updating. For disconnected clients, the system may only recognize them as offline after a set period, typically over 5 minutes. This delay means that not all information is displayed in real time. However, the cliclientd wltool sta command can provide real-time updates on client connection status and statistical data.
- What can it be used for
With this command, the AP will actively scan all supported channels to detect the BSS (Basic Service Set) on each wireless channel of the current network, including the total number of the BSS on each channel, the maximum and minimum RSSI values of the BSS detected on each channel, and the each channel’s Rx utilization.
- Example
If all wireless clients in the current wireless network experience significant lag when accessing the internet and local resources, and some factors, such as insufficient ISP bandwidth, low cable specifications, excessive distance, and too many associated clients, have been ruled out, check if the lag is caused by poor wireless environment. If the Omada Controller manages the AP, enable the RF Scan feature on the Controller to scan for interference across all channels, manually adjust it to a cleaner/less interfered channel, and set an appropriate power level.
Another more efficient method is to perform WLAN Optimization for automatic network deployment. However, please note that APs in mesh networks cannot perform RF Scan and WLAN Optimization. In such cases, access the device via an SSH command: run the cliclientd wltool scan command to quickly scan each channel supported by the AP, and then adjust the AP to the channel with the minimum total BSS, the lowest "maximum RSSI of BSS," and the lowest Rx utilization.
Note: This command is only suitable for a rough assessment of the current wireless environment and does not take interference from non-wireless devices like microwaves or Bluetooth devices into account. It is recommended to optimize your wireless network using the RF Scan and WLAN Optimization features on the Omada Controller if possible.
This article only introduces some simple and typical scenarios for troubleshooting the network using SSH commands. In addition to these commands, try more commands from the SSH Commands Guide for Omada AP and take other troubleshooting measures to locate issues and seek appropriate solutions for a better network experience.
Related FAQs
- How to troubleshoot the CPE in AP and Client mode when the wireless speed is slow
- How to use iPerf to test the speed between the EAP and the wireless client
- Troubleshooting: A wireless Client Cannot Access the Internet Through an Omada Wi-Fi Access Point
- TP-Link Omada AP Mesh Network Troubleshooting Guide
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