New MS 15.19 stable release candidate firmware - (edit) MS390 only

[cmr]

And a few MS390 fixes...

Switch firmware versions MS 15.19 changelog

Alerts

• HTTP proxy is no longer supported on MS 15+. Nodes that use HTTP proxy without any other means to connect to dashboard may fail to connect.
• While Meraki switches have traditionally relied on UDP port 7351 for cloud communication and TCP ports 80 and 443 for backup communications, with MS 15.1+ we are beginning a transition to using TCP port 443 as the primary means for cloud connectivity. In order to ensure proper connectivity to the Meraki cloud after this upgrade, please ensure that all “Meraki cloud communication” traffic specified in the Help > Firewall Info page is allowed through any firewalls or security filtering devices that may be deployed upstream of your Meraki switches. These requirements have been updated on Nov 2022, so it’s important that you review them.

Ms390 alerts

• MS390 series switches can only downgrade to MS 12 with an incremental step to MS 14
• Upgrades to this version will result in a full system reload

Ms390 features

• Additional client analytics added
• Alternate Management Interface (AMI) support
• Critical/failed authentication support
• Group policy ACL support
• IPv6 static routing support
• MAC flap detection support
• Meraki authentication support
• Multi-auth with voice VLAN bypass support
• Netflow and Encrypted Traffic Analytics (ETA) support
• STP anomaly detection
• Stack power is supported by default
• UDLD support
• UPoE (802.3bt) support
• URL redirect support

New features

• IPv6 management interface support

General fixes

• AMI IP addresses do not send gratuitous ARP packets which can lead to packet loss if the AMI address has aged out in the network
• Sporadically, SNMP walks will fail by not increasing the OID (present since MS 14.13)

Ms2xx/350/355/4xx fixes

• Stack routing tables can be incorrect after removing an SVI (present since MS 14.32)

Ms390 fixes

• ARP live tool only shows a maximum of 63 entries
• Adaptive policy config fails to be configured when more than 7 ACLs are mapped to a policy (present since MS 15)
• DHCP fixed IP assignments are not removed until the system is rebooted
• Disabled LACP ports do not remain shut down after a reboot (present since MS 15.15)
• In very rare scenarios, the switch's VLAN database may become incompatible after an upgrade requiring a factory reset (present since MS 15.15)
• Management plane may lose connectivity momentarily after changes are made to the storm control percentage
• Management plane may restart after removing L3 interfaces (present since MS 15.17)
• OSPF seeing duplicate neighbor IDs will result in the system becoming unresponsive (present since MS 15)
• Only 255 out of 256 static routes can be configured
• Stack members may not reset their configuration when another member is reset
• Switchports with allowed VLANs character lists greater than 223 characters fail to be configured (always present)
• Traffic statistics may fail to show on dashboard (present since MS 15.15)

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)
• Enabling NAT detection may cause issues with TCP streams resulting in pages failing to load entirely or taking longer than usual to load (present since MS 14)
• Non-MS390 switches move LACP ports to an active forwarding state if configured. This can cause loops when connecting to an MS390 unless the bundles are configured on the MS390 first. All Non-MS390 ports are configured in passive LACP mode so that loops do not occur between Meraki switches (always present)

Ms120 known issues

• In rare instances, switches may return empty packet captures until they are rebooted
• Switches in extremely rare instances will experience reboots every few minutes (present since MS 11)

Ms120/125 known issues

• Ports with an odd-numbered MTU value fail to initialize (predates MS 11)
• Switches will never move a RADIUS server's connectivity status to available if it was ever lost resulting in all authentications being placed into the critical auth VLAN (present since MS 14.32)

Ms125 known issues

• The local status page cannot be accessed from the management port (always present)

Ms2xx/350/355/4xx known issues

• Cross-stack LACP bundles experiencing a switch reboot will cause the remaining online port to experience an outage for up to 30 seconds. The same is seen again when the switch comes back online (present since MS 10)
• Loops can be seen when rebooting a stack member containing a cross-stack lag port (always present)
• 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

Ms350/355 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.

Ms355 known issues

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

Ms390 known issues

• "Port Up/Down" events will generate an event log for each stack member
• Adding additional ports to a port bundle will cause the entire bundle to be reconfigured causing traffic loss (always present)
• Fixed IP assignments are not deconfigured until the system is fully reloaded (present since MS 14.33)
• IGMP snooping enabled will send an IGMP message on every configured VLAN every 125 seconds (always present)
• In very rare instances, the management plane will restart every few minutes and requires a full reboot to self-correct (present since MS 15)
• Loop detection is not supported
• Multiple CoA policies sharing the same IP but using different ports fails to be configured (always present)
• Rebooting a switch in a stack via the UI will result in the entire stack rebooting (always present)
• Receiving incorrectly flooded CDP packets may incorrectly report VLAN mismatches and SFP port information (present since MS 12)
• Warm spare/VRRP is not supported

Ms425 known issues

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

[cmr]

As it contained the SVI fix, we deployed it to a new four switch MS355-48X stack this morning and so far so good.

[Kyle_Smith]

@cmrI apologize for the confusion. MS 15.19 encountered last-minute challenges with the MS1XX/2XX/35X/4XX series switches, so it was not released for those products. Instead of canceling the release entirely, it was decided to move forward with a "split release" due to the important MS390 fixes included. There was a breakdown in communication while the changelog was being written which is why fixes were incorrectly added. This has been corrected and will be reflected in dashboard within a few hours.

MS 15.19 was a "split release" only for the MS390 series switches. This means that if you schedule your network to run MS 15.19 which has MS390s and any other switch, like an MS250, the MS390s will upgrade to 15.19, while the other switch will run MS 15.18.

This has been called out in the changelog alerts as such:

• MS 15.19 is the same as MS 15.18 for the MS1XX/2XX/320/35X/4XX switch models

The SVI fixes are planned to be apart of the next release, MS 15.20, which should be expected in the coming weeks.

Again, I apologize for the confusion this has caused.

[cmr]

[cmr]

@Kyle_Smith thank you for the update.  I see the release notes published on the dashboard have now been updated, but shouldn't the missing fixes now be listed as known issues as they aren't fixed?

[Kyle_Smith · Accepted solution]

You're correct. These changes have been made. This will be reflected in dashboard in a few hours.