Self-Driving Marvis Actions

Use self-driving Marvis Actions to simplify and automate troubleshooting.

Marvis actions provide both driver-assist and self-driving actions. Driver-assist actions require user intervention based on the details and recommendations provided by Marvis. Here’s an example of a driver-assist action. Marvis provides the necessary details that enable you to address the issue.

In contrast, when you grant permissions to Marvis, it autonomously initiates self-driving actions to execute corrective measures without any user involvement. This effectively automates the process of identifying and resolving issues. For example, a driver-assist action involves a network administrator having to manually upgrade the firmware on an AP. Conversely, a self-driving action automatically initiates the firmware upgrade when Marvis detects a firmware non-compliance on an AP.

By utilizing the self-driving capabilities, you can automate simple repetitive tasks, streamline troubleshooting processes, minimize downtime, and enhance overall network efficiency.

When an issue is fixed by a self-driving action, the status of the issue changes to Marvis Self Driven as shown in the following example. After the issue is fixed, Marvis performs checks to ensure that the issue is indeed resolved. If the issue is not observed during the validation time, Marvis changes the status to AI Validated. The validation time is the time taken for Marvis to mark an open Marvis action as AI validated.

Dashboard showing non-compliant access points with site names, issues like version mismatch, timestamps, and resolution statuses such as Marvis Self Driven.

The self-driving capability is available for the following actions:

Table 1: Self-Driving Marvis Actions
Category	Actions with Self-Driving Capability
Wireless	Non-compliant Dynamic Capacity Optimization DFS Optimization (self-driving capability enabled by default; cannot be disabled)
Wired	Port Stuck (self-driving capability enabled by default) Rogue DHCP Server Detected
WAN	Non-compliant
WAN	Intermittent WAN Connectivity (self-driving capability enabled by default)

How to Enable Self-Driving Actions

To enable self-driving actions, you must grant Marvis the necessary permissions by using the Marvis Self Driven button on the Marvis Actions page. You can grant permissions at the organization or site level. Permissions granted at the organization level are applicable to all sites in the organization. You can change the permissions at the site level to override the permissions granted at the organization level.

The self-drive permission is disabled by default. If the self-drive permission is disabled for a Marvis action, Marvis will not attempt to automatically resolve the issue; instead, it provides an option for you to manually initiate the corrective action.

Actions with self-driving capabilities are tagged with the Marvis icon, allowing you to easily identify self-driving actions.

WAN edge dashboard showing status: 1 WAN edge monitored, MTU Mismatch 0, Bad WAN Uplink 0, VPN Path Down 0, Non-compliant 1 highlighted in yellow, Negotiation Incomplete 0.

When you enable the self-driving feature for an action, the Marvis icon will change as shown in the following example:

WAN monitoring dashboard showing 1 WAN edge device with 0 MTU mismatch, 0 bad WAN uplink, 0 VPN path down, 1 non-compliant issue highlighted in yellow, and 0 negotiation incomplete.

You can also enable the self-driving capability for a specific action by using the toggle button in the Recommended Actions section.

Note:

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.

Once a self-driven action is completed, you can view it by selecting either the All or self-driven filter options.

Self-Driven Actions Time Series Graph

You can use the time series graph on the Marvis Actions page to view historical patterns or trends for self-driven actions at the site or organization level. The graph displays the number of self-driven actions generated for a site or organization for the selected time range.

Click Self-Driven to view the automatically resolved issues. Note that the Self-Driven option is hidden for actions without the self-driving capability.

Self-Driving Wired Actions

For switches, the self-driving capability is available for the following actions:

Port Stuck—The self-driving capability for this action is enabled by default. Marvis automatically bounces the port to fix the issue. Marvis will attempt to bounce the port three times and if the issue remains unresolved, then Marvis will set the issue status as Open and provide details of the automatic remediation steps taken. Stopping the automatic bounce after three attempts prevents continuous port bounce cycles. You can then check whether the port stuck issue is due to a hardware issue with the device connected to the switch port.
Rogue DHCP Server Detected—If you enabled the self-driving capability for this action, then Marvis automatically disables the port where the rogue DHCP server is detected. The self-driving capability disables the access port where a rogue DHCP server is detected. Note that this action doesn’t apply to rogue DHCP servers connected to trunk ports.

Self-Driving Wireless Actions

For APs, the self-driving capability is available for the following actions:

Non-Compliant—If you enabled the self-driving capability for this action, Marvis automatically initiates the firmware upgrade on the APs.

Automatic upgrade involves upgrading one AP at a time during periods of low network usage at a site to minimize network downtime and impact to users. Consequently, if multiple APs need to be upgraded, the process might take a few days as Marvis upgrades one AP in a 24-hour window during periods of low site usage to avoid creating any network coverage issues.
Dynamic Capacity Optimization—If you enabled the self-driving capability for this action, Marvis automatically adjusts the channel band and bandwidth based on the available wireless capacity observed based on peak client usage and interference. For example, to increase the overall capacity, Marvis can enable dual band operation on APs. Similarly, it can increase the channel width to improve the throughput.
DFS Optimization—The self-driving capability for the DFS Optimization action is enabled by default and cannot be disabled. DFS Optimization enhances visibility into how the Mist Radio Resource Management (RRM) system processes Dynamic Frequency Selection (DFS) radar events and their impact on Wi‑Fi channel assignments. It provides a clear, seven‑day insight into how radar‑affected channels are evaluated and how that history shapes ongoing channel selection decisions.

Self-Driving WAN Actions

For WAN Edges, the self-driving capability is available for the following actions:

Non-Compliant—If you enabled the self-driving capability for this action, Marvis automatically initiates the Snapshot Device feature to update the Junos OS version on the backup partition of an SRX Series device so that it matches the version that is currently running on the primary partition.

Automatic upgrade involves upgrading one device at a time during periods of low network usage at a site to minimize network downtime and impact to users. Consequently, if multiple devices need to be upgraded, the process might take a few days as Marvis upgrades one device in a 24-hour window during periods of low site usage to avoid creating any network disruption.
Intermittent WAN Connectivity—The self-driving capability for this action is enabled by default. When Marvis detects an uplink port on a WAN Edge device that is unable to pass traffic due to one of the following reasons, it automatically bounces the port to fix the issue:
- ARP resolution for the gateway fails for the ISP server provided IP address.
- Uplink port does not receive an IP address from the ISP.
Marvis will attempt to bounce the port three times and if the issue remains unresolved, then Marvis will set the issue status as Open.

Find Self-Driven Actions Using Filters

The RECOMMENDED ACTION section on the Marvis Actions page provides filters to list issues based on the status. For information about the filter options, see Filter Marvis Recommended Actions by Status.

For any self-driving action with permissions enabled, Marvis identifies and automatically remediates the issue by taking the necessary action. After the issue is resolved, the status of the issue changes to Marvis Self Driven. Marvis then validates that the issue has not reoccurred and then changes the status to AI Validated.

You can view issues resolved through a self-driven action by selecting the Marvis Self Driven or AI Validated filter. If you do not select a filter, all issues are listed including any Marvis Self Driven, AI Validated, and Open issues.

If an issue resolved by a self-driving action reoccurs, then Marvis changes the status of the issue to Open.

You can click the download (down arrow) icon next to the toggle button to download the list of issues for your organization or site in CSV format.

ON THIS PAGE