Skip to main content
Cisco Meraki

Dashboard Alerts - Configuration Issues

Overview

This document list all the alerts available under "Configuration Issues" alert category and their triggers and troubleshooting steps. Please refer to network alert hub documentation to learn more. 

Misconfigured DNS

Triggers

As with almost every device used on the internet, Meraki devices rely on DNS to resolve the dashboard URLs. If a device is reporting issues with its DNS configuration, typically the device is not receiving responses to DNS requests.

Troubleshooting Steps

There are a few things to check to try and find the source of the issue:

  • Firewall rules blocking traffic to or from the DNS servers being used or traffic to UDP port 53
  • Routing traffic to or from the DNS servers
  • Invalid responses back from the DNS server
    • Take a packet capture on an upstream device to see what traffic the device is sending and receiving
      • Filtering for the IP address or MAC address of the device and downloading the .pcap file is recommended for larger networks

If there are no firewall rules blocking DNS traffic and there aren't issues with routing traffic, a way to work around this issue is to change the DNS servers to a working public resolver on the DHCP server. Have the Meraki devices request another IP or set the IP manually, and set the DNS servers to a known working public resolver.

Uplink IP address in conflict with another device

Triggers

This means that another device in the network is also using the same IP address as the Meraki device. 

Troubleshooting Steps

Resolving this problem means making sure all devices have unique IP addresses in a network. The Network-wide > clients list may help pinpoint the duplicate IP addresses in use:

  1. Open the clients by navigating to the client page Network-wide > clients.
  2. Find one that has a matching IP address to the device showing the alert.

Both devices, the device showing the alert and the other device using the same IP address, will struggle to reach the internet until this problem is resolved.

Bad IP assignment configuration

Triggers

This alert means a bad static IP or an incorrect VLAN tag with DHCP is being assigned to the Meraki device. Typically, network hardware will simply not work if you assign a bad IP address to it. Meraki devices, however, will automatically switch back to DHCP (automatic IP assignment) so that it can check in to the cloud and alert you about the problem if at all possible.

Troubleshooting Steps

  • The device has had a working static IP, make sure the IP address is still valid.
  • A typo or otherwise incorrect value while assigning a static IP.
  • The wrong VLAN tag is used for DHCP.
  • Switch to DHCP - The error message can only be displayed if the Meraki device has found another working IP address. By switching the IP assignment to DHCP instead of static (only specify a VLAN tag if you know what it should be), the device will keep using the current addressing and the error will go away over time.

Device(s) VLAN mismatch

Triggers

This alert is triggered if there is a management VLAN mismatch. Management VLAN mismatch alert occurs when there is a mismatch between operational, configured, and global management VLAN ID. This alert only applies to Meraki Switches.

Troubleshooting Steps

  • Make sure the device is not using a VLAN different from what is configured for its management interface. 
  • Make sure the device management VLAN is not configured with a different VLAN from what is configured under switch > switch settings page

Port(s) VLAN mismatch

Triggers

This feature utilizes CDP and LLDP packets from the past 3 hours to determine which switchports are connected. If any two connected switch ports belong to Meraki switches in the same dashboard organization, the switchport VLAN configurations are compared.

If any mismatch is found in native, allowed, or access VLANs, both switches will display an alert in the dashboard. The switches will continue displaying the alert until the VLAN mismatch is resolved.

Currently, VLAN mismatch detection is supported on Meraki switches in the same organization. VLAN mismatch detection for other Meraki devices (MRs, MXs, etc.) and non-Meraki devices is not supported.

Troubleshooting Steps

  • Make sure both ports allow the same VLANs. Please refer to this documentation to learn more about how to correct VLAN mismatch error. 

Outdated/unreachable configuration

Triggers

This alert is shown when a configuration change is made in the dashboard, but the Meraki device can't download that change.

Troubleshooting Steps

Before contacting support, there are a few things to try to resolve this error:

  • Give the alert at least 5 minutes to go away naturally. In this time, check to see if any changes to the network are taking hold. For example, change the password on a wireless network and see if a phone can associate with the new password.
  • Try rebooting the device. In some cases this can resolve a configuration fetch issue.
  • If possible, try a different connection to the internet to rule out an upstream network problem.

If the above fails, open a support case for further assistance.

Regulatory domain mismatch

Triggers

Access points have their regulatory body set when they are ordered. As an example, an AP purchased in the US will have the regulatory domain of the Federal Communications Commission (FCC), dictating which channels can be used on the device.

Troubleshooting Steps

  • Be sure the public IP and the order region of the access point match. If the management traffic is using a VPN to another country, try avoiding this to see if the problem is resolved as a test.
  • If the above options are not possible, please contact support to begin an investigation of the next steps.

Country/region mismatch

Please refer to this documentation for more information how this alert is triggered and how to resolve the issue.

Country detection mismatch

Please refer to this documentation for more information how this alert is triggered and how to resolve the issue.

Manual country mismatch

Please refer to this documentation for more information how this alert is triggered and how to resolve the issue.

Switch received high OSPF routes

Triggers

If the count of dynamically learned routes crosses the limit a switch can support this alert is triggered.

Troubleshooting Steps

  • Make sure the count of routes advertised by the OSPF neighbors is within the limit of the Cisco Meraki switch. Please refer to this documentation for more information on the number of routes supported by Cisco Meraki switches. 

Misconfigured switch

Triggers

This alert is triggered if a switch is part of a stack configuration, but that stack configuration does not match what is actually physically connected.

Troubleshooting Steps

Unconfigured switch

Triggers

This alert is triggered if a switch has been physically made part of a stack, but the stack has not been configured in the dashboard.

Troubleshooting Steps

Switch not connected to stack 

Triggers 

This alert is triggered if a switch is part of a stack configuration but is not physically part of the stack.

Troubleshooting Steps 

Host overflow

Triggers

More information on this alert coming soon.

Troubleshooting Steps

More information on this alert coming soon. 

  • Was this article helpful?