Skip to content

Commit a222c55

Browse files
committed
Updates to code
1 parent d1092af commit a222c55

File tree

1 file changed

+10
-3
lines changed

1 file changed

+10
-3
lines changed

articles/load-balancer/load-balancer-migrate-nic-to-ip-based-backend-pools.md

Lines changed: 10 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -15,11 +15,16 @@ ms.custom: template-how-to
1515

1616
In this article, you'll learn how to migrate a load balancer with NIC-based backend pools to use IP-based backend pools with virtual machines and virtual machine scale sets
1717

18+
## Prerequisites
19+
20+
- <!-- prerequisite 1 -->
21+
- <!-- prerequisite 2 -->
22+
- <!-- prerequisite n -->
1823
## What is IP-based Load Balancer
1924

2025
IP-based load balancers reference the private IP address of the resource in the backend pool rather than the resource’s NIC. IP-based load balancers enable the pre-allocation of private IP addresses in a backend pool, without having to create the backend resources themselves in advance.
2126

22-
## Migrating NIC-based virtual machine backend pools to IP-based
27+
## Migrating NIC-based virtual machine backend pools too IP-based
2328

2429
To migrate a load balancer with NIC-based backend pools to IP-based with VMs (not virtual machine scale sets instances) in the backend pool, you can utilize the following migration REST API.
2530

@@ -51,8 +56,8 @@ az rest –m post –u “https://management.azure.com/subscriptions/MySubscript
5156
## Upgrading LB with virtual machine scale sets attached
5257

5358
To upgrade a NIC-based load balancer to IP based load balancer with virtual machine scale sets in the backend pool, follow the following steps:
54-
1. Configure the upgrade policy of the virtual machine scale sets to be automatic. Note that if the upgrade policy is not set to automatic, all virtual machine scale sets instances must be upgraded after calling the migration API.
55-
1. Using the Azure’s migration REST API, upgrade the NIC based LB to an IP based LB. a. Note, if a manual upgrade policy is in place, upgrade all VMs in the virtual machine scale sets before step 3.
59+
1. Configure the upgrade policy of the virtual machine scale sets to be automatic. If the upgrade policy isn't set to automatic, all virtual machine scale sets instances must be upgraded after calling the migration API.
60+
1. Using the Azure’s migration REST API, upgrade the NIC based LB to an IP based LB. If a manual upgrade policy is in place, upgrade all VMs in the virtual machine scale sets before step 3.
5661
1. Remove the reference of the load balancer from the network profile of the virtual machine scale sets, and update the VM instances to reflect the changes.
5762

5863
A full example using the CLI is shown here:
@@ -64,3 +69,5 @@ Az rest –m post –u “https://management.azure.com/subscriptions/MySubscript
6469
az virtual machine scale sets update --resource-group MyResourceGroup --name MyVMSS --remove virtualMachineProfile.networkProfile.networkInterfaceConfigurations[0].ipConfigurations[0].loadBalancerBackendAddressPools
6570
6671
```
72+
73+
## Next Steps

0 commit comments

Comments
 (0)