Meraki

robdean-pgi

There was at the time but that isnt the case anymore, Is that process just a matter of Unclaiming the MX and then Claiming it in the new network? If so how long does that take a work thru the systems. Is there a guide out there on this somewhere? This remote site is out of the country and has limited on site support so taking it completely offline is a little sensitive.

robdean-pgi

BGP isnt something we have configured currently, How difficult is it to implement? Would it be worth migrating the remote network over to our Organization as it is another MX just not in the same Org.

robdean-pgi

I have a standard Meraki Multi-Hub and Spoke Site-to-Site configuration between all of our sites but one. That site we are using a traditional IPSEC tunnel to connect to it. From the main Hub I am able to connect over the IPSEC tunnel, but from any of the other sites I am unable to reach the remote site. The route shows up in route tables on all sites. Is this a limit to with the auto S2S? Do I need to configured a S2S IPSEC tunnel on all Hubs? any help would be greatly appreciated thanks

Meraki

Community

About robdean-pgi

robdean-pgi

Community Record

Re: Meraki Hub and Spoke S2S connections with a NON-Meraki IPSEC tunnel

Re: Meraki Hub and Spoke S2S connections with a NON-Meraki IPSEC tunnel

Meraki Hub and Spoke S2S connections with a NON-Meraki IPSEC tunnel