Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
ON THIS PAGE
 

HPE Marvis Minis FAQ

Find answers to common questions about HPE Marvis minis.

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

HPE Marvis minis validations might not run for the following reasons:

  • AP firmware requirements not met—HPE 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, HPE Marvis minis does not run the validations for that site.

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

  • Insufficient HPE Marvis subscriptions—Validations will not run if HPE Marvis subscriptions have expired or have been transferred to another organization, resulting in an insufficient number of HPE 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 HPE 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 HPE Marvis minis.

Is HPE Marvis minis enabled by default?

Yes, HPE 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 HPE Marvis for Wireless subscription. HPE Marvis minis for wired is supported on EX4100, EX4400, and EX4650 switches running Junos OS version 25.4R2 or later.

Which applications does HPE Marvis minis test by default?

HPE 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?

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

Does adding a new AP to a site impact HPE Marvis minis validations?

If the new AP is running an unsupported firmware version, HPE 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, HPE Marvis minis validations will continue without any disruption.

Do offline APs impact validations?

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

Do HPE Marvis minis validations start immediately after setting up a site?

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

Is HPE Marvis minis enabled by site or organization?

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

Will HPE Marvis minis make any configuration changes to my network?

No.

Where can I view the results from the HPE Marvis minis validations?

The results of HPE Marvis minis validations are surfaced through the HPE 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).

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

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

HPE 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 HPE Marvis minis selects APs that collectively cover the important VLANs in the site. HPE 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 HPE Marvis minis stop running DNS and default application validations?

HPE 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, HPE 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 HPE Marvis minis highlighting the ongoing unaddressed issue.

Do I need a separate subscription for HPE Marvis minis?

No, HPE Marvis minis does not require a separate subscription. If your organization already has an active HPE Marvis for Wireless subscription, you automatically get access to HPE Marvis minis for wireless networks. To use HPE Marvis minis for wired networks, a HPE 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.

We will be introducing curl-based monitoring to continuously monitor critical applications, enabling faster and more effective issue detection.

How does HPE Marvis minis distinguish between critical and noncritical applications?

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

What does HPE Marvis minis test as part of authentication validations?

HPE Marvis minis automatically detects the RADIUS authentication servers configured in your network and validates their reachability. Using preset credentials, HPE 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.

Why does the HPE Marvis minis network test not validate TCP ports such as x.x.x.x:22?

Currently, HPE Marvis minis only supports ICMP-based connectivity checks (standard ping using ICMP packets). It can verify whether a host is reachable, but cannot test connectivity to specific TCP ports, such as x.x.x.x:22.

Support for TCP-based connectivity checks will be introduced through a phased rollout.

Why is trace path not visible on the Application Services SLE page?

Trace path is only visible for APs running firmware version 0.15.34994 that have Critical Application Monitoring enabled. To enable critical application monitoring, see Add Custom URLs for HPE Marvis Minis Validation.

What is First-Mile Baseline in HPE Marvis minis?

First-Mile Baseline (previously shown as minis Baseline on the network latency, network loss, and application latency graphs) is a performance benchmark created by HPE Marvis minis by validating application reachability and performance against a globally hosted minis cloud application, served through a CDN.

From the tests, HPE Marvis minis establishes expected baseline behavior for key metrics such as network latency, network loss, and application latency. If metrics like latency or packet loss deviate from the baseline, administrators can quickly determine whether the issue is within the local network (switches, VLANs, gateways—the first mile) or caused by WAN links and external application servers.