Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

Wireless Throughput SLE

SUMMARY Use the Throughput SLE to assess users' experiences with throughput on your wireless network.

Throughput is one of the wireless Service-Level Expectations (SLEs) that you can track on the Monitor page of the Juniper Mist™ portal. Understand what's measured by this SLE and what issues can contribute to a low SLE.

What Does the Wireless Throughput SLE Measure?

Juniper Mist calculates the estimated throughput on a per-client basis for the entire site. The estimator considers effects such as AP bandwidth, load, interference events, the type of wireless device, signal strength, and wired bandwidth, to arrive at the probabilistic throughput.

You can click the Settings button to set the success threshold for this SLE.

Classifiers for Low Throughput

When the throughput threshold is not met, Juniper Mist classifies the issues as follows.

  • Device Capability—Low throughput is primarily due to the device capability.

  • Capacity—Low throughput is due to one of these factors:
    • Load on the associated AP.

    • Wireless or non-wireless interference on the channel.

    The capacity classifier has four sub-classifiers:
    • High Bandwidth Utilization

    • Non Wi-Fi Interference

    • Excessive Client Load

    • Wi-Fi Interference

    You can use these sub-classifiers to analyze users and APs below the SLE goal, the timeline of failures and system changes, and the distribution of failures. You can also analyze related network processes that these sub-classifiers can influence.

  • Coverage—Low throughput is primarily due to the client’s weak signal strength.

  • Network Issues—Low throughput is primarily due to the capacity of the wired network.

Example

Throughput Example
  • Success Rate—On the left, you see that the threshold was met 99 percent of the time.

  • Timeline—In the middle, you can drag your mouse to explore the success rate over time. In this example, there was an 87 percent success rate at the selected time. To adjust the scope of the timeline, use the timeline drop-down list at the top of the Monitor page. For example, set the timeline to Today, Yesterday, This Week, or a custom date range.

  • Classifiers—On the right, you see a high-level root cause analysis for the user minutes that did not meet the threshold. More than 99 percent of these issues were due to Capacity. Less than 1 percent were due to Coverage.

Note:

You can click the Values button to show numbers instead of the success rate and the classifier percentages. In this example, the left side of the screen shows the average throughput during the specified time period. The timeline shows the average throughput at each point in time. The right side of the screen shows the number of user minutes that were impacted by each classifier.

Throughput Example with Values