The DHCP server has run out of address leases on a site. In this scenario, which SLE would be useful to what is happening?

The Successful Connects Service Level Expectation (SLE) monitors the time and success rate for clients to complete the entire connection process. This process is broken down into three key stages: Association, Authentication, and DHCP. When a DHCP server runs out of address leases, clients attempting to connect will fail at the DHCP stage. The Successful Connects SLE dashboard would specifically classify these failures under the "DHCP" sub-classifier, providing direct visibility into the root cause of the connection problem.

A. capacity: The Capacity SLE measures network load against configured thresholds, focusing on AP resource utilization (CPU/memory) and client counts, not failures within the connection protocol stack.

B. throughput: The Throughput SLE measures the data transfer rates for clients that are already successfully connected to the network. A DHCP failure prevents the connection from being established in the first place.

C. roaming: The Roaming SLE measures the performance and success rate of clients moving between different access points. This is unrelated to the initial DHCP lease acquisition process.

1. Juniper Mist Documentation, "Service Level Expectations (SLEs)": In the section describing the "Successful Connects" SLE, it states, "The Successful Connects SLE measures the percentage of successful connections versus failures. It looks at the time it takes for a client to complete the association, authentication, and DHCP processes." The documentation further illustrates that DHCP is a primary sub-classifier for connection failures.

2. Juniper Mist Documentation, "Capacity SLE": This document defines the Capacity SLE as a measure of "network capacity based on the number of users and their traffic load," with sub-classifiers like "Coverage" and "Capacity" that relate to signal strength and AP resource load, not DHCP protocol failures.