Dashboard Alerts - Device Health

Triggers

If one of the power supplies of the switch is connected, but it is offline or not powered on. 

Troubleshooting Steps

• Make sure both power supplies are receiving power. Check the power outlet to make sure it is providing power. 
• Reset the power supply and reboot the device. 
• If the issue persists, contact Meraki support for further troubleshooting steps. 

Triggers

If the redundant power system is connected but offline or powered off.

Troubleshooting Steps

• Make sure the redundant power supply is receiving power. Check the power outlet to make sure it is providing power.
• Reset the connection between the redundant power supply and the switch. Reboot the switch. 
• If the issue persists, contact Meraki support for further troubleshooting steps. 

Triggers

When the switch is not using the connected redundant power supply. 

Troubleshooting Steps

• Make sure the redundant power supply is receiving power. Check the power outlet to make sure it is providing power.
• Reset the connection between the redundant power supply and the switch. Reboot the switch. 
• If the issue persists, contact Meraki support for further troubleshooting steps. 

Triggers

If one or more fans are connected but not functioning properly. 

Troubleshooting Steps

• Reset the fan and reboot the device. 
• If the issue persists, contact Meraki support for further troubleshooting steps. 

Triggers

STP change alerts are created whenever a high or very high rate of STP topology change notifications (TCNs) are detected or received on a switch port. TCNs are triggered when a switch detects changes in the topology.

Troubleshooting Steps

Historical STP topology changes can be found on the port connectivity bar.

Some of the common root causes of STP topology changes are as follows:

• Port flaps between 2 switches. It can happen if the cable is faulty. 
• Delay in sending or receiving BPDUs due to high CPU usage or packet loss.
• STP BPDU conflicts when multiple BPDUs are received within a small window that identifies different sending ports.

Triggers

There are 2 types of CRC errors:

• High CRC errors: A port is sending or receiving a high amount (greater than 100 hits/hour or greater than 1% of traffic) of CRC align errors. 
• Very high CRC errors: A port is sending or receiving a high amount (greater than 1000 hits/hour or greater than 10% of traffic) of CRC align errors.

Guided Troubleshooting Flow

This feature is designed to reduce troubleshooting effort, make issue resolution more intuitive, and save more time for our customers. Guided CRC troubleshooting flow automates and outlines suggested action items (refer to flow diagram and the short video below) to be performed to resolve CRC error alerts. This tool is designed to help network administrators efficiently and effectively identify the root cause of the CRC error on switch ports and resolve it.

Configuration Mismatch issue	Cable and other issues

Triggers

• Verify there is no duplex configuration mismatch between two neighboring ports. 
• Run cable test to verify the cable is healthy or not.
• Verify the switch port is healthy by connecting the end device with the same cable to a known working port. If the issue does not persist then the original switch port is possibly faulty, please contact Meraki support, if persists, move to the next troubleshooting step.
• Verify the end device is healthy by connecting it to the original port using a known working cable bypassing any patch panels. If the issue persists then the end device's NIC card is possibly faulty, if not, move to the next troubleshooting step.
• Verify the copper/fiber transceiver is healthy by installing a known working transceiver on the port. If the issue does not persist then the original copper/fiber transceiver is possibly faulty, if the issue persists, move to the next troubleshooting step.
• If the issue persists after attempting the above steps, then the patch panel is possibly faulty or there is electromagnetic interference near the cable.

Triggers

A beacon is a wireless LAN packet that signals the availability and presence of the wireless device. Clients may disassociate or roam to another AP when they miss eight consecutive beacons. 

Troubleshooting Steps

• Check AP functionality and wiring.
• Check client wifi device operating correctly.
• Check client wireless drivers.
• Check for environment radio interference.

Triggers

AP did not negotiate sufficient PoE parameters for full power operation.

Troubleshooting Steps

• Check AP PoE needs and switch specs to make sure switch is providing required PoE level.
• Check cabling to make sure the AP is not running beyond PoE length standards for the protocol.

Triggers

AP did not negotiate full capability of local LAN port. Any AP running with half-duplex or with negotiated link speeds of less than 1000Base-T are flagged for this error.

Troubleshooting Steps

• Check port settings (speed and duplex) on switch.
• Check cabling to make sure using CAT spec cable matching desired ethernet speeds.

Triggers

If the port is detecting a high amount (greater than 10% of transmitted traffic) of collisions.

