I already mentioned the issue. Workaround: rollback to MX 16 while waiting for their developer to fix it. ... View more

Z3's here and a MX250 Hub.  18.107 caused major issues.  See this ping response!   Pinging 10.59.97.249 with 32 bytes of data: Reply from 10.59.97.249: bytes=32 time=1682ms TTL=60 Reply from 10.59.97.249: bytes=32 time=3423ms TTL=60 Reply from 10.59.97.249: bytes=32 time=3168ms TTL=60 Reply from 10.59.97.249: bytes=32 time=2440ms TTL=60 Request timed out. Reply from 10.59.97.249: bytes=32 time=1823ms TTL=60 Reply from 10.59.97.249: bytes=32 time=2578ms TTL=60 Request timed out. Ping statistics for 10.59.97.249: Packets: Sent = 8, Received = 6, Lost = 2 (25% loss), Approximate round trip times in milli-seconds: Minimum = 1682ms, Maximum = 3423ms, Average = 2519ms   Rolling back to 17.10.2 fixed issue for most, but didn't work on all.  Seems the rollback fails often. ... View more

After ~ 3 hours on the phone with Meraki and sharing the information provided by @IDV , @Raphael, @dgander , @dade80vr  & @dade80vr we have a "bandage" to resolve this until an update to fix it is released.  I was informed that Meraki is aware of the issue and is working on a solution.  No ETA as to when the actual fix will be known.  Meraki also stated that this is only affecting MX84's.  I suspect it may affect other models as well that the setting listed below is available on.   Solution:  Disable Web Cache and reboot router. Security & SD-WAN -> SD-WAN & Traffic Shaping   Unfortunately a reboot is required for the change to take effect.   I hope this helps anyone currently having the issue.     ... View more

Posting if this helps others, upgrading MX units to 18.105 which only have cellular/4G internet (ie, no ethernet internet connectivity) there appears to be a bug which the unit reports on the dashboard as upgraded to 18.105 however the device goes offline for 15 minutes every 2 hours. Meraki support engineer confirmed the device was stuck in a upgrade loop and was actually still running 17.10.2 firmware even though the dashboard says its updated. Telling the MX to reboot via the web dashboard 'fixes' the issue for a few hours before it comes back again. The actual fix is to pull the power out of the MX and reconnect, the hard power off/on appears to force it to update correctly. ... View more