HTTP proxy is no longer supported on MS 15+. Nodes that use HTTP proxy without any other means to connect to dashboard may fail to connect.
While Meraki switches have traditionally relied on UDP port 7351 for cloud communication and TCP ports 80 and 443 for backup communications, with MS 15.1+ we are beginning a transition to using TCP port 443 as the primary means for cloud connectivity. In order to ensure proper connectivity to the Meraki cloud after this upgrade, please ensure that all “Meraki cloud communication” traffic specified in the Help > Firewall Info page is allowed through any firewalls or security filtering devices that may be deployed upstream of your Meraki switches. These requirements have been updated on Nov 2022, so it’s important that you review them.
MS 15.23 is the same as MS 15.22 for all models except the MS130 switch models
New feature highlights
IPv6 management interface support
Ms130 fixed issues
Cable length is reported as double the actual length during cable tests in some scenarios (always present)
Cable tests may fail on non-mGig ports (always present)
If a device is rebooted in quick succession, ports may fail to initialize correctly resulting in packet loss (always present)
Devices may be provided incorrect firmware download URLs resulting in firmware images failing to be downloaded and devices remaining on the prior release
General known issues
Connecting a stacking cable to a stack that is online may result in a stack member going offline (present since MS 12)
Non-MS390 switches move LACP ports to an active forwarding state if configured. This can cause loops when connecting to an MS390 unless the bundles are configured on the MS390 first. All Non-MS390 ports are configured in passive LACP mode so that loops do not occur between Meraki switches (always present)
In rare instances, the port status will fail to update to dashboard until the system reboots (present since MS 14)
Ms120 known issues
Switches in extremely rare instances upon reboot will experience persistent reboots every few minutes, failed firmware upgrade, or fail to reconnect with dashboard (present since MS 11)
Switches may fail to provide PoE power to legacy access points (always present)
Ms125 known issues
The local status page cannot be accessed from the management port (always present)
Ms12x known issues
Ports with an odd-numbered MTU value fail to initialize (predates MS 11)
Switches will never move a RADIUS server's connectivity status to available if it was ever lost resulting in all authentications being placed into the critical auth VLAN (present since MS 14.32)
Ms2xx/35x/4xx known issues
Cross-stack LACP bundles experiencing a switch reboot will cause the remaining online port to experience an outage of up to 30 seconds. The same is seen again when the switch comes back online (present since MS 10)
IPv6 multicast packets tagged for a VLAN may not be filtered correctly resulting in packets egressing into other VLANs (present since MS 14)
IPv6 solicited-node packets bypass port isolation (present since MS 14)
Rebooting a stack member may result in internal stacking packets being sent out into the LAN (present since MS 15)
SVI default route can be incorrectly removed from the routing table after L3 changes are made on dashboard. Removing and re-adding the route is required to resync the stack (present since MS 15)
Stack routing tables can get out of sync when L3 changes are made. Making an additional change to L3 can resolve the sync issue (present since MS 15)
Switch stacks will learn MAC addresses from ports in the STP blocking state which can trigger a constant flood of MAC flaps in the event log
Ms355 known issues
In rare instances, stack ports fail to initialize after an upgrade (always present)
Ms35x known issues
Enabling Combined Power results in events being logged once per minute (present since MS 11)
UPoE does not negotiate over LLDP correctly (always present)
mGig switches will have an amber light for all physical ports that do not negotiate to the highest supported speed. Dashboard will continue showing a light green status for all ports above 100Mbps. For example, MS355 switch ports will incorrectly show an amber light for 1G, 2.5G, and 5G, but will show a green light for 10G.
Ms425 known issues
Large number of SNMP walks to switches in H.A. may destabilize the VRRP connection resulting in flapping (present since MS 15)
Stacks in rare instances will start dropping DHCP traffic on trusted ports while DAI is enabled until rebooted (present since MS 12)
Ms4xx known issues
When an SFP module is inserted/removed, BPDUs can be delayed leading to STP transitions in the network (predates MS 12)
