Skip to main content
Cisco Meraki

Dashboard Alerts - Insight

NOTE:  This feature is currently in Beta

Troubleshooting Guide

This document enlists all the available alert categories under Meraki Insight’s Web Application Performance and the triggers and recommended next steps to resolve the application issue on the network.

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

1. Performance Degradation

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

Triggers

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).

2. ISP issues

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 the SD-WAN & Traffic shaping page

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 the SD-WAN & Traffic shaping page (link to the SD-WAN and traffic shaping page)

  • Check Bandwidth restrictions by referring to the Global Bandwidth limit considerations KB article 

  • Look at the event logs to notice if there are continuous VPN registry changes and refer to the Site-to-Site VPN troubleshooting doc or Meraki Auto VPN -Configuration and Troubleshooting 

  • Look at network status on the WAN Health page, or 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

3. 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, then this alert is triggered. There is a check for other major problems/outages  considering this root cause High confidence

Troubleshooting steps

  • Check the WAN health portfolio in Meraki insight to see if the overall network is having high latency.

  • Check VPN status page to see usage information for any bandwidth throttling

4. 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 the SD-WAN & Traffic shaping page) 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 the SD-WAN & Traffic shaping page[insert SD-WAN and traffic shaping page dash link]

  • Check Bandwidth restrictions by referring to the Global Bandwidth limit considerations KB article 

  • 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

5. Dual Active MXes

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, this alert is triggered. 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

6. 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 and Traffic shaping page

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 the SD-WAN and Traffic shaping page 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

 

7. Sticky client

Triggers

If poor performance detected between SSID and client connection due to suboptimal AP selection this alert will be triggered. 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 please refer to this documentation.