Merge pull request #227041 from cherylmc/throughput-table

Add throughput values

Author: American-Dipper

articles/virtual-wan/virtual-wan-faq.md

@@ -3,7 +3,7 @@ title: 'Azure Virtual WAN FAQ | Microsoft Docs'
 description: See answers to frequently asked questions about Azure Virtual WAN networks, clients, gateways, devices, partners, and connections.
 author: cherylmc
 ms.service: virtual-wan
-ms.topic: conceptual
+ms.topic: faq
 ms.date: 10/13/2022
 ms.author: cherylmc
 # Customer intent: As someone with a networking background, I want to read more details about Virtual WAN in a FAQ format.
@@ -158,7 +158,11 @@ While Virtual WAN VPN supports many algorithms, our recommendation is GCMAES256
 
 Packets per second or PPS is a factor of the total # of packets and the throughput supported per instance. This is best understood with an example. Lets say a 1 scale unit 500-Mbps site-to-site VPN gateway instance is deployed in a virtual WAN hub. Assuming a packet size of 1400, expected PPS for that vpn gateway instance *at a maximum* = [(500 Mbps * 1024 * 1024) /8/1400] ~ 47000.
 
-Virtual WAN has concepts of VPN connection, link connection and tunnels. A single VPN connection consists of link connections. Virtual WAN supports up to 4 link connections in a VPN connection. Each link connection consists of two IPsec tunnels that terminate in two instances of an active-active VPN gateway deployed in a virtual hub. The total number of tunnels that can terminate in a single active instance is 1000, which also implies that throughput for 1 instance will be available aggregated across all the tunnels connecting to that instance. Each tunnel also has certain throughput values. For GCM algorithm, a tunnel can support up to a maximum 1.25 Gbps. In cases of multiple tunnels connected to a lower value scale unit gateway, it's best to evaluate the need per tunnel and plan for a VPN gateway that is an aggregate value for throughput across all tunnels terminating in the VPN instance.
+Virtual WAN has concepts of VPN connection, link connection and tunnels. A single VPN connection consists of link connections. Virtual WAN supports up to 4 link connections in a VPN connection. Each link connection consists of two IPsec tunnels that terminate in two instances of an active-active VPN gateway deployed in a virtual hub. The total number of tunnels that can terminate in a single active instance is 1000, which also implies that throughput for 1 instance will be available aggregated across all the tunnels connecting to that instance. Each tunnel also has certain throughput values. For GCM algorithm, a tunnel can support up to a maximum of 1250 Mbps. In cases of multiple tunnels connected to a lower value scale unit gateway, it's best to evaluate the need per tunnel and plan for a VPN gateway that is an aggregate value for throughput across all tunnels terminating in the VPN instance.
+
+**Values for various scale units supported in Virtual WAN**
+
+[!INCLUDE [values for scale units](../../includes/virtual-wan-tunnels-throuput-instance-include.md)]
 
 ### Which device providers (Virtual WAN partners) are supported?
 
@@ -262,7 +266,6 @@ No. Virtual WAN doesn't require ExpressRoute from each site. Your sites may be c
 
 Network throughput is per service in a virtual WAN hub. In each hub, the VPN aggregate throughput is up to 20 Gbps, the ExpressRoute aggregate throughput is up to 20 Gbps, and the User VPN/point-to-site VPN aggregate throughput is up to 200 Gbps. The router in virtual hub supports up to 50 Gbps for VNet-to-VNet traffic flows and assumes a total of 2000 VM workload across all VNets connected to a single virtual hub.
 
-
 To secure upfront capacity without having to wait for the virtual hub to scale out when more throughput is needed, you can set the minimum capacity or modify as needed. See [About virtual hub settings - hub capacity](hub-settings.md#capacity). For cost implications, see *Routing Infrastructure Unit* cost in the [Azure Virtual WAN Pricing](https://azure.microsoft.com/pricing/details/virtual-wan/) page.
 
 When VPN sites connect into a hub, they do so with connections. Virtual WAN supports up to 1000 connections or 2000 IPsec tunnels per virtual hub. When remote users connect into virtual hub, they connect to the P2S VPN gateway, which supports up to 100,000 users depending on the scale unit(bandwidth) chosen for the P2S VPN gateway in the virtual hub.

includes/virtual-wan-tunnels-throuput-instance-include.md

@@ -0,0 +1,34 @@
+---
+ms.author: cherylmc
+author: cherylmc
+ms.date: 02/10/2023
+ms.service: virtual-wan
+ms.topic: include
+---
+
+|Scale unit| Max throughput per tunnel (Mbps)|Max PPS per tunnel |Max throughput per instance (Mbps) |Max PPS per instance |
+|---|---|---|---|---|
+|1  |500  |47K  |500  |47K  |
+|2  |1000 |94K |1000  |94K  |
+|3  |1500 |140K |1500 |140K |
+|4  |1500 |140K |2000 |187K |
+|5  |1500 |140K |2500 |234K |
+|6  |1500 |140K |3000 |281K |
+|7  |2300 |215K |3500 |328K |
+|8  |2300 |215K |4000 |374K |
+|9  |2300 |215K |4500 |421K |
+|10 |2300 |215K |5000 |468K |
+|11 |2300 |215K |5500 |515K |
+|12 |2300 |215K |6000 |562K |
+|13 |2300 |215K |6500 |609K |
+|14 |2300 |215K |7000 |655K |
+|15 |2300 |215K |7500 |702K |
+|16 |2300 |215K |8000 |749K |
+|17 |2300 |215K |8500 |796K |
+|18 |2300 |215K |9000 |843K |
+|19 |2300 |215K |9500 |889K |
+|20 |2300 |215K |10000 |936K|
+
+>[!NOTE]
+> All numbers are based on GCM algorithm.
+>