Advertisement
Quick Links
Using the Cisco Meraki Device 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.
Accessing the Local Status Page
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 username for devices that have default authentication credentials or have not fetched configuration will be the serial number (upper case letters and
dashes) with no password. Authentication credentials should be changed to have a strong password after their initial use. Please see the
Credentials
section below.
To reach MR devices, the client must be wirelessly connected to the access point (AP) using a configured service set identifier (SSID) or the "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.
•
MR
-
http://ap.meraki.com
•
MS
-
http://switch.meraki.com
•
MX
-
http://mx.meraki.com
•
MG
-
http://mg.meraki.com
•
Any
-
http://setup.meraki.com
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.
Note: MR does not provide access to the local status page via a wired connection (for example, when a client is connected directly to one of the AP's
Ethernet ports) for security reasons. Refer to the subsequent section for access to local status page via SSID.
• 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
or
http://wired.meraki.com
or
http://my.meraki.com
Changing Log-In
1
Advertisement
Related Manuals for Cisco Meraki MR Series
Summary of Contents for Cisco Meraki MR Series
- Page 1 Using the Cisco Meraki Device 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.
- Page 2 Subnet mask: 255.255.255.0 • 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.
- Page 3 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 access point, the access point's current network and channels, as well as other cloud connectivity and status information. ◦...
- Page 4 The channel utilization information on the local status page is sourced from the client-serving radio. The client-serving radio on the Meraki access point has a counter that is updated every 20 seconds. Counters indicate how many times the AP was transmitting, receiving, and saw congestion on the channel, as well as the total cycle count.
- Page 5 Provides information about any neighboring access points. 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 access point, putting the MR access point into site survey mode (see Conducting Site Surveys with MR Access Points), manual channel and power adjustment, and...
- Page 6 MS Series MS switches offer the following information and configuration options on their local status page: • Connection...
- Page 7 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.
- Page 8 Additionally, the packet capture function found on the local status page has a default filter that is specific to Meraki Cloud Connectivity requirements and will not capture or display anything outside of that filter. This filter is not configurable. This filter is set to capture the following traffic patterns to/from the switch MAC which were determined to be critical to Meraki Cloud connectivity: •...
- Page 9 • Switch ports configuration Provides options for limited configuration changes on switch ports, including enabled/disabled, native VLAN, and link negotiation.
- Page 10 MX Series with Single Dedicated WAN Link MX security appliances with single dedicated WAN links 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.
- Page 11 additional troubleshooting if you are unable to get the unit online (see more in Support Data Bundle (SDB) article). 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 Auto VPN and 802.1x authentication traffic.
- Page 12 MX Series with Multiple Dedicated WAN Links MX security appliances with multiple dedicated WAN links 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.
- Page 13 • 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. ◦ The Download support data function will allow you to download a special file to submit to Meraki support for additional troubleshooting if you are unable to get the unit online (see more in Support Data Bundle (SDB) article).
- Page 14 • Ethernet Allows local changes to the speed/duplex settings of the internet/WAN and LAN ports.
- Page 15 MX Series with Multiple Dedicated SFP WAN Links MX security appliances with dedicated Small-Form Factor Plugable (SFP) WAN links 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.
- Page 16 ◦ Speed test Provides a tool for conducting a speed test from the client to the appliance. ◦ The Download support data function will allow you to download a special file to submit to Meraki support for additional troubleshooting if you are unable to get the unit online (see more in Support Data Bundle (SDB) article).
- Page 17 • Ethernet Allows local changes to the speed/duplex settings of the internet/WAN and LAN ports.
- Page 19 Note: Navigating to http://wired.meraki.com http://mx.meraki.com when directly connected to a LAN port on a spare MX security appliance in active MX warm spare deployments will present the local status page of the primary MX appliance. The spare must be disconnected from the LAN in order to access its local status page.
- Page 20 Connection page from MG 1.11 onwards:...
- Page 21 The connection statistics is moved to Cellular Status Page • Cellular Status...
- Page 22 ◦ Speed test Provides a tool for conducting a speed test from the client to the gateway. The speed test functionality on the local status page is deprecated on all MG cellular gateway devices starting with MG 3.1+ firmware. • Configure Configure section contains options for modifying bearer settings such as Access Point Name (APN), PIN, and authentication.
- Page 23 ◦ Default mode This is the default mode that MG cellular gateway will be configured with out-of-the-box or when a factory reset is performed. In default mode, the standard operation and roles of both ports on the MG cellular gateway are set as LAN ports.
- Page 24 ◦ Download support data function will allow you to download a special file to submit to Meraki support for additional troubleshooting if you are unable to get the unit online (see more in Support Data Bundle (SDB) article). Ethernet Allows local changes to the speed/duplex settings of the LAN ports.
- Page 25 Note: On the MG 1.11 beta, the Connection tab now only presents basic information about the carrier, APN, and signal strength. A new Cellular Status tab presents additional information on the status of the cellular connection. MG41 Cellular Status The cellular statistics is moved to a new "Cellular Status" tab on the MG41.
- Page 27 Configure The MG41 also provides an option to switch the SIM slot. If there is more than one active SIM card, its possible to set the APN settings for the standby SIM card in advance. If the primary SIM card needs special/private APN settings which is different from what the MG41 is currently using, then the override primary SIM setting can be used to override the necessary APN.
- Page 28 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.
- Page 29 Both ap.meraki.com and my.meraki.com are locally-hosted sites useful for configuring an access point (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 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.
- Page 30 After connecting, open a web browser and connect to one of the local status page addresses A list of the administrative tasks which are available to use can be found on the Using the Cisco Meraki Device Local Status Page article.
- Page 31 PPPoE When configuring PPPoE through the local status page, both IPv4 and IPv6 will be negotiated in the same PPP session.
- Page 32 Similarly as to how we can manually set up the IPv4 address of our end of the PPP connection, it’s possible to configure a static link-local IPv6 address to be used in the PPP tunnel. In the unlikely scenario where negotiating both IPv4 and IPv6 in the same PPP session causes the ISP to make the whole session fail, it’s possible to disable IPv6 over PPPoE by using the magic keyword “disabled”...
- Page 33 Refer to the main document: IPv6 Support on MX Security & SD-WAN Platforms [Core Fundamentals]...