Typical SSH commands for Omada AP troubleshooting

Knowledgebase
Troubleshooting Guide
CLI
Wireless
08-05-2024

Contents

Objective

Requirements

Introduction

Typical SSH Commands for Troubleshooting

iwconfig

iperf

restart / cliclientd reset

cliclientd wltool sta

cliclientd wltool scan

Conclusion

Objective

This article introduces how to troubleshoot some common issues with Omada APs using SSH commands.

Requirements

  • Omada AP
  • SSH Client

Introduction

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 in roaming between APs, try troubleshooting the wireless network through different methods. For example, modify relevant configuration settings on the Omada Controller or the Web UI of APs in the 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. Here, 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 certain commands varies from model to model. Refer to SSH Commands Guide for Omada AP to learn about all SSH commands supported by Omada APs.

Typical SSH Commands for Troubleshooting

iwconfig

  • 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.

iperf

  • 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. Here is a typical topology 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 accurately pinpoint the location of the issue. 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 not compatible. 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.

restart / cliclientd reset

  • 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 is not 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.

cliclientd wltool sta

  • What can it be used for

This command is used to view the statistical information of all wireless clients associated with the current AP, providing more comprehensive and real-time information compared to 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 update. 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.

cliclientd wltool scan

  • 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 AP is managed by the Omada Controller, 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 for it. 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.

Conclusion

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.

Get to know more details of each function and configuration please go to Download Center to download the manual of your product.

Please Rate this Document