New MS 14.22 release candidate firmware - MS120 boot issue and MS355 reboot issue fixed. Yay!

[cmr]

Switch firmware versions MS 14.22 changelog

Alerts

• MS390 upgrades from MS 14.19 or later will result in minimal impact to client traffic
• 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

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

• MS120-48 series switches with a high number of active ports with access policies configured may not successfully boot, requiring a configuration change and a factory reset
• MS355 stacks upon reboot have a chance that the uplink port will go into STP blocking state (predates MS 12)

Known issues

• In rare instances, a stack member may go offline until rebooted (present since MS 12)
• The traceroute live tool fails to run
• Stackings running PIM may encounter synchronization issues which can result in some receivers being unable to receive certain streams
• 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)

Specific model known issues below

• In rare instances, MS390s can lose connectivity to dashboard and require a manual reboot to recover. Control plane traffic is not impacted when this issue is encountered.
• 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)
• MS120s on rare occasions will reboot (present since MS 11)
• 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.
• Stackpower is not enabled on MS390s by default
• 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 UI for MS390 series switches will report the old STP bridge information until rebooted
• MS390 port traffic in the UI on occasion can show negative traffic for a client
• The UI will show clients connected to MS390 access ports as being on the "native" VLAN
• MS390s acting as STP root incorrectly reports "00:00:00:00:00:00 (priority 0)" on the switch details page (present since MS 12)
• Enabling Combined Power on MS350/355 switches results in events being logged once per minute (present since MS 11)
• MS220 and MS320 switches may randomly reboot in large L2 domains (present since MS 11)
• 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

[KarstenI]

I wish the release-notes had a "do not show MS390 stuff"-button. Going through the notes only would take 10 seconds ... 😉

[DarrenOC]

hi @cmr  - that MS355 uplink one you've highlighted red is interesting....