For any Juniper device (switch, AP, firewall) to be managed by Mist, it must have basic IP connectivity to the internet, including the ability to resolve the Mist cloud’s domain names via DNS. This is the foundational requirement for cloud registration and ongoing communication.

Marvis is the AI and Machine Learning engine within Mist AI. Its primary role is to provide proactive insights, root-cause analysis, and a natural language query interface to simplify network operations and troubleshooting, moving beyond traditional dashboards and logs.

In the Mist cloud-managed model, devices must be claimed (by serial number or claim code) into the organization and assigned to a site *before* they are powered on and connected to the network. This step authorizes the device to establish a secure connection to the Mist cloud upon boot-up.

Sites are the primary configuration containers in Mist. They allow administrators to apply specific wireless, wired, and security settings (e.g., unique SSIDs, switch port profiles, firewall policies) to groups of devices based on their deployment location, such as different offices, campuses, or retail stores.

Mist WAN Assurance focuses on the underlay and overlay network performance of wide area network links. It provides monitoring, analytics, and insights for SD-WAN tunnels (and the underlying internet/MPLS circuits) connecting distributed sites, helping ensure application performance and user experience across the WAN.

Mist’s RF Heatmaps are a graphical tool that overlays metrics like signal strength, channel utilization, and interference onto a floor plan. This visualization is ideal for identifying the physical location and severity of RF problems, such as non-Wi-Fi interference, which is crucial for effective troubleshooting.

In Mist architecture, a Gateway typically refers to a Juniper SRX Series firewall (physical or vSRX) that is managed by the Mist Cloud. It provides critical security and connectivity functions for a site, including stateful firewall policies, NAT, and IPsec VPN tunnels for SD-WAN, all configured and monitored through the Mist portal.

Templates are a foundational automation feature in Mist. They allow network engineers to define a standard set of configurations (for switches, APs, or gateways) and apply them to many devices or sites at once. This ensures uniformity, drastically reduces manual configuration errors, and makes network-wide changes efficient and scalable.

A core principle of Mist cloud management is that the Mist portal (web UI and its underlying APIs) becomes the primary interface for configuration, monitoring, and troubleshooting. While the Junos CLI is still accessible for advanced diagnostics, all policy-driven configuration is intended to be pushed from and managed by the cloud.

For any Juniper device (switch, AP, firewall) to be managed by Mist, it must have basic IP connectivity to the internet, including the ability to resolve the Mist cloud’s domain names via DNS. This is the foundational requirement for cloud registration and ongoing communication.0