Skip to content

Latest commit

 

History

History
134 lines (85 loc) · 8.87 KB

upgrade-InternalBasic-To-PublicStandard.md

File metadata and controls

134 lines (85 loc) · 8.87 KB
title description services author ms.service ms.topic ms.date ms.author
Upgrade from Basic Internal to Standard Public - Azure Load Balancer
This article shows you how to upgrade Azure Basic Internal Load Balancer to Standard Public Load Balancer
load-balancer
irenehua
load-balancer
how-to
01/23/2020
irenehua

Upgrade Azure Internal Load Balancer - Outbound Connection Required

Azure Standard Load Balancer offers a rich set of functionality and high availability through zone redundancy. To learn more about Load Balancer SKU, see comparison table. Since Standard Internal Load Balancer does not provide outbound connection, we provide a solution to create a Standard Public Load Balancer instead.

There are four stages in a upgrade:

  1. Migrate the configuration to Standard Public Load Balancer
  2. Add VMs to backend pools of Standard Public Load Balancer
  3. Set up NSG rules for Subnet/VMs that should be refrained from/to the Internet

This article covers configuration migration. Adding VMs to backend pools may vary depending on your specific environment. However, some high-level, general recommendations are provided.

Upgrade overview

An Azure PowerShell script is available that does the following:

  • Creates a Standard SKU Public Load Balancer in the resource group and location that you specify.
  • Seamlessly copies the configurations of the Basic SKU Internal Load Balancer to the newly create Standard Public Load Balancer.
  • Creates an outbound rule which enables egress connectivity.

Caveats\Limitations

  • Script supports Internal Load Balancer upgrade where outbound connection is required. If outbound connection is not required for any of the VMs, refer to this page for best practice.
  • The Standard Load Balancer has a new public address. It’s impossible to move the IP addresses associated with existing Basic Internal Load Balancer seamlessly to Standard Public Load Balancer since they have different SKUs.
  • If the Standard load balancer is created in a different region, you won’t be able to associate the VMs existing in the old region to the newly created Standard Load Balancer. To work around this limitation, make sure to create a new VM in the new region.
  • If your Load Balancer does not have any frontend IP configuration or backend pool, you are likely to hit an error running the script. Make sure they are not empty.

Download the script

Download the migration script from the PowerShell Gallery.

Use the script

There are two options for you depending on your local PowerShell environment setup and preferences:

  • If you don’t have the Azure Az modules installed, or don’t mind uninstalling the Azure Az modules, the best option is to use the Install-Script option to run the script.
  • If you need to keep the Azure Az modules, your best bet is to download the script and run it directly.

To determine if you have the Azure Az modules installed, run Get-InstalledModule -Name az. If you don't see any installed Az modules, then you can use the Install-Script method.

Install using the Install-Script method

To use this option, you must not have the Azure Az modules installed on your computer. If they're installed, the following command displays an error. You can either uninstall the Azure Az modules, or use the other option to download the script manually and run it.

Run the script with the following command:

Install-Script -Name AzurePublicLBUpgrade

This command also installs the required Az modules.

Install using the script directly

If you do have some Azure Az modules installed and can't uninstall them (or don't want to uninstall them), you can manually download the script using the Manual Download tab in the script download link. The script is downloaded as a raw nupkg file. To install the script from this nupkg file, see Manual Package Download.

To run the script:

  1. Use Connect-AzAccount to connect to Azure.

  2. Use Import-Module Az to import the Az modules.

  3. Examine the required parameters:

    • oldRgName: [String]: Required – This is the resource group for your existing Basic Load Balancer you want to upgrade. To find this string value, navigate to Azure portal, select your Basic Load Balancer source, and click the Overview for the load balancer. The Resource Group is located on that page.
    • oldLBName: [String]: Required – This is the name of your existing Basic Balancer you want to upgrade.
    • newrgName: [String]: Required – This is the resource group in which the Standard Load Balancer will be created. It can be a new resource group or an existing one. If you pick an existing resource group, note that the name of the Load Balancer has to be unique within the resource group.
    • newlocation: [String]: Required – This is the location in which the Standard Load Balancer will be created. We recommend inheriting the same location of the chosen Basic Load Balancer to the Standard Load Balancer for better association with other existing resources.
    • newLBName: [String]: Required – This is the name for the Standard Load Balancer to be created.

  4. Run the script using the appropriate parameters. It may take five to seven minutes to finish.

    Example

    AzurePublicLBUpgrade.ps1 -oldRgName "test_publicUpgrade_rg" -oldLBName "LBForPublic" -newrgName "test_userInput3_rg" -newlocation "centralus" -newLbName "LBForUpgrade"

Add VMs to backend pools of Standard Load Balancer

First, double check that the script successfully created a new Standard Public Load Balancer with the exact configuration migrated over from your Basic Public Load Balancer. You can verify this from the Azure portal.

Be sure to send a small amount of traffic through the Standard Load Balancer as a manual test.

Here are a few scenarios of how you add VMs to backend pools of the newly created Standard Public Load Balancer may be configured, and our recommendations for each one:

  • Moving existing VMs from backend pools of old Basic Public Load Balancer to backend pools of newly created Standard Public Load Balancer.

    1. To do the tasks in this quickstart, sign in to the Azure portal.

    2. Select All resources on the left menu, and then select the newly created Standard Load Balancer from the resource list.

    3. Under Settings, select Backend pools.

    4. Select the backend pool which matches the backend pool of the Basic Load Balancer, select the following value: - Virtual Machine: Drop down and select the VMs from the matching backend pool of the Basic Load Balancer.

    5. Select Save.

    [!NOTE] For VMs which have Public IPs, you will need to create Standard IP addresses first where same IP address is not guaranteed. Disassociate VMs from Basic IPs and associate them with the newly created Standard IP addresses. Then, you will be able to follow instructions to add VMs into backend pool of Standard Load Balancer.

  • Creating new VMs to add to the backend pools of the newly created Standard Public Load Balancer.

    • More instructions on how to create VM and associate it with Standard Load Balancer can be found here.

Create an outbound rule for outbound connection

Follow the instructions to create an outbound rule so you can

  • Define outbound NAT from scratch.
  • Scale and tune the behavior of existing outbound NAT.

Create NSG rules for VMs which to refrain communication from or to the Internet

If you would like to refrain Internet traffic from reaching to your VMs, you can create an NSG rule on the Network Interface of the VMs.

Common questions

Are there any limitations with the Azure PowerShell script to migrate the configuration from v1 to v2?

Yes. See Caveats/Limitations.

Does the Azure PowerShell script also switch over the traffic from my Basic Load Balancer to the newly created Standard Load Balancer?

No. The Azure PowerShell script only migrates the configuration. Actual traffic migration is your responsibility and in your control.

I ran into some issues with using this script. How can I get help?

You can send an email to slbupgradesupport@microsoft.com, open a support case with Azure Support, or do both.

Next steps

Learn about Standard Load Balancer