There are a number of options available in the Meraki Dashboard for email alerts to be sent when certain network or device events occur. This article outlines which options are available for each product, as well as additional considerations when using network alerts.
Configuring Network Alerts
Network alerts can be configured in Dashboard under Network-wide > Configure > Alerts.
Network alerts can be configured by specifying the Default recipients for all selected alerts, and by configuring additional recipients on a per-alert basis. There are two options to denote who will receive email alerts:
- All network admins
This will send email alerts to both Full and Read-only network admins. This does not include any of the Organization admins.
- Other email addresses
This allows for a custom list of recipients, where email alerts will go to all email addresses listed. To specify other email addresses, type an email address into the Default recipients field and hit enter.
The following screenshot shows an example network alerts configuration on a combined network:
The following alerts can be configured on multiple Cisco Meraki products:
- Configuration settings are changed
Available on all platforms, sends an email if any configuration change is made in Dashboard.
- A VPN connection comes up or goes down
Available on both the MR and MX platform, sends an email if a configured VPN tunnel goes up or down.
Note that for MX, only AutoVPN connections are monitored for alerts. The connectivity status of Non-Meraki Site-to-Site VPN is not monitored because it cannot be monitored from both sides of the tunnel.
- A rogue AP is detected
Sends an alert if a rogue AP is detected on the network.
- Network usage exceeds (x) KB/MB/GB/TB in 20 minutes/4 hours/1 day
Sends an alert if the specified amount of data is seen on the network for the specified timeframe.
Alerts can be configured for the following MR Access Point events:
- A gateway goes offline for (x) minutes
Sends an email if any gateway AP is unreachable from Dashboard for the configured number of minutes. Please note that the AP may still be functioning, this only indicates that it is unable to contact Dashboard.
- A repeater goes offline for (x) minutes
Sends an email if any repeater AP is unreachable from the Dashboard for the configured number of minutes.
- A gateway becomes a repeater
Sends an email if a gateway AP loses its link to the network, and comes online as a repeater.
For more information on this behavior, please refer to our documentation regarding Gateway vs. Repeater APs.
Alerts can be configured for the following MX Security Appliance events:
- A security appliance goes offline for (x) minutes
Sends an email if the MX is unreachable from Dashboard for the configured number of minutes. Please note that the MX may still be functioning, this only indicates that it is unable to contact Dashboard.
- The primary uplink status changes
Sends an email if the status of the primary uplink changes, which could be a failover event or downed link.
Note: It is not recommended to configure this alert if you are running an appliance with only a cellular uplink, as you may see false alerts about failing over to a cellular uplink if the node reboots, or experiences an issue with connectivity. In such situations, it's recommended to use the cellular connection state alerts, or appliances goes offline alerts instead.
- The DHCP lease pool is exhausted
Indicates that the MX has run out of available IPs in one or more of its configured DHCP scopes, and is unable to provide an IP address to a requesting client.
- An IP conflict is detected
Sends an email if the MX has observed traffic from multiple MAC addresses, using the same IP address.
Note: Due to the nature of certain device types, this event may occur as a result of normal network behavior. For a common example, please refer to our documentation regarding IP Conflicts Triggered by iOS Devices.
- Cellular connection state changes
Sends an email if the appliance establishes or loses its connection to the cellular network.
- A rogue DHCP server is detected
Sends an email if the MX observes multiple MAC addresses responding to DHCP Discover or DHCP Request messages. This can occur if a DHCP relay server is configured on a VLAN where the MX is configured to respond to DHCP.
For more information, please refer to our documentation regarding DHCP configuration in Dashboard.
- A warm spare failover occurs
Sends an email if the primary MX of a High Availability pair fails over to the spare, or vice versa.
For more information, please refer to our documentation regarding Troubleshooting MX Warm Spare.
- Malware is blocked
This alert will be triggered when a malicious file download is blocked.
- Malware is downloaded
This alert will be triggered when a file previously downloaded on your network is determined to be malicious in retrospect.
- Clients connect or disconnect from the LAN
Sends an email if select clients connect or disconnect from the LAN, as observed by the MX.
Wireless MX/Z-series Alerts
The following additional alert is available for wireless MX devices or the Z-series Teleworker Gateway:
- A rogue AP is detected
Sends an alert if a rogue AP is detected on the network.
Alerts can be configured for the following MS Switch events:
- A switch goes offline for (x) minutes
Sends an email if a switch is unreachable from Dashboard for the configured number of minutes. Please note that the switch may still be functioning, this only indicates that it is unable to contact Dashboard.
- A new DHCP server is detected on the network
Sends an email if a DHCP Offer, ACK, or NACK message from a new MAC address (not seen in the last month) is observed by the switch.
- Any/specific port(s) goes down for more than (x) minutes
Sends an email if the switch port(s) specified goes down for more than the configured number of minutes.
- Any/specific port(s) detects a cable error
Sends an email if the switch port(s) specified detects an issue with the connected cable.
- Any/specific port(s) changes link speed
Sends an email if the switch port(s) specified renegotiates or fails over to another link speed.
Note: Alerting for specific port(s) requires the port(s) to be tagged under Switch > Switch ports. If no ports are tagged, "any port" will be the only option in the drop-down menu. Please note that multiple ports can share the same tag.
- A power supply goes down
Sends an email if one of the removable power supplies on the MS fails.
- A redundant power supply is powering a switch
This alert will be triggered if redundant (not modular) power supplies are providing power to a switch.
- Unidirectional link detection (UDLD) errors exist on a port
This alert will be triggered if UDLD errors are seen on a switch port.
- A switch is operating at critical temperature
This alert will be triggered if a switch detects that it is operating at critical temperature. Critical temperature is a serious scenario requiring serious consideration of the operating environment of the switch. This alert is supported for the MS120 series, MS220-24P, MS210 series, MS225 series, MS250 series, MS320 series, MS350 series, MS410 series, and MS425 series.
System Manager offers a number of advanced alert options, unique from the rest of the Meraki product line.
For more information about SM alerts, please refer to our product documentation.
Most major mobile carriers allow you to send emails to an SMS phone number (see the list of phone number “conversions” by carrier below). Take advantage of this “hack” in the Dashboard to get alerts sent directly to a mobile device as a text.
- Alltel: firstname.lastname@example.org
- AT&T: email@example.com
- T-Mobile: firstname.lastname@example.org
- Virgin Mobile: email@example.com
- Sprint: firstname.lastname@example.org
- Verizon: email@example.com
- Nextel: firstname.lastname@example.org
- US Cellular: email@example.com
All network alerts will be sourced from the same email address. To ensure that alerts are not being lost to a spam filter, please be sure to add firstname.lastname@example.org as a trusted email source.