Dashboard Alerts - Device Health

Triggers

The alert is triggered if one of the power supplies of the switch is connected but 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. 

• Try reseating the power supply and reboot the device. 

• If the issue persists, contact Cisco Meraki support for further troubleshooting steps. 

Triggers

The alert is triggered 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.
• Reseat the connection between the redundant power supply and the switch. Reboot the switch. 
• If the issue persists, contact Cisco Meraki support for further troubleshooting steps. 

Triggers

The alert is triggered 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.
• Reseat the connection between the redundant power supply and the switch. Reboot the switch. 
• If the issue persists, contact Cisco Meraki support for further troubleshooting steps. 

Triggers

The alert is triggered if one or more fans are connected but not functioning properly. 

Troubleshooting Steps

• Try reseating the fans and reboot the device. 
• If the issue persists, contact Cisco 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 

While we are working on creating proper troubleshooting steps for this alert here is some useful information.

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

Troubleshooting Steps 

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