Marvis Virtual Network Assistant and AI-Driven Troubleshooting
Marvis Virtual Network Assistant and AI-Driven Troubleshooting
This domain tests how to use Marvis as an AI troubleshooting assistant and how to act on Marvis Actions without treating them as unquestionable commands. Expect natural-language queries, root-cause evidence, and prioritized actions.
Core rules
- Marvis VNA is the conversational assistant in the Mist portal. Ask about a specific client, AP, switch, site, or symptom; Marvis uses SLEs, device events, client events, and telemetry to return a classification, evidence, and recommended action.
- Marvis Actions is a prioritized list of network issues. It groups problems by scope and impact so you fix the highest-value issue first. Actions may include an apply or fix control, but you should verify scope and blast radius.
- Marvis troubleshoots; it does not replace the configuration source of truth. A recommendation to change power, disable a band, or alter a WLAN must be implemented in the correct RF, WLAN, or switch template.
- Marvis depends on available telemetry and subscription entitlement. It cannot inspect encrypted payloads or magically see a device that is not reporting.
Worked example
A user asks Marvis why a client is slow. Marvis reports sticky roaming: the client remains on a distant AP with low RSSI and does not roam. Reasoning: check client events for roam attempts and the RF template for 802.11k/v/r and power settings. If fast roaming is disabled and power is unbalanced, enable the supported roaming features and adjust power, then confirm the Roaming SLE improves.
Traps
- Applying a Marvis Action without checking which sites or clients it affects.
- Treating Marvis as a configuration console.
- Ignoring that a missing subscription limits Marvis features.
- Expecting Marvis to decrypt application traffic.
- Assuming a high-confidence answer is a guarantee.