A new stable switch firmware version is available. Firmware MS 17.2.1 was just released on 2025-03-19 and has been in this firmware category since 2025-03-19.
MS17 introduces a change to the default login credentials for the device local status page, using "admin" as the username, and the device serial number (upper case with dashes) as the password
Ms12x important notes
MS 16 introduced DAI on MS100 series platforms. If you are upgrading to a current release from MS 15 or earlier please ensure trusted ports and/or DAI-allow lists are configured prior to upgrading.
New feature highlights
DOM (Digital Optical Monitoring)
Intelligent Capture
RSPAN and VLAN Based SPAN
SmartPorts
New ms130x feature highlights
Adaptive Policy on MS130X/R models
General fixed issues
All new LAG configurations will block redundant links if the connected device is not configured for LACP. This change fixes an issue where switches would sometimes move LAG ports to an active forwarding state prior to LACP convergence, creating the potential for loops. The change does not apply to existing LAG configurations.
Corrected the Local Status Page to show the 1 Gbps (forced) option, previously mislabeled as 1 Gbps (auto)
Fixed a bug that caused some clients using Hybrid, 802.1X, or MAB Access Policies to fail to authenticate after a switch reboot
Port-bounce CoA commands now correctly cycle PoE ports
Resolved an issue that caused some clients to be incorrectly added to a configured Guest VLAN when authenticated via RADIUS immediately after a switch reboot
Resolved an issue that prevented some MS210 and MS225 devices from correctly releasing MAC addresses from the MAC forwarding table
Resolved an issue that sometimes caused MS350 switches to remove existing L3 SVIs when enabling Auto-stacking
Ms120 fixed issues
Fixed a bug that prevented MS120-48 switches from correctly forwarding multicast traffic on ports 25-48
Resolved a bug that caused Epson POS printers to fail to authenticate when using MAB hybrid auth access policies
Ms12x fixed issues
Fixed an issue that prevented MS120 and MS125 switches from forwarding link-local multicast (224.0.0.x) traffic when 'Flood unknown multicast traffic' was disabled
Ms130 fixed issues
Fixed a bug that caused some MS130-X switches to experience slow upstream when connected directly to an MX device via an mGig port
Ms225 fixed issues
Resolved an issue that caused some MS225-48FP devices to become unresponsive and fail to forward traffic until rebooted
Ms350 fixed issues
Fixed a bug that prevented cable tests from correctly functioning on mGig ports
Ms35x fixed issues
Resolved an issue that caused some MS350-24X and MS355 switches to fail to negotiate 802.3bt UPoE LLDP connections
General known issues
LACP links may take up to two minutes to come back up when the Active Member of a stack reboots
On MS250 and MS350 switches, MAC addresses learned via AGGR are not removed when LAG ports are disabled. Mac addresses will be removed correctly within 5 minutes of reenabling LAG ports.
RADIUS communications may not recover after an initial failure when Critical Auth is enabled
Some switches may encounter an error, "incompatible configuration for attributes: allowed_vlans" when attempting to aggregate ports regardless of allowed VLANs configured in Dashboard
Ms120 known issues
Switches may fail to provide PoE power to legacy access points (always present)
Ms225 known issues
In rare circumstances MS225 switches may encounter a software crash that results in a reboot
Ms250 known issues
In rare circumstances MS250 switches using Multi-Domain Hybrid auth access policies may enter a 'port not forwarding' state, sending clients to the Guest VLAN until the switch is rebooted
Ms355 known issues
When reconnecting a stack cable between MS355-48X2 swithces a stack member may go offline until both switches are rebooted
Ms35x known issues
In rare instances, stack ports fail to initialize after an upgrade (always present)
Incorrect SFP port mappings may disrupt SFP functionality
Switches may experience an unexpected reboot (present since MS 15)
Ms425 known issues
In rare circumstances MS425 switches may encounter a software crash that results in a reboot
MS425s in stack configurations may periodically trigger New DHCP Server alerts that include mismatched VLANs/subnets
Powering off the active switch in a MS425 stack may result in up to 5 minutes of downtime while the stack reconverges
Welcome to the Meraki Community!
To start contributing, simply sign in with your Cisco ID. If you don't yet have a Cisco ID, you can sign up.
