Skip to content

Commit f35c076

Browse files
authored
Update expressroute-howto-gateway-migration-portal.md
remove all info about adding second prefix
1 parent 9f680ac commit f35c076

File tree

1 file changed

+1
-23
lines changed

1 file changed

+1
-23
lines changed

articles/expressroute/expressroute-howto-gateway-migration-portal.md

Lines changed: 1 addition & 23 deletions
Original file line numberDiff line numberDiff line change
@@ -29,28 +29,6 @@ The following SKUs are available for ExpressRoute virtual network gateways:
2929

3030
- Review the [Gateway migration](gateway-migration.md) article before you begin.
3131
- You must have an existing [ExpressRoute Virtual network gateway](expressroute-howto-add-gateway-portal-resource-manager.md) in your Azure subscription.
32-
- A second prefix is required for the gateway subnet. If you have only one prefix, you can add a second prefix by following the steps in the [Add a second prefix to the gateway subnet](#add-a-second-prefix-to-the-gateway-subnet) section.
33-
34-
## Add a second prefix to the gateway subnet
35-
36-
The gateway subnet needs two or more address prefixes for migration. If you have only one prefix, you can add a second prefix by following these steps.
37-
38-
1. First, update the `Az.Network` module to the latest version by running this PowerShell command:
39-
40-
```powershell-interactive
41-
Update-Module -Name Az.Network -Force
42-
```
43-
44-
1. Then, add a second prefix to the **GatewaySubnet** by running these PowerShell commands:
45-
46-
```powershell-interactive
47-
$vnet = Get-AzVirtualNetwork -Name $vnetName -ResourceGroupName $resourceGroup
48-
$subnet = Get-AzVirtualNetworkSubnetConfig -Name GatewaySubnet -VirtualNetwork $vnet
49-
$prefix = "Enter new prefix"
50-
$subnet.AddressPrefix.Add($prefix)
51-
Set-AzVirtualNetworkSubnetConfig -Name GatewaySubnet -VirtualNetwork $vnet -AddressPrefix $subnet.AddressPrefix
52-
Set-AzVirtualNetwork -VirtualNetwork $vnet
53-
```
5432

5533
## Migrate to a new gateway in Azure portal
5634

@@ -98,4 +76,4 @@ Here are the steps to migrate to a new gateway in Azure portal.
9876
## Next steps
9977

10078
* Learn more about [designing for high availability](designing-for-high-availability-with-expressroute.md).
101-
* Plan for [disaster recovery](designing-for-disaster-recovery-with-expressroute-privatepeering.md) and [using VPN as a backup](use-s2s-vpn-as-backup-for-expressroute-privatepeering.md).
79+
* Plan for [disaster recovery](designing-for-disaster-recovery-with-expressroute-privatepeering.md) and [using VPN as a backup](use-s2s-vpn-as-backup-for-expressroute-privatepeering.md).

0 commit comments

Comments
 (0)