Meraki

cmr

Switch firmware versions MS 18.1.3.1 changelog

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 a bug that sometimes caused switches in stack configurations to fail to remove older entries from the MAC forwarding table

Ms150 fixed issues

Resolved an issue that caused some wireless clients to lose connectivity when roaming between access points connected to different members of the same switch stack
Fixed a bug that sometimes caused MS150s to experience transmission errors and lose connectivity until they were rebooted

Ms425 fixed issues

Resolved an issue that caused clients authenticating via 802.1X with an access policy using hybrid authentication to not correctly log their RADIUS sessions
Fixed an issue that caused some switches in stack configurations to experience high CPU utilization in multicast scenarios that sometimes resulted in network instability

General known issues

MS130 and MS150 switches may not properly display IPv6 RA packets in dashboard packet captures
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.
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.
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

Ms150 known issues

Some SFP and QSFP modules may experience intermittent flapping on MS150 switches running MS18 firmware
MS150 switches in stack configurations may lose connectivity while reporting redundant uplinks as blocked. As a workaround, connectivity can be reestablished by disconnecting the impacted redundant uplink.
MS150 switches in stack configurations may incorrectly flood unknown multicast traffic despite the flood unknown multicast setting being disabled
48 port MS150 switches connected to an MX gateway may experience a reduction in uplink throughput if the uplink is connected on ports 41 through 48. As a workaround, connecting to the MX using ports outside of the 41-48 range will pass traffic at expected speeds.

Ms225 known issues

MS225 switches may infrequently stop forwarding client traffic until the switch is rebooted

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

If my answer solves your problem please click Accept as Solution so others can benefit from it.

Mloraditch

All I know is I did a new install this week of an MS150 Stack running Layer 3 and tried to use 18.1.4 and ended up on 17.2.2 and destacked it before it appeared to all work. No idea if I hit new bugs or existing bugs, but support was not super helpful.

If you found this post helpful, please give it Kudos. If my answer solves your problem please click Accept as Solution so others can benefit from it.

KarstenI

Resolved an issue that caused some wireless clients to lose connectivity when roaming between access points connected to different members of the same switch stack

This one hit us quite hard.

If you found this post helpful, please give it Kudos. If my answer solves your problem, please click Accept as Solution so others can benefit from it.

redsector

It´s not more Meraki... It´s getting Cisco´ised. 😭

henleyjj

>I can see "Open" 802.1x authentication mode finally available within Access Policies page, on our lab network, but with only C9300 switches added.

>I can't see much information on all of the release notes on MS18.X regarding "Open" mode. On MS Access Policies tech notes page, it still states "Currently open mode is only available on MS130 and MS150 models"

>Can anyone confirm if the new feature is enabled it's for all MS Family switches (expect MS120/125) and CS family switches?

>We're looking forward to using Open Auth Mode for a upcoming wired NAC rollout, saves us from having to use workaround method during profiling phase.