SEs Reporting 0 Service Units Licensed in Avi Load Balancer Enterprise with Cloud Services.

Products

• VMware Avi Load Balancer

Issue/Introduction

• On the Avi licensing page, the “Used Service Units” value shows as zero, even though the SEs are active and have cores assigned.

 

• The show service engine summary command is reporting the licensed service core count as zero.

 

• The SE Manager resets the licensed service unit count for SEs to zero whenever the License Manager reports an UNDETERMINED state—even if the SE was initially licensed correctly. You can find the logs on location /var/lib/avi/lig/se-mgr*.log .

se_mgr-7.log.INFO.20240807-195544.4954:I0807 19:55:44.593932  4954 db_cache.cc:332] Starting DB Cache for licensestatusse_mgr-0.INFO:I0205 21:37:55.859714  5588 se_mgr_svc_object.cc:4948] F[CheckoutLicenseAction] [##:se-b6722c] [rpc out] CheckoutLicense [005056b60ca7-se_mgr:0-->go_license_mgr] se_uuid[se-****] cookie[f15f0f0e-a349-4186-941f-fce26a52e1f6] lic_state[1] lic_cores[0]
se_mgr-0.INFO:  license_type: LIC_CORES
se_mgr-0.INFO:  license_tier: ENTERPRISE_WITH_CLOUD_SERVICES
se_mgr-0.INFO:  license_type: LIC_CORES
se_mgr-0.INFO:  license_tier: ENTERPRISE_WITH_CLOUD_SERVICES
se_mgr-.log.INFO.20250421-180740.5538:I0426 01:12:16.123262  5538 se_mgr_service_impl.cc:1219] F[UpdateLicense] [se-****] [rpc in] [005056b60ca7-se_mgr:2<--*******-license_mgr:0]
se_mgr-.log.INFO.20250421-180740.5538:license_state: LICENSE_STATE_UNDETERMINED
se_mgr-log.INFO.20250421-180740.5538:licensed_service_cores: 0

 

 

Cause

If the Controller remains disconnected from Cloud Services for an extended period, the SE Manager incorrectly resets licensed_service_cores to 0 instead of retaining the original core count. When the Controller later reconnects, the License Manager should re-evaluate and restore the correct license cores, but that re-evaluation does not occur due to the bug.

Resolution

Temporary Workaround:

 

• Reboot the SE.

     OR

• Disconnect the SE from the Controller for 10 minutes, then reconnect it.
  Note: This may cause the Controller to spawn a new SE, potentially leaving the original SE headless.

 

Permanent Fix:

This issue is scheduled to be resolved in version 31.2.1.