Troubleshooting Steps

Check for anomalies:

• Physically inspect the layer 1 cable.
• Check speed/duplex.
• Assess path from the switch to the client.

Triggers

If the port is sending or receiving a high amount (greater than 1000 hits/hour or greater than 10% of traffic) of fragments.

Troubleshooting Steps

Check for anomalies:

• Physically inspect the layer 1 cable.
• Assess path from the switch to the client.

Triggers

If the port is sending or receiving a high amount (greater than 1000 hits/hour) of jabbers.

Troubleshooting Steps

Check for anomalies:

• Physically inspect the layer 1 cable.
• Assess path from the switch to the client.

Triggers

If the port is sending or receiving a high amount (greater than 10% of traffic) of oversized or undersized packets.

Troubleshooting Steps

Check network MTU settings to make sure it is consistent throughout path.

Triggers

Various stages of SecurePort Authentication.

Troubleshooting Steps

Troubleshoot based on stage of alert, check that LLDP is enabled on network and the MR/MS is running the minimum required firmware.

Triggers

When a BPDU guard enabled port receives a BPDU from the connected device, the port is disabled and its state is changed to errdisable state. The switch will also start discarding packets received on the port.

Troubleshooting Steps

Remove the offending device sending the BPDU and check the topology configuration.

Triggers

If a non-designated port with loop guard enabled stops receiving BPDUs, it will transition into a loop-inconsistent blocking state. In this state, the port will still process BPDUs but will not learn MAC addresses or forward traffic, thereby preventing a loop from forming.

Troubleshooting Steps

Check switch topology and STP configuration.

Triggers

Root guard is a feature in Spanning Tree Protocol (STP) that prevents a switch port from becoming a root port if it receives superior Bridge Protocol Data Units (BPDUs) from another switch. When root guard is enabled on a port, it discards incoming BPDUs from switches that claim to be the root bridge.

Troubleshooting Steps

Check switch topology, STP configuration, specifically root bridge settings.

Triggers

MV devices are having issues uploading to the cloud.

Troubleshooting Steps

• Check network settings for MV.
• Check firewall settings.

Triggers

When the camera cannot mount its storage. 

Troubleshooting Steps

Open a support case.

Triggers

Issues reaching/talking to NTP servers.

Troubleshooting Steps

• Check network settings, DHCP options, and ping NTP servers.
• Confirm an NTP server is configured on the switch in the running configuration (ntp server {address}).
• Confirm the NTP server is accessible.
• Additional troubleshooting steps are available in NTP Troubleshooting and Debugging Guide.

Triggers

A member of a switch stack has experienced an anomaly that indicates an unhealthy status.

Troubleshooting Steps

Determine which stack member is alerting and troubleshoot deeper or replace the device.

Triggers

A configured access policy is limiting or denying traffic.

Troubleshooting Steps

Check access policies and configure as needed.

Triggers

When an MT20 detects a tamper state.

Troubleshooting Steps

Check that:

• You are using the included magnet bar.
• The gap between the MT20 and the magnet bar does not fall below 5 millimeters (0.5 cm).

Note that this can also trigger when an unknown magnet strength is detected, potentially indicating physical tampering.

Triggers

Netconf-yang process has experienced an anomaly.

Troubleshooting Steps

• Netconf is a protocol used within the encrypted tunnel to communicate between the switch and cloud.
• If this error appears, additional information may be provided in the syslog (show log) of the switch regarding resolution steps.
• After resolving based on any log information shown, the netconf process should be restarted (no netconf-yang; netconf-yang in the running configuration).
• Any other processes requiring netconf will be unavailable while netconf restarts.
• The error may take up to an hour to resolve in dashboard following the process restart.

PoE Port Was Denied Power

PoE Overload

Detected an Unsupported Cable Type

Device Reboots

Device Rebooted Due to no_xmit_mon

Device Panic Reboots

1 Gigabit Link Failed, Speed Downshifted

Received BPDUs From Multiple Senders

Probe Disconnected

UDLD TX/RX Loop Detection

UDLD Neighbor Mismatch Detection

UDLD Unidirectional Link Detection

Water Leak Cable Disconnected

Water Leak Cable Connected

WLC Redundancy Has Member in Active Recovery

WLC Redundancy Has Member in Standby Recovery

WLC Redundancy Standby Member Offline

WLC Redundancy Failover Occurred in Past Day