Skip to content

Commit d8a3d93

Browse files
committed
tweak
1 parent 50521ab commit d8a3d93

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

includes/route-server-limits.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -14,6 +14,6 @@ ms.date: 01/09/2023
1414

1515
<sup>1</sup> If your NVA advertises more routes than the limit, the BGP session will get dropped.
1616

17-
<sup>2</sup> ExpressRoute Private Peering has a [limit](../articles/azure-resource-manager/management/azure-subscription-service-limits.md#expressroute-limits) of 1,000 routes per connection from Virtual Network Gateway towards ExpressRoute circuit. For instance, the total number of routes from all Virtual Network Address Spaces + Route Server Branch-to-branch, must not exceed 1000.
17+
<sup>2</sup> Azure private peering has a [limit](../articles/azure-resource-manager/management/azure-subscription-service-limits.md#expressroute-limits) of 1,000 routes per connection from Virtual Network Gateway towards ExpressRoute circuit. For instance, the total number of routes from VNet address space and Route Server, when **Branch-to-branch** enabled, must not exceed 1,000.
1818

1919
<sup>3</sup> The number of VMs that Azure Route Server can support isn't a hard limit, and it depends on how the Route Server infrastructure is deployed within an Azure Region.

0 commit comments

Comments
 (0)