Skip to content

Commit 169f4dc

Browse files
v-dirichardsv-dirichards
authored
Merge pull request #217063 from duongau/erlimits
ExpressRoute - limits update
2 parents d4d504a + 897d067 commit 169f4dc

File tree

4 files changed

+84
-69
lines changed

4 files changed

+84
-69
lines changed

‎articles/expressroute/TOC.yml

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -95,6 +95,8 @@
9595
href: expressroute-global-reach.md
9696
- name: About ExpressRoute encryption
9797
href: expressroute-about-encryption.md
98+
- name: About ExpressRoute limits
99+
href: ../azure-resource-manager/management/azure-subscription-service-limits.md?toc=/azure/expressroute/toc.json#expressroute-limits
98100
- name: ExpressRoute Traffic Collector
99101
href: traffic-collector.md
100102
- name: Connect Azure to public cloud

‎articles/expressroute/expressroute-about-virtual-network-gateways.md

Lines changed: 5 additions & 34 deletions
Original file line numberDiff line numberDiff line change
@@ -47,49 +47,20 @@ For all other downgrade scenarios, you'll need to delete and recreate the gatewa
4747

4848
The following table shows the features supported across each gateway type.
4949

50-
|**Gateway SKU**|**VPN Gateway and ExpressRoute coexistence**|**FastPath**|**Max Number of Circuit Connections**|
50+
|Gateway SKU|VPN Gateway and ExpressRoute coexistence|FastPath|Max Number of Circuit Connections|
5151
| --- | --- | --- | --- |
5252
|**Standard SKU/ERGw1Az**|Yes|No|4|
5353
|**High Perf SKU/ERGw2Az**|Yes|No|8
5454
|**Ultra Performance SKU/ErGw3Az**|Yes|Yes|16
5555

56-
### <a name="aggthroughput"></a>Estimated performances by gateway SKU
57-
58-
The following table shows the gateway types and the estimated performance scale numbers. 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 the testing conditions.
59-
60-
### Testing conditions
61-
##### **Standard/ERGw1Az** #####
62-
63-
- Traffic sent from on-premises: 1,000 Mega-Bits per second
64-
- Number of routes advertises by the Gateway: 500
65-
- Number of routes learned: 4,000
66-
##### **High Performance/ERGw2Az** #####
67-
68-
- Traffic sent from on-premises: 2,000 Mega-Bits per second
69-
- Number of routes advertises by the Gateway: 500
70-
- Number of routes learned: 9,500
71-
##### **Ultra Performance/ErGw3Az** #####
72-
73-
- Traffic sent from on-premises: 10,000 Mega-Bits per second
74-
- Number of routes advertises by the Gateway: 500
75-
- Number of routes learned: 9,500
76-
77-
This table applies to both the Resource Manager and classic deployment models.
78-
79-
|**Gateway SKU**|**Connections per second**|**Mega-Bits per second**|**Packets per second**|**Supported number of VMs in the Virtual Network**|
80-
| --- | --- | --- | --- | --- |
81-
|**Standard/ERGw1Az**|7,000|1,000|100,000|2,000|
82-
|**High Performance/ERGw2Az**|14,000|2,000|250,000|4,500|
83-
|**Ultra Performance/ErGw3Az**|16,000|10,000|1,000,000|11,000|
84-
85-
> [!IMPORTANT]
86-
> * Application performance depends on multiple factors, such as the 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, control plane and data path capacity of the gateway is reduced.
87-
> * During a maintenance period, you may experience intermittent connectivity issues to private endpoint resources.
88-
8956
>[!NOTE]
9057
> The maximum number of ExpressRoute circuits from the same peering location that can connect to the same virtual network is 4 for all gateways.
9158
>
9259
60+
### <a name="aggthroughput"></a>Estimated performances by gateway SKU
61+
62+
[!INCLUDE [expressroute-gateway-preformance-include](../../includes/expressroute-gateway-performance-include.md)]
63+
9364
## <a name="gwsub"></a>Gateway subnet
9465

9566
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.

