Avi Controller version: 30.x
Cloud Provider: Microsoft Azure
default_license_tier configured in the System Configuration and the license_tier configured in the Azure Cloud Connector. If these license tiers do not align, or if the license_type in the Azure Cloud configuration is not explicitly set to LIC_CORES or lic_metered_se_bandwidth, the system will prevent the creation of new Service Engine groups and return an error in the UI.How to check System Configuration Setting in UI:
Navigate to Avi Controller UI > Administration > Licensing > Click on the gear icon to view the configured system's default_license_tier: Enterprise or Enterprise with cloud services
How to check System Configuration Setting in CLI:
Follow these steps to check the license_type and license_tier in the Azure Cloud Configuration:
SSH to the Avi Controller.
Enter the shell mode:
admin@:~$ shell
[admin:]: > show systemconfiguration | grep default_license_tier
| default_license_tier | ENTERPRISE |
How to check Azure Cloud Connector Settings in CLI:
[admin:]: > show cloud Azure | grep license_tier
| license_tier | ENTERPRISE |
[admin:10-80-37-100]: > show cloud Azure | grep license_type
| license_type | LIC_CORES |
Resolution:
To resolve this issue, ensure that the default_license_tier in the system configuration and the license_tier in the Azure Cloud configuration are same. Additionally, confirm that the license_type for the Azure Cloud is set to either LIC_CORES or LIC_METERED_SE_BANDWIDTH.
Follow these steps to update the license_type and license_tier in the Azure Cloud Configuration:
Configure the Azure cloud
[admin:]: > configure cloud Azure
[admin:]: cloud> license_type <lic_cores or lic_metered_se_bandwidth>
[admin:]: cloud> license_tier <enterprise or enterprise_with_cloud_services>
[admin:]: cloud> save
After making these changes, you should be able to create new Service Engine Groups with the SE Bandwidth-based license in your Azure cloud environment.
The Basic tier of Avi Load Balancer reached its End of Availability (EoA) date on January 30, 2024. For more details, refer to the Broadcom Knowledge Base article: https://knowledge.broadcom.com/external/article?legacyId=96386