Skip to content

Commit bf14aee

Browse files
authored
Update scenario-bgp-peering-hub.md
updating BGP peering limitation
1 parent 90c7f21 commit bf14aee

File tree

1 file changed

+2
-1
lines changed

1 file changed

+2
-1
lines changed

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

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -41,7 +41,8 @@ The virtual hub router now also exposes the ability to peer with it, thereby exc
4141
* Public ASNs: 8074, 8075, 12076
4242
* Private ASNs: 65515, 65517, 65518, 65519, 65520
4343
* ASNs reserved by IANA: 23456, 64496-64511, 65535-65551
44-
* While the virtual hub router exchanges BGP routes with your NVA and propagates them to your virtual network, it directly facilitates propagating routes from on-premises via the virtual hub hosted gateways (VPN gateway/ExpressRoute gateway/Managed NVA gateways).
44+
* While the virtual hub router exchanges BGP routes with your NVA and propagates them to your virtual network, it directly facilitates propagating routes from on-premises via the virtual hub hosted gateways (VPN gateway/ExpressRoute gateway/Managed NVA gateways).
45+
* BGP peering is only supported with an IP address that is assigned to an interface of the NVA. Peering with loopbacks is not supported.
4546

4647
The virtual hub router has the following limits:
4748

0 commit comments

Comments
 (0)