15.42 Has gone Release Candidate and is being pushed
FYI, I've had no issues with 15.x, but it appears they are now pushing it out. Got notices for several clients to get pushed from 14.53 to 15.42 over the next month.
Added support for establishing non-Meraki VPN tunnels using IKEv2
Added support for configuring source-based default routes
Local breakout of SaaS applications to use public Internet links instead of Auto VPN tunnels. L3 breakout policies are available with all license tiers. Smart application breakouts are available with the Secure SD-WAN Plus license.
Legacy products notice
When configured for this version, Z1, MX60, MX60W, MX80, and MX90 devices will run MX 14.55.
Bug fixes
Stability improvements to Z3(C) 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.
Some stability-impacting issues present in MX 14.19 that affect a small population of MX250 and MX450 devices still exist.
Some stability-impacting issues present in MX 14 that affect a small population of MX67(C,W) and MX68(W,CW) appliances still exist.
Some stability-impacting issues present in MX 14 that affect a small population of Z3(C) appliances still exist.
Please note that until certification has been obtained, the Z3C will not be supported on Verizon's network.
World-wide device SKUs of the MX67C, MX68CW, and Z3C units cannot be deployed in North America and North America device SKUs of the MX67C, MX68CW, and Z3C units cannot be deployed outside of North America.
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.
Due to issues still under investigation, Z3(C) appliances are more likely to experience a device reboot when the wireless functionality is being utilized.
Due to an MX 15 regression, the management port on MX84 appliances does not provide access to the local status page.
Does that mean I just won't be able to see the status? Or will I not be able to configure the IP address and ethernet settings on an MX84 via the management port?
@Malarkey_MX I don’t have an MX84 to confirm with but I believe it means you’ll get nothing if you connect to the Management port. The MX84 will behave like other MXs where you connect to one of the internal IP addresses (i.e. often the ones configured as VLAN gateways) to get the local status pages.
