Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

Wireless Successful Connects SLE

SUMMARY Use the Wireless Successful Connects SLE to assess your users' experiences connecting to your wireless network.

Successful Connects is one of the wireless Service-Level Expectations (SLEs) that you can track on the Wireless SLEs dashboard.

Successful Connects SLE Example
Note:

To find the Wireless SLEs dashboard, select Monitor > Service Levels from the left menu of the Juniper Mist™ portal, and then select the Wireless button.

What Does the Wireless Successful Connects SLE Measure?

Juniper Mist tracks the success or failure of authorization, association, DHCP, ARP, and DNS attempts. These connection attempts include initially connecting to the network, roaming from one AP to another, and ongoing connectivity.

You don't need to set up a threshold for this SLE. It's assumed that you want 100 percent successful connects.

Classifiers

When connection attempts fail, Juniper Mist sorts the issues into classifiers. The classifiers appear on the right side of the SLE block. In this example, 92 percent of issues happened during the DHCP process. Another 7 percent failed during authorization, and 1 percent failed during association. No issues (0 percent) were attributed to the other classifiers. (See the classifier descriptions below the example.)

Successful Connects SLE Example
  • Association—The connection failed during the association process.

  • Authorization—The connection failed during the authorization process.

  • DHCP—The connection failed during the DHCP process (DCHP timeouts).

    The DHCP classifier has four sub-classifiers:

    • Renew Unresponsive

    • Nack

    • Incomplete

    • Discover Unresponsive

  • ARP—The client experienced one of these problems:

    • ARP failure for the default gateway during the initial connection

    • ARP gateway failures after the initial connection or roam

  • DNS—The client experienced DNS failures during or after the connection process.