New beta firmware 12.12 released

[cmr]

Only one fix from 12.11 and no known issues resolved:

• Rare condition where packet loss can be generated when routing to a next hop on switch stack

Complete changelog below and I've applied it to a 3 node stack of MS210s to see how it fares.

Switch firmware versions MS 12.12 changelog

Alerts

• MS210/225/250 switches cannot forward IPv6 Router Advertisement and Neighbor Solicitation packets when flood unknown multicast is disabled (has always been true)

Additions

• Support for MS390 Series Switches
• Loop Detection on MS210/225/250/350/355/410/420/425/450 series switches
• MAC Flap Detection on MS210/225/250/350/355/410/420/425/450 series switches
• MS390 Local Status Page identifies ports on other stack members by name instead of MAC address
• Features now supported on MS390: RADIUS Testing

Bug fixes

• Rare condition where packet loss can be generated when routing to a next hop on switch stack

Known issues

• MS390 stack members may not report client-level detail
• MS390 series switches Max MTU is limited to 9198 bytes
• MS390 series switches will not display packet details in the DHCP Servers page
• MS390 series switches do not support the 'next-server' or 'bootfile' parameters in DHCP messages
• Rebooting a single switch in an MS390 stack will reboot the entire stack
• LLDP frames from MS390 series switches will use a single system name instead of the Dashboard given name
• MS390 series switches will not display the advertising router ID for OSPF
• MS390 series switches with OSPF enabled will default to an IP MTU of 1500 bytes on every OSPF enabled interface
• MS390 series switches do not support the multicast routing livetool
• Stacked MS390 series switches do not report traffic/client analytics correctly in all cases
• MS390 series switches do not support tagged traffic bypass for voice on ports with a Multi-Auth access policy
• Dynamic VLAN assignment from a RADIUS server on MS390 series switches must already be an allowed VLAN on the port for it to function
• MS390 series switches may not display link state on links at mGig speeds (2.5G, 5G)
• MS390 series switches do not currently support the following features: VRRP, SM Sentry, Syslog server, SNMP, Traceroute, IPv6 connectivity to dashboard, Meraki Auth, URL Redirection, MAC Whitelisting, RADIUS Accounting, RADIUS CoA, QoS, Power Supply State, PoE power status/usage, Loop Detection, UDLD, MAC Flap Detection
• ARP entry on L3 switch can expire despite still being in use (predates MS 10.x)
• SM Sentry does not support Windows based clients (predates MS 10.x)
• MS425 series switches do not forward frames larger than 9416 bytes (predates MS 10.x)
• MS350-24X and MS355 series switches do not negotiate UPoE over LLDP correctly (predates MS 10.x)

Other

• Various performance and stability improvements

[DarrenOC]

Looks like those MS390’s are struggling a little! Quite a few “Known Issues” listed!

[cmr]

I applied it to the ms220 that was experiencing port speed issues with an MR55 when I tried 12.10 here:

https://community.meraki.com/t5/Switching/Port-speed-issues-with-MS-12-10/m-p/78765

It appears that this is another fix, although not listed.

[ToddB]

And 12.13 has now been released.   Looks like a  MS390 bug fix is the only change.

Switch firmware versions MS 12.13 changelog

Alerts

• MS210/225/250 switches cannot forward IPv6 Router Advertisement and Neighbor Solicitation packets when flood unknown multicast is disabled (has always been true)

Additions

• Support for MS390 Series Switches
• Loop Detection on MS210/225/250/350/355/410/420/425/450 series switches
• MAC Flap Detection on MS210/225/250/350/355/410/420/425/450 series switches
• MS390 Local Status Page identifies ports on other stack members by name instead of MAC address
• Features now supported on MS390: RADIUS Testing

Bug fixes

• MS390 ports do not reflect PoE status in Dashboard

Known issues

• MS390 stack members may not report client-level detail
• MS390 series switches Max MTU is limited to 9198 bytes
• MS390 series switches will not display packet details in the DHCP Servers page
• MS390 series switches do not support the 'next-server' or 'bootfile' parameters in DHCP messages
• Rebooting a single switch in an MS390 stack will reboot the entire stack
• LLDP frames from MS390 series switches will use a single system name instead of the Dashboard given name
• MS390 series switches will not display the advertising router ID for OSPF
• MS390 series switches with OSPF enabled will default to an IP MTU of 1500 bytes on every OSPF enabled interface
• MS390 series switches do not support the multicast routing livetool
• MS390 series switches do not support tagged traffic bypass for voice on ports with a Multi-Auth access policy
• Dynamic VLAN assignment from a RADIUS server on MS390 series switches must already be an allowed VLAN on the port for it to function
• MS390 series switches may not display link state on links at mGig speeds (2.5G, 5G)
• MS390 series switches do not currently support the following features: VRRP, SM Sentry, Syslog server, SNMP, Traceroute, IPv6 connectivity to dashboard, Meraki Auth, URL Redirection, MAC Whitelisting, RADIUS Accounting, RADIUS CoA, QoS, Power Supply State, PoE power status/usage, Loop Detection, UDLD, MAC Flap Detection
• ARP entry on L3 switch can expire despite still being in use (predates MS 10.x)
• SM Sentry does not support Windows based clients (predates MS 10.x)
• MS425 series switches do not forward frames larger than 9416 bytes (predates MS 10.x)
• MS350-24X and MS355 series switches do not negotiate UPoE over LLDP correctly (predates MS 10.x)

Other

• Various performance and stability improvements

[DW2]

Im seeing MS390 stack members may not report client-level detail on the 11.3. Be good if they can fix it as im starting to wish we purchased 9300s.

[sebas]

So when will they fix that ARP issue ?!