Skip to content

Commit 9a108e6

Browse files
authored
Update scenario-bgp-peering-hub.md
updating limitation
1 parent d9eaae9 commit 9a108e6

File tree

1 file changed

+0
-1
lines changed

1 file changed

+0
-1
lines changed

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

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -61,7 +61,6 @@ The virtual hub router now also exposes the ability to peer with it, thereby exc
6161

6262
* When configuring BGP peering with the hub, you'll see two IP addresses. Peering with both these addresses is required. Not peering with both addresses can cause routing issues. The same routes must be advertised to both of these addresses. Advertising different routes will cause routing issues.
6363

64-
* The next hop IP address on the routes being advertised from the NVA to the virtual HUB route server has to be the same as the IP address of the NVA, the IP address configured on the BGP peer. Having a different IP address advertised as next hop IS NOT supported for Virtual WAN at the moment.
6564
## BGP peering scenarios
6665

6766
This section describes scenarios where BGP peering feature can be utilized to configure routing.

0 commit comments

Comments
 (0)