Alerts This version's IOS image is based on 17.9.3 CCO. Upgrades to this version will result in a full system reload New features 802.1X Control Direction Adaptive Policy ACL hit counter live tool MAC Allow list on access ports Named VLAN Bug fixes CDP fails to populate all port module data (always present) In rare instances, large configurations would fail to apply LLDP information for the IPv4 management VLAN is incorrect (present since CS 16) MAB authentication may intermittently fail on stacks Storm control configurations can fail to be updated on LACP groups after changes are made (present since CS 16) Traffic analytics is missing categorizing some applications (always present) General known issues DHCP options longer than 180 characters may fail to be configured on the device resulting in the configuration being reverted (always present) DHCP server information is incorrectly reported, such as the subnet mask and "Last Seen" fields (always present) Meraki native switches move LACP ports to an active forwarding state if configured. This can cause loops when connecting to an MS390 or other Catalyst switch unless the bundles are configured on the Catalyst side first. All Meraki native ports are configured in passive LACP mode so that loops do not occur between Meraki native switches (always present) Large changes made via the API for a single device may take 10+ minutes to apply ... View more

Interesting new detail on the backend IOS version Alerts This version's IOS image is based on 17.9.3 CCO. Upgrades to this version will result in a full system reload. New features 802.1X Control Direction Adaptive Policy ACL hit counter live tool MAC Allow list on access ports Named VLAN Bug fixes A stack may fully reboot if a stack member crashes (present since CS 15) Cloning a stack member results in configurations for LACP to be missing, requiring the bundles to be reconfigured or the system to be rebooted (present since MS 15.14) IPv6 information is incorrectly presented in CDP/LLDP packets (always present) Modifying storm control can result in the configuration lines not being removed (present since MS 15) Portchannel is going down upon attaching adaptive policy configs and not coming back up after removing adaptive policy configs as well. Ports that are in LACP suspended show as offline instead of errored in dashboard (present since MS 14) RADIUS message NAS IP address is incorrectly 1.1.3.1 (present since CS 15) General known issues "Port Up/Down" events will generate an event log for each stack member DHCP options longer than 180 characters may fail to be configured on the device resulting in the configuration being reverted (always present) DHCP server information is incorrectly reported, such as the subnet mask and "Last Seen" fields (always present) 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) 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) ... View more

New features Added support for configuring VPN exclusion rules for non-Meraki VPN peers. Bug fixes Resolved an issue that could result in drops of cellular connectivity when IPv6 was in use with some cellular networks. Added firmware support for LLDP on LAN ports of MX95, MX105, MX250, and MX450 appliances Performance improvements for MX250 and MX450 appliances Corrected an issue that could result in EBGP peering instability when 1) a large number of AutoVPN routes were being advertised via EBGP and 2) the MX appliance had a reduced WAN MTU. Resolved an issue that resulted in IPv6 traffic being dropped when sent over an IPv4 tunnel formed with a non-Meraki VPN peer. Fixed an MX 18.1XX performance regression on MX64(W) and MX65(W) appliances. Corrected an issue that could result in traffic to non-Meraki VPN peers being incorrectly NAT’ed when the peer was configured using an FQDN as opposed to an IP address. Resolved several rare issues for MX67C, MX68CW, and Z3C appliances that could result in the integrated cellular modem being unable to properly initialize after an upgrade from MX 16 was performed. Fixed an MX 18.1XX regression that could result in MX appliances configured in HA or passthrough mode to lose WAN connectivity. Corrected an issue that could result in a device reboot of MX appliances. Corrected an issue that could result in the global IPv6 address being unreachable to some LAN clients when the IP address was obtained via SLAAC on a cellular uplink. Resolved a rare issue that could result in traffic being misclassified by NBAR. Stability improvements for VMX-L appliances deployed in the Umbrella Cloud. Known issues After making some configuration changes on MX84 appliances, a brief period of packet loss may occur. This will affect all MX84 appliances on all MX firmware versions Due to an MX 15 regression, the management port on MX84 appliances does not provide access to the local status page Client traffic will be dropped by MX65(W), MX67(C,W), and MX68(W,CW) appliances if 1) The client is connected to a LAN port with 802.1X authentication enabled and 2) The VLAN ID of the port is configured to 16, 32, 48, 64, 80, 96, 112, 128, 144, 160, 176, 192, 208, 224, or 240. There is an increased risk of encountering device stability and performance issues on all platforms and across all configurations. ... View more