Skip to content

Commit a28a556

Browse files
authored
Merge pull request #232865 from halkazwini/rs-ps
Route Server: Updates: Quickstart: Create and configure Route Server using Azure PowerShell
2 parents 49cb2d1 + 485c25e commit a28a556

File tree

4 files changed

+16
-4
lines changed

4 files changed

+16
-4
lines changed

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

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -161,6 +161,8 @@ RouteServerIps : {10.5.10.4, 10.5.10.5} "virtualRouterAsn": 65515,
161161
162162
```
163163

164+
[!INCLUDE [NVA peering note](../../includes/route-server-note-nva-peering.md)]
165+
164166
## Configure route exchange
165167

166168
If you have an ExpressRoute and an Azure VPN gateway in the same virtual network and you want them to exchange routes, you can enable route exchange on the Azure Route Server.

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

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -86,8 +86,7 @@ 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.
89+
[!INCLUDE [NVA peering note](../../includes/route-server-note-nva-peering.md)]
9190

9291
## Configure route exchange
9392

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

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@ ms.custom: devx-track-azurepowershell, mode-api, template-quickstart
1212

1313
# Quickstart: Create and configure Route Server using Azure PowerShell
1414

15-
This article helps you configure Azure Route Server to peer with a Network Virtual Appliance (NVA) in your virtual network using Azure PowerShell. Route Server will learn routes from your NVA and program them on the virtual machines in the virtual network. Azure Route Server will also advertise the virtual network routes to the NVA. For more information, see [Azure Route Server](overview.md).
15+
This article helps you configure Azure Route Server to peer with a Network Virtual Appliance (NVA) in your virtual network using Azure PowerShell. Route Server learns routes from your NVA and program them on the virtual machines in the virtual network. Azure Route Server also advertises the virtual network routes to the NVA. For more information, see [Azure Route Server](overview.md).
1616

1717
:::image type="content" source="media/quickstart-configure-route-server-portal/environment-diagram.png" alt-text="Diagram of Route Server deployment environment using the Azure PowerShell." border="false":::
1818

@@ -55,7 +55,7 @@ $virtualNetwork = New-AzVirtualNetwork @vnet
5555

5656
### Add a dedicated subnet
5757

58-
Azure Route Server requires a dedicated subnet named *RouteServerSubnet*. The subnet size has to be at least /27 or short prefix (such as /26 or /25) or you'll receive an error message when deploying the Route Server. Create a subnet configuration named **RouteServerSubnet** with [Add-AzVirtualNetworkSubnetConfig](/powershell/module/az.network/add-azvirtualnetworksubnetconfig):
58+
Azure Route Server requires a dedicated subnet named *RouteServerSubnet*. The subnet size has to be at least /27 or shorter prefix (such as /26 or /25) or you'll receive an error message when deploying the Route Server. Create a subnet configuration named **RouteServerSubnet** with [Add-AzVirtualNetworkSubnetConfig](/powershell/module/az.network/add-azvirtualnetworksubnetconfig):
5959

6060
```azurepowershell-interactive
6161
$subnet = @{
@@ -138,6 +138,8 @@ RouteServerAsn : 65515
138138
RouteServerIps : {10.5.10.4, 10.5.10.5}
139139
```
140140

141+
[!INCLUDE [NVA peering note](../../includes/route-server-note-nva-peering.md)]
142+
141143
## <a name = "route-exchange"></a>Configure route exchange
142144

143145
If you have an ExpressRoute and an Azure VPN gateway in the same virtual network and you want them to exchange routes, you can enable route exchange on the Azure Route Server.
Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,9 @@
1+
---
2+
author: halkazwini
3+
ms.author: halkazwini
4+
ms.service: route-server
5+
ms.topic: include
6+
ms.date: 03/30/2023
7+
---
8+
> [!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.

0 commit comments

Comments
 (0)