Hi there, The TLDR version is: We didn't. It remains a problem. The slightly longer explanation is as follows: It turned out that it wasn't just WAN interface drops - the whole appliance was rebooting. The problem seemed to self-resolve once support got involved. For months we'd had these random drops, but support blamed the ISP. It wasn't until we put a switch between the MX and our ISP demarc/router and could prove the MX interface was dropping that support really took any notice. Once that was proved conclusively they started looking into it some more, and the conclusion they came to was that we were overloading the appliance with too many WAN users at once. We were forced to upgrade to an appliance which could handle more users, which we are very unimpressed about. We regularly have between 250-300 active devices at once and support's view was that the 75 was not designed to handle over 200. They wouldn't look into the matter further. I won't throw any individual agent under the bus, but here's what they said: Performance from the last day on this device is still receiving a few performance spikes up to 100 percent CPU Usage, However at about average this device seems to be under about 75 percent on average, however this again could be because this device is over spec'd above the documentation of 200 clients. Due to the recent panics of this device we will continue to monitor moving forward on this device to see if any further reboots occur. Please let me know if you have any further questions. We had an unexpected reboot again on 6th Jan and this is what support said this time: Thanks for calling Cisco Meraki Technical Support today. I investigated your WAN outage and consequent loss of LAN connectivity at around 11 am this morning. I examined back-end logs and can confirm that this was due to the MX unexpectedly rebooting. I am glad to hear that the recovery time for the network was under a minute. I have collected initial data regarding this and will be collecting further data with a view to raising an internal case to investigate the issue further. I will keep the case open and keep you informed of progress. Please let me know in the case comments if you experience this issue again. Thank you for being a valued Meraki customer. I've chased them today for an update - Support are notoriously bad at getting back to you. What they said on the phone was that they could see "an event which caused the device to reboot" but wouldn't be drawn on what that "event" was. So we await the installation of our new MX105 in an HA pair to hopefully solve this problem once and for all. And Meraki - if you're reading this, your support sucks. Do better.
... View more