Skip to content

Commit 3a82c95

Browse files
committed
removed foot note
1 parent 364b060 commit 3a82c95

File tree

1 file changed

+2
-6
lines changed

1 file changed

+2
-6
lines changed

includes/route-server-limits.md

Lines changed: 2 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -8,10 +8,6 @@ ms.date: 07/26/2022
88
| Resource | Limit |
99
|----------|-------|
1010
| Number of BGP peers supported | 8 |
11-
| Number of routes each BGP peer can advertise to Azure Route Server <sup>1</sup> | 1000 |
11+
| Number of routes each BGP peer can advertise to Azure Route Server | 1000 |
1212
| Number of routes that Azure Route Server can advertise to ExpressRoute or VPN gateway | 200 |
13-
| Number of VMs in the virtual network (including peered virtual networks) that Azure Route Server can support <sup>2</sup> | 2000 |
14-
15-
<sup>1</sup> If your NVA advertises more routes than the limit, the BGP session will get dropped. In the event BGP session is dropped between the gateway and Azure Route Server, you'll lose connectivity from your on-premises network to Azure.
16-
17-
<sup>2</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.
13+
| Number of VMs in the virtual network (including peered virtual networks) that Azure Route Server can support | 2000 |

0 commit comments

Comments
 (0)