Site-to-Site VPN (Non Meraki Peer) using secondary uplink

CBMontesclaros
Getting noticed

Site-to-Site VPN (Non Meraki Peer) using secondary uplink

Hi Meraki Peeps.

Good day. Would like to know if we have a solution for this scenario.

Primary Uplink will use ISP 1.
Secondary uplink will use ISP 2 and will be used by Site-to-Site VPN (Non Meraki Peers which is AWS).

Is this possible to be configured on the MX device?

We had a same situation but we are also using ISP 2 as the primary uplink. However, when I shifted to ISP 1 as the primary uplink, we had issues on the S-to-S VPN connection. We want to avoid configuring anything on the non-Meraki peer side (AWS).

2 Replies 2
ww
Kind of a big deal
Kind of a big deal

It uses the primary, ( wan1 or wan2 depending on which you set to primary.)

 

You can work with flow preferences  to send other traffic to other wan interface

https://documentation.meraki.com/MX/Firewall_and_Traffic_Shaping/MX_Load_Balancing_and_Flow_Preferen...

PhilipDAth
Kind of a big deal
Kind of a big deal

You'll get a lot more flexibility if you use something like a VMX-S in AWS.

https://meraki.cisco.com/product/security-sd-wan/virtual-appliances/vmx-small/ 

Get notified when there are additional replies to this discussion.
Welcome to the Meraki Community!
To start contributing, simply sign in with your Cisco account. If you don't yet have a Cisco account, you can sign up.
Labels