New MS 16.6 stable release candidate - LACP and RADIUS fixes

cmr
Kind of a big deal
Kind of a big deal

New MS 16.6 stable release candidate - LACP and RADIUS fixes

Switch firmware versions MS 16.6 changelog

Ms12x alerts

  • 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 alerts

  • Devices configured for this version will run MS 15.22

General features

  • ACL hit counter
  • DHCPv6 and IPv6 RA guard
  • Local Status Page Packet Capture

Ms12x features

  • DAI support

New features

  • MS Classic Packet Ingress Pipeline Enhancement

General fixes

  • Single host mode clients may fail to be moved to the critical VLAN when the RADIUS server is unreachable
  • Stacks with a large number of LACP bundles (10+) may see ports failing to come up after a member reboot (present since MS 16)

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)

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

Ms355 known issues

  • In rare instances, stack ports fail to initialize after an upgrade (always present)

Ms355/450 known 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 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)
4 Replies 4
RaphaelL
Kind of a big deal
Kind of a big deal

Very intrigued by : 

NEW FEATURES

  • MS Classic Packet Ingress Pipeline Enhancement  🤔
PhilipDAth
Kind of a big deal
Kind of a big deal

Agreed.  What does that mean?

This was removed. It was accidentally added and to demystify this a bit, it's internal jargon pertaining to how switches snoop traffic to send to the CPU. Examples include snooping DNS traffic to determine if you're requesting `switch.meraki.com` for the LSP, snooping ARP packets for DAI, etc.

mplewis1215
New here

We just turned up a pair of 355-24X2's last night running 16.5.  We cannot get any of the SFP+ ports to work - modules aren't even recognized.   The release notes for 16.5 and these for 16.6 list an issue where QSFP ports dont work unless the modules are present at boot time but has anyone seen this behavior with the regular SFP+ ports?

Get notified when there are additional replies to this discussion.