Skip to content

Commit c000e9c

Browse files
authored
Clarify active-active gateway configuration description
Clarified the description of active-active gateway configuration to specify that both VMs process traffic simultaneously.
1 parent 5a57878 commit c000e9c

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

articles/reliability/reliability-virtual-network-gateway.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -136,7 +136,7 @@ Ordinarily, traffic is routed through your virtual network gateway. However, if
136136

137137
You configure the gateway SKU. Each SKU supports a different level of throughput, and a different number of VPN connections. For more information, see [About gateway SKUs](../vpn-gateway/about-gateway-skus.md).
138138

139-
Depending on your high availability requirements, you can configure your gateway as *active-standby*, which means that one gateway VM processes traffic and the other is a standby gateway VM, or as *active-active*, which means that both gateway VMs process traffic. Active-active isn't always possible due to the asymmetric nature of connection flows. For more information, see [Design highly available gateway connectivity for cross-premises and VNet-to-VNet connections](../vpn-gateway/vpn-gateway-highlyavailable.md).
139+
Depending on your high availability requirements, you can configure your gateway as *active-standby*, which means that one gateway VM processes traffic and the other is a standby gateway VM, or as *active-active*, which means that both gateway VMs process traffic at the same time. Active-active isn't always possible due to the asymmetric nature of connection flows. For more information, see [Design highly available gateway connectivity for cross-premises and VNet-to-VNet connections](../vpn-gateway/vpn-gateway-highlyavailable.md).
140140

141141
::: zone-end
142142

0 commit comments

Comments
 (0)