Two correct statements about Juniper Mist Dynamic Packet Capture are that no configuration is necessary for Mist’s Dynamic Packet Capture and it is automatically attached to a client event displayed on the Insights page. So the correct answers are  A. No configuration is necessary for Mist’s Dynamic Packet Capture  and  B. It is automatically attached to a client event displayed on the Insights page .

According to the Mist documentation 1 , a Mist AP will pull a management IP address from the Native VLAN by default. However, if the Local Status Page is configured for the Site, all the site APs will pull their own IP address from the Management VLAN, but also addresses for each of the VLANs configured on the AP. This is because each AP creates a Switch Virtual Interface (SVI) for each VLAN on its eth0 interface.

The Local Status Page is a feature that allows you to access information about an AP’s status and configuration through a web browser by connecting to its IP address 2 . This feature can be enabled or disabled at the site level under Site Settings > Access Points > Advanced Settings.

According to the Virtual Network Assistant | Juniper Networks US document 3 , two SLEs that measure the amount of time that it takes for a process to complete are:

Roaming, which measures how long it takes for a client to switch from one AP to another without losing connectivity.

Time to Connect, which measures how long it takes for a client to complete all steps of network access such as authentication, DHCP, and DNS.

According to the Cisco Catalyst 9800 Series Wireless Controller Software Configuration Guide 1 , a config template is a configuration object that can be used to apply consistent WxLAN and WLAN policies across all sites within the same organization. A config template can be applied to a site group, which is a collection of sites that share common attributes.

In the context of Juniper Mist AI and high-performance wireless design, Co-Channel Contention (CCC) —often referred to as Co-Channel Interference (CCI)—occurs when two or more access points (APs) share the same frequency channel and are within " hearing " distance of one another. 1 The key to understanding this specific range lies in the 802.11 CSMA/CA mechanism, specifically the Clear Channel Assessment (CCA) process.

When a Mist AP or a client device wants to transmit, it first performs a CCA. If it detects a Wi-Fi preamble from another device on the same channel at a signal strength above the Signal Detect (SD) threshold (typically around -82 to -85 dBm for many radios, though performance drops much sooner), it must defer its transmission. However, for " contention " to become a significant performance bottleneck that triggers Mist SLE alerts, the signal strength usually falls within the -45 dBm to -65 dBm range.

In this range, the signals are strong enough that the APs are effectively " in the same room " or nearby rooms, meaning they will constantly see the medium as " busy " whenever the other AP is transmitting. This effectively merges the two APs into a single contention domain, forcing them to share the total available airtime. For example, if two APs on the same channel both see each other at -60 dBm, they cannot transmit simultaneously; instead, they must take turns.

Mist ' s Radio Resource Management (RRM) and the Capacity SLE specifically monitor for these overlapping BSS (OBSS) conditions. If the AI detects that an AP is seeing a neighbor on the same channel at these high signal levels, it will attempt to change the channel or reduce transmit power to " shrink " the cell size, aiming to push the neighbor ' s signal strength below the point where it causes constant deferrals, thereby improving the overall capacity and user experience for the site.

The Wi-Fi Assurance SLE and classifier that would provide information about possible interference from a neighboring Wi-Fi network are Capacity and Wi-Fi Interference.

In the Juniper Mist AI ecosystem, Service Level Expectations (SLEs) provide a proactive way to monitor the health of a wireless network from the perspective of the end-user. When investigating potential interference—whether it is from neighboring Wi-Fi networks or non-Wi-Fi sources like microwaves or motion sensors—the Capacity SLE is the primary metric to analyze. While interference certainly impacts the overall Throughput SLE, Mist categorizes the specific environmental factors that limit airtime availability under the " Capacity " umbrella.

The Capacity SLE tracks " user minutes " during which a client experiences a drop in available RF channel capacity. It is specifically designed to identify why a client might be struggling to transmit data despite having a strong signal. Within the Capacity SLE block, Mist provides granular classifiers that pinpoint the root cause of the capacity degradation. These classifiers include:

Wi-Fi Interference: This identifies airtime contention caused by other 802.11 networks (Co-Channel Interference or Adjacent Channel Interference).

Non-Wi-Fi Interference: This identifies energy from non-802.11 sources detected by the AP ' s dedicated scanning radio.

Client Count: High density leading to contention.

Client Usage: A single " bandwidth hog " consuming the available airtime.

By checking the Capacity SLE in the Mist dashboard before heading to a site, an administrator can see a historical timeline of interference events. If the " Wi-Fi Interference " or " Non-Wi-Fi Interference " classifiers show a high percentage of " Bad User Minutes, " the administrator can confirm that the client ' s complaint is indeed valid. This allows for remote troubleshooting and may even enable the admin to resolve the issue by adjusting Radio Resource Management (RRM) settings or identifying a specific rogue device, potentially saving an unnecessary truck roll.