JNCIP-MistAI key terms

The top-level container in Mist that holds sites, inventory, admin accounts, and subscription entitlements. Settings applied here cascade to every site unless a site or a template overrides them.

A logical grouping of access points, switches, and clients that share configuration and appear as one location in Mist. Sites inherit organization settings and can consume templates for WLANs and devices.

A time-limited entitlement that unlocks specific Mist capabilities, such as Wi-Fi Assurance, Wired Assurance, or Marvis, for a defined number of devices. Expired subscriptions disable those features but leave the organization intact.

The list of Mist-owned devices such as access points, switches, and gateways recorded against an organization after claim. Devices in inventory can be assigned to a site and adopt configuration from templates.

A short alphanumeric code printed on Mist hardware or supplied with the purchase record. Entering it in the Mist dashboard transfers the device into the organization's inventory.

Mist's role-based permission model that assigns admin roles such as Super Admin, Network Admin, or read-only observer. Roles determine which organizations, sites, and actions an account can access.

A managed service provider account structure that lets one administrator manage many customer organizations from a single login. MSPs use organization groups and delegated roles while keeping each customer's data separated.

An organization-level definition of an SSID and its security, VLAN, and policy settings. Applying the template to sites pushes a consistent wireless configuration without editing each site individually.

Named placeholders such as a VLAN identifier or network name that are defined per site and substituted into templates. They let one shared template produce site-specific values without duplication.

A wireless network profile broadcast by Mist access points and identified by an SSID. It defines authentication method, VLAN assignment, and client-facing policies such as splash portals and bandwidth limits.

A reusable set of radio settings, including channels, transmit power, band steering, and RRM behavior, applied to access points. RF templates keep wireless behavior consistent across many sites.

Radio Resource Management, Mist's automated channel and power optimization for access points. It continuously monitors interference and client distribution, then adjusts radios to reduce co-channel interference without manual survey work.

A Mist access point running cloud-managed Mist OS that delivers Wi-Fi, Bluetooth LE, and assurance telemetry. APs reach the Mist cloud over HTTPS and require no on-premises controller.

Service Level Expectation, a measurable wireless quality objective such as successful connection rate or coverage, scored from 0 to 100 percent. SLEs aggregate client telemetry and highlight which users or sites fall below target.

The breakdown of a failed SLE into contributing causes, for example DHCP failure, authentication failure, or interference. Classifiers show where to focus troubleshooting instead of guessing.

A captive web page shown to clients joining a guest WLAN before internet access is granted. Mist supports click-through, password, and external splash options with terms-of-use and voucher flows.

A chronological view of everything a single client did on the network, including association, DHCP, DNS, authentication, and roaming events. It is the primary tool for client-level wireless troubleshooting.

A named collection of switch port settings such as VLAN membership, PoE, speed, and authentication that can be applied to many ports at once. Port profiles simplify wired configuration and reduce per-port errors.

An organization-level set of switch configuration, including port profiles and VLANs, that sites inherit. Template changes deploy automatically to attached switches and keep the wiring plan consistent.

The Mist subscription feature that scores switch and wired-client health using SLEs such as switch uptime and wired client success. It adds telemetry and assurance beyond basic switch management.

A group of Mist switches managed as one logical device that shares configuration and control-plane state. Virtual chassis simplifies management and provides redundancy when one member fails.

Zero Touch Provisioning, the process where a new switch or access point boots, contacts the Mist cloud using its claim record, and downloads assigned configuration automatically. No console session or manual staging is required.

Mist's EVPN-VXLAN architecture for building a scalable, loop-free switched campus. Switches act as leaf or spine nodes, and the Mist cloud orchestrates underlay and overlay configuration.

Mist's virtual network assistant that answers natural-language questions and surfaces proactive actions about wireless, wired, and WAN health. It combines telemetry, SLEs, and AI models to explain problems.

A prioritized list of issues Marvis detects across the organization, such as offline access points or bad cables, each with an explanation and a recommended fix. Actions replace hunting through dashboards manually.

Synthetic wireless clients that Mist runs on access points to continuously test connectivity, DHCP, DNS, and authentication. Minis detect problems before real users report them.

The chat interface where an administrator asks Marvis questions in plain language, such as why a client cannot connect, and receives an answer grounded in live network data.

Marvis's explanation of why an issue occurred, linking symptoms to underlying causes such as a misconfigured VLAN, a failing cable, or an authentication server timeout. It shortens mean time to repair.

The practice of comparing current network behavior against learned baselines to flag unusual events, like a sudden drop in client count or an unexpected roaming pattern. Alerts fire without static thresholds.

A JSON-over-HTTPS interface for reading and changing Mist configuration, statistics, and inventory. It follows REST conventions, supports organization, site, and MSP scopes, and powers most third-party integrations.

A credential generated in the Mist dashboard that authenticates programmatic requests. Tokens are scoped to a user or organization and are sent in the Authorization header as a Bearer value.

The cap Mist places on how many API requests a token may make per hour, enforced to protect the cloud service. Responses include headers showing remaining quota, and exceeding it returns HTTP 429.

A user-defined HTTPS endpoint that Mist calls when matching events occur, pushing JSON payloads in near real time. Webhooks avoid polling the API and feed ticketing, chat, or SIEM systems.

The category of event that triggers a webhook delivery, such as audits, alarms, device up/down, client sessions, or location. Each topic produces a different JSON payload schema.

An optional shared secret configured on a Mist webhook and sent in the request header, letting the receiver verify the payload genuinely came from Mist. It prevents forged event deliveries.

An infrastructure-as-code plugin that manages Mist organizations, sites, WLANs, and devices through declarative configuration files. It uses the Mist REST API and supports versioned, reviewable network change workflows.