Release notes below for those of you who don't want to try 15.x
Bug fixes
- Fixed several issues that could result in MX and Z appliances being unable to successfully fetch a configuration from the Meraki Dashboard without Meraki Support’s intervention.
- Fixed an issue that resulted in devices connected through a client VPN connection to an MX operating as a VPN concentrator being unable to communicate with other client VPN clients.
- Fixed an issue that resulted in MX appliances incorrectly re-advertising routes that were learned via EBGPbeing to Non-Meraki VPN peers.
Known issues
- 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.
- 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.
- 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.
Other
- Added an Event Log entry for when all of the IP addresses designated for the Client VPN subnet have been exhausted.
