MS 14.24 release candidate available - multiple fixes since 14.22

[cmr]

Switch firmware versions MS 14.24 changelog

Alerts

• MS390 upgrades from MS 14.19 or later will result in minimal impact to client traffic

Branch additions

• SNMP support for MS390s
• RADIUS accounting support for MS390s
• Alternate Management Interface support for MS210/MS225/MS250/MS350/MS355/MS410/MS425/MS450 series switches
• QoS support for MS390s
• CoA support for MS390s
• STP anomaly detection events for non-MS390 series switches
• Adaptive policy support for MS390 series switches
• SecureConnect support for MS210/MS225/MS250/MS350/MS355/MS410/MS425/MS450 series switches

Bug fixes in 14.23

• MS390s - If duplicate DNS IPs were used in an SVI configuration, the MS390 SVI would not be updated
• Access policies configured in hybrid mode with critical auth VLANs defined would fail to authenticate MAB clients
• MS390 port traffic in the UI on occasion can show negative traffic for a client
• MS390 - OSPF area ID could not be configured higher than 65535. This has been resolved so a 32-bit value can be used
• In rare instances, MS390s can lose connectivity to dashboard and require a manual reboot to recover. Data plane traffic is not impacted when this issue is encountered.
• L3 stacks will experience packet loss after an L3 configuration change is made. In order to restore complete stack stability, a reboot may be required.
• MS390 stacks could report incomplete RSTP root information
• MS390s acting as STP root incorrectly reports "00:00:00:00:00:00 (priority 0)" on the switch details page (present since MS 12)
• MS390 ARP tables would show incorrect age values
• The UI for MS390 series switches will report the old STP bridge information until rebooted

Bug fixes in 14.24

• A port's STP configuration could be placed into a disabled state incorrectly if the port was removed from an LACP bundle
• MS390 stability enhancements
• MS120/125 series switches with multi-host authentication would not update hardware with new client information resulting in all traffic being inspected
• Adaptive Policy tag configurations on non-SGT peer interfaces received incorrect port configurations
• MS390 series switches have the option to have uplink client sampling disabled by Support. This is helpful for some deployments (https://documentation.meraki.com/MS/Monitoring_and_Reporting/Last_Seen_Switch_Port_of_Client_Keeps_C...)

Known issues

• Multiple RADIUS timeouts can lead to the switch rebooting
• In rare instances, a stack member may go offline until rebooted (present since MS 12)
• In rare instances, non-390 stack members will reboot (present since 12.29+)
• Due to FEC incompatibility between MS450 and Cisco Fabric Interconnect 6454, 100GbE links do not establish
• MS120s switchports with MAB authentication may randomly deauthenticate clients. In order to resume client authentication on that port, a switch reboot is required (present since MS 12)
• Packet loss is observed when pinging the MS390 management IP
• MS120s on rare occasions will reboot (present since MS 11)
• Stackpower is not enabled on MS390s by default
• Broadcast types of traffic can leak into the Guest VLAN if a port that fails authentication has a Voice VLAN configured, and dashboard has a Guest VLAN defined (present since MS 11)
• Links being established on a MS120 can result in neighboring ports to flap (present since MS 11)
• MS120s with multiple access policies enabled may reboot when port changes are made
• The traceroute live tool fails to run
• The UI will show clients connected to MS390 access ports as being on the "native" VLAN
• Stackings running PIM may encounter synchronization issues which can result in some receivers being unable to receive certain streams
• Enabling Combined Power on MS350/355 switches results in events being logged once per minute (present since MS 11)
• Networks containing a high number of switches may encounter issues saving changes on the Switch Settings page
• MS220 and MS320 switches may randomly reboot in large L2 domains (present since MS 11)
• The list of switches to clone from fails to load when cloning a switch in an organization with a large number of switches and networks
• Switchport tags cannot be removed if they are added after a port profile is attached to the switch
• In rare instances, when a stack reboots, ports may come up as "LACP blocked state", even if LACP is not configured (present since MS 10)
• MS390 stacks on rare occasions will require a manual reboot after the upgrade has completed
• MS390 series switches do not support SM sentry
• MS390 series switches do not support Syslog
• MS390 series switches do not support Meraki authentication
• MS390 series switches do not support URL redirection
• MS390 series switches do not support MAC whitelists
• MS390 series switches do not support loop detection
• MS390 series switches do not support warm spare/VRRP
• MS390 series switches do not support UDLD
• MS390 series switches do not support MAC flap detection
• MS350-24X and MS355 series switches do not negotiate UPoE over LLDP correctly (predates MS 10)
• Rebooting any MS390 stack member via the UI will result in the entire stack rebooting

[DarrenOC]

That one has been around for a while and it’s frustrating 

• The traceroute live tool fails to run

[PhilipDAth]

Could be worse.  You could have an MS390.

[DarrenOC]

@PhilipDAth  🤣😂