Switch firmware versions MS 14.20 changelog
Alerts
- Upgrades from MS 14.20 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
- MS390s that had a voice VLAN on access ports in a link aggregation would lose the port's VLAN configuration and default to VLAN 1 after a reboot
- L3 switches with a DHCP relay configured could sporadically drop DHCP Offers (present since 12.11)
Known issues
- In rare instances, a stack member may go offline until rebooted (present since MS 12)
- 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.
- OSPF fails to form adjacencies when more than 164 SVIs are configured on a switch
- 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)
- Client connection tool show "NaN%" values between an MR and upstream MS
- MS120s on rare occasions will reboot (present since MS 11)
- MS355 stacks upon reboot have a chance that the uplink port will go into STP blocking state (predates MS 12)
- 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
- 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)
- The UI for MS390s may incorrectly aggregate ethernet ports when SFP ports were selected
- MS120s with multiple access policies enabled may reboot when port changes are made
- MS390 port traffic in the UI on occasion can show negative traffic for a client
- 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
- 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)
- 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 IPv6 connectivity to dashboard
- 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
- MS390 upgrades from 14.20 or later will result in minimal impact to client traffic
