How to define non-Meraki VPN peers on per-network level?

[Boyan1]

Hi everyone,

I hope the subject says it all. It appears that non-Meraki VPN peers are defined on DO (dashboard organization) level, I will spare my comments and confine my question as asked: each "network" has its own unique needs to interface with non-Meraki VPN peers and that's that. Global peers proliferated to all networks is exactly what I do not want nor need. Each geographic site is defined as a "network" in the dashboard and has its specific VPN peers, which are not universal to every other site.

I know the answer but, again I will spare my comments - define each office as a separate DO but please let that not be the answer?

Thanks
Boyan

[Brash · Accepted solution]

Take a look at the "Peer Availability" heading in the site to site VPN documentation.

Essentially you can use network tags to control which appliances will connect to the peer.

https://documentation.meraki.com/MX/Site-to-site_VPN/Site-to-Site_VPN_Settings#Peer_availability

[Boyan1]

@Brash You're awesome, the best outcome is when one's worst fears don't materialize and tags looks super promising, Thank you, will flag as solved once I test this today