Merge pull request #285008 from duongau/ergateway

Jill Grant · web-flow · commit 1ac9c429943a · 2024-09-10T20:36:02.000-06:00
ExpressRoute - About gateway (reorganizing article)
diff --git a/articles/expressroute/expressroute-about-virtual-network-gateways.md b/articles/expressroute/expressroute-about-virtual-network-gateways.md
@@ -5,9 +5,9 @@ services: expressroute
 author: duongau
 ms.service: azure-expressroute
 ms.topic: conceptual
-ms.date: 03/18/2024
+ms.date: 08/19/2024
 ms.author: duau
-ms.custom: ignite-2023
+ms.custom: references_regions
 ---
 
 # About ExpressRoute virtual network gateways
@@ -28,43 +28,16 @@ Each virtual network can have only one virtual network gateway per gateway type.
 
 [!INCLUDE [expressroute-gwsku-include](../../includes/expressroute-gwsku-include.md)]
 
-If you want to upgrade your gateway to a higher capacity gateway SKU, you can use the `Resize-AzVirtualNetworkGateway` PowerShell cmdlet or perform the upgrade directly in the ExpressRoute virtual network gateway configuration page in the Azure portal. The following upgrades are supported:
+If you want to upgrade your gateway to a higher capacity gateway SKU, you can use the Seamless Gateway Migration tool in either Azure portal or PowerShell. The following upgrades are supported:
 
-- Standard to High Performance
-- Standard to Ultra Performance
-- High Performance to Ultra Performance
-- ErGw1Az to ErGw2Az
-- ErGw1Az to ErGw3Az
-- ErGw2Az to ErGw3Az
-- Default to Standard
+- Non-Az enabled SKU on Basic IP to Non Az enabled SKU on Standard IP.
+- Non-Az enabled SKU on Basic IP to Az-enabled SKU on Standard IP.
+- Non-Az enabled SKU on Standard IP to Az-enabled SKU on Standard IP.
 
-Additionally, you can downgrade the virtual network gateway SKU. The following downgrades are supported:
-- High Performance to Standard
-- ErGw2Az to ErGw1Az
+For more information, see [Migrate to an availability zone-enabled gateway](expressroute-howto-gateway-migration-powershell.md).
 
 For all other downgrade scenarios, you need to delete and recreate the gateway. Recreating a gateway incurs downtime.
 
-## Virtual network gateway limitations and performance
-
-### <a name="gatewayfeaturesupport"></a>Feature support by gateway SKU
-
-The following table shows the features supported across each gateway types and max number of ExpressRoute circuit connections supported by each gateway SKU.
-
-| Gateway SKU | VPN Gateway and ExpressRoute coexistence | FastPath | Max Number of Circuit Connections |
-|--|--|--|--|
-| **Standard SKU/ERGw1Az** | Yes | No | 4 |
-| **High Perf SKU/ERGw2Az** | Yes | No | 8 |
-| **Ultra Performance SKU/ErGw3Az** | Yes | Yes | 16 |
-| **ErGwScale (Preview)** | Yes | Yes - minimum 10 of scale units | 4 - minimum 1 of scale unit<br>8 - minimum of 2 scale units<br>16 - minimum of 10 scale units |
-
->[!NOTE]
-> The maximum number of ExpressRoute circuits from the same peering location that can connect to the same virtual network is 4 for all gateways.
->
-
-### <a name="aggthroughput"></a>Estimated performances by gateway SKU
-
-[!INCLUDE [expressroute-gateway-preformance-include](../../includes/expressroute-gateway-performance-include.md)]
-
 ## <a name="gwsub"></a>Gateway subnet
 
 Before you create an ExpressRoute gateway, you must create a gateway subnet. The gateway subnet contains the IP addresses that the virtual network gateway VMs and services use. When you create your virtual network gateway, gateway VMs are deployed to the gateway subnet and configured with the required ExpressRoute gateway settings. Never deploy anything else into the gateway subnet. The gateway subnet must be named 'GatewaySubnet' to work properly. Naming the gateway subnet 'GatewaySubnet' lets Azure know to deploy the virtual network gateway VMs and services into this subnet.
@@ -86,6 +59,27 @@ Add-AzVirtualNetworkSubnetConfig -Name 'GatewaySubnet' -AddressPrefix 10.0.3.0/2
 
 [!INCLUDE [vpn-gateway-no-nsg](../../includes/vpn-gateway-no-nsg-include.md)]
 
