When you connect multiple VPN devices from the same on-premises network to Azure, you need to create one local network gateway for each VPN device, and one connection from your Azure VPN gateway to each local network gateway.
You need to create multiple S2S VPN connections from your VPN devices to Azure.There are some requirements and constraints: This configuration provides multiple active tunnels from the same Azure VPN gateway to your on-premises devices in the same location. You can use multiple VPN devices from your on-premises network to connect to your Azure VPN gateway, as shown in the following diagram: To provide better availability for your cross premises connections, there are a few options available: For P2S VPN client connections to the gateway, the P2S connections will be disconnected and the users will need to reconnect from the client machines. For unplanned issues, the connection recovery will be longer, about 1 to 3 minutes in the worst case. For planned maintenance, the connectivity should be restored within 10 to 15 seconds. The switch over will cause a brief interruption. For any planned maintenance or unplanned disruption that happens to the active instance, the standby instance would take over (failover) automatically, and resume the S2S VPN or VNet-to-VNet connections.
About VPN gateway redundancyĮvery Azure VPN gateway consists of two instances in an active-standby configuration. This article provides an overview of Highly Available configuration options for your cross-premises and VNet-to-VNet connectivity using Azure VPN gateways.
0 kommentar(er)
