While Meraki appliances have traditionally relied on UDP port 7351 for cloud communication and TCP ports 80 and 443 for backup communications, with MX 16 we are beginning a transition to using TCP port 443 as the primary means for cloud connectivity. In order to ensure proper connectivity to the Meraki cloud after this upgrade, please ensure that all “Meraki cloud communication” traffic specified in the Help > Firewall Info page is allowed through any firewalls or security filtering devices that may be deployed upstream of your Meraki appliances. These requirements have been updated on Nov 2022, so it’s important that you review them.
HTTP proxy, which allows default management traffic from MX appliances to be sent through a proxy, is deprecated on MX 16 and higher firmware versions.
The transition to Cisco Talos intelligence for our content filtering services means that some URL categories have changed names, some categories are no longer available, and multiple new categories are now available. Please review your configuration after upgrading to ensure content filtering is effectively tailored to your needs and deployment environment.
Corrected an issue that could result in configuration changes to the Layer 3 firewall rules not taking effect when the MX was configured in passthrough mode and only AnyConnect client VPN was configured.
Resolved an issue that could result in MX100 appliances becoming unresponsive and unable to be recovered with a factory reset after upgrading to MX 17.10.5 or MX 18.1.07 from very old, unsupported firmware versions that reflect as critically out of date from the Organization > Firmware upgrades page in Dashboard.
Legacy products notice
When configured for this version, Z1 and MX80 devices will run MX 14.56.
When configured for this version, MX400 and MX600 devices will run MX 16.16.9.
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
Due to an MX 15 regression, the management port on MX84 appliances does not provide access to the local status page
Due to an MX 17 regression, RADIUS messages that transit across AutoVPN may fail to be routed correctly.