Skip to main content

 

Cisco Meraki Documentation

Cisco Meraki Local Status Page: Overview

  1. Last updated
  2. Save as PDF

Click 日本語 for Japanese

Accessing the Local Status Page

Most Cisco Meraki devices have a local status page that can be accessed to make local configuration changes, monitor device status and channel utilization, and perform local troubleshooting. This article provides instructions on how to access the local status page, the functions/information available on it, and how to manage and access them. 

The local status page of any Meraki device is accessible via the web browser of a host machine. By default, users are required to log in to pages that provide configurable options. The local status page uses digest authentication with Message Digest Algorithm 5 (MD5) hashing for the connection between the administering computer and the Meraki device to protect these sensitive settings.

The authentication credentials for a device that uses the default authentication credentials or a device that has not fetched configuration will depend on the firmware version the device is running.

Default credentials when logging in for the first time  

Product family

Firmware Version

Username

Password

All Products

All other/prior versions

Serial number of the device (upper case letters and dashes). Same as Cloud ID/Meraki Serial Number in Dashboard   

No password/empty

Switching - MS

MS 17+ firmware

admin


 

Serial number of the device (upper case letters and dashes). Same as Cloud ID/Meraki Serial Number in Dashboard     

Switching - Catalyst

CS 17+ firmware

admin


 

Serial number of the device (upper case letters and dashes). Same as Cloud ID/Meraki Serial Number in Dashboard     

MX

MX 19+ firmware

admin


 

Serial number of the device (upper case letters and dashes). Same as Cloud ID/Meraki Serial Number in Dashboard   

MR

MR 31.7.1+ firmware

admin


 

Serial number of the device (upper case letters and dashes). Same as Cloud ID/Meraki Serial Number in Dashboard   
MG MG 4.1.1+ Firmware admin Serial number of the device (upper case letters and dashes). Same as Cloud ID/Meraki Serial Number in Dashboard   

To ensure the highest level of security and meet evolving regulatory requirements, we are implementing mandatory passwords for all Local Status Page access on devices created after August 1, 2025. For more details, refer to the documentation on Changing Log-In Credentials.

To reach MR devices, the client must be wirelessly connected to the access point (AP) using a configured service set identifier (SSID) or one of the SSIDs mentioned in the Default SSIDs section, such as "meraki-setup" SSID. However, MS and MX devices can be accessed by any device with access to their LAN IP. This is done by entering the LAN IP address in the URL bar of a web browser. Additionally, each device can be accessed by DNS name if the client traffic passes through the device while browsing the following URLs. This can be useful for determining which AP/switch/firewall a client's traffic is going through to reach the internet. 

Note: These URLs will work for any Meraki devices listed above, but will only access the first device in its path.

Since the URL above can be used to access the local status page, UDP port 53 is enabled on Meraki devices and will be detected as open by any scanning tool.

If access by DNS name is not possible, you can access the local status page by IP address. This is often helpful when initially configuring the device on a network without DHCP, or when setting a device's IP configuration prior to deployment.

  • MR - 10.128.128.126
    In order to access this address, configure a device with the following IP settings, and then browse the address in a web browser.
    IP address: 10.128.128.125
    Subnet mask: 255.255.255.0
     
  • CG: 198.18.0.1
    Campus Gateway has a dedicated service port that can be used without needing to set a static IP on your client. When connected to the management port of a Meraki switch, your device can obtain the appropriate IP settings via DHCP. Alternatively, the following can be used by the client device to access the Local Status Page. 

    In order to access this address, configure a device with the following IP settings, and then browse the address in a web browser.
    IP address: 198.18.0.2
    Subnet mask: 255.255.255.240
    DNS: 198.18.0.1
     
  • MS : Select MS switches have a dedicated management port that can be used without needing to set a static IP on your client. When connected to the management port of a Meraki switch, your device can obtain the appropriate IP settings via DHCP. Alternatively, the following IP settings can be used by the client device to access the Local Status Page.
     
    • MS390 and C9300-M on firmware versions CS 16 and higher:  198.18.0.1
      In order to access this address, configure a device with the following IP settings, and then browse the address in a web browser.
      IP address: 198.18.0.2
      Subnet mask:255.255.255.240
      DNS: 198.18.0.1
       
    • MS390 and C9300-M on firmware versions CS 15.21.1 and lower:  10.128.128.130 
      In order to access this address, configure a device with the following IP settings, and then browse the address in a web browser.
      IP address: 10.128.128.132
      Subnet mask:255.0.0.0
      DNS: 10.128.128.130 
       
    • All other MS switches - 1.1.1.100
      In order to access this address, configure a device with the following IP settings, and then browse the address in a web browser.
      IP address: 1.1.1.99
      Subnet mask: 255.255.255.0
  • MX - (varies)
    Most MX models have a dedicated management port used to access the local status page. In addition, all models can access the local status page using the MX LAN IP address. 
    By default, MX devices run DHCP. Once the client is connected to a LAN interface of the MX, find the client's IP address and default gateway, then open the default gateway address in a web browser.
  • MG - (varies)
    The local status page is accessible at the MG cellular gateway's LAN IP address. By default, MG devices run DHCP. Once the client is connected to a LAN interface of the MG cellular gateway, find the client's IP address and default gateway, then open the default gateway address in a web browser.

