Skip to content

Commit c8b5a8b

Browse files
authored
Update scenario-bgp-peering-hub.md
clarify bgp peer limit
1 parent 7f8308f commit c8b5a8b

File tree

1 file changed

+2
-0
lines changed

1 file changed

+2
-0
lines changed

articles/virtual-wan/scenario-bgp-peering-hub.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -48,6 +48,8 @@ The virtual hub router now also exposes the ability to peer with it, thereby exc
4848
| Resource | Limit |
4949
|---|---|
5050
| Number of routes each BGP peer can advertise to the virtual hub.| The hub can only accept a maximum number of 10,000 routes (total) from its connected resources. For example, if a virtual hub has a total of 6000 routes from the connected virtual networks, branches, virtual hubs etc., then when a new BGP peering is configured with an NVA, the NVA can only advertise up to 4000 routes. |
51+
| Number of BGP peers | A maximum of 8 BGP Peers can be connected to a single Virtual WAN Hub |
52+
5153
* Routes from NVA in a virtual network that are more specific than the virtual network address space, when advertised to the virtual hub through BGP aren't propagated further to on-premises.
5254
* Currently we only support 4,000 routes from the NVA to the virtual hub.
5355
* Traffic destined for addresses in the virtual network directly connected to the virtual hub can't be configured to route through the NVA using BGP peering between the hub and NVA. This is because the virtual hub automatically learns about system routes associated with addresses in the spoke virtual network when the spoke virtual network connection is created. These automatically learned system routes are preferred over routes learned by the hub through BGP.

0 commit comments

Comments
 (0)