You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This article walks you through the steps to add, resize, and remove a virtual network gateway for a pre-existing virtual network (VNet) using PowerShell. The steps for this configuration apply to VNets that were created using the Resource Manager deployment model for an ExpressRoute configuration. For more information about virtual network gateways and gateway configuration settings for ExpressRoute, see [About virtual network gateways for ExpressRoute](expressroute-about-virtual-network-gateways.md).
19
+
This article walks you through the steps to add, resize, and remove a virtual network gateway for a preexisting virtual network (VNet) using PowerShell. The steps for this configuration apply to VNets that were created using the Resource Manager deployment model for an ExpressRoute configuration. For more information about virtual network gateways and gateway configuration settings for ExpressRoute, see [About virtual network gateways for ExpressRoute](expressroute-about-virtual-network-gateways.md).
20
20
21
21
:::image type="content" source="./media/expressroute-howto-add-gateway-portal-resource-manager/gateway-circuit.png" alt-text="Diagram showing an ExpressRoute gateway connected to the ExpressRoute circuit." lightbox="./media/expressroute-howto-add-gateway-portal-resource-manager/gateway-circuit.png":::
22
22
23
23
## Prerequisites
24
24
25
25
### Configuration reference list
26
26
27
-
The steps for this task use a VNet based on the values in the following configuration reference list. Additional settings and names are also outlined in this list. We don't use this list directly in any of the steps, although we do add variables based on the values in this list. You can copy the list to use as a reference, replacing the values with your own.
27
+
The steps for this task use a VNet based on the values in the following configuration reference list. More settings and names are also outlined in this list. We don't use this list directly in any of the steps, although we do add variables based on the values in this list. You can copy the list to use as a reference, replacing the values with your own.
28
28
29
29
| Setting | Value |
30
30
| --- | --- |
@@ -36,7 +36,7 @@ The steps for this task use a VNet based on the values in the following configur
36
36
| Subnet1 Name |*FrontEnd*|
37
37
| Gateway Subnet name |*GatewaySubnet*|
38
38
| Gateway Subnet address space |*192.168.200.0/26*|
39
-
| Region |*East US*|
39
+
| Region |*West US*|
40
40
| Gateway Name |*GW*|
41
41
| Gateway IP Name |*GWIP*|
42
42
| Gateway IP configuration Name |*gwipconf*|
@@ -55,7 +55,19 @@ The steps for this task use a VNet based on the values in the following configur
55
55
56
56
```azurepowershell-interactive
57
57
$RG = "TestRG"
58
-
$Location = "East US"
58
+
$Location = "West US"
59
+
$GWName = "GW"
60
+
$GWIPName = "GWIP"
61
+
$GWIPconfName = "gwipconf"
62
+
$VNetName = "TestVNet"
63
+
```
64
+
65
+
If you want to create the gateway in an Azure Extended Zone, add the **$ExtendedLocation** variable.
66
+
67
+
```azurepowershell-interactive
68
+
$RG = "TestRG"
69
+
$Location = "West US"
70
+
$ExtendedLocation = "losangeles"
59
71
$GWName = "GW"
60
72
$GWIPName = "GWIP"
61
73
$GWIPconfName = "gwipconf"
@@ -90,6 +102,11 @@ The steps for this task use a VNet based on the values in the following configur
If you want to create the gateway in an Azure Extended Zone, request a public IP address in the Extended Zone using the **-ExtendedLocation** parameter.
0 commit comments