‎includes/expressroute-gateway-performance-include.md

Lines changed: 35 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,35 @@
1+
---
2+
title: include file
3+
description: include file
4+
services: expressroute
5+
author: duongau
6+
ms.service: expressroute
7+
ms.topic: include
8+
ms.date: 11/03/2022
9+
ms.author: duau
10+
ms.custom: include file
11+
---
12+
13+
The following table shows the gateway types and the estimated performance scale numbers. 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.
14+
15+
#### Testing conditions
16+
17+
| Gateway SKU | Traffic sent from on-premises | Number of routes advertised by gateway | Number of routes learned by gateway |
18+
|--|--|--|--|
19+
| **Standard/ERGw1Az** | 1 Gbps | 500 | 4000 |
20+
| **High Performance/ERGw2Az** | 2 Gbps | 500 | 9,500 |
21+
| **Ultra Performance/ErGw3Az** | 10 Gbps | 500 | 9,500 |
22+
23+
### Performance results
24+
25+
This table applies to both the Resource Manager and classic deployment models.
26+
27+
|Gateway SKU|Connections per second|Mega-Bits per second|Packets per second|Supported number of VMs in the Virtual Network|
28+
| --- | --- | --- | --- | --- |
29+
|**Standard/ERGw1Az**|7,000|1,000|100,000|2,000|
30+
|**High Performance/ERGw2Az**|14,000|2,000|250,000|4,500|
31+
|**Ultra Performance/ErGw3Az**|16,000|10,000|1,000,000|11,000|
32+
33+
> [!IMPORTANT]
34+
> * 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.
35+
> * During a maintenance period, you may experience intermittent connectivity issues to private endpoint resources.

‎includes/expressroute-limits.md

