Switch firmware versions MS 16.2 changelog
Alerts
- MS420 devices configured for this version will run MS 15.21.1
General features
- ACL hit counter
- DHCPv6 and IPv6 RA guard
- Local Status Page Packet Capture
Ms12x features
General fixes
- ICMPv6 echo packets destined to FF02::1 are incorrectly dropped (always present)
Ms120 fixes
- DHCP relay fails to relay packets (present since MS 15.14)
Ms2xx/35x/4xx fixes
- Cross-stack LACP groups may fail to fully initialize, resulting in one or more ports staying offline (present since MS 16.1)
- IPv6 packets destined to the switch will not be fragmented and reassembled correctly (always present)
- If the same MAC address is associated with multiple IPs, adding or removing an SVI may lead to an incorrect VLAN ID mapping leading to packet loss on one or more SVIs
Ms450 fixes
- Unplugging 40G/100G SFP modules can result in a system reboot (present since MS 16.1)
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)
- Critical Authentication may incorrectly keep RADIUS server status as unreachable after a failed connection resulting in all subsequent authentication attempts failing (always present)
- In rare instances, the port status will fail to update to dashboard until the system reboots (present since MS 14)
- 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 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
- End devices connected at 100Mbps may fail to re-establish a link after the cable test has been run on the port (present since MS 14)
- IPv6 multicast packets tagged for a VLAN may not be filtered correctly resulting in packets egressing into other VLANs (present since MS 14)
- IPv6 solicited-node packets bypass port isolation (present since MS 14)
- Rebooting a stack member may result in internal stacking packets to be sent out into the LAN (present since MS 15)
- 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
Ms355 known issues
- In rare instances, stack ports fail to initialize after an upgrade (always present)
Ms35x known issues
- Enabling Combined Power results in events being logged once per minute (present since MS 11)
- 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
- Large number of SNMP walks to switches in H.A. may destabilize the VRRP connection resulting in flapping (present since MS 15)
- Stacks in rare instances will start dropping DHCP traffic on trusted ports while DAI is enabled until rebooted (present since MS 12)
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.
