Meraki Community

Mloraditch · ‎Aug 25 2021

Alerts

MS390 upgrades to this version will experience a full system reload

Branch additions

Syslog support for MS390 series switches
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

L3 stack stability improvements
In very rare circumstances, MS220/320/420 series switches would encounter boot loops
In rare instances, redundant links on stacks can incorrectly stay in a forwarding state if a stack member is rebooted
In rare circumstances, the next hop VLAN is incorrectly modified for existing OSPF SVIs when a new SVI is added which will also participate in OSPF. A reboot will correct this (present since MS 11)
A high amount of constant STP TCNs in a network may result in instability, and in rare instances, switch crashes
Default SGTs are missing from the Adaptive Policy configuration
Deconfiguring Adaptive Policy could result in the switch going offline
IPv6 router advertisements sent by unicast to the link-local address are missed
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)
In rare instances, non-MS390 switches will reboot (present since MS 12)

Known issues

In large layer 2 networks, MS390s may drop ARP packets if there is an excess of 500 ARP packets per second
In rare instances, a switch stack member may reboot
MS390 ports are limited to the lowest link speed since boot if QoS is enabled
In rare instances, non-MS390 switches will reboot (present since MS 12)
MS120s may show PoE usage on the incorrect port
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+)
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
MS390 - Port Up/Down Events Shown Across All Members
Clients connected to a trunk port on the native VLAN will show "native" for the VLAN information rather than the native VLAN ID.
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. Example, MS355 switchports 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
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)
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 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

Mloraditch · ‎Aug 25 2021

Gotten notices that it was pushing to over 50 networks at various revs in the past hour

cmr · ‎Aug 26 2021

We got bitten by this one:

In rare instances, redundant links on stacks can incorrectly stay in a forwarding state if a stack member is rebooted

Fortunately we use a separate physical link for management so it was simple to recover, glad it has been fixed though 😎