Lines changed: 42 additions & 35 deletions
Original file line numberDiff line numberDiff line change
@@ -5,47 +5,54 @@
55
author: duongau
66
ms.service: expressroute
77
ms.topic: include
8-
ms.date: 01/12/2021
8+
ms.date: 11/03/2022
99
ms.author: duau
1010
ms.custom: include file
1111
---
12+
1213
| Resource | Limit |
1314
| --- | --- |
14-
| ExpressRoute circuits per subscription |50 |
15-
| ExpressRoute circuits per region per subscription, with Azure Resource Manager |10 |
16-
| Maximum number of IPv4 routes advertised to Azure private peering with ExpressRoute Standard |4,000 |
17-
| Maximum number of IPv4 routes advertised to Azure private peering with ExpressRoute Premium add-on |10,000 |
18-
| Maximum number of IPv6 routes advertised to Azure private peering with ExpressRoute Standard |100 |
19-
| Maximum number of IPv6 routes advertised to Azure private peering with ExpressRoute Premium add-on |100 |
20-
| Maximum number of IPv4 routes advertised from Azure private peering from the VNet address space for an ExpressRoute connection | 1,000 |
21-
| Maximum number of IPv6 routes advertised from Azure private peering from the VNet address space for an ExpressRoute connection | 1,000 |
22-
| Maximum number of IPv4 routes advertised to Microsoft peering with ExpressRoute Standard |200 |
23-
| Maximum number of IPv4 routes advertised to Microsoft peering with ExpressRoute Premium add-on |200 |
24-
| Maximum number of IPv6 routes advertised to Microsoft peering with ExpressRoute Standard |200 |
25-
| Maximum number of IPv6 routes advertised to Microsoft peering with ExpressRoute Premium add-on |200 |
26-
| Maximum number of ExpressRoute circuits linked to the same virtual network in the same peering location |4 |
27-
| Maximum number of ExpressRoute circuits linked to the same virtual network in different peering locations |16 (For more information, see [Gateway SKU](../articles/expressroute/expressroute-about-virtual-network-gateways.md#aggthroughput).) |
28-
| Number of virtual network links allowed per ExpressRoute circuit |See the [Number of virtual networks per ExpressRoute circuit](#vnetpercircuit) table. |
15+
| ExpressRoute circuits per subscription | 50 (Submit a support request to increase limit) |
16+
| ExpressRoute circuits per region per subscription, with Azure Resource Manager | 10 |
17+
| Maximum number of circuits in the same peering location linked to the same virtual network | 4 |
18+
| Maximum number of circuits in different peering locations linked to the same virtual network |Standard / ERGw1Az - 4 </br> High Perf / ERGw2Az - 8 </br> Ultra Performance / ErGw3Az - 16 |
2919
| Maximum number of IPs for ExpressRoute provider circuit with Fastpath | 25,000 |
30-
| Maximum number of IPs for ExpressRoute Direct 10Gbps with Fastpath | 100,000 |
31-
| Maximum number of IPs for ExpressRoute Direct 100Gbps with Fastpath | 200,000 |
32-
33-
34-
#### <a name="vnetpercircuit"></a> Number of virtual networks per ExpressRoute circuit
35-
| **Circuit size** | **Number of virtual network links for Standard** | **Number of virtual network links with Premium add-on** |
36-
| --- | --- | --- |
37-
| 50 Mbps |10 |20 |
38-
| 100 Mbps |10 |25 |
39-
| 200 Mbps |10 |25 |
40-
| 500 Mbps |10 |40 |
41-
| 1 Gbps |10 |50 |
42-
| 2 Gbps |10 |60 |
43-
| 5 Gbps |10 |75 |
44-
| 10 Gbps |10 |100 |
45-
| 40 Gbps* |10 |100 |
46-
| 100 Gbps* |10 |100 |
47-
48-
**100 Gbps ExpressRoute Direct Only*
20+
| Maximum number of IPs for ExpressRoute Direct 10 Gbps with Fastpath | 100,000 |
21+
| Maximum number of IPs for ExpressRoute Direct 100 Gbps with Fastpath | 200,000 |
22+
| Maximum number of flows for ExpressRoute Traffic Collector | 30,000 |
23+
24+
#### Route advertisement limits
25+
26+
| Resource | Local / Standard SKU | Premium SKU |
27+
|--|--|--|
28+
| Maximum number of IPv4 routes advertised to Azure private peering | 4,000 | 10,000 |
29+
| Maximum number of IPv6 routes advertised to Azure private peering | 100 | 100 |
30+
| Maximum number of IPv4 routes advertised from Azure private peering from the VNet address space | 1,000 | 1,000 |
31+
| Maximum number of IPv6 routes advertised from Azure private peering from the VNet address space | 1,000 | 1,000 |
32+
| Maximum number of IPv4 routes advertised to Microsoft peering | 200 | 200 |
33+
| Maximum number of IPv6 routes advertised to Microsoft peering | 200 | 200 |
34+
35+
36+
#### Virtual networks links allowed for each ExpressRoute circuit limit
37+
38+
| Circuit size | Local / Standard SKU | Premium SKU |
39+
| --- | --- |--|
40+
| 50 Mbps | 10 | 20 |
41+
| 100 Mbps | 10 | 25 |
42+
| 200 Mbps | 10 | 25 |
43+
| 500 Mbps | 10| 40 |
44+
| 1 Gbps | 10 | 50 |
45+
| 2 Gbps | 10 | 60 |
46+
| 5 Gbps | 10| 75 |
47+
| 10 Gbps | 10| 100 |
48+
| 40 Gbps* | 10 | 100 |
49+
| 100 Gbps* | 10| 100 |
50+
51+
**100-Gbps ExpressRoute Direct Only*
4952

5053
> [!NOTE]
5154
> Global Reach connections count against the limit of virtual network connections per ExpressRoute Circuit. For example, a 10 Gbps Premium Circuit would allow for 5 Global Reach connections and 95 connections to the ExpressRoute Gateways or 95 Global Reach connections and 5 connections to the ExpressRoute Gateways or any other combination up to the limit of 100 connections for the circuit.
55+
56+
#### ExpressRoute gateway performance limits
57+
58+
[!INCLUDE [expressroute-gateway-preformance-include](expressroute-gateway-performance-include.md)]

0 commit comments

Comments
 (0)