@paulreveco - sorry to hear! Can you please send an email to our community team at community-help@meraki.net - we will get your badge sorted! ... View more

We have done some packet captures. The source interface of the radius requests was the WAN interface, not the L3 vlan interface. ... View more

Very interesting... We also have a similar issue. We are adding an MX 67 on our spokes that goes over AutoVPN to our DC and it only happened a few times in the beginning, but now with every migration of adding an MX 67 to a spoke for SD-WAN, we need to reboot our MX.  We are also connecting to a Fritzbox and most of the time it is the 7590. We just passed the 100 mark for migrations, but our issue is with the CAP WAP traffic of Cisco AP's that do not want to show up on WLC (Flex Connect) and the only option at the moment to fix this is to reboot MX then it is fixed.  We do have an open case with Meraki and they have no clue why it is, but we can see that the UDP port is changed when it comes back to the spoke. I am going to check the firmware of the Fritzbox and see if this is related.  ... View more

Maybe it can help you:     https://documentation.meraki.com/MX/Site-to-site_VPN/Tag-Based_IPsec_VPN_Failover ... View more

Yes. Then you can only reach local vlans or the internet (wan default route) ... View more

I can't think of an easy way of doing this.   You could write a script and use this API call to search for ports with high CRC error rates. https://developer.cisco.com/meraki/api-v1/#!get-device-switch-ports-statuses  ... View more