@Mikekaleny wrote:
My understanding is that I'll need to use a default static route at the hub MX pass traffic to the core. Is that correct?
Hey @Mikekaleny.,
Not a default, but you will need a static. The way Meraki has implemented OSPF on the MX allows it to _advertise_ AutoVPN learned routers via OSPF, but it cannot _learn_ routes via OSFP. This means that no matter what LSA's the MX has in its LSDB it will never, ever install an OSPF route (I suspect it doesn't even run Dijkstra... But that's just a guess). So to allow your MX to reach networks in the core you need to add a static route (you also add this route into AutoVPN so your spokes can reach the core).
You should avoid using a default route as this will cause inconsistent behavior with the default route on the WAN port used to reach the Meraki cloud.
@Mikekaleny wrote:
My understanding is that I'll need to use a default static route at the hub MX pass traffic to the core. Is that correct?
Hey @Mikekaleny.,
Not a default, but you will need a static. The way Meraki has implemented OSPF on the MX allows it to _advertise_ AutoVPN learned routers via OSPF, but it cannot _learn_ routes via OSFP. This means that no matter what LSA's the MX has in its LSDB it will never, ever install an OSPF route (I suspect it doesn't even run Dijkstra... But that's just a guess). So to allow your MX to reach networks in the core you need to add a static route (you also add this route into AutoVPN so your spokes can reach the core).
You should avoid using a default route as this will cause inconsistent behavior with the default route on the WAN port used to reach the Meraki cloud.
You can configure OSPF in either routed or concentrator mode, but you must have VLANs disabled.
https://documentation.meraki.com/MX/Site-to-site_VPN/Using_OSPF_to_Advertise_Remote_VPN_Subnets
