Switch firmware versions MS 16.7.1 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.23
New feature highlights
- ACL hit counter
- DHCPv6 and IPv6 RA guard
- Local Status Page Packet Capture
New ms12x feature highlights
Ms130r fixes
- PoE fails to be applied to additional ports after the PoE budget exceeds 120W (always present)
Ms130x fixed issues
- Under heavy load STP BPDUs may no longer be processed resulting in a loop or STP transitions depending on the topology (always present)
General known issues
- 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)
Ms120 known issues
- Switches in extremely rare instances upon reboot will experience persistent reboots every few minutes, failed firmware upgrade, or fail to reconnect with dashboard (present since MS 11)
- Switches may fail to provide PoE power to legacy access points (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.
Ms425 known issues
- Under heavy multicast load, stacks or members of stacks can become unresponsive and go offline in dashboard (present since MS 15)
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.
