You should look closely at the the Release Notes For 14.46....    There is a known issue with the MX67 and MX68 platform that is causing this kind of behaviour.    I am told it is fixed in this upcoming release and so far it appears to be fixed.         FYI,   I have bricked over a dozen MX68CW the same way. ... View more

I understand the path Meraki is taking to "Simplify" the experience,   but to dumb down things to the point that only a reboot or a Support call is the only solution is not the answer.     For items such as VPN tunnel creation and reset,   having 100's of VPN connections and not have the ability to just drop one VPN and reestablish is a serious shortcoming.       It is obvious shortcoming for an Enterprise solution.   Yes,  we have dual Meraki's in our Datacenters in Warm Spare configuration,   that isn't the point.  As end users we need the ability to do some of the basic management of the VPN tunnels without a reboot of an appliance failover for every remote VPN in the process.   Just my two cents,  and by the way.   If Meraki's is listening the ability to get ACCURATE information about he code level your Meraki is running would be helpful in the dashboard as well.   Right now it shows the level that you hope the device is on .   Many time have spoke with Meraki support to find out that firmware is stuck and not upgrading successfully.  Basic stuff guys.             ... View more

Looking at this on a wider view,   there is no way to clear statistics on a network without creating a new network and moving the appliance.   Sometimes you just want a fresh look.  As a Enterprise Administrator the ability to do this would be helpful.   Thanks   ... View more

What code release will this enhancement come out.   ... View more

I have put in a feature request for exactly that item.     As far as I know there is no way to know when the secondary WAN link goes down.    There other issue is the ability to know when the Secondary Link is acting as the active link.   We use cellular extenders on the MX65W to plug into the Secondary WAN port,  our odd work around has been to monitor the traffic on WAN2 via SNMP and if it exceeds a threshold we have a notification sent from our SNMP Collector.   I know a long way to get to a solution but it seems to work.   THanks   ... View more

Also it is my understanding that the MX does a number of checks before it fails a WAN Interface and goes to cellular.    This for sure can take some time  up to 5 minutes or so.    One key factor is the ability to communicate with a designated IP for example Google's DNS  8.8.8.8,  but also the Meraki Cloud etc.   I don't know all of the specific checks that the MX Performs before it fails over but I would like to hear from a Meraki Engineer what they are.   Thanks PK ... View more