Home > General Administration > Tools and Troubleshooting > Using the Cisco Meraki Device Local Status Page

Using the Cisco Meraki Device Local Status Page

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

Accessing the Local Status Page

The local status page of any Cisco Meraki device is accessible via the web browser of a host machine. To reach MR devices, the client must be wirelessly connected to the AP (using a configured SSID or the 'meraki-setup' SSID), but MS and MX/Z1 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 from a client whose traffic passes through it, by browsing to the following URLs from the client. This can be useful for determining what AP/Switch/Firewall a client's traffic is going through to reach the Internet. 

If access by DNS name is not possible, the local status page is also accessible 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
     
  • MS - 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
    Note: Select MS switches have a dedicated management port that can be used without needing to set a static IP on your client.
     
  • MX and Z1 - Varies
    Most MX models have a dedicated Management port used to access the local status page. Otherwise, the local status page is accessible at the MX or Z1's LAN IP address. 
    By default, MX and Z1 devices run DHCP. Once the client is connected to a LAN interface of the MX or Z1, find the client's IP address and default gateway. Then open the default gateway address in a web browser.
    Note: If the MX is in passthrough mode and its uplink is on a subnet that overlaps with a remote subnet over VPN, either the MX will need to be temporarily removed from VPN to be accessed locally, or the Local Status Page can only be accessed via VPN.

Local Status Page Options

Every device's status page includes useful information about the status of the device, limited configuration options (such as setting a static IP), and other tools. This section will cover what is available for each device.

MR Series

MR Access Points provide the following information and configuration options on their local status page:

  • Connection
    Provides information regarding the client's connectivity to the AP, the AP's current network and channels, as well as other cloud connectivity and status information.
  • Neighbors
    Provides information about any neighboring APs. Includes information like SSID, BSSID, Signal (signal-to-noise ratio in DB), Channel, Mode, and Encryption.
  • Configure
    Provides options for setting the IP address of the AP, other addressing settings, or configuring a proxy for Meraki Cloud traffic.
    Note: The HTTP proxy allows all default management traffic from the Meraki device to be sent through a proxy. This does not include optional cloud communication, including AutoVPN and 802.1x auth traffic.
  • Speed test
    Provides a tool for conducting a speed test from the wireless client to the AP. If using Internet Explorer, only versions 10 and above are supported.

MS Series

MS Switches offer the following information and configuration options on their local status page:

  • Overview
    Provides information regarding the client's connectivity to the switch, the switch's current network, as well as other cloud connectivity and status information.
  • Uplink configuration
    Provides options for setting the IP address of the switch, other addressing settings, or configuring a proxy for HTTP traffic.
    Note: The HTTP proxy allows all default management traffic from the Meraki device to be sent through a proxy. This does not include optional cloud communication, including AutoVPN and 802.1x auth traffic.
  • Switch ports status
    Provides information regarding the configuration and status of ports on this switch.
  • Switch ports configuration
    Provides options for limited configuration changes on switch ports, including enabled/disabled, native VLAN, and link negotiation.

MX/Z1 Series

MX Security Appliances and the Z1 Teleworker Gateway offer the following information and configuration options on their local status pages:

  • Connection
    Provides information regarding the client's connectivity to the appliance, the appliance's current network, uplink status, as well as other cloud connectivity and status information.
  • Configure
    Provides options for setting the IP address of the appliance on its WAN interfaces, other addressing settings, or configuring a proxy for HTTP traffic.
    Note: The HTTP proxy allows all default management traffic from the Meraki device to be sent through a proxy. This does not include optional cloud communication, including AutoVPN and 802.1x auth traffic.
  • Ethernet
    Allows local changes to the speed/duplex settings of the Internet/WAN and LAN ports.
  • Speed test
    Provides a tool for conducting a speed test from the client to the appliance. If using Internet Explorer, only versions 10 and above are supported.

Configuring the Local Status Page

The following Dashboard configuration options may be used to control access to the local status page:

Changing Login Credentials

By default, users are required to log in to pages that provide configurable options. The default credentials are the Serial Number of the device (all upper-case with dashes) as the username, and a blank password. This can be modified to have an admin defined password. To do so, navigate to Network-wide > General > Device configuration and provide a Password. This can then be used with the username "admin" to access certain pages, including the Local Status Page.

Controlling Remote Access to the Local Status Page

On MX/Z1 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 Appliance > Configure > Firewall > Layer 3 > 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.

Disabling the Local Status Page

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

Note: The local status page allows administrators to change the IP configuration of their Cisco 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.

 

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

Troubleshooting the Local Status Page 

Cannot connect to the Local Status Page URL when wired

All DNS queries for setup.meraki.com (or any other local status page URL) that route through the MX or MS 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 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. 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 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 

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, then 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.

Cannot connect to the Local Status Page when connected to an SSID

Both ap.meraki.com and my.meraki.com are locally-hosted sites useful for configuring an AP when it cannot reach the Meraki Cloud. This is often seen on a static, non-DHCP network or when there are strict firewall rules. After a Cisco Meraki access point (AP) has lost its connection to the Internet but is still receiving power, it will broadcast a default service set identifier (SSID) that can be connected to for administrative tasks.

 

Connect to the default SSID by completing the following steps:

  1. Physically inspect the AP
    1. Check that the AP has power (See the LED codes section of the installation guides here)
    2. Copy the MAC address (See the article here).
  2. Check for available wireless networks 
    1. Check if a known default SSID is being broadcast
  3. If a default SSID is being broadcast, connect your device to it
    1. If no known default SSIDs are present, set up a manual wireless network connection 
    2. For the SSID name, use 'meraki-<MAC_Address>' e.g. 'meraki-XX:XX:XX:XX:XX:XX'

If a Meraki Access Point does not have a configuration from the Meraki Cloud Controller it will instead broadcast a default SSID of "Meraki-Scanning." The AP takes an address of 10.128.128.128, the SSID runs DHCP, and it will try to assign any clients that associate with it an address. This is merely to provide connection between a client and the AP to allow for local configuration.

  1. After connecting, open a web browser and connect to one of the Local Status Page addresses
  2. A list of the administrative tasks which are available to use can be found here 

Default SSIDs

Potential known default SSID names along with potential causes/solutions:

<SSID_name>-bad-gateway

Cause: An AP's configured default gateway has failed to respond to 15 consecutive ARP requests.

Solution: Check the AP's IP address configuration and reachability to its default gateway.

<SSID_name>-connecting

Cause: An AP's SSID that is configured to use a VPN concentrator is unable to connect.

Solution: Verify connectivity to the concentrator using the tools in Dashboard. Also, confirm that your local firewall is not blocking the connection.

<SSID_name>-scanning

Cause: Similar to 'bad-gateway', an AP is unable to connect to its default gateway.

Solution: Check the AP's IP address configuration and reachability to its default gateway.

Meraki Setup

Cause: An AP has never connected to the Meraki cloud controller (MCC) or has been factory reset.

Solution: Establish MCC connectivity for the AP by ensuring appropriate Internet access. 

 

You must to post a comment.
Last modified

Tags

Classifications

This page has no classifications.

Other Languages

Explore the Product

Click to Learn More

Article ID

ID: 6381

Explore Meraki

You can find out more about Cisco Meraki on our main site, including information on products, contacting sales and finding a vendor.

Explore Meraki

Contact Support

Most questions can be answered by reviewing our documentation, but if you need more help, Cisco Meraki Support is ready to work with you.

Open a Case

Ask the Community

In the Meraki Community, you can keep track of the latest announcements, find answers provided by fellow Meraki users and ask questions of your own.

Visit the Community