Skip to content

Commit b43b424

Browse files
authored
Update vpn-gateway-highlyavailable.md
1 parent f50a055 commit b43b424

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/vpn-gateway/vpn-gateway-highlyavailable.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -62,7 +62,7 @@ Here you create and set up the Azure VPN gateway in an active-active configurati
6262

6363
All gateways and tunnels are active from the Azure side, so the traffic is spread among all 4 tunnels simultaneously, although each TCP or UDP flow will again follow the same tunnel or path from the Azure side. Even though by spreading the traffic, you may see slightly better throughput over the IPsec tunnels, the primary goal of this configuration is for high availability. And due to the statistical nature of the spreading, it's difficult to provide the measurement on how different application traffic conditions will affect the aggregate throughput.
6464

65-
This topology requires two local network gateways and two connections to support the pair of on-premises VPN devices, and BGP is required to allow the two connections to the same on-premises network. These requirements are the same as the [above](#activeactiveonprem).
65+
This topology requires two local network gateways and two connections to support the pair of on-premises VPN devices, and BGP is required to allow simultaneous connectivity on the two connections to the same on-premises network. These requirements are the same as the [above](#activeactiveonprem).
6666

6767
## Highly Available VNet-to-VNet
6868

0 commit comments

Comments
 (0)