Switch firmware versions MS 15.3 changelog
Alerts
- HTTP proxy is no longer supported on MS 15+. Nodes that use HTTP proxy without any other means to connect to dashboard may fail to connect.
- MS210/225/250/350/355/410/425 series switches may be unable to initialize 1Gbps SFP modules. This is currently scoped to only impact some MA-SFP-1GB-SX modules (present since MS 15.0).
- SecureConnect fails on MS355 series switches
- MS390 ports are not disabled when configured to do so by dashboard
- Moving or re-provisioning an MS390 stack in dashboard can cause at least one member to stay offline until rebooted (this only affects control plane traffic).
- MS390 upgrades from MS 15.2 or later will result in minimal impact to client traffic
Branch additions
- IPv6 static routing support for MS390 series switches
- Additional client analytics added for MS390 series switches
- Meraki authentication support for MS390 series switches
- Alternate Management Interface (AMI) support for MS390 series switches
- UDLD support for MS390 series switches
- Group policy ACL support for MS390 series switches
- IPv6 management interface support
- URL redirect support for MS390 series switches
- UPoE (802.3bt) support for MS390 series switches
- Netflow export for Adaptive Policy
- Critical/failed authentication support for MS390 series switches
- Multi-auth with voice VLAN bypass support
- MAC flap detection support for MS390 series switches
- Named VLAN support for MS120/125/210/225/250/350/355/390 series switches
- Stack power is supported by default for MS390 series switches
- Netflow support for MS390 series switches
Bug fixes
- SFP modules plugged into SFP+ ports will not initialize for the MS210/225/250/410 series switches
- Stability improvements for the MS390 series switches
- ACL configurations are not removed for MS390s when updated to do so. A reboot resolved this (present since MS 14.26)
Known issues
- Group-policy ACL rules that use TCP or UDP port ranges apply for a single port in the range on MS390 series switches
- In rare scenarios, changes made to SVIs may result in connectivity loss for one or more SVIs until reboot (predates MS 12)
- In rare instances, DAI inspection may fail to snoop DHCP transactions on stacks leading to those clients being in a blocked state
- MS390 ports are limited to the lowest link speed since boot if QoS is enabled
- Connecting a stacking cable to a stack that is online may result in a stack member going offline (present since MS 12)
- In rare instances, MS120 series switches may have empty packet captures until they are rebooted
- In rare instances, a stack member may go offline until rebooted (present since MS 12)
- MS390s may experience a brief 1-2 minute control plane outage. The data plane will not experience issues during this time.
- Packet loss is observed when pinging the MS390 management IP
- Links being established on an MS120 can result in neighboring ports to flap (present since MS 11)
- MS390 - Port Up/Down Events Shown Across All Members
- Enabling Combined Power on MS350/355 switches results in events being logged once per minute (present since MS 11)
- Networks containing a large number of switches may encounter issues saving changes on the Switch Settings page
- Stack members are not being marked to update their configuration when changes are made on other members
- mGig switches will have an amber light for all physical ports that do not negotiate to the highest supported speed. Dashboard will continue showing a light green status for all ports above 100Mbps. For example, MS355 switch ports will incorrectly show an amber light for 1G, 2.5G, and 5G, but will show a green light for 10G.
- 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
- 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)
- MS120s switch ports 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)
- 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
- 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
- AMI IP addresses do not send gratuitous ARP packets which can lead to packet loss if the AMI address has aged out in the network
- Meraki authentication does not work with guest VLAN
- Moving or re-provisioning an MS390 stack in dashboard can cause at least one member to stay offline until rebooted (this only affects control plane traffic).
- MS390 ports are not disabled when configured to do so by dashboard
- SecureConnect fails on MS355 series switches
- MS210/225/250/350/355/410/425 series switches may be unable to initialize 1Gbps SFP modules. This is currently scoped to only impact some MA-SFP-1GB-SX modules (present since MS 15.0).
- Ports with an odd-numbered MTU value fail to initialize for MS120/125 series switches (predates MS 11)
- When an SFP module is inserted/removed on MS420/425 series switches, BPDUs can be delayed leading to STP transitions in the network (predates MS 12)
