Skip to content

Commit d346934

Browse files
Merge pull request #223192 from mialdrid/patch-187
Peering each NVA to both RS instances
2 parents d987cda + cedaf22 commit d346934

File tree

1 file changed

+3
-0
lines changed

1 file changed

+3
-0
lines changed

articles/route-server/quickstart-configure-route-server-portal.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -86,6 +86,9 @@ You'll need the Azure Route Server's peer IPs and ASN to complete the configurat
8686

8787
:::image type="content" source="./media/quickstart-configure-route-server-portal/route-server-overview.png" alt-text="Screenshot of Route Server overview page.":::
8888

89+
> [!IMPORTANT]
90+
> To ensure that virtual network routes are advertised over the NVA connections, and to achieve high availability, we recommend peering each NVA with both Route Server instances.
91+
8992
## Configure route exchange
9093

9194
If you have an ExpressRoute gateway and/or VPN gateway and you want them to exchange routes with the Route Server, you can enable route exchange.

0 commit comments

Comments
 (0)