Avi ALB Cluster VIP SKU Migration from Basic to Standard in Azure Cloud
Article ID: 406417
Updated On:
Products
Issue/Introduction
Azure Cloud implementation of VMware Avi Load Balancer uses Azure Basic LB for various purposes such as Cluster VIP configuration, vsVIP placement and Public IPs. The existing deployed VMware Avi ALB with Cluster VIP Azure basic SKU will stay till September 30, 2025 and after that data traffic will stop working. As a result, customers require a migration path from Basic to Standard SKU of Cluster VIP. This doc presents the steps to migrate to Standard ALB for Avi Resources.
- Announcement by Microsoft
https://azure.microsoft.com/en-us/updates?id=azure-basic-load-balancer-will-be-retired-on-30-september-2025-upgrade-to-standard-load-balancer - Azure Basic SKU and Standard SKU
https://learn.microsoft.com/en-us/azure/virtual-network/ip-services/public-ip-basic-upgrade-guidance#basic-sku-vs-standard-sku
Environment
Azure Cloud
Cause
How to migrate the Cluster VIP (Private IP) from Basic SKU ALB to Standard SKU ALB
Resolution
For Avi Load Balancer 3 Node Cluster VIP SKU Migration
- Change the SKU of the Cluster VIP (Private IP) from Basic to Standard in Azure
These issue have been fixed in 31.1.1 version which is released and available for download on the support portal.
Controller versions 22.1.x, 30.1.x, 30.2.3, or 30.2.4 must upgrade to the 30.2.4-2p1 patch to ensure successful cluster IP functionality.
Step1: Patch Upgrade Cluster to 30.2.4-2p1 version
Step2: Remove the existing Cluster VIP
Navigate to Controller UI > Administration > Controller > Nodes > Click EDIT > Remove Controller Cluster IP and Save
Step3: Re-Configure cluster VIP with same private IP manually, which will result in provisioning with a Standard SKU for Cluster VIP
Navigate to Controller UI > Administration > Controller > Nodes > Click EDIT > Add Previous Controller Cluster IP > Save
With re-configure new Cluster VIP, it created with Standard SKU by default on Version 30.2.4-2p1, 30.2.5
Note: Cluster VIP with standard SKU require Internet connectivity to talk to the Azure Public API endpoint, which is an additional step required before the movement to migrate SKU from Basic to Standard
AV-244065: Cluster IP cannot be migrated from being Basic ALB based to Standard ALBTo apply the patch, please refer to the following guide: https://techdocs.broadcom.com/us/en/vmware-security-load-balancing/avi-load-balancer/avi-load-balancer/31-1/vmware-avi-load-balancer-administration-guide/nsx-advanced-load-balancer-controller-operations/upgrade-and-patches/patch-guide/patch-upgrade-for-avi-controller/patch-upgrade-using-ui.html
- Change the SKU of the Cluster VIP (Public IP) from Basic to Standard in Azure
No, a Public IP is not directly supported as a Cluster VIP for the Avi Load Balancer Controller in an Azure Cloud environment. The Cluster VIP must reside within the same virtual network (vNET) as the Avi Load Balancer Controllers to ensure proper connectivity and operation
Note: Public IPs are primarily used for Virtual Service VIPs (VS VIPs) and Azure DNS integration.
Additional Information
- From VMware Avi Load Balancer versions 22.x and 30.x: When an 3 node cluster is formed in Azure Cloud and a Cluster VIP is configured, Azure CloudConnector automatically creates an Azure Basic Load Balancer (Basic SKU) for Cluster VIP
- From VMware Avi Load Balancer version 31.1.x onwards (31.x) :The Cluster VIP configuration supports Azure Standard Load Balancer (Standard SKU) instead of the Basic SKU
- Avi Controller version 31.1.1, a new cluster VIP will be created with the standard LB as the default mode
- Associating a NAT gateway with cluster VIP / Subnet of the Avi Controller is required for the outbound access.
Feedback
