Merge pull request #213968 from cfields475/main

update BGP limit

Author: prmerger-automator[bot]

articles/virtual-wan/about-virtual-hub-routing-preference.md

@@ -1,5 +1,5 @@
 ---
-title: 'Virtual WAN virtual hub routing preference - Preview'
+title: 'Virtual WAN virtual hub routing preference'
 titleSuffix: Azure Virtual WAN
 description: Learn about Virtual WAN Virtual virtual hub routing preference.
 author: cherylmc
@@ -8,16 +8,13 @@ ms.topic: conceptual
 ms.date: 05/31/2022
 ms.author: cherylmc
 ---
-# Virtual hub routing preference (Preview)
+# Virtual hub routing preference
 
 A Virtual WAN virtual hub connects to virtual networks (VNets) and on-premises using connectivity gateways, such as site-to-site (S2S) VPN gateway, ExpressRoute (ER) gateway, point-to-site (P2S) gateway, and SD-WAN Network Virtual Appliance (NVA). The virtual hub router provides central route management and enables advanced routing scenarios using route propagation, route association, and custom route tables.
 
 The virtual hub router takes routing decisions using built-in route selection algorithm. To influence routing decisions in virtual hub router towards on-premises, we now have a new Virtual WAN hub feature called **Hub routing preference** (HRP). When a virtual hub router learns multiple routes across S2S VPN, ER and SD-WAN NVA connections for a destination route-prefix in on-premises, the virtual hub router’s route selection algorithm will adapt based on the hub routing preference configuration and selects the best routes. You can now configure **Hub routing preference** using the Azure Preview Portal. For steps, see [How to configure virtual hub routing preference](howto-virtual-hub-routing-preference.md).
 
-> [!IMPORTANT]
-> The Virtual WAN feature **Hub routing preference** is currently in public preview. If you are interested in trying this feature, please follow the documentation below.
-This public preview is provided without a service-level agreement and shouldn't be used for production workloads. Certain features might not be supported, might have constrained capabilities, or might not be available in all Azure locations. For more information, see [Supplemental Terms of Use for Microsoft Azure Previews](https://azure.microsoft.com/support/legal/preview-supplemental-terms/).
->
+
 
 ## <a name="selection"></a>Route selection algorithm for virtual hub
 
@@ -51,14 +48,10 @@ This section explains the route selection algorithm in a virtual hub along with
          * If all the routes are local to the virtual hub, then choose routes from ER connections.
          * If all the routes are through remote virtual hubs, then choose routes from S2S VPN connections.
 
-1. If there are still multiple routes, load-balance across all paths using equal-cost multi-path (ECMP) routing.
-
 **Things to note:**
 
 * When there are multiple virtual hubs in a Virtual WAN scenario, a virtual hub selects the best routes using the route selection algorithm described above, and then advertises them to the other virtual hubs in the virtual WAN.
 
-* **Limitation:** If a route-prefix is reachable via ER or VPN connections, and via virtual hub SD-WAN NVA, then the latter route is ignored by the route-selection algorithm. Therefore, the flows to prefixes reachable only via virtual hub SD-WAN NVA will take the route through the NVA. This is a limitation during the Preview phase of  the **Hub routing preference** feature.
-
 ## Routing scenarios
 
 Virtual WAN hub routing preference is beneficial when multiple on-premises are advertising routes to same destination prefixes, which can happen in customer Virtual WAN scenarios that use any of the following setups.

articles/virtual-wan/howto-virtual-hub-routing-preference.md

@@ -1,5 +1,5 @@
 ---
-title: 'Configure virtual hub routing preference - Preview'
+title: 'Configure virtual hub routing preference'
 titleSuffix: Azure Virtual WAN
 description: Learn how to configure Virtual WAN virtual hub routing preference.
 author: cherylmc
@@ -8,14 +8,10 @@ ms.topic: conceptual
 ms.date: 05/30/2022
 ms.author: cherylmc
 ---
-# Configure virtual hub routing preference (Preview)
+# Configure virtual hub routing preference
 
 The following steps help you configure virtual hub routing preference settings. For information about this feature, see [Virtual hub routing preference](about-virtual-hub-routing-preference.md).
 
-> [!IMPORTANT]
-> The Virtual WAN feature **Hub routing preference** is currently in public preview. If you are interested in trying this feature, please follow the documentation below.
-This public preview is provided without a service-level agreement and shouldn't be used for production workloads. Certain features might not be supported, might have constrained capabilities, or might not be available in all Azure locations. For more information, see [Supplemental Terms of Use for Microsoft Azure Previews](https://azure.microsoft.com/support/legal/preview-supplemental-terms/).
->
 
 ## Configure
 

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

@@ -49,11 +49,15 @@ The virtual hub router now also exposes the ability to peer with it, thereby exc
    |---|---|
    |  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. |
 * 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 are not propagated further to on-premises.
-* Currently we only support 1,000 routes from the NVA to the virtual hub.
+* Currently we only support 4,000 routes from the NVA to the virtual hub.
 * Traffic destined for addresses in the virtual network directly connected to the virtual hub cannot 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.
 * This feature is not supported for setting up BGP peering between an NVA in a spoke VNet and a virtual hub with Azure Firewall.
 * In order for the NVA to exchange routes with VPN and ER connected sites, branch to branch routing must be turned on.
 
+* When configuring BGP peering with the hub, you will see two IP addresses. Peering with both these addresses is required. Not peering with both addresses can cause routing issues. 
+
+* 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 on virtual WAN at the moment.
+
 ## BGP peering scenarios
 
 This section describes scenarios where BGP peering feature can be utilized to configure routing.