New MX 18.101 beta firmware - see below and in the new firmware blog

Kind of a big deal
Kind of a big deal

New MX 18.101 beta firmware - see below and in the new firmware blog

Security appliance firmware versions MX 18.101 changelog

Important notice

  • 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 traffic using TCP port 443 between is allowed through any firewalls that may be deployed upstream of your Meraki appliances.
  • 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.

Legacy products notice

  • When configured for this version, Z1, MX60, MX60W, MX80, and MX90 devices will run MX 14.56.
  • When configured for this version, MX400 and MX600 devices will run MX 16.16.5.

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
  • 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.
  • There is an increased risk of encountering device stability and performance issues on all platforms and across all configurations.


  • Stability and performance improvements
Kind of a big deal
Kind of a big deal

What new features does 18 add?

Getting noticed

I hope we finally get source NAT.

Kind of a big deal
Kind of a big deal

101 new features I'd guess... Sorry, couldn't resist! 😜

Well .. the non-public betas I have been part of the firmware have always been called .99 perhaps .101 is ehhh .. another kind of non-public beta, and someone made this public by mistake ?

Getting noticed

I wonder if this was accidentally released wide vs internal....

Building a reputation

Think I'll wait until there is a little more detail before moving to 18.x 

Head in the Cloud

So far it's running fine - upgraded 3 hours ago. 😉

LinkedIn :::

Like what you see? - Give a Kudo ## Did it answer your question? - Mark it as a Solution 🙂
Kind of a big deal

What new features did you find?

I haven't found anything new so far. Perhaps there are features in there, like for example WPN feature for Access points, buy you still need support to enable them. That would be my guess. Just annoying that the release notes does not mention anything, so we have no idea what to ask for.

I haven't found any new features yet either.

LinkedIn :::

Like what you see? - Give a Kudo ## Did it answer your question? - Mark it as a Solution 🙂

For fun I am upgrading our lab 🙂

Getting noticed

Really hoping there's a fix for the random reboots on the MX67C that's been present in every version of 17.x

Comes here often

Throughput bug on MX64 - V18.101


Just experienced a weird bug that made my net slower. No issues on 17.8, upon upgrade to 18.101, internet speeds seem to cap at 50mbps. Made troubleshooting (made client whitrlisted, changed to a new group profile with higher speed, changed network ports) but to no avail. I thought at first it was a ISP issue, but doing a dashboard throughput test, I'm getting around 100mbps (I'm sure cable is ok). Reverted back to 17.9 and the issue goes away. 

Get notified when there are additional replies to this discussion.
Welcome to the Meraki Community!
To start contributing, simply sign in with your Cisco account. If you don't yet have a Cisco account, you can sign up.