- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
MX HA deployment with two Data Centers and Z3 Teleworker - Sensing link to reach the best MX
We have two data center, North, and South. In each Datacenter, we need to deploy an MX100 like a VPN concentrator for connections from Z3 device for teleworkers. Besides, we want the HA between the datacenters in a hub-and-spoke model.
So, the question is: it is possible, from the perspective of a Z3 teleworker, sensing the best data center to make the VPN connection (like jitter or delay for example)?
Solved! Go to solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Interesting. I know for sure when you setup the spokes you can set up multiple hubs to connect to but I believe it connects to the hubs based on "Hubs will be prioritized in descending order."
If this was helpful click the Kudo button below
If my reply solved your issue, please mark it as a solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Interesting. I know for sure when you setup the spokes you can set up multiple hubs to connect to but I believe it connects to the hubs based on "Hubs will be prioritized in descending order."
If this was helpful click the Kudo button below
If my reply solved your issue, please mark it as a solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
See "Datacenter Redundancy" here: https://documentation.meraki.com/MX-Z/Site-to-site_VPN/Site-to-Site_VPN_Failover_Behavior
As @Adam said, this is not an active-active solution so the Z3 will send traffic to whatever the highest priority hub is unless it becomes unreachable.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
