Dashboard Alerts - Insight

Last updated
Save as PDF

Troubleshooting Guide

This document lists alerts in the category of Insights, some alerts may require access to the Meraki Insight feature for those with Advanced Security licenses and higher. Included are the triggers and recommended next steps to help remediate the issue identified

The root cause currently covers the WAN problems detected by passive analysis of application flows on the web app health WAN problems

Application Performance Degradation

Triggers

If no root cause for an issue has been found, the alert will show as Performance Degradation.

Troubleshooting Steps

Web App Health goodput or response time data for a particular application and network drops below whatever threshold the user has set (either smart thresholds or manually set).

ISP Issue

Triggers

Goodput on the WAN for passively collected flows per application and network drops below whatever threshold the user has set (either smart thresholds or manually set).
Uplink usage is less than 80% of the bandwidth defined on SD-WAN & Traffic Shaping.
Goodput of actively collected ICMP ping data for the alerting uplink drops below 2.5KB.

Troubleshooting Steps

Check to see if you have configured the bandwidth on SD-WAN & Traffic Shaping.
Check bandwidth restrictions by referring to Global Bandwidth Limit Considerations.
Look at the event logs to notice if there are continuous VPN registry changes (Refer to Meraki Auto VPN - Configuration and Troubleshooting).
Look at the network status on the WAN Health page or the Uplink tab on Appliance status page to check loss and latency reported from ping data.
Look at the Meraki Insight Web App Health drill down page to check passive goodput.

High Latency Over VPN

Triggers

Goodput on the WAN for passively collected flows per application and network drops below whatever threshold the user has set (either smart thresholds or manually set).
The flow goes over VPN and there is latency detected on the WAN for this application only. There is a check for other major problems/outages.

Troubleshooting Steps

Check the WAN Health portfolio in Meraki Insight to see if the overall network is having high latency.
Check the VPN Status page to see usage information for any bandwidth throttling.

Uplink Saturation

Triggers

Goodput on the WAN for passively collected flows per application and network drops below whatever threshold the user has set (either smart thresholds or manually set).
If the uplink usage is greater than 80% (as configured on SD-WAN & Traffic Shaping) then there is high confidence that the application performance is suffering due to the uplink being saturated.

Troubleshooting Steps

Check to see if you have configured the bandwidth on SD-WAN & Traffic Shaping.
Check bandwidth restrictions by referring to Global Bandwidth Limit onsiderations.
Check WAN Health page to see if the given network shows a high usage alert on the availability graph.
If a certain user is utilizing more than the required bandwidth, refer to Creating and Applying Group Policies to add policies to restrict or limit bandwidth utilized.

VRRP Warm Spare Failover

Triggers

When there are unexpected numbers of VRRP transition events on the event log for primary and spare MX that can hamper the flows of the application to be interrupted or cause loss. There is also a check to see if the WAN overall is seeing a loss:

If yes, then this alert is triggered with high confidence that the reason for the issue is due to VRRP transitions and high WAN loss.
If no, then this alert is triggered with medium confidence that this might only be due to the VRRP transitions.

Troubleshooting Steps

Check the Connection Monitoring for MX by referring to MX VRRP Transitions.

Traffic Shaping Rule Saturation

Triggers

Goodput on the WAN for passively collected flows per application and network drops below whatever threshold the user has set (either smart thresholds or manually set).
The app configured on Web App Health has a traffic shaping rule with a bandwidth limit applied to it under the SD-WAN & Traffic Shaping.
Usage of the app is >80% of the configured bandwidth limit as configured by traffic shaping.

Troubleshooting Steps

Check the traffic shaping rule section under SD-WAN & Traffic Shaping to increase the limit on the bandwidth provided to the application.
Refer to Traffic and Bandwidth Shaping for more information on limitations that can be applied to application traffic.

Sticky Client

Triggers

There is poor performance detected between the SSID and client connection due to suboptimal AP selection. Client devices choose which AP to connect to. Meraki APs cannot force a client to choose a particular AP.

Troubleshooting Steps

Try to force the client to re-select a more optimal AP by having the client disassociate and reassociate.
To learn more about setting to avoid sticky client issues, refer to Wireless Issue Resolution Guide.

MAC Address Flap Anomaly

Triggers

A MAC flap event is triggered when a MAC address is learned 3 times or more on 2 or more different ports within 10 seconds. Sometimes these events can become noisy due to wireless roaming, which is expected. Due to this noise, it is hard to tell which events are expected vs unexpected. Networks with APs in bridge mode are susceptible to this issue.

It is difficult to separate and identify unexpected events. To solve this problem, Cisco Meraki built a machine-learning algorithm to detect these unexpected events more accurately.

The machine learning algorithm looks at the past 35 days of hourly event counts and creates hourly thresholds for the next 7 days. It monitors the real-time hourly event counts, and if the real-time hourly count breaches the expected threshold, it will create an alert - MAC flap anomaly detected on “SWITCHNAME” from “TIMESTAMP”.

The alert will only resolve itself if the algorithm detects the real-time hourly counts goes below the threshold, which happens at the top of the hour from the time of anomaly detection, otherwise, it will persist.

Troubleshooting Steps

Make sure there is no loop in the network.
Follow the High-Density Wi-Fi Deployment Guidelines to make sure the network meets the optimal network criteria.
Sometimes a bad WiFi adapter on a client device can cause frequent connection failure and cause frequent roaming.

ARP Failure

Triggers

Large number of clients experiencing issues with the ARP protocol/gateway, gateway timeout, excessive ARP requests.

Troubleshooting Steps

Check that the gateway is online and reachable.
Make sure that there is no congestion in the network.

Insight Web App Alert "Name of Application"

(Header can be set dynamically based on what app is experiencing outage)

Triggers

When a custom monitored application triggers a threshold/event that is deemed necessary to alert.

Troubleshooting Steps

Begin troubleshooting within application environment.