A new candidate appliance firmware version is available. Firmware MX 18.211.0.1 was just released on 2024-05-20 and has been in this firmware category since 2024-05-20.
USB modems with MX/Z series devices running firmware MX 18 or newer will be limited to best effort support and will not be receiving any future firmware fixes or improvements.
Bug fixes
Fixed an MX 18.211 regression that resulted in MX75, MX85, MX95, MX105, MX250, and MX450 appliances that had traffic shaping rules configured with "high" or "low" priority incorrectly dropping traffic being routed between VLANs or AutoVPN.
Legacy products notice
When configured for this version, Z1 devices will run MX 14.56.
When configured for this version, MX400 and MX600 devices will run MX 16.16.9.
When configured for this version, MX64(W), MX65(W), MX84, MX100, and vMX100 devices will run MX 18.107.10.
Known issues status
This list is being reviewed and updated.
Known issues
In rare cases, MX67C, MX68CW, and Z3C appliances may fail to enter into a "Ready" state despite being able to register to a cellular network and obtain an IP address for the modem.
The Non-Meraki VPN service may fail to properly establish IKEv2 tunnels when the MX appliance is acting as the IKEv2 responder and many allowed subnets are configured.
Due to an MX 18.2 regression, the link light LED for WAN2 on MX75 appliances will not light up if WAN2 is the only wired interface in use.
Due to an issue with no known method of reproduction, the IDS and IPS process may unexpectedly restart.
When a WAN failover occurs, Non-Meraki VPN tunnels will persist on the backup, non-primary uplink after a failback to the primary WAN interface if the WAN interface uses IPv6.
Due to an issue still under investigation, MX appliances may experience an unexpected reboot when ThreatGrid is enabled.
MX AutoVPN tunnels fail to generate new connections when the AutoVPN flow has been blocked or filtered unidirectionally by an upstream or intermediary device. This prevents appliances from automatically working around this partially connected state.
MX appliances may experience unstable eBGP connections when 1) the MX appliance is configured in Routed mode and 2) the MX learns a large number of routes from its eBGP neighbor. This may result in eBGP-learned routes being inaccessible.
Welcome to the Meraki Community!
To start contributing, simply sign in with your Cisco account. If you don't yet have a Cisco account, you can sign up.
