Security appliance firmware versions MX 15.44.2 changelog
Important notice
- Due to underlying changes present in MX 15, MX appliances will now strictly validate the remote ID parameter during VPN tunnel formation. If you notice issues with non-Meraki VPN tunnel connectivity after upgrading to MX 15 for the first time, please ensure the remote ID configured in the site-to-site VPN page for a given non-Meraki peer matches what is configured as the local ID on that device.
- This firmware version contains important changes required for communications between MX appliances and the AMP and ThreatGrid clouds. Customers will need to upgrade to MX 14.56, MX 15.43, MX 16.7, or higher before the second half of 2022.
Legacy products notice
- When configured for this version, Z1, MX60, MX60W, MX80, and MX90 devices will run MX 14.56.
Bug fixes
- Fixed a rare case where non-Meraki VPN connections would not attempt to form when devices were configured in a warm spare / HA topology.
- Fixed a rare case that could result in a device reboot when ICMP traffic was sent from a ClientVPN client to a non-Meraki VPN peer.
- Further upgrade reliability improvements for MX64(W) and MX65(W) appliances.
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.
- Please note that until certification has been obtained, the Z3C will not be supported on Verizon's network.
- When deployed in warm spare / high availability (HA), MX67C and MX68CW do not support using their cellular connectivity to pass client traffic. In this deployment, the cellular connectivity can only be used for device monitoring or network troubleshooting. This is an expected limitation for these platforms.
- MX67C, MX68CW, and Z3C units must be connected to the Meraki Dashboard initially to retrieve an update to allow for proper use of the integrated cellular connectivity. This is most likely to be an issue when bringing the units online for the very first time.
- On the MX67(C,W) and MX68(W,CW) platforms, when the MX is providing PoE to a connected device, this information will not be reflected on the Meraki Dashboard.
- Once a Z3 has been updated to this firmware version it can only run MX 14.31 or MX15.8 and higher. This is an expected result of updates to the device booting mechanisms and this limitation will not be resolved in future releases.
- The DES encryption algorithm is no longer supported for use in formation of VPN tunnels.
- Creating VPN tunnels using aggressive mode IKE is no longer supported.
- Due to MX 15 regressions, USB cellular connectivity may be less reliable on some modems.
- 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.
If my answer solves your problem please click Accept as Solution so others can benefit from it.
