Troubleshoot Meraki MX Issues: 3 Steps

Last Updated: May 2026


For the approved list of dCloud team-tested and verified routers, see Supported Meraki Routers .

Use this page to diagnose and fix connectivity issues between your Meraki MX appliance and a dCloud session. It walks you through three main steps: verifying the MX–session connection, decoding the MX LED status, and confirming basic network settings. If needed, it also shows you when and how to reset the device to factory defaults so you can quickly return to a known-good state.


Troubleshoot Meraki MX Issues

Instructions

To troubleshoot Meraki MX issues, follow the 3 main steps below.

Step 1. Perform 2 checks to verify the connection

Perform these two checks after your session has been active for 10 minutes or more, because the VPN tunnel can take up to 10 minutes to become fully operational after a session starts.

  1. Check the connection between the Meraki MX and your session.
  2. If you added your Meraki MX to a session and think the MX is not connecting to the active session, check the MX connection to dCloud and the VPN tunnel required for router–session communication.

If either check above is not successful, contact Cisco dCloud Support for help.

Step 2. Decode the Meraki MX LED status and take action

  • Observe the status indicator. The Meraki MX uses an LED to inform you of the device's status. LED patterns, their meanings, and recommended troubleshooting actions are described below.
    LED PatternMeaningWhat To Do Next
    Solid orangePower is applied but the appliance is not connected to the Meraki Dashboard.
    • Confirm Internet connectivity and Meraki cloud connectivity.
    • Verify the MX is connected to a DHCP-enabled network and obtaining an IP address.
    • Check firewall rules to ensure Meraki cloud traffic is allowed.
    • If the uplink is not DHCP-enabled, configure a static IP address.
    Rainbow colorsThe appliance is attempting to connect to the Meraki Dashboard.
    • Confirm Internet connectivity and Meraki cloud connectivity.
    • Verify the MX is connected to a DHCP-enabled network and obtaining an IP address.
    • Check that Meraki cloud traffic is not blocked by the firewall.
    Flashing whiteFirmware upgrade in progress.Wait for the upgrade to complete. Do not power off the device during the upgrade.
    Solid whiteFully operational.
    • Confirm client devices can connect and obtain an IP address in the 100.127.0.0/16 subnet.
    • If using a wireless MX, check SSID and wireless connectivity.
    • Ping a device in the vPod network (for example, 198.18.133.1) to verify end-to-end connectivity.

Step 3. Configure basic connectivity and other networking parameters

  1. Using a client machine such as a laptop, connect to one of the four LAN ports of the MX.
  2. Using a browser on the client machine, access the appliance's built-in web service by browsing to http://setup.meraki.com. (You do not have to be connected to the Internet to reach this address.)
  3. On the Local status tab, click Uplink configuration. The default credentials use the device serial number as the username, with a blank password field.
  4. Choose Static for the IP Assignment option.
  5. Enter the IP address, subnet mask, default gateway IP, and DNS server information.
  6. If LED status is solid white, confirm:
    • If you are using a wireless-capable MX appliance, confirm you can connect a laptop or wireless device to the advertised SSID and obtain an IP address in the 100.127.0.0/16 subnet range.
    • If you are not using a wireless-capable MX appliance, confirm you can connect a laptop or wired device and obtain a DHCP IP address in the 100.127.0.0/16 subnet range.
  7. From the laptop connected to the MX appliance, attempt to ping a device within the vPod network (for example, 198.18.133.1).

Troubleshooting Tip:
If your Meraki MX appliance is obtaining an uplink IP address and Meraki cloud traffic is allowed, but it is still not issuing DHCP addresses in the 100.127.0.0/16 subnet or is not connecting to the vPod network, try resetting the MX to factory defaults.

Troubleshooting: Reset Meraki Device to Factory Default

When to Reset
If your Meraki MX appliance is obtaining an uplink IP address and traffic to the Meraki cloud is allowed, but the MX is not issuing DHCP addresses in the 100.127.0.0/16 subnet or is not connecting to the vPod network, a factory reset may resolve the issue.

Important: A factory reset restores default settings. You will need to reconfigure any custom network settings after the reset.

How to Reset

  1. Locate the Reset button on your Cisco Meraki device.
  2. Use a paper clip or similar object with a long, thin tip.
  3. Press and hold the Reset button for 10–15 seconds (or until the power light goes out).
  4. Release the button. The device will reset to factory defaults and automatically reboot.
  5. Note: If a static IP address was configured previously, you will need to re-enter it using the local status page after the reset.

For more information and support, contact Cisco dCloud Support for help.


On this page