Skip to content

Commit dfdb657

Browse files
Merge pull request #287051 from halkazwini/rs-ps
Tweaks
2 parents aeb2136 + 78897eb commit dfdb657

File tree

1 file changed

+6
-3
lines changed

1 file changed

+6
-3
lines changed

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

Lines changed: 6 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ author: halkazwini
55
ms.author: halkazwini
66
ms.service: azure-route-server
77
ms.topic: quickstart
8-
ms.date: 09/20/2024
8+
ms.date: 09/19/2024
99
ms.custom: devx-track-azurepowershell, mode-api
1010
---
1111

@@ -60,12 +60,13 @@ In this section, you create a route server. Prior to creating the route server,
6060
6161
```azurepowershell-interactive
6262
# Create a Standard public IP and place it into a variable.
63-
$publicIp = New-AzPublicIpAddress -ResourceGroupName 'RouteServerRG' -Name 'myRouteServerIP' -Location 'WestUS' -AllocationMethod 'Static' -Sku 'Standard' IpAddressVersion = 'Ipv4'
63+
$publicIp = New-AzPublicIpAddress -ResourceGroupName 'RouteServerRG' -Name 'myRouteServerIP' -Location 'WestUS' -AllocationMethod 'Static' -Sku 'Standard' -IpAddressVersion 'Ipv4'
6464
```
6565
6666
1. Create the route server using [New-AzRouteServer](/powershell/module/az.network/new-azrouteserver). The following example creates a route server named **myRouteServer** in the **WestUS** region. The *HostedSubnet* is the resource ID of the RouteServerSubnet created in the previous section.
6767
6868
```azurepowershell-interactive
69+
# Create a route server.
6970
New-AzRouteServer -RouteServerName 'myRouteServer' -ResourceGroupName 'RouteServerRG' -Location 'WestUS' -HostedSubnet $subnetId -PublicIP $publicIp
7071
```
7172
@@ -76,6 +77,7 @@ In this section, you create a route server. Prior to creating the route server,
7677
In this section, you learn how to configure BGP peering with a network virtual appliance (NVA). Use [Add-AzRouteServerPeer](/powershell/module/az.network/add-azrouteserverpeer) to establish BGP peering from the route server to your NVA. The following example adds a peer named **myNVA** that has an IP address of **10.0.0.4** and an ASN of **65001**. For more information, see [What Autonomous System Numbers (ASNs) can I use?](route-server-faq.md#what-autonomous-system-numbers-asns-can-i-use)
7778
7879
```azurepowershell-interactive
80+
# Add a peer.
7981
Add-AzRouteServerPeer -ResourceGroupName 'RouteServerRG' -RouteServerName 'myRouteServer' -PeerName 'myNVA' -PeerAsn '65001' -PeerIp '10.0.0.4'
8082
```
8183

@@ -84,10 +86,11 @@ Add-AzRouteServerPeer -ResourceGroupName 'RouteServerRG' -RouteServerName 'myRou
8486
To complete the peering setup, you must configure the NVA to establish a BGP session with the route server's peer IPs and ASN. Use [Get-AzRouteServer](/powershell/module/az.network/get-azrouteserver) to get the IP and ASN of the route server.
8587

8688
```azurepowershell-interactive
89+
# Get the route server details.
8790
Get-AzRouteServer -ResourceGroupName 'RouteServerRG' -RouteServerName 'myRouteServer'
8891
```
8992

90-
The output looks like the following:
93+
The output looks like the following example:
9194

9295
```output
9396
ResourceGroupName Name Location RouteServerAsn RouteServerIps ProvisioningState HubRoutingPreference AllowBranchToBranchTraffic

0 commit comments

Comments
 (0)