Switch firmware versions MS 15.10 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. Moving or re-provisioning an MS390 stack in dashboard can cause the management plane of at least one member to stay offline until rebooted (present since MS 15.0) MS390 upgrades from MS 15.8 or later will result in minimal impact to client traffic Branch additions STP anomaly detection support for MS390 series switches 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 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 and Encrypted Traffic Analytics (ETA) support for MS390s Bug fixes Port isolation fails to isolate traffic between ports (present since MS 15.9) MA-SFP-1GB-TX links may fail to reconnect after link loss (present since MS 12) In rare instances, static DAI entries can remain in the configuration, even after being removed on dashboard (present always) SNMPv3 fails to start (present since MS 15.1) Switches in an IPv6 only network will experience reboots The Voice VLAN fails to stay authenticated if it is authenticated before the Data VLAN (present since 14.28) Client MAC addresses may fail to be learned on a port right after an access policy is applied (present since 14.28) SVI changes made to stacks may result in incorrect route mappings resulting in packet loss (present since MS 14.31) DAI on stacks incorrectly sync snooping tables when a member reboots resulting in clients being blocked (present since MS 12) MS390 MS390 IPv6 ACLs fail to be configured (present since MS 15.1) MS390 upgrades between MS 15 and another version may result in failure (present since MS 15.1) MS390 clients can get stuck in the Critical VLAN for an extended period of time even after connectivity to the Authenticator has been restored (present since MS 15.1) MS390s in some scenarios will detect the uplink as an access point resulting in loss of connectivity to dashboard (present since MS 15.1) MS390 8-member stack management plane would restart often (present since MS 15.7) MS390 clients may fail to be learned on the critical VLAN in Single-Host mode (present since MS 15.1) MS390s with group policy ACLs configured will take up to 5 minutes to update with a new configuration (present since MS 15) MS390 clients in rare instances are stuck in the unauthorized state when Multi-Host is used (present since MS 15) MS390 ports are not disabled when configured to do so in dashboard (present since MS 15.1) MS390s do not have StackPower enabled by default MS390s are not correctly configuring static route redistribution (always present) Known issues MS390s in rare circumstances will experience a full system restart (preset since MS 14) MS390 management plane in rare instances will restart (present since MS 12) MS390 stack members may experience a full system restart When the MS390 management plane experiences a restart, LACP flapping can occur Stack ports may fail to initialize properly upon reboot. A subsequent reboot of the switch would be needed (present since MS 14) MS390 stacks may send frequent DHCP requests despite having a valid static IP address, which can result in IP flapping (present since MS 14) MS390s that receive incorrectly flooded CDP packets may incorrectly report VLAN mismatches and SFP port information (present since MS 12) 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 Switch stacks will learn MAC addresses from ports in the STP blocking state which can trigger a constant flood of MAC flaps in the event log Packet loss is observed when pinging the MS390 management IP (present since MS 12) In rare instances MAC addresses will fail to be relearned on ports configured with Access Policies. This is currently scoped to only impact MS210/250 models (present since MS 12) Links being established on an MS120 can result in neighboring ports to flap (present since MS 11) MS120 series switches in extremely rare instances will experience reboots every few minutes (present since MS 11) MS390 "Port Up/Down" events will be 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 may experience delays in updating their configuration for up to an hour after a config change (present since MS 9) In rare instances, RADIUS accounting sessions may not be removed after a client disconnects with an EAPoL logoff message (present since MS 11) 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. In rare circumstances, MS390 series switches may disconnect from dashboard until rebooted. Data plane traffic is not impacted unless RADIUS authentication is used (present since MS 14.28) Cable tests run on 100Mbps connections may return the wrong information (predates MS 9) 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 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) 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 the management plane of at least one member to stay offline until rebooted (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) MS350/450 series switches in a stack configuration will lose dashboard connectivity if a "Deny Any Any" ACL is added without having higher "Allow" rules in place for dashboard connectivity (predates MS 12) Rebooting an MS390 switch in a stack via the UI will result in the entire stack rebooting
... View more