New MS 16.7 stable release candidate firmware - combined power, QSFP+ and MS130 fixes
Switch firmware versions MS 16.7 changelog
Ms12x important notes
If DAI is enabled prior to upgrading the network to MS 16, ensure that trusted ports and/or DAI-allow lists are configured prior to upgrading to avoid potential network outages.
Ms420 important notes
Devices configured for this version will run MS 15.22
New ms12x feature highlights
DAI support
New feature highlights
ACL hit counter
DHCPv6 and IPv6 RA guard
Local Status Page Packet Capture
General fixed issues
Client sessions continue being policed by group policies if they are reauthenticated without a group policy (present since MS 14)
In rare instances, devices using PIM routing may encounter a system crash
Stacks with more than 10 LACP bundles may experience LACP ports incorrectly initializing and blocking after a member reboot (present since MS 14)
Ms130 fixed issues
Cable length is reported as double the actual length during cable tests in some scenarios (always present)
Cable tests may fail on non-mGig ports (always present)
If a device is rebooted in quick succession, ports may fail to initialize correctly resulting in packet loss (always present)
Ms210/225/250/425 fixed issues
Factory reset button fails to fully reset the device (preset since MS 16)
Ms355/450 fixed issues
QSFP ports without modules inserted at system boot will fail to initialize and come up until a module is inserted and the system is rebooted (present since MS 16)
Ms35x fixed issues
Enabling combined power results in event logs being generated once per minute (present since MS 11)
General known issues
Connecting a stacking cable to a stack that is online may result in a stack member going offline (present since MS 12)
Switches move LACP ports to an active forwarding state if configured. This can cause loops when connecting to an MS390 or other Catalyst switches unless the bundles are configured on the MS390/Catalyst switches first. All non-catalyst ports are configured in passive LACP mode so that loops do not occur between Meraki switches (always present)
A stack containing more than 10 LACP bundles may encounter a brief network loop when a stack member is rebooted (present since MS 15)
Ms120 known issues
Factory resetting a device can lead to the local status page being unavailable from the LAN port (present since MS 15)
Switches in extremely rare instances will experience reboots every few minutes (present since MS 11)
Switches may fail to provide PoE power to legacy access points (always present)
Ms125 known issues
The local status page cannot be accessed from the management port (always present)
Ms12x known issues
Ports with an odd-numbered MTU value fail to initialize (predates MS 11)
Ms210 known issues
Stack ports have an orange LED instead of green (present since MS 11)
Ms2xx/35x/4xx known issues
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
Ms350x known issues
Switches may experience an unexpected reboot (present since MS 15)
Ms355 known issues
In rare instances, stack ports fail to initialize after an upgrade (always present)
Ms35x known issues
UPoE does not negotiate over LLDP correctly (always present)
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.
Ms4xx known issues
When an SFP module is inserted/removed, BPDUs can be delayed leading to STP transitions in the network (predates MS 12)
If my answer solves your problem please click Accept as Solution so others can benefit from it.
