Juniper Mist Network Operations
Juniper Mist Network Operations
This domain tests the SLE-driven operating model: how Mist scores user experience, how classifiers point to root cause, and which tools confirm the diagnosis.
SLE framework
Mist scores Service Level Expectations per site, including Coverage, Capacity, Roaming, Throughput, Time to Connect, Successful Connect, and AP Health. Each SLE has a threshold, a score weighted by client-minutes, and classifiers naming the failure mode, such as weak signal, sticky client, DHCP failure, or authentication failure. Clicking a classifier lists the affected clients and APs.
Investigation tools
- Site wireless view: RF health, channel and power, interference, rogue and neighbor AP counts.
- Client page: RSSI, SNR, retries, roaming events, connection timeline, and DHCP/DNS/AAA steps.
- Dynamic packet capture triggers automatically on SLE failures and can also be started manually from an AP or client.
- Alarms and events separate infrastructure faults (AP down, PoE) from client experience issues.
Worked example
Coverage SLE falls to 78% at one site. Classifiers split 60% weak signal and 40% sticky client. The RF page shows APs at maximum power on 2.4 GHz with clients holding on at −82 dBm. Fix by lowering 2.4 GHz power, enabling band steering, and checking minimum-RSSI settings. Turning power up would raise the score's symptom, not fix the cause.
Traps
SLEs measure experience, not uptime. A classifier is a symptom label, not a guaranteed root cause. Lowering an SLE threshold hides the problem. At small sites, one bad client can dominate the score. Also check whether the issue is upstream (DHCP, DNS, AAA) before blaming RF.