A new candidate switch firmware version is available. Firmware MS 18.1.5 was just released on 2026-01-05 and has been in this firmware category since 2026-01-05.
This firmware release only includes updates for MS150 switches. All other MS switches on MS 18.1.5 will run firmware identical to MS 18.1.3.1.
New feature highlights
Group Policy ACL on MS130 & MS150
Maximum MAC support in MAC Allowlists
802.1x limited access mode with pre-auth GPACL
Local Status Page connectivity diagnostics enhancements
Layer 2 multicast live tool
Traffic Mirroring: RSPAN & VLAN Based SPAN
General fixed issues
Fixed an issue that caused some switches to report an "incompatible configuration for attributes: allowed_vlans" error when attempting to aggregate ports
Ms150 fixed issues
Fixed a bug that caused some clients to fail to authenticate and resolve DHCP in voice VLANs
Resolved a bug that caused some MR access points to be incorrectly assigned to the Default profile instead of the preconfigured Access Point profile when initially connected to a switch port that used Smartport Automation
Fixed a bug that caused MS150 switches to incorrectly advertise 60-watt PoE++ on all ports. PoE++ is only available on mGig ports; ports 17-24 on MS150 24MP-4X switches, and ports 33-48 on MS150 48MP-4x switches.
Fixed a bug that caused some MS150 switches in stack configurations to experience a software crash following a stack member reboot, resulting in a multicast storm and possible interruption of connectivity until the stack was been rebooted
General known issues
MS130 and MS150 switches may not properly display IPv6 RA packets in dashboard packet captures
In rare circumstances switches may experience uplink instability when IPv6 link-local addresses are enabled. If this issue is encountered it can be resolved by enabling IPv6 RA Guard to block ICMPv6 neighbor discovery messages.
Ms120 known issues
Switches may fail to provide PoE power to legacy access points (always present)
Cable tests may report incorrect cable lengths
Ms130 known issues
MS130X mGig ports may fail to establish a link when both sides are forced to 100 Mbps full-duplex. If either side of the connection uses auto-negotiation the link will be established normally
Switches may incorrectly remove or update SGT tags when no policy or VLAN mapping is defined. Until a firmware fix is available, correct SGT tags can be preserved by defining a policy for the SGT group in Adaptive Policies, and binding the SGT group to a VLAN using VLAN profiles.
Ms150 known issues
MS150 switches using cross-stack LACP may place a port into a discarding state after a stack member reboot, with the affected port failing to transmit LACPDUs until the LAG group is recreated.
Some clients may experience reduced upload speeds while connected to an MS150 switch that is connected to an MX68 gateway
In rare cirumstances, MS150 switches in stack configurations may experience unicast traffic floods that result in degraded network performance
A rebooting switch stack member may not correctly learn the default gateway MAC address for some VLANs, resulting in packet loss for clients on those VLANs
When a stacking cable is disconnected from MS150 switches in stack configurations the disconnected port will incorrectly continue to be marked as connected while the still-connected stacking port will incorrectly be marked as disconnected
MS150 switches may intermittently negotiate USB-C Ethernet adapters at 10 Mbps half-duplex instead of the expected speed for the switchport, requiring a physical reseat to correct the issue.
Ms350x known issues
Switches may experience an unexpected reboot (present since MS 15)
Ms355 known issues
Switches in stack configuration may experience some ports failing to reconnect after a firmware upgrade
Ms410 known issues
Some MS410 switches may encounter alerts for fan failures that will eventually self-resolve
Ms425 known issues
In rare circumstances MS425 switches may encounter a software crash that results in a reboot
In rare circumstances MS425 switches in stack configurations may encounter a software crash that results. in a reboot
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.
