Troubleshoot Meraki MX Issues

Last updated: May 2023

Troubleshoot Meraki MX Issues

Procedures

Follow this procedure to troubleshoot Meraki MX issues. 
 

1. Perform the following two checks

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

  • Check the connection between Meraki MX and your Session.
  • If you added your Meraki MX to a session and think the MX is not connecting to the active session, you can 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.

 

2. Decode Meraki MX Led Status

  1. Observe the Status Indicator. The Meraki MX uses an LED to inform the user of the device's status. LED patterns and their meanings are described below.
    LED StatusMeaning
    Solid orangePower is applied but the appliance is not connected to the Meraki Dashboard
    Rainbow Colors The appliance is attempting to connect to Meraki Dashboard
    Flashing White Firmware upgrade in progress
    Solid WhiteFully operational
  2. Observe the color LED status color. If it is solid orange or rainbow colors, Internet connectivity and connectivity to the Meraki cloud should be confirmed.
  3. Verify the MX appliance is connected to a DHCP-enabled network obtaining an IP address.
  4. Verify Meraki cloud communication traffic is not being blocked. Confirm the required traffic is being allowed via the firewall rules if applicable.
  5. If the Meraki MX appliance internet uplink is not connected to a DHCP enabled network, the user can configure a static IP address.
  6. To ensure that the client PC is redirected to the local web service in the following step, you must disable all other network services (ex: Wi-Fi) on your client machine.
  7. Supported Routers and Endpoints
  8. Reset Meraki Device to Factory Default
  9. Routers FAQs


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:
    1. 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.
    2. 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 ping 198.18.133.1


4. If MX is still not issuing DHCP addresses ranges from the 100.127.0.0/16 subnet range and/ or not connecting to vPod network, try to reset the MX to factory defaults.

If Meraki MX appliance is obtaining an uplink IP address, and traffic to Meraki cloud is allowed but MX is still not issuing DHCP addresses ranges from the 100.127.0.0/16 subnet range and/ or not connecting to vPod network, try to reset the MX to factory defaults.


5. Reset Meraki Device to Factory Default when necessary

You can reset Cisco Meraki devices can be reset to their factory defaults using the Reset button on the device. This requires a paper clip or object with a long thin tip. Insert the tip of the paper clip into the reset button, press and hold for 10-15 seconds, or until the power light goes out, whichever occurs first. This will reset the device to factory defaults and reboot. If a static IP address was configured for the device, it will need to be configured again using the local status page.


References

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



On this page