Site-to-Site VPN Active/Standby to On-Prem

Soeb 1 Reputation point
2021-05-07T13:12:26.623+00:00

Hello,

We have a requirement where S2S VPN from Azure VPN Gateway to two on-prem sites is required. I know that active/active is possible, but the client has active/standby setup on their end meaning on-prem site A will act as active and site B will only become active should site A fail. The routing on their end is configured to take care of it. I want to know if this scenario is possible with Azure S2S VPN connections and if so any document explaining how we can deploy it.

Azure VPNGW (VNET e.g. 10.0.0.0/16) ---> On-Prem Site A (e.g. 11.1.1.1) -->Active (Local N/W 172.16.0.0/16)
Azure VPNGW (VNET e.g. 10.0.0.0/16) ---> On-Prem Site B (e.g. 12.2.2.2) -->Standby (Local N/W 172.16.0.0/16)

Any suggestions or inputs will be much appreciated.

Thanks
Shoeb

Azure VPN Gateway
Azure VPN Gateway
An Azure service that enables the connection of on-premises networks to Azure through site-to-site virtual private networks.
1,803 questions
0 comments No comments
{count} votes

2 answers

Sort by: Most helpful
  1. msrini-MSFT 9,291 Reputation points Microsoft Employee
    2021-05-07T13:48:44.007+00:00

    Hi,

    Is your site A and site B belongs to same On-Premises ?

    You can still deploy Active-Active Gateways and enable BGP. Then by using AS path you can prefer one path over the other. In that case if the primary BGP goes down, then the traffic is routed via secondary path

    0 comments No comments

  2. Soeb 1 Reputation point
    2021-05-07T14:44:50.903+00:00

    Hi,
    No site A and site B belong to different locations.
    Bgp AS path manipulation on on-prem is fine, Is it possible to manipulate BGP attributes on Azure VPN gateway so that site A tunnel can be primary and site B backup.

    Any other possibilities to achieve this setup.

    Thanks,
    Shoeb


Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.