Doesn't include some MS390 fixes in 14.x
Alerts
- MS210/225/250 switches cannot forward IPv6 Router Advertisement and Neighbor Solicitation packets when flood unknown multicast is disabled (has always been true)
- MS390 upgrades from MS 12.31 or earlier will trigger a full system reload
- 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
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, RADIUS CoA
Bug fixes
- MS425 stacks directly exposed to large L2 domains can experience stability reduction
- Non-MS390 switches can manifest packet loss for routed traffic after making a L3 config change
Known issues
- Routing to a particular next-hop can fail under specific conditions for non-MS390 switch stacks
- 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, QoS, Power Supply State, PoE power status/usage, 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
If my answer solves your problem please click Accept as Solution so others can benefit from it.
