JNCIS-MistAI-Wired key terms

A hosted management platform that configures, monitors, and troubleshoots Juniper switches and wireless gear through a web portal and APIs, using telemetry from managed devices rather than on-premises controllers.

The Mist subscription service that brings Juniper EX and QFX switches under cloud management, providing configuration templates, health scoring, and AI-driven insights for wired networks.

A Juniper switch that has been adopted into the Mist cloud but is not yet assigned to a site or template, so it receives limited or no configuration from the platform.

The process of claiming a switch into a Mist organization using its serial number or activation code so the cloud can manage and monitor it.

A numeric or alphanumeric code printed on Juniper hardware or provided in a purchase record, used during adoption to associate the device with a Mist organization.

The top-level tenant in Mist that contains sites, devices, admins, and subscriptions; it isolates one customer's managed estate from others in the shared cloud.

A logical grouping inside a Mist organization that represents a physical location such as a campus or branch, and carries its own settings, templates, and device assignments.

The collection of network, switching, and policy settings applied to all devices at a Mist site, including VLANs, templates, and authentication options.

A reusable set of switch settings in Mist that can be applied to many devices or sites, reducing manual CLI work and keeping configurations consistent.

A Mist object that bundles port profiles, VLANs, and other switch-level settings for assignment to one or more switches, often derived from a template.

A named set of per-port settings in Mist, such as mode, VLAN membership, PoE, and authentication, that is applied to switch ports instead of configuring each one individually.

The act of sending a desired configuration from the Mist cloud down to a managed switch, after which the device reports whether it applied the change successfully.

A condition where a switch's running configuration no longer matches the configuration intended in Mist, often caused by manual CLI edits or a failed push.

A manual modification made directly on a switch, through CLI or local tools, that bypasses the Mist cloud and can cause configuration drift.

A numeric rating Mist computes for each switch from telemetry such as resource usage, errors, and connectivity, used to spot degrading devices before users report outages.

Mist's AI assistant that answers natural-language questions about the network, correlates events, and suggests root causes for client and switch problems.

Prioritized issue cards generated by Mist AI that identify problems needing attention, such as a flapping port or a misconfigured VLAN, with recommended remediation.

Periodic status and performance data that managed switches send to the Mist cloud, forming the basis for health scores, alerts, and troubleshooting insights.

A Juniper feature that lets multiple physical switches operate as one logical device with a shared control plane, simplifying management and providing redundancy.

The link, often a dedicated or uplink port, that connects member switches inside a Virtual Chassis and carries traffic between them.

Bonding multiple physical links into one logical link, using LACP or static configuration, to increase bandwidth and provide resilience if a member link fails.

Link Aggregation Control Protocol, an IEEE standard that negotiates and monitors bundled links so both ends agree on which ports form the aggregate.

The logical interface created when several physical ports are bundled together for increased throughput and redundancy, identified by a name such as ae0.

A Layer 2 protocol that prevents loops in redundant switched topologies by blocking some paths, leaving a loop-free tree of forwarding links.

Rapid Spanning Tree Protocol, an evolution of STP that converges much faster after a topology change while still preventing Layer 2 loops.

A switch port protection feature that disables or blocks an edge port if it receives a spanning-tree BPDU, preventing unauthorized switches from joining the topology.

A switch port that belongs to a single VLAN and typically connects to an end device such as a PC, printer, or access point.

A switch port that carries traffic for multiple VLANs, tagging frames so a downstream switch or server can separate the VLANs.

A virtual local area network that logically segments a physical switch into separate broadcast domains, improving security and traffic control.

The VLAN whose traffic is sent untagged on a trunk port; both ends must agree on it to avoid misforwarding or VLAN hopping issues.

Power over Ethernet, which delivers electrical power along with data over a copper Ethernet cable so devices like access points and cameras need no separate power supply.

Link Layer Discovery Protocol, a neighbor-discovery protocol that advertises device identity and capabilities, helping map topology and power requirements on switch ports.

A map of how switches, access points, and other devices are interconnected, which Mist builds from telemetry and neighbor data to support troubleshooting.

A switch port used to connect to another switch or to the distribution layer, typically configured as a trunk or part of a link aggregation group.

A port configured for end devices rather than other switches, allowing rapid forwarding because no loop is expected through it.

A RESTful programmatic interface that lets scripts and third-party systems read and change Mist organizations, sites, and devices, supporting automation and integration.

A secret credential generated in Mist and used by scripts or integrations to authenticate API calls, scoped to the privileges of the account that created it.

A configurable HTTP callback in Mist that pushes event notifications, such as alarms or audit logs, to an external system in near real time.

A category of events, such as device alarms or audit logs, that a Mist webhook subscribes to so only relevant notifications are delivered to the receiving endpoint.

A protocol that centralizes authentication, authorization, and accounting for network access, commonly used with switch port authentication and 802.1X.

An IEEE standard for port-based network access control that authenticates a device or user before allowing traffic on a switch port.