Marvis Minis FAQ

Why are Marvis Minis validations not running despite being enabled for the organization?

Marvis Minis validations might not run for two main reasons:

• AP firmware requirements not met—Marvis Minis runs validations only when all the access points (APs) in a site are running firmware version 0.14.29313 or later. If even one AP is running an earlier firmware version, Marvis Minis does not run the validations for that site.

• Switch not running the required Junos OS version—Marvis Minis is supported on EX4100, EX4400, and EX4650 switches running Junos OS version 25.4R2 or later.

• Insufficient Marvis subscriptions—Validations will not run if Marvis subscriptions have expired or have been transferred to another organization, resulting in an insufficient number of Marvis subscriptions in the organization.

How can I verify that all APs in a site meet the firmware requirement?

Navigate to the site AP inventory and review the firmware version for each AP. Update any earlier firmware version running on any AP to a supported version (0.14.29313 or later), then allow time for validations to start.

What should I do if validations do not run even after meeting all the requirements?

Open a support ticket for further assistance. See Create a Support Ticket.

Can I disable Marvis Minis validations

Yes, you can disable validations either at the organization level or at the site level. Note that the site-level settings override the organization-level settings. See Disable Marvis Minis.

Is Marvis Minis enabled by default?

Yes, Marvis Minis for wireless is enabled by default on all sites with APs running firmware version 0.14.29313 and later, provided your organization has an active Marvis for Wireless subscription. Marvis Minis for wired is supported on EX4100, EX4400, and EX4650 switches running Junos OS version 25.4R2 or later.

Which applications does Marvis Minis test by default?

Marvis Minis by default tests four applications for application reachability and Internet connectivity:

• Microsoft Teams (https://teams.microsoft.com)

• Office (https://office.com)

• Apple's captive portal (https://captive.apple.com)

• Google's connectivity check endpoint (https://connectivitycheck.gstatic.com)

Why are validations running for some sites but not others?

Marvis Minis might skip running validations on a site if any AP in that site is running an unsupported firmware version. For Marvis Minis to run validations, all APs within the site must meet the required prerequisites.

Does adding a new AP to a site impact Marvis Minis validations?

If the new AP is running an unsupported firmware version, Marvis Minis validations might stop for the entire site until the AP firmware is upgraded to the minimum required version. However, if the newly added AP is running a supported firmware version, Marvis Minis validations will continue without any disruption.

Do offline APs impact validations?

Marvis Minis runs validations only on APs that are connected to the Mist cloud. If an AP is offline, Marvis Minis will not run tests on that AP.

Do Marvis Minis validations start immediately after setting up a site?

If all requirements are met, Marvis Minis typically starts running validations within a couple of hours after the site is set up.

Is Marvis Minis enabled by site or organization?

Marvis Minis can be enabled either at the organization level or at the site level.

Will Marvis Minis make any configuration changes to my network?

No.

Where can I view the results from the Marvis Minis validations?

The results of Marvis Minis validations are surfaced through the Marvis Minis service-level experience (SLE) dashboard that categorizes data under two SLEs—Network Services and Application. You can see overall health status, individual service or application SLEs, and outcomes of the validations. From these views, you can drill down to understand which tests ran, which services or applications were impacted, and why a validation might have failed. For a more focused analysis, you can filter SLE data by a specific application or VLAN. See Marvis Minis SLE Dashboard (Beta).

Marvis Minis-detected failures are listed under the Connectivity category on the Marvis Actions page.

Why doesn’t Marvis Minis run tests on all my APs?

Marvis Minis intelligently selects only a subset of APs (per site) and then learns what to test based on actual network usage. Each AP is associated with one or more VLANs, and Marvis Minis selects APs that collectively cover the important VLANs in the site. Marvis Minis leverages the mapping between service set identifiers (SSIDs) and VLANs to determine the SSIDs to test from specific APs. Validations are focused on VLANs with active clients. The test scope includes targeted application tests that reflect actual usage patterns at that site, making the tests more meaningful and actionable.

Why does Marvis Minis stop running DNS and default application validations?

Marvis Minis stops highlighting issues when the same checks fail continuously over a long period without remediation. When a test fails repeatedly with no detected changes or corrective action, Marvis Minis assumes that the issue is a known, persistent condition rather than a new or actionable event. The validations continue to run, but without Marvis Minis highlighting the ongoing unaddressed issue.

Do I need a separate subscription for Marvis Minis?

No, Marvis Minis does not require a separate subscription. If your organization already has an active Marvis for Wireless subscription, you automatically get access to Marvis Minis for wireless networks. To use Marvis Minis for wired networks, a Marvis for Wired subscription is required.

How often are my critical applications tested?

Critical applications are validated based on the protocol used. For example:

• For TCP-based applications, validations run less frequently, generally every 5–15 minutes. Because TCP includes built-in reliability (such as acknowledgments and retransmissions), issues can be monitored effectively without frequent testing, reducing overhead on both the system and the application.

• For ICMP-based or UDP-based applications, validations are more aggressive, typically running every minute. Because these protocols lack TCP’s built-in mechanisms for confirming that data was received, more frequent checks are needed to detect issues quickly.

How does Marvis Minis distinguish between critical and noncritical applications?

While adding applications to be included in the Marvis Minis validations, you can mark applications that are critical to your organization as high priority. Marvis Minis considers such applications critical and validates these applications more frequently.

What does Marvis Minis test as part of authentication validations?

Marvis Minis automatically detects the RADIUS authentication servers configured in your network and validates their reachability. Using preset credentials, Marvis Minis sends an authentication request to the RADIUS server. A rejected response confirms that the server is reachable and operational. This functionality is currently supported only on switches.