Configuring the Local Status Page

Refer to Configuring the Local Status Page documentation for more. 

Controlling Remote Access to the Local Status Page

On MX series devices, by default, access to the local status page is only available to devices via the LAN IP address(es). However, it is possible to allow access via the WAN/internet IP as well. 

  1. Navigate to Security & SD-WAN > Configure > Firewall > Layer 3 > WAN appliance services.
  2. In the field for Web (local status & configuration), enter "any" to allow access from any remote IPs, or enter address ranges in CIDR notations separated by commas.
    Ex. 192.168.13.73/32, 192.168.47.0/24
  3. Click Save Changes.

 

For all other devices, the local status page can be accessed by IP after enabling remote device status pages on the Network-wide > Configure > General page. This allows you to connect to the local status page of a Meraki device via its LAN IP over the network.

Disabling the Local Status Page

Though the local status page is enabled by default, administrators do have the option to disable the local status page on their devices.

Note: The local status page allows administrators to change the IP configuration of their Meraki devices. If the local status page is disabled and a device's current IP configuration does not allow it to contact the cloud controller, the only option will be to perform a factory reset and clear the local configuration (Resetting Cisco Meraki Devices to Factory Defaults article).

 

The option to enable/disable the local status page is available in the dashboard under Network-wide > General > Device configuration. 

Note: If your device has a physical management port, it will always remain active regardless of the value of this setting.

Troubleshooting the Local Status Page 

All DNS queries for setup.meraki.com (or any other local status page URL) that route through a meraki device are intercepted and responded to with an "A record" pointing to the local IP address of the device's local status page interface. If DNS queries for setup.meraki.com (or any other local status page URL) do not pass through the Meraki device in question, the DNS queries will not resolve to the correct local IP address and clients will not be able to reach the local status page. You may also get an error (example) shown below due to DNS not resolving to the local IP of Meraki device or be redirected to the developer hub.

Screenshot 2023-08-24 at 9.44.41 AM.png

If a client is unable to resolve the local status page, be sure to check the following:

  • Client is connected to the network and is within the same subnet as the Meraki device.
  • DNS is set to the Meraki device IP or to a DNS server that will route through the Meraki device
  • Try all relevant local status page URLs (see top of this article)
  • Try incognito/private browsing to eliminate potential caching issues 
  • Ensure if you are hard-wired to turn WiFi off

This issue frequently occurs when the DNS server used by clients on the LAN does not send its DNS queries through the MX, as is the case when the DNS server uses a different default gateway. If this is the case, it can be resolved by either pointing the DNS server through the MX or by creating a specific "A record" in the DNS server to point the appropriate local status page URL to the correct device IP. 

If the local status page URLs are still unreachable for some reason, the local status page can also be reached by going to the LAN IP of the device through a web browser. For more information about connecting to the local status page using a static IP, see the Accessing the Local Status Page  section at the top of this article.