Marvis Virtual Network Assistant
Marvis Virtual Network Assistant
This domain tests what Marvis can answer, how Marvis Actions differ from alarms, and where synthetic testing fits into operations.
What Marvis does
- Answers natural-language queries over Mist telemetry, such as why a client is slow, which APs are down, or where DHCP failures are occurring.
- Marvis Actions provides a prioritized list of client-impacting issues with root cause, for example AP offline, bad cable, DHCP scope exhaustion, authentication failures, missing VLAN, or PoE problems, plus remediation where supported.
- Marvis Minis runs synthetic tests that emulate client onboarding (association, DHCP, DNS, RADIUS) to catch problems before users report them.
- Dynamic packet capture and auto-troubleshoot supply evidence, and the Marvis Client app can contribute client-side telemetry.
Worked example
Users at a branch report slow joins. Ask Marvis why clients are failing to connect at that site. It correlates with the Successful Connect SLE, points to DHCP failures on VLAN 20, and shows the DHCP scope exhausted at 09:12. The reasoning chain matters: symptom, then SLE, then classifier, then the DHCP server. The action is to expand the scope.
Traps
Marvis does not design or replace WLAN configuration. Actions are impact-ranked and proactive, while alarms are event-based notifications, so they are not the same list. Minis are synthetic probes, not real user traffic, so they can pass while a real client-specific problem persists. Marvis is also only as good as the telemetry reaching the cloud.