Merge pull request #290947 from siddomala/BGPpeering

Peer with both virtual hub IPs

Author: prmerger-automator[bot]

articles/route-server/route-server-faq.md

@@ -22,7 +22,7 @@ No. Azure Route Server is a service designed with high availability. Your route
 
 ### Do I need to peer each NVA with both Azure Route Server instances?
 
-Yes, to ensure that routes are successfully advertised to Route Server and to configure high availability, it is required to peer each NVA instance with both instances of Route Server. It is also recommended to peer at least 2 NVA instances with both instances of Route Server. 
+Yes, to ensure that routes are successfully advertised to Route Server and to configure high availability, it is required to peer each NVA instance with both instances of Route Server and advertise the same routes to both instances. It is also recommended to peer at least 2 NVA instances with both instances of Route Server. 
 
 >[!NOTE]
 > During Route Server maintenance events, BGP peering may go down between your NVA and one of Route Server's instances. As a result, if you configure your NVA to peer with both instances of Route Server, then your connectivity will remain up and running during maintenance events. 

articles/virtual-wan/create-bgp-peering-hub-portal.md

@@ -60,6 +60,8 @@ After your hub router status is provisioned, create a connection between your hu
 
     :::image type="content" source="./media/create-bgp-peering-hub-portal/view-peer.png" alt-text="Screenshot of the BGP peers page with the new peer.":::
 
+1. On the virtual hub resource, you'll see two IP addresses under "virtualRouterIps". It is required to peer with both these addresses and advertise the same routes to both these addresses. This ensures that the routes are successfully advertised to your virtual hub.  
+
 ### Modify a BGP peer
 
 1. On the **Virtual Hub** resource, go to the **BGP Peers** page.