You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
description: Learn about Azure ExpressRoute FastPath to send network traffic by bypassing the gateway
4
+
services: expressroute
5
+
author: cherylmc
6
+
7
+
ms.service: expressroute
8
+
ms.topic: conceptual
9
+
ms.date: 12/05/2019
10
+
ms.author: cherylmc
11
+
12
+
---
13
+
# About ExpressRoute FastPath
14
+
15
+
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.
16
+
17
+
## Requirements
18
+
19
+
### Circuits
20
+
21
+
FastPath is available on all ExpressRoute circuits.
22
+
23
+
### Gateways
24
+
25
+
FastPath still requires a virtual network gateway to be created to exchange routes between virtual network and on-premises network. For more information about virtual network gateways and ExpressRoute, see [ExpressRoute virtual network gateways](expressroute-about-virtual-network-gateways.md).
26
+
27
+
The virtual network gateway must be either:
28
+
29
+
* Ultra Performance
30
+
* ErGw3AZ
31
+
32
+
## Supported features
33
+
34
+
While FastPath supports most configurations, it does not support the following features:
35
+
36
+
* UDR on the gateway subnet: If you apply a UDR to the gateway subnet of your virtual network, the network traffic from your on-premises network will continue to be sent to the virtual network gateway.
37
+
38
+
* VNet Peering: If you have other virtual networks peered with the one that is connected to ExpressRoute, the network traffic from your on-premises network to the other virtual networks (i.e. the so-called "Spoke" VNets) will continue to be sent to the virtual network gateway. The workaround is to connect all the virtual networks to the ExpressRoute circuit directly.
39
+
40
+
* Basic Load Balancer: If you deploy a Basic internal load balancer in your virtual network or the Azure PaaS service you deploy in your virtual network uses a Basic internal load balancer, the network traffic from your on-premises network to the virtual IPs hosted on the Basic load balancer will be sent to the virtual network gateway. The solution is to upgrade the Basic load balancer to a [Standard load balancer](https://docs.microsoft.com/azure/load-balancer/load-balancer-overview).
41
+
42
+
* Private Link: If you connect to a [private endpoint](../private-link/private-link-overview.md) in your virtual network from your on-premises network, the connection will go through the virtual network gateway.
43
+
44
+
## Next steps
45
+
46
+
To enable FastPath, see [Link a virtual network to ExpressRoute](expressroute-howto-linkvnet-arm.md#configure-expressroute-fastpath).
Copy file name to clipboardExpand all lines: articles/expressroute/expressroute-about-virtual-network-gateways.md
+11-15Lines changed: 11 additions & 15 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,11 +8,11 @@ ms.service: expressroute
8
8
ms.topic: conceptual
9
9
ms.date: 10/14/2019
10
10
ms.author: mialdrid
11
-
ms.custom: seodec18
12
11
13
12
---
14
-
# ExpressRoute virtual network gateway and FastPath
15
-
To connect your Azure virtual network and your on-premises network via ExpressRoute, you must create a virtual network gateway first. A virtual network gateway serves two purposes: exchange IP routes between the networks and route network traffic. This article explains gateway types, gateway SKUs and estimated performance by SKU. This article also explains ExpressRoute [FastPath](#fastpath), a feature that enables the network traffic from your on-premises network to bypass the virtual network gateway to improve performance.
13
+
# About ExpressRoute virtual network gateways
14
+
15
+
To connect your Azure virtual network and your on-premises network via ExpressRoute, you must create a virtual network gateway first. A virtual network gateway serves two purposes: exchange IP routes between the networks and route network traffic. This article explains gateway types, gateway SKUs, and estimated performance by SKU. This article also explains ExpressRoute [FastPath](#fastpath), a feature that enables the network traffic from your on-premises network to bypass the virtual network gateway to improve performance.
16
16
17
17
## Gateway types
18
18
@@ -74,16 +74,11 @@ Zone-redundant gateways use specific new gateway SKUs for ExpressRoute gateway.
74
74
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 also have the option to deploy the gateway in a specific zone. This 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.
75
75
76
76
## <aname="fastpath"></a>FastPath
77
-
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.
78
77
79
-
FastPath is available on all ExpressRoute circuits. It still requires a virtual network gateway to be created to exchange routes between virtual network and on-premises network. The virtual network gateway must be either Ultra Performance or ErGw3AZ.
78
+
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.
79
+
80
+
For more information about FastPath, including limitations and requirements, see [About FastPath](about-fastpath.md).
80
81
81
-
FastPath doesn't support the following features:
82
-
* UDR on Gateway subnet: if you apply a UDR to the Gateway subnet of your virtual network the network traffic from your on-premises network will continue to be sent to the virtual network gateway.
83
-
* VNet Peering: if you have other virtual networks peered with the one that is connected to ExpressRoute the network traffic from your on-premises network to the other virtual networks (i.e. the so-called "Spoke" VNets) will continue to be sent to the virtual network gateway. The workaround is to connect all the virtual networks to the ExpressRoute circuit directly.
84
-
* Basic Load Balancer: if you deploy a Basic internal load balancer in your virtual network or the Azure PaaS service you deploy in your virtual network uses a Basic internal load balancer, the network traffic from your on-premises network to the virtual IPs hosted on the Basic load balancer will be sent to the virtual network gateway. The solution is to upgrade the Basic load balancer to a [Standard load balancer](https://docs.microsoft.com/azure/load-balancer/load-balancer-overview).
85
-
* Private Link: if you connect to a [private endpoint](../private-link/private-link-overview.md) in your virtual network from your on-premises network the connection will go through the virtual network gateway.
86
-
87
82
## <aname="resources"></a>REST APIs and PowerShell cmdlets
88
83
For additional technical resources and specific syntax requirements when using REST APIs and PowerShell cmdlets for virtual network gateway configurations, see the following pages:
89
84
@@ -93,10 +88,11 @@ For additional technical resources and specific syntax requirements when using R
See [ExpressRoute Overview](expressroute-introduction.md) for more information about available connection configurations.
97
91
98
-
See [Create a virtual network gateway for ExpressRoute](expressroute-howto-add-gateway-resource-manager.md) for more information about creating ExpressRoute gateways.
92
+
For more information about available connection configurations, see [ExpressRoute Overview](expressroute-introduction.md).
93
+
94
+
For more information about creating ExpressRoute gateways, see [Create a virtual network gateway for ExpressRoute](expressroute-howto-add-gateway-resource-manager.md).
99
95
100
-
See [Create a zone-redundant virtual network gateway](../../articles/vpn-gateway/create-zone-redundant-vnet-gateway.md) for more information about configuring zone-redundant gateways.
96
+
For more information about configuring zone-redundant gateways, see [Create a zone-redundant virtual network gateway](../../articles/vpn-gateway/create-zone-redundant-vnet-gateway.md).
101
97
102
-
See [Link virtual network to ExpressRoute](expressroute-howto-linkvnet-arm.md) for more information about how to enable FastPath.
98
+
For more information about FastPath, see [About FastPath](about-fastpath.md).
0 commit comments