Meraki

Mloraditch

New feature highlights

Group Policy ACL on MS130 & MS150
Maximum MAC support in MAC Allowlists
Multi-auth support for Guest, Critical, and failed VLANs with 802.1x limited access mode
Local Status Page connectivity diagnostics enhancements
Layer 2 multicast live tool
Traffic Mirroring: RSPAN & VLAN Based SPAN

General fixed issues

Fixed a bug that caused an incorrect SNMP response of “0” when polling switches for ifInDiscards
Resolved an issue that caused frequent notifications about new DHCP servers that have mismatched VLANs/subnets
Fixed a bug that prevented switches from correctly flushing MAC addresses matched to a switch port after disabling or disconnecting the port
Resolved an issue that prevented some clients from accessing the Local Status Page via 1.1.1.100 and and switch.meraki.com while the network was configured for with Track-by-IP or Cloud Track
Resolved a bug that prevented MS250 and MS350 switches from correctly removing MAC addresses learned via AGGR when LAG ports were disabled

Ms130 fixed issues

Fixed a bug that caused some DNS response packets to be lost when DNS inspection was enabled

Ms150 fixed issues

Resolved an issue that caused degraded uplink speeds when an MS150 was connected to an MX device using an mgig port
Fixed a bug that caused occasional software crashes and reboots on MS150s in stack configurations
Fixed a bug that, in rare cases, could cause member switches in MS150 stacks with cross-stack LAG links to have incorrect MAC-to-port mappings

Ms225 fixed issues

Fixed a bug that occasionally caused software crashes and switch reboots when more than 8 hybrid auth clients were connected to the same port

Ms25x fixed issues

Resolved an issue that caused ports to fail to connect after performing a cable test
Fixed a bug that sometimes caused switches enter a 'port not forwarding' state, where client devices were placed on the guest VLAN, and prevented the switch from sending RADIUS requests until rebooted
Resolved an issue that sometimes caused up to 5 minutes of downtime after powering off the active switch in a MS425 stack

Ms35x fixed issues

Resolved an issue that caused switchport LEDs to show an Amber light while the UI showed that the port is negotiating while using 2.5Gbps mgig ports

Ms425 fixed issues

Fixed a bug that sometimes caused core stack members to encounter MRMP failures, which resulted in the stack or the network going offline

General known issues

Clients authenticating via 802.1X with an access policy using hybrid authentication may not correctly log their RADIUS sessions
Clients that fail to pass RADIUS authentication and are connected to ports using access policies may get stuck in an authentication loop, possibly resulting in a switch reboot
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

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
Switches in stack configurations may experience high CPU utilization in multicast scenarios that may result in network instability

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.

RaphaelL

Does anyone know what this is about ? DNS inspection on MS switches ?

Fixed a bug that caused some DNS response packets to be lost when DNS inspection was enabled

Ryan_Miles

Looking at the internal bug notes seems to be related to high rate of DNS packets hitting a rate limit and being dropped. Support might be able to give more details if you open a case.

And it appears to be MS130 specific.

cmr

The MS425 stack member power down issue is fixed, but the document has it in a MS25X section. Is there an MS25X that is anything other than an MS250???

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

RaphaelL

Upgraded a MS130 to this version and I don't see anywhere this new tool :

Layer 2 multicast live tool

cmr

I tried to upgrade an MS130-8P-I to this version, but it didn't come back on line (orange LED) and then rebooted itself back to 17.2.2, so I rolled back the upgrade for now...