And Meraki have already (before it appeared on the dashboard) scheduled an upgrade of my network running 15.32, though the others on 15.33 haven't been scheduled...
Important notice
- This is a beta version for the next major MX release. Due to this, we recommend taking additional caution before upgrading production appliances. Where applicable, MX 14 releases will provide a more stable upgrade alternative.
Supported products notice
- Z1, MX60, MX60W, MX80, and MX90 devices are not supported on MX 15 and newer releases.
Bug fixes
- Resolved a rare issue that could result in WMI queries to Active Directory servers being increasingly likely to timeout after 2,147,483,647 events occurred on the Active Directory server.
- Stability improvements for Z3(C), MX250, and MX450 appliances.
- Reverted an MX 15.8 change that caused OSPF interfaces with /30 subnets to be advertised as a “PtP” link. The MX will now advertise these as “Broadcast”, which is consistent with the behavior in all MX 14 versions.
- Resolved an issue that could result in MX appliances providing DHCP leases prior to syncing time correctly. In some cases, this could result in undesired behavior such as a false “DHCP leases exhausted” alert being generated or clients not accepting the initial DHCP offers provided by the MX.
- Fixed an issue that could cause MX appliances to incorrectly send a DHCP NAK rejection to clients attempting to renew their DHCP IP addresses in some cases when the MX was configured to relay those requests to another DHCP server.
- Corrected a rare issue that could result in large file downloads failing while Advanced Malware Protection (AMP) was enabled.
- Fixed an issue that resulted in routes learned via EBGP being incorrectly re-advertised to non-Meraki VPN peers.
- Resolved an issue that could result in MX appliances sending EBGP route update messages with the Next Hop attribute incorrectly set to 192.0.2.1.
- Overall stability improvements.
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.
- MX250 and MX450 appliances will not apply the configured VLAN ID to traffic transmitted on their WAN interfaces if VLANs are also enabled on the LAN for other downstream clients and traffic.
- MI Web App Health is currently not supported, and will report no data, until backend upgrades occur. Once backend update is done, MI Web App Health functionality will resume automatically with no further firmware upgrade needed.
- As a new major version evolving through beta, there are a number of new, uncommon issues that may result in device reboot that we are continuing to investigate and work through. In particular, the Z3(C), MX84, MX100, MX400, MX600, MX250, and MX450 appliances have unresolved issues that we are tracking closely and continuing to investigate and drive towards resolution.
