Monitoring and Troubleshooting
Wireless Connections

Wireless Performance issue Troubleshooting

5min

Introduction

This document includes steps to troubleshoot Wireless client performance-related issues.

While troubleshooting a performance issue we need to find out if the issue is related to:

  • Internet
  • High load on client site
  • Nile NSB
  • Wireless Coverage  
  • Client Itself  (Laptops, Mobile devices etc.)

As an example we will check the following working and non-working scenario to see the difference:

Scenario 1:  client has high load of traffic

From the Nile Portal (NP) Device details page for a particular client, we could click "RUN TEST" on the top right corner to check if there is any Latency:

In our case we could see latency of 323 milliseconds (ms), while Air Quality and Coverage is good. 

Nile portal: Run test
Nile portal: Run test


Additionally, we can check Client Details Usage to see if there are any traffic load spikes:

We see that the client is using 135 Mbps per second of data download:

Devices: Signal info
Devices: Signal info


A speed test from the client side would be a good way to see if there any Speed related issues:

The speed test shows us that the download capacity is 2.46 Mbps while upload is quite higher:

Speed test info
Speed test info


Scenario 2:  client does not have high load of traffic:

"Run Test" for this particular client checks if there is any Latency.This time there is no latency on ARP/Ping and Air Quality and Coverage is good.

Nile portal: Run test
Nile portal: Run test


Checking Client Details Usage shows if there are any traffic load spikes.

This time we do not see any high Usage of Outbound or Inbound traffic.

Devices: client info
Devices: client info


The Speed test from the client shows if there are any Speed related issues.

In this case, the speed test shows us High Download and Upload speed.

Speed test
Speed test


Also, we could use my.nilesecure.com when device is connected to Nile Network to check the status of the client device connection. Read more..