SoftTech AI Registry
Juniper Networks · Juniper Mist

Marvis self-driving network remediation

Marvis uses Mist AI/model-derived network-condition identification to trigger predefined self-driving remediation associated with supported Marvis Actions. For supported actions, Marvis can automatically execute corrective changes against managed network infrastructure without per-action human involvement — for example adding a missing VLAN to an affected switch port. This is bounded self-driving remediation tied to specific detected conditions, not open-ended autonomous network administration.

Recorded characteristics

Function
Juniper documents that Marvis Actions provide "both driver-assist and self-driving actions". Driver-assist actions "require user intervention"; "when you grant permissions to Marvis, it autonomously initiates self-driving actions to execute corrective measures without any user involvement." Recorded chain: Mist AI/model-derived condition identification → predefined Marvis Action → self-driving remediation logic → Mist management/control plane → managed network infrastructure → post-action validation. Representative documented self-driving remediations: Missing VLAN — "Marvis automatically adds the missing VLAN to the affected switch port, restoring connectivity for impacted clients" (the clearest persistent configuration change; outcome shown as "Add Missing VLAN on Switch Port"); Port Stuck — "Marvis automatically bounces the port"; Rogue DHCP Server Detected — "Marvis automatically disables the port where the rogue DHCP server is detected" (access ports only; not trunk ports; CX Series switches do not support this action); Loop Detected — "Marvis automatically disables the port on which it detects a Layer 2 loop" (ports can be re-enabled with the Enable Port option); AP Non-Compliant — "Marvis automatically initiates the firmware upgrade on the APs", one AP per 24-hour window during low site usage; Dynamic Capacity Optimization — "Marvis automatically adjusts the channel band and bandwidth", e.g. enabling dual band operation or increasing channel width; WAN Non-Compliant — initiates the Snapshot Device feature to update the Junos OS version on the backup partition of an SRX Series device to match the primary partition; Intermittent WAN Connectivity — automatically bounces a WAN Edge uplink port that cannot pass traffic (gateway ARP resolution failure or no IP address from the ISP). These listed actions do not establish general network-management authority.
Data access
Juniper documents model input features per Marvis Action, drawn from network telemetry: e.g. Missing VLAN uses AP port and uplink port statistics and "correlates data from two or more APs"; Port Stuck uses switch port statistics ("Sudden deviation in traffic patterns for end devices on access ports… considers traffic patterns across similar endpoints for inference"); Loop Detected uses switch port events (STP topology changes). Marvis "proactively scans your network for events and actionable insights. Using data from statistics and events". The action affects the configuration and operating state of managed switches, APs and WAN Edge/SRX devices.
Actions
Can take actions
External actions
Yes
Human confirmation
Not required
Permission basis
Not established
Administrative control
Self-driving permission is granted using the Marvis Self Driven button on the Marvis Actions page, at organization or site level; site-level settings can override organization-level permissions. Self-driving can also be enabled per action with the toggle in the Recommended Actions section. "You can disable the self-driving capability for an action at any point in time. If you disable the capability, ongoing self-driving tasks will complete, but subsequent tasks will not be self-driven." With self-drive permission disabled for an action, "Marvis will not attempt to automatically resolve the issue; instead, it provides an option for you to manually initiate the corrective action." Human confirmation: once self-driving authority is available for a supported action, Marvis can execute the corrective action without runtime user involvement. Prior organisation/site configuration or administrative permission is prior authorisation and is not classified as runtime human confirmation. Not every Marvis Action is autonomous — driver-assist actions require user intervention. Permission basis: the evidence establishes that administrators can grant Marvis self-driving permission at organisation/site level; it does not establish the runtime identity, credential or principal under which the resulting network-device change executes.
Default state
Conditional
Availability
Documented default behaviour varies by self-driving action. The general documentation says "The self-drive permission is disabled by default", while the same current source identifies individual actions with different defaults: Port Stuck "(self-driving capability enabled by default)"; Intermittent WAN Connectivity "(self-driving capability enabled by default)"; DFS Optimization "(self-driving capability enabled by default; cannot be disabled)"; Loop Detected — "By default, the self-driving capability for the action is disabled"; Rogue DHCP Server Detected, Missing VLAN, AP and WAN Non-Compliant and Dynamic Capacity Optimization are described as acting "If you enabled the self-driving capability". The Registry therefore records the capability as conditional and preserves the action-specific evidence rather than imposing a single global default. Generally available in Juniper Mist; available actions depend on device type and subscription.
Licensing
Juniper states "Your subscriptions determine the actions that you can see on the Actions dashboard" and that Marvis for switches requires "the Marvis for Wired subscription in association with the Wired Assurance base license". Detailed subscription mapping for each self-driving action is not recorded here.
External model or provider
Juniper attributes detection to Mist AI; its back-end documentation describes per-action "model input feature[s]" and "trigger conditions", and names an "LSTM-based model" for certain connectivity actions (which are not self-driving actions). No external model provider is documented.
Limitations and uncertainty
Bounded remediation only: the record does not claim arbitrary AI-generated configuration, arbitrary Junos execution, autonomous routing changes, firewall-policy modification, arbitrary VLAN operations, autonomous multi-action planning or general autonomous network administration. Public evidence does not establish that every final remediation decision uses ML at the final decision stage rather than a mixture of AI/model-derived signals and deterministic trigger/remediation logic (e.g. Loop Detected's input is STP topology-change events). Juniper lists DFS Optimization among self-driving actions, but the reviewed public description does not establish the specific corrective infrastructure change it executes; it is therefore not relied upon as action evidence for this record. Retries: bounded retry is documented only for Port Stuck and Intermittent WAN Connectivity ("Marvis will attempt to bounce the port three times and if the issue remains unresolved, then Marvis will set the issue status as Open"). Validation: after a self-driven fix the status becomes "Marvis Self Driven" and, if the issue is not observed during the validation time, "AI Validated"; a recurring issue returns to "Open". These mechanisms are not generalised to every action. No universal rollback, exactly-once execution or atomic configuration change is established. The runtime identity, credential or principal executing device changes, audit logging of self-driven changes, and the contradiction between the general "disabled by default" statement and the action-specific defaults remain unresolved.

Evidence