I've read this blog, and I know that     1.Non-Meraki VPN routes are not advertised to AutoVPN peers. 2.Remote non-Meraki VPN subnets cannot overlap with any existing Dashboard subnets/routes.     Say I have a topogy like this, MX (1.1.1.1/16) ( BRANCH) --> AutoVpn -> MX (HUB) --> Non-Meraki peer (2.2.2.2/16)   According to the docs, If I don't do anything, the branch MX, and the Non-Meraki peer won't have reachability to each other.   But what if I just configure a static route on the branch MX (1.1.1.1/16) pointing to Non-Meraki peer (2.2.2.1/16) with a next hop of the Hub MX, and do the reverse on the Non-Meraki peer?   It looks simpler than the solution suggested in the blog. Will this work or Am I just misunderstanding something here?   Thanks in advance.       ... View more

Hi, I have a few questions about one-arm concentrator mode & Hub and spoke & BGP but couldn't find the answers after reading all the docs I could find.    1.Can I deploy the branch MX as a spoke while setting it at one-arm concentrator mode ?   2.In this doc, https://documentation.meraki.com/MX/Networks_and_Routing/BGP   it says that  A one-armed VPN concentrator will learn routes advertised to it by other AutoVPN peers and re-advertise these IBGP learned routes to EBGP peers. But in Scenario 3: Datacenter Redundancy (DC-DC Failover), it seems that two one-armed concentrator MXs are not learning routes from each other.   So MXs in one-armed concentrator mode will not be AutoVPN peers or iBGP peers?   3.In the same scenario, Will the routes which VPN Spoke MX learned from One-armed Concentrator MX, be treated as AutoVPN Routes or BGP learned Routes?   Thanks in advance!     ... View more