+## Virtual network gateway limitations and performance
+
+### <a name="gatewayfeaturesupport"></a>Feature support by gateway SKU
+
+The following table shows the features supported across each gateway types and max number of ExpressRoute circuit connections supported by each gateway SKU.
+
+| Gateway SKU | VPN Gateway and ExpressRoute coexistence | FastPath | Max Number of Circuit Connections |
+|--|--|--|--|
+| **Standard SKU/ERGw1Az** | Yes | No | 4 |
+| **High Perf SKU/ERGw2Az** | Yes | No | 8 |
+| **Ultra Performance SKU/ErGw3Az** | Yes | Yes | 16 |
+| **ErGwScale (Preview)** | Yes | Yes - minimum 10 of scale units | 4 - minimum 1 of scale unit<br>8 - minimum of 2 scale units<br>16 - minimum of 10 scale units |
+
+>[!NOTE]
+> The maximum number of ExpressRoute circuits from the same peering location that can connect to the same virtual network is 4 for all gateways.
+>
+
+### <a name="aggthroughput"></a>Estimated performances by gateway SKU
+
+[!INCLUDE [expressroute-gateway-preformance-include](../../includes/expressroute-gateway-performance-include.md)]
+
 ### <a name="zrgw"></a>Zone-redundant gateway SKUs
 
 You can also deploy ExpressRoute gateways in Azure Availability Zones. This configuration physically and logically separates them into different Availability Zones, protecting your on-premises network connectivity to Azure from zone-level failures. 
@@ -97,57 +91,12 @@ Zone-redundant gateways use specific new gateway SKUs for ExpressRoute gateway.
 * ErGw1AZ
 * ErGw2AZ
 * ErGw3AZ
+* ErGwScale (Preview)
 
 The new gateway SKUs also support other deployment options to best match your needs. When creating a virtual network gateway using the new gateway SKUs, you can deploy the gateway in a specific zone. This type of gateway is referred to as a zonal gateway. When you deploy a zonal gateway, all the instances of the gateway are deployed in the same Availability Zone.
 
 To learn about migrating an ExpressRoute gateway, see [Gateway migration](gateway-migration.md).
 
-## VNet to VNet and VNet to Virtual WAN connectivity
-
-By default, VNet to VNet and VNet to Virtual WAN connectivity is disabled through an ExpressRoute circuit for all gateway SKUs. To enable this connectivity, you must configure the ExpressRoute virtual network gateway to allow this traffic. For more information, see guidance about [virtual network connectivity over ExpressRoute](virtual-network-connectivity-guidance.md). To enabled this traffic, see [Enable VNet to VNet or VNet to Virtual WAN connectivity through ExpressRoute](expressroute-howto-add-gateway-portal-resource-manager.md#enable-or-disable-vnet-to-vnet-or-vnet-to-virtual-wan-traffic-through-expressroute).
-
-## <a name="fastpath"></a>FastPath
-
-ExpressRoute virtual network gateway is designed to exchange network routes and route network traffic. FastPath is designed to improve the data path performance between your on-premises network and your virtual network. When enabled, FastPath sends network traffic directly to virtual machines in the virtual network, bypassing the gateway.
-
-For more information about FastPath, including limitations and requirements, see [About FastPath](about-fastpath.md).
-
-## Connectivity to private endpoints
-
-The ExpressRoute virtual network gateway facilitates connectivity to private endpoints deployed in the same virtual network as the virtual network gateway and across virtual network peers. 
-
-> [!IMPORTANT]
-> * Throughput and control plane capacity may be half compared to connectivity to non-private-endpoint resources.
-> * During a maintenance period, you may experience intermittent connectivity issues to private endpoint resources.
-> * Customers need to ensure their on-premises configuration, including router & firewall settings are correctly setup to ensure that packets for the IP 5-tuple transits via a single next hop (Microsoft Enterprise Edge router - MSEE) unless there is a maintenance event. If a customer's on-premises firewall or router configuration is causing the same IP 5-tuple to frequently switch next hops, then the customer will experience connectivity issues.
-
-### Private endpoint connectivity and planned maintenance events
-
-Private endpoint connectivity is stateful. When a connection to a private endpoint gets established over ExpressRoute private peering, inbound and outbound connections get routed through one of the backend instances of the gateway infrastructure. During a maintenance event, backend instances of the virtual network gateway infrastructure are rebooted one at a time, which could lead to intermittent connectivity issues.
-
-To avoid or minimize connectivity issues with private endpoints during maintenance activities, we recommend setting the TCP time-out value to fall between 15-30 seconds on your on-premises applications. Test and configure the optimal value based on your application requirements.
-
-## Route Server
-
-The creation or deletion of an Azure Route Server from a virtual network that has a Virtual Network Gateway (either ExpressRoute or VPN) might cause downtime until the operation is completed.
-
-## <a name="resources"></a>REST APIs and PowerShell cmdlets
-
-For more technical resources and specific syntax requirements when using REST APIs and PowerShell cmdlets for virtual network gateway configurations, see the following pages:
-
-| **Classic** | **Resource Manager** |
-| --- | --- |
-| [PowerShell](/powershell/module/servicemanagement/azure) |[PowerShell](/powershell/module/az.network#networking) |
-| [REST API](/previous-versions/azure/reference/jj154113(v=azure.100)) |[REST API](/rest/api/virtual-network/) |
-
-## VNet-to-VNet connectivity
-
-By default, connectivity between virtual networks is enabled when you link multiple virtual networks to the same ExpressRoute circuit. Microsoft recommends not using your ExpressRoute circuit for communication between virtual networks. Instead, we recommend you to use [virtual network peering](../virtual-network/virtual-network-peering-overview.md). For more information about why VNet-to-VNet connectivity isn't recommended over ExpressRoute, see [connectivity between virtual networks over ExpressRoute](virtual-network-connectivity-guidance.md).
-
-### Virtual network peering
-
-A virtual network with an ExpressRoute gateway can have virtual network peering with up to 500 other virtual networks. Virtual network peering without an ExpressRoute gateway might have a higher peering limitation.
-
 ## ExpressRoute scalable gateway (Preview)
 
 The ErGwScale virtual network gateway SKU enables you to achieve 40-Gbps connectivity to VMs and Private Endpoints in the virtual network. This SKU allows you to set a minimum and maximum scale unit for the virtual network gateway infrastructure, which auto scales based on the active bandwidth or flow count. You can also set a fixed scale unit to maintain a constant connectivity at a desired bandwidth value.
@@ -159,6 +108,7 @@ ErGwScale supports both zonal and zonal-redundant deployments in Azure availabil
 ErGwScale is available in preview in the following regions:
 
 * Australia East
+* Brazil South
 * Canada Central
 * East US
 * East Asia
@@ -171,6 +121,7 @@ ErGwScale is available in preview in the following regions:
 * Sweden Central
 * UAE North
 * UK South
+* West US 2
 * West US 3
 
 ### Autoscaling vs. fixed scale unit
@@ -204,7 +155,49 @@ ErGwScale is free of charge during public preview. For information about Express
 | 20 | 20 | 2,000,000 | 140,000 | 30,000 | 2,000,000 |
 | 40 | 40 | 4,000,000 | 280,000 | 50,000 | 4,000,000 |
 
-<sup>1</sup> Maximum VM connections scales differently beyond 10 scale units. The first 10 scale units will provide capacity for 2,000 VMs per scale unit. Scale units 11 and above will provide 1,000 additional VM capacity per scale unit.
+<sup>1</sup> Maximum VM connections scale differently beyond 10 scale units. The first 10 scale units provide capacity for 2,000 VMs per scale unit. Scale units 11 and above provides 1,000 more VM capacity per scale unit.
+
+## VNet to VNet and VNet to Virtual WAN connectivity
+
+By default, VNet to VNet and VNet to Virtual WAN connectivity is disabled through an ExpressRoute circuit for all gateway SKUs. To enable this connectivity, you must configure the ExpressRoute virtual network gateway to allow this traffic. For more information, see guidance about [virtual network connectivity over ExpressRoute](virtual-network-connectivity-guidance.md). To enable this traffic, see [Enable VNet to VNet or VNet to Virtual WAN connectivity through ExpressRoute](expressroute-howto-add-gateway-portal-resource-manager.md#enable-or-disable-vnet-to-vnet-or-vnet-to-virtual-wan-traffic-through-expressroute).
+
+## <a name="fastpath"></a>FastPath
+
+ExpressRoute virtual network gateway is designed to exchange network routes and route network traffic. FastPath is designed to improve the data path performance between your on-premises network and your virtual network. When enabled, FastPath sends network traffic directly to virtual machines in the virtual network, bypassing the gateway.
+
+For more information about FastPath, including limitations, and requirements, see [About FastPath](about-fastpath.md).
+
+## Connectivity to private endpoints
+
+The ExpressRoute virtual network gateway facilitates connectivity to private endpoints deployed in the same virtual network as the virtual network gateway and across virtual network peers. 
+
+> [!IMPORTANT]
+> * The throughput and control plane capacity for connectivity to private endpoint resources may be reduced by half compared to connectivity to non-private-endpoint resources.
+> * During a maintenance period, you may experience intermittent connectivity issues to private endpoint resources.
+> * You need to ensure their on-premises configuration, including router & firewall settings, are correctly set up to ensure that packets for the IP 5-tuple transits uses a single next hop (Microsoft Enterprise Edge router - MSEE) unless there is a maintenance event. If your on-premises firewall or router configuration is causing the same IP 5-tuple to frequently switch next hops, then you will experience connectivity issues.
+
+### Private endpoint connectivity and planned maintenance events
+
+Private endpoint connectivity is stateful. When a connection to a private endpoint gets established over ExpressRoute private peering, inbound, and outbound connections get routed through one of the backend instances of the gateway infrastructure. During a maintenance event, backend instances of the virtual network gateway infrastructure are rebooted one at a time, which could lead to intermittent connectivity issues.
+
+To avoid or minimize connectivity issues with private endpoints during maintenance activities, we recommend setting the TCP time-out value to fall between 15-30 seconds on your on-premises applications. Test and configure the optimal value based on your application requirements.
+
+## <a name="resources"></a>REST APIs and PowerShell cmdlets
+
+For more technical resources and specific syntax requirements when using REST APIs and PowerShell cmdlets for virtual network gateway configurations, see the following pages:
+
+| **Classic** | **Resource Manager** |
+| --- | --- |
+| [PowerShell](/powershell/module/servicemanagement/azure) |[PowerShell](/powershell/module/az.network#networking) |
+| [REST API](/previous-versions/azure/reference/jj154113(v=azure.100)) |[REST API](/rest/api/virtual-network/) |
+
+## VNet-to-VNet connectivity
+
+By default, connectivity between virtual networks is enabled when you link multiple virtual networks to the same ExpressRoute circuit. Microsoft recommends not using your ExpressRoute circuit for communication between virtual networks. Instead, we recommend you to use [virtual network peering](../virtual-network/virtual-network-peering-overview.md). For more information about why VNet-to-VNet connectivity isn't recommended over ExpressRoute, see [connectivity between virtual networks over ExpressRoute](virtual-network-connectivity-guidance.md).
+
+### Virtual network peering
+
+A virtual network with an ExpressRoute gateway can have virtual network peering with up to 500 other virtual networks. Virtual network peering without an ExpressRoute gateway might have a higher peering limitation.
 
 ## Next steps
 
diff --git a/includes/expressroute-gateway-performance-include.md b/includes/expressroute-gateway-performance-include.md
@@ -10,7 +10,7 @@
  ms.custom: include file
 ---
 
-The following tables provides an overview of the different types of gateways, their respective limitations, and their expected performance metrics. These numbers are derived from the following testing conditions and represent the max support limits. Actual performance may vary, depending on how closely traffic replicates these testing conditions.
+The following tables provide an overview of the different types of gateways, their respective limitations, and their expected performance metrics. These numbers are derived from the following testing conditions and represent the max support limits. Actual performance may vary, depending on how closely traffic replicates these testing conditions.
 
 #### Testing conditions
 
@@ -35,7 +35,7 @@ This table applies to both the Azure Resource Manager and classic deployment mod
 | **Ultra Performance/ErGw3Az** | 10,000 | 1,000,000 | 11,000 | 1,000,000 |
 | **ErGwScale (per scale unit)** | 1,000 | 100,000 | 2,000 | 100,000 per scale unit |
 
-<sup>1<sup/> The values in the table are estimates and varies depending on the CPU utilization of the gateway. If the CPU utilization is high and the number of supported VMs gets exceeded, the gateway will start to dropping packets.
+<sup>1<sup/> The values in the table are estimates and vary depending on the CPU utilization of the gateway. If the CPU utilization is high and the number of supported VMs gets exceeded, the gateway will start to drop packets.
 
 > [!IMPORTANT]
 > * Application performance depends on multiple factors, such as end-to-end latency, and the number of traffic flows the application opens. The numbers in the table represent the upper limit that the application can theoretically achieve in an ideal environment. Additionally, Microsoft performs routine host and OS maintenance on the ExpressRoute Virtual Network Gateway, to maintain reliability of the service. During a maintenance period, the control plane and data path capacity of the gateway is reduced.
