Skip to content

Commit 6742bdd

Browse files
committed
add resiliency example
1 parent de47439 commit 6742bdd

File tree

1 file changed

+62
-6
lines changed

1 file changed

+62
-6
lines changed

articles/expressroute/expressroute-howto-circuit-arm.md

Lines changed: 62 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -4,15 +4,15 @@ description: This quickstart shows you how to create, provision, verify, update,
44
services: expressroute
55
author: duongau
66
ms.author: duau
7-
ms.date: 12/28/2023
7+
ms.date: 09/17/2024
88
ms.topic: quickstart
99
ms.service: azure-expressroute
1010
ms.custom: devx-track-azurepowershell, mode-api
1111
---
1212

1313
# Quickstart: Create and modify an ExpressRoute circuit using Azure PowerShell
1414

15-
This quickstart shows you how to create an ExpressRoute circuit using PowerShell cmdlets and the Azure Resource Manager deployment model. You can also check the status, update, delete, or deprovision a circuit.
15+
This quickstart shows you how to create an ExpressRoute circuit in three different resiliency types: **Maximum Resiliency**, **High Resiliency**, and **Standard Resiliency** using Azure PowerShell. You'll learn how to check the status, update, delete, or deprovision a circuit using PowerShell cmdlets.
1616

1717
:::image type="content" source="media/expressroute-howto-circuit-portal-resource-manager/environment-diagram.png" alt-text="Diagram of ExpressRoute circuit deployment environment using Azure PowerShell." lightbox="media/expressroute-howto-circuit-portal-resource-manager/environment-diagram.png":::
1818

@@ -48,19 +48,76 @@ Check to see if your connectivity provider is listed there. Make a note of the f
4848

4949
You're now ready to create an ExpressRoute circuit.
5050

51+
### Get the list of resilient locations
52+
53+
If you're creating an ExpressRoute circuit with a resiliency type of **Maximum Resiliency**, you need to know the list of resilient locations. Here are the steps to retrieve this information:
54+
55+
#### Clone the script
56+
57+
1. Clone the setup script from GitHub.
58+
59+
```azurepowershell-interactive
60+
git clone https://github.com/Azure-Samples/azure-docs-powershell-samples/
61+
```
62+
63+
1. Change to the directory where the script is located.
64+
65+
```azurepowershell-interactive
66+
CD azure-docs-powershell-samples/expressroute/
67+
```
68+
69+
#### Run the script
70+
71+
Run the **Get-AzExpressRouteResilientLocations.ps1** script to get the list of resilient locations. The following example shows how to get the resilient locations for a specific subscription sorted by distance from Silicon Valley:
72+
73+
```azurepowershell-interactive
74+
$SubscriptionId = Get-AzureSubscription -SubscriptionName "<SubscriptionName>"
75+
highAvailabilitySetup/Get-AzExpressRouteResilientLocations.ps1 -SubscriptionId $SubscriptionId -RelativeLocation "silicon valley"
76+
```
77+
If you don't specify the location, you get a list of all resilient locations.
78+
5179
### Create an ExpressRoute circuit
5280

53-
If you don't already have a resource group, you must create one before you create your ExpressRoute circuit. You can do so by running the following command:
81+
If you don't already have a resource group, you must create one before you create your ExpressRoute circuit. You can do so by running the **New-AzResourceGroup** cmdlet:
5482

5583
```azurepowershell-interactive
56-
New-AzResourceGroup -Name "ExpressRouteResourceGroup" -Location "West US"
84+
$resourceGroupName = (New-AzResourceGroup -Name "ExpressRouteResourceGroup" -Location "West US").ResourceGroupName
5785
```
5886

59-
The following example shows how to create a 200-Mbps ExpressRoute circuit through Equinix in Silicon Valley. If you're using a different provider and different settings, replace that information when you make your request. Use the following example to request a new service key:
87+
If you already have a resource group, you can use **Get-AzResourceGroup** to get the resource group name into a variable:
88+
89+
```azurepowershell-interactive
90+
$resourceGroupName = (Get-AzResourceGroup -Name "<ResourceGroupName>").ResourceGroupName
91+
```
92+
93+
# [**Maximum Resiliency**](#tab/maximum)
94+
95+
The following example shows how to create two ExpressRoute circuits through Equinix with local redundancy in Silicon Valley and Washington DC. If you're using a different provider and different settings, replace that information when you make your request.
96+
97+
> [!NOTE]
98+
> This example uses the **New-AzHighAvailabilityExpressRouteCircuits.ps1** script. You need to clone the script from GitHub and run it to create the circuits. For more information, see [Clone the script](#clone-the-script).
99+
100+
101+
```azurepowershell-interactive
102+
$SubscriptionId = Get-AzureSubscription -SubscriptionName "<SubscriptionName>"
103+
highAvailabilitySetup/New-AzHighAvailabilityExpressRouteCircuits.ps1 -SubscriptionId $SubscriptionId -ResourceGroupName $resourceGroupName -Location "westus" -Name1 $circuit1Name -Name2 $circuit2Name -SkuFamily1 "MeteredData" -SkuFamily2 "MeteredData" -SkuTier1 "Standard" -SkuTier2 "Standard" -ServiceProviderName1 "Equinix" -ServiceProviderName2 "Equinix" -PeeringLocation1 "Silicon Valley" -PeeringLocation2 "Washington DC" -BandwidthInMbps 1000
104+
```
105+
106+
:::image type="content" source="./media/expressroute-howto-circuit-portal-resource-manager/maximum-resiliency.png" alt-text="Diagram of maximum resiliency for an ExpressRoute connection.":::
107+
108+
> [!NOTE]
109+
> Maximum Resiliency provides maximum protection against location wide outages and connectivity failures in an ExpressRoute location. This option is strongly recommended for all critical and production workloads.
110+
111+
# [**Standard Resiliency**](#tab/standard)
112+
113+
The following example shows how to create an ExpressRoute circuit through Equinix in Silicon Valley. If you're using a different provider and different settings, replace that information when you make your request. Use the following example to request a new service key:
60114

61115
```azurepowershell-interactive
62116
New-AzExpressRouteCircuit -Name "ExpressRouteARMCircuit" -ResourceGroupName "ExpressRouteResourceGroup" -Location "West US" -SkuTier Standard -SkuFamily MeteredData -ServiceProviderName "Equinix" -PeeringLocation "Silicon Valley" -BandwidthInMbps 200
63117
```
118+
:::image type="content" source="./media/expressroute-howto-circuit-portal-resource-manager/standard-resiliency.png" alt-text="Diagram of standard resiliency for an ExpressRoute connection.":::
119+
120+
---
64121

65122
Make sure that you specify the correct SKU tier and SKU family:
66123

@@ -69,7 +126,6 @@ Make sure that you specify the correct SKU tier and SKU family:
69126

70127
> [!IMPORTANT]
71128
> Your ExpressRoute circuit is billed from the moment a service key is issued. Ensure that you perform this operation when the connectivity provider is ready to provision the circuit.
72-
>
73129
74130
The response contains the service key. You can get detailed descriptions of all the parameters by running the following command:
75131

0 commit comments

Comments
 (0)