Skip to content

Commit 080eb69

Browse files
authored
Update scenario-bgp-peering-hub.md
1 parent c8b5a8b commit 080eb69

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -48,7 +48,7 @@ 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 |
51+
| Number of BGP peers | A maximum of 8 BGP peers can be connected to a single Virtual WAN Hub |
5252

5353
* 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.
5454
* Currently we only support 4,000 routes from the NVA to the virtual hub.

0 commit comments

Comments
 (0)