A new candidate switch firmware version is available. Firmware MS 15.20 was just released on 2023-02-17 and has been in this firmware category since 2023-02-17.
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.
Ms390 alerts
MS390 series switches can only downgrade to MS 12 with an incremental step to MS 14
Stacks may fail to complete an upgrade to this version and will revert back to the starting version. If this happens, splitting the stack and upgrading individually is required (present since MS 15.15)
Upgrades to this version will result in a full system reload
Ms390 features
Additional client analytics added
Alternate Management Interface (AMI) support
Critical/failed authentication support
Group policy ACL support
IPv6 static routing support
MAC flap detection support
Meraki authentication support
Multi-auth with voice VLAN bypass support
Netflow and Encrypted Traffic Analytics (ETA) support
STP anomaly detection
Stack power is supported by default
UDLD support
UPoE (802.3bt) support
URL redirect support
New features
IPv6 management interface support
General fixes
AMI IP addresses do not send gratuitous ARP packets which can lead to packet loss if the AMI address has aged out in the network (always present)
NAT detection incorrectly shows IPv4 addresses as hexadecimal instead of dotted decimal notation (present since MS 15)
Ports will fail to correctly revert to the previously configured VLAN when disabling SecurePort. A reboot or port VLAN change corrects this (present since MS 15)
Sporadically, SNMP walks will fail by not increasing the OID (present since MS 14.13)
Ms2xx/35x/4xx fixes
Clients may fail to be relearned by the MAC table after going into sleep mode and waking back up (present since MS 15.15)
Stack routing tables can be incorrect after removing an SVI (present since MS 14.32)
Ms390 fixes
Bundling port(s) that have a voice VLAN configured results in the LACP bundle failing to be configured (present since MS 15.14)
Changing the OSPF router ID will cause the system to go offline (present since MS 15.19)
STP event logs are not being logged (always present)
Stacks will drop DHCP relay ACK packets after modifications are made to the DHCP allowed/blocked policy (present since MS 14.32)
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)
Enabling NAT detection may cause issues with TCP streams resulting in pages failing to load entirely or taking longer than usual to load (present since MS 14)
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)
Ms120 known issues
In rare instances, switches may return empty packet captures until they are rebooted
Switches in extremely rare instances will experience reboots every few minutes (present since MS 11)
Ms120/125 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)
Ms125 known issues
The local status page cannot be accessed from the management port (always present)
Ms2xx/350/355/4xx known issues
Cross-stack LACP bundles experiencing a switch reboot will cause the remaining online port to experience an outage for up to 30 seconds. The same is seen again when the switch comes back online (present since MS 10)
Loops can be seen when rebooting a stack member containing a cross-stack lag port (always present)
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
Ms350/355 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.
Ms355 known issues
In rare instances, stack ports fail to initialize after an upgrade (always present)
Ms390 known issues
"Port Up/Down" events will generate an event log for each stack member
Adding additional ports to a port bundle will cause the entire bundle to be reconfigured causing traffic loss (always present)
Changing the OSPF router ID requires a system restart to become active (always present)
Cloning a stack member results in configurations for LACP to be missing, requiring the bundles to be reconfigured or the system to be rebooted (present since MS 15.14)
IGMP snooping enabled will send an IGMP message on every configured VLAN every 125 seconds (always present)
In very rare instances, the management plane will restart every few minutes and requires a full reboot to self-correct (present since MS 15)
Large stacks may experience intermittent management plane loss resulting in config fetch delays (always present)
Loop detection is not supported
Multiple CoA policies sharing the same IP but using different ports fails to be configured (always present)
Rebooting a switch in a stack via the UI will result in the entire stack rebooting (always present)
Receiving incorrectly flooded CDP packets may incorrectly report VLAN mismatches and SFP port information (present since MS 12)
Stacks may fail to complete an upgrade to this version and will revert back to the starting version. If this happens, splitting the stack and upgrading individually is required (present since MS 15.15)
Warm spare/VRRP is not supported
Ms425 known issues
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)
Welcome to the Meraki Community!
To start contributing, simply sign in with your Cisco account. If you don't yet have a Cisco account, you can sign up.
