MS firmware 14.8 released, crash fix and routing fix for non MS390s!

[cmr]

Switch firmware versions MS 14.8 changelog

Alerts

• MS390 stacks of 4 or more may experience instability on this release. For stacks of 4 or more please stay on the current general release to ensure stability and functionality.
• MS390 upgrades from MS 14.7 or later will result in minimal impact to client traffic
• MS390 client authentication may fail closed if RADIUS server passes unsupported AVPs
• Auth session state on RADIUS server may be stale following an MS390 CoA update until RADIUS Accounting is supported
• MS210/225/250 switches cannot forward IPv6 Router Advertisement and Neighbor Solicitation packets when flood unknown multicast is disabled (has always been true)

Bug fixes

• Rare chance non-MS390 switch stack can crash and reboot using multicast routing
• Incoming packets to a non-MS390 switch stack can be routed suboptimally after members of the stack reboot

Known issues

• MS425 stacks directly exposed to large L2 domains can experience stability reduction
• 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 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, Loop Detection, UDLD, MAC Flap Detection
• 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

[Roska]

Thanks for sharing. MS390 stacking instability seems to continue if you happen to have more than 2 members

[cmr]

Upgraded plenty of MS120 and MS220/210/225 switches now and all gone well so far, even a L3 stack.

One odd thing I noticed over the last few upgrades; MS120 switches upgrade about 10 minutes after requesting, whereas MS220/210/225 switches upgrade about 35 minutes after requesting...