Coverage SLE
SUMMARY Use the Coverage SLE to assess your users' experiences with signal strength.
Coverage 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 Coverage SLE Measure?
Juniper Mist tracks active clients' Received Signal Strength Indicator (RSSI), as measured by the access point.
You can click the Settings button to set the RSSI level that you want to use as the success threshold for this SLE.
Classifiers for Poor Coverage
When the RSSI threshold is not met, Juniper Mist classifies the issues as follows.
-
Asymmetry Uplink—Clients received a weak signal due to asymmetric uplink strength between the AP and the client device. (Uplink traffic is the traffic going from the client to the AP, and then to the Internet.) Asymmetry can occur for various reasons, such as clients being too far from the AP.
-
Asymmetry Downlink—Clients received a weak signal due to asymmetric downlink transmission strength between the AP and a client device. (The traffic going from the AP to the client is called downlink traffic.)
-
Weak Signal—Clients received a weak signal due to other factors.
Example
-
Success Rate—On the left, you see that the threshold was met 94 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 a 96 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 experiences that were impacted by poor coverage. The majority of the issues (63 percent) were due to Asymmetry Uplink. Another 36 percent were due to Weak Signal, and 1 percent were due to Asymmetry Downlink.
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 RSSI during the specified time period. The timeline shows the average RSSI at each point in time. The right side of the screen shows the number of user minutes that were impacted by each classifier.
