Apparently the DevNet Learning lab link above is broken. Here's the right one: https://developer.cisco.com/learning/labs/meraki-dashboard-terraform/introduction/
... View more
The hub subnets in this case still need to be advertised to the other MX's which should participate in Auto VPN. The "hub" (spoke) vpn subnets also need to be enabled for the ipsec with non-meraki peers. There are a handful of MX's in the organization which only connect to non-meraki peers in Site A and another site via ipsec tunnel with some identical subnets required between the Auto VPN MX hub and non-meraki ipsec peers. The lack of Auto VPN opt out without also disabling ipsec with non-meraki peers could mean placing MX's in separate organizations is the only solution.
... View more
@Tundra Make sure you have a /29 subnet from each ISP and use an unmanaged L2 switch on each to split the connection to the two MXs. You then have ISP and MX redundancy.
... View more
If you're running MR firmware 29, consider seeing how the network performs with client balancing disabled in the relevant RF profile(s); the way that clients implement 802.11v in particular varies quite widely and can cause issues. I'd also check you're on the latest version of 29 too - currently 29.6.1 (RC)
... View more
