Migrate an Azure Virtual Network Gateway to new SKU

Everpure Cloud Dedicated for Azure
Audience
Public
Source Type
Documentation

The Azure Virtual Network Gateway is the key component for connecting AVS and Everpure Cloud Dedicated. Azure Virtual Network Gateways are available in multiple SKUs (the list and specifications of available SKUs can be found here) that are primarily differentiated by the level of network bandwidth, performance and Availability Zone affinity.

To provide maximum network bandwidth between AVS and Everpure Cloud Dedicated, it is strongly recommended to use the ErGw3AZ SKU for the Virtual Network Gateway. This SKU provides the Ultra SKU performance with FastPath capability and it allows you to deploy into the same Azure Availability Zones where Everpure Cloud Dedicated and AVS are deployed.

The following steps describe how to migrate Azure Virtual Network Gateway from one SKU to another without causing any downtime to the current environment.

  1. Add a second IP prefix to the gateway subnet.

    The gateway subnet needs to have two or more address prefixes for the migration. If you have only one prefix in your gateway subnet, you need to add a second prefix by running following PowerShell commands:

    $vnet = Get-AzVirtualNetwork -Name myVNET -ResourceGroupName  myResourceGroup
$subnet = Get-AzVirtualNetworkSubnetConfig -Name GatewaySubnet -VirtualNetwork $vnet
$prefix = "New IP prefix"
$subnet.AddressPrefix.Add($prefix) 
Set-AzVirtualNetworkSubnetConfig -Name GatewaySubnet -VirtualNetwork $vnet -AddressPrefix $subnet.AddressPrefix
Set-AzVirtualNetwork -VirtualNetwork $vnet
  2. Migrate to a new gateway SKU in the Azure portal.

    In the Azure portal, navigate to your Virtual Network Gateway resource, under Settings > Gateway SKU Migration.

  3. Select Validate to check if the gateway is ready for migration.

    You will first see a list of prerequisites that must be met before the migration can begin. If these prerequisites aren't met, the validation will fail and you cannot proceed.

  4. Once the validation is successful, continue to enter the Prepare stage.

    Here, a new Virtual Network gateway will be created. Under Virtual Network Gateway Details, select the new Gateway SKU together with the new Public IP address.

  5. Select Prepare to create the new gateway. This operation could take about 30 minutes to complete.
  6. After the new gateway is created, you will proceed to the Migrate stage.

    Here, select the new gateway you created in the previous steps (In this example, it is myERGateway_migrated). This transfers the settings from your old gateway to the newly created one. All network traffic, control plane, and data path connections from your old gateway will transfer without any interruptions. To start this process, select Migrate Traffic. This operation could take up to 5 minutes.

  7. After the traffic migration is completed, you will proceed to the Commit stage.

    In this stage, you finalize the migration, which involves deleting the old gateway and old Public IP address. To do this, select Commit migration.