A new candidate switch firmware version is available. Firmware MS 18.1.2 was just released on 2025-09-17 and has been in this firmware category since 2025-09-17.
Local Status Page connectivity diagnostics enhancements
Layer 2 multicast live tool
Traffic Mirroring: RSPAN & VLAN Based SPAN
Fixed issues
Fixed a bug in Voice VLAN bypass, which caused Voice clients to get authenticated when re-authentication interval was configured
Fixed an issue with MAB authorization that incorrectly placed clients in Critical Auth VLAN when suspend port bounce was enabled
Resolved an issue that sometimes prevented SmartPort Automation rules using LLDP from correctly functioning with PoE+ clients on mGig ports
Resolved a bug that sometimes caused clients to get stuck in an authentication loop after failing to pass an initial RADIUS authentication
General known issues
MS130 and MS150 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.
Clients authenticating via 802.1X with an access policy using hybrid authentication may not correctly log their RADIUS sessions
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.
LACP links may take an extended time to come back up when the Active Member of a stack reboots
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)
Cable tests may report incorrect cable lengths
Ms225 known issues
MS225 switches may infrequently stop forwarding client traffic until the switch is rebooted
Ms35x 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
Switches in stack configurations may experience high CPU utilization in multicast scenarios that may result in network instability
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.
