Cisco Meraki Local Status Page: MS Switches
MS Switches LSP Overview
This article covers the features, configuration options, and access methods available on the Cisco Meraki Local Status Page (LSP) for MS switches. It outlines how to use the LSP for monitoring connectivity, adjusting network settings, troubleshooting, and managing various configuration options. By default on MS devices running 17+ firmware, the LSP uses the username of "admin" and the password is the serial number/Cloud ID of the device, older firmware uses the username as the serial number without a password.
Accessing the Local Status Page
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:
- 1.1.1.100
In order to access this address, configure a device with the following IP settings, and then browse to the IP in a web browser.
IP address: 1.1.1.99
Subnet mask: 255.255.255.0
DNS 1.1.1.100
MS Series (includes CS Catalyst Meraki-Managed mode Pre-IOS XE) 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.
MS switches offer the following information and configuration options on their local status page:
- Connection
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.
- 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).
- The packet capture option will assist with troubleshooting Meraki Cloud connectivity. Additionally, there is a packet capture tool found here that will assist with troubleshooting Meraki Cloud connectivity on a switch uplink.
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. HTTP proxy is no longer supported on MS 15+ firmware. Nodes that use HTTP proxy without any other means to connect to dashboard may fail to connect. Starting in MS17+, MS devices will now support HTTP CONNECT proxy.
Note: The local status page packet capture requires a minimum firmware version of MS16 and is only supported on a single physical port. At this time, this is not supported for MS390/Catalyst switches.
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:
- ARP,
- DHCP (UDP 67/68)
- DNS (TCP/UDP 53)
- ICMP (type 0, 3 and 8)
- UDP 7351
- HTTPS (TCP 443)
- LLDP
- Switch port 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.
