Skip to content

Commit c236d45

Browse files
authored
Merge pull request #286795 from halkazwini/rs-include
Update two include files
2 parents fc3ccae + 9f3a43a commit c236d45

File tree

2 files changed

+4
-4
lines changed

2 files changed

+4
-4
lines changed

includes/route-server-note-nva-peering.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ author: halkazwini
33
ms.author: halkazwini
44
ms.service: azure-route-server
55
ms.topic: include
6-
ms.date: 03/30/2023
6+
ms.date: 09/16/2024
77
---
88
> [!IMPORTANT]
9-
> We recommend peering each NVA with both Route Server instances to ensure that virtual network routes are advertised over the NVA connections and achieve high availability.
9+
> We recommend peering each NVA with both route server instances to ensure that virtual network routes are advertised over the NVA connections and achieve high availability.

includes/route-server-note-vpn-gateway.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ author: halkazwini
33
ms.author: halkazwini
44
ms.service: azure-route-server
55
ms.topic: include
6-
ms.date: 8/26/2024
6+
ms.date: 09/16/2024
77
---
88
> [!IMPORTANT]
9-
> The Azure VPN gateway must be configured in [**active-active**](../articles/vpn-gateway/vpn-gateway-activeactive-rm-powershell.md) mode and have the ASN set to **65515**. It's not a requirement to have BGP enabled on the VPN gateway to communicate with the route server.
9+
> The Azure VPN gateway must be configured in [**active-active**](../articles/vpn-gateway/active-active-portal.md) mode and have the ASN set to **65515**. It's not a requirement to have BGP enabled on the VPN gateway to communicate with the route server.

0 commit comments

Comments
 (0)