A new candidate appliance firmware version is available. Firmware MX 19.1.8.1 was just released on 2025-06-13 and has been in this firmware category since 2025-06-13.
As of MX 19.1, Cisco Meraki will no longer support USB-based Cellular Failover on the MX and Z platforms.
Legacy products notice
When configured for this version, Z1 devices will run MX 14.56.
When configured for this version, MX64(W), MX65(W), MX84, MX100, and vMX100 devices will run MX 18.107.13.
Executive summary
This is a small hotfix release for MX 19.1.8 that addresses a possible device reboot when content filtering is in use.
Customers already running on MX 19.1.8 without using content filtering can skip this release. There are no other changes present.
Bug fixes - general fixes
Resolved an issue that could result in an unexpected device reboot when content filtering was enabled and MX appliances lost connectivity to the TALOS URL service.
Known issues status
This list is being reviewed and updated.
Known issues
During the upgrade process, MX appliances upgrading from version prior to MX 19 may experience a failure to properly classify traffic. This issue will be resolved once the appliance has completed the upgrade to MX 19. (MX-36307)
Due to an issue under investigation, MX appliances may incorrectly route traffic destined to subnets learned through eBGP over a Non-Meraki VPN connection. (MX-34803)
Due to an issue under investigation, making certain configuration changes to WAN interfaces (such as disabling or enabling an interface) can cause the IDPS process to fail. This issue may also cause high device utilization. The issue can be worked around by rebooting the MX appliance or disabling and then re-enabling IDPS. (MX-34504)
When failover is configured between non-Meraki VPN tunnels, the Route Table page on Dashboard may incorrectly show the route for the primary VPN tunnel is inactive. (MX-36316)
During the upgrade process, MX appliances upgrading from versions prior to MX 19 will experience a failure to connect to non-Meraki VPN peers if any VPN peer names contain a space. This issue will be resolved once the appliance has completed the upgrade to MX 19. (MX-36312)
Welcome to the Meraki Community!
To start contributing, simply sign in with your Cisco ID. If you don't yet have a Cisco ID, you can sign up.
