
Licenses in A10 Control define the entitlement, capacity, and validity for managing bandwidth, devices, and platform services. Depending on the license type and its capacity, various details and states are displayed. This section explains how to view license information, interpret license fields, and understand license validation states.
To view the license information:
On the Licenses page, expand a license to open the License Information tab.
The License Information page displays the following license details based on the license type:
| Column | Description |
|---|---|
|
Entitlement Token |
Generated when a new license is created in GLM. |
|
Platform |
The category of license platforms. For example, A10 Control, A10 Control ADO, RHEL Support, Capacity FlexPool, and Instance FlexPool. This is applicable only for A10 Control license. |
|
SKU Description |
The SKU (Stock-Keeping Unit) associated with the license pool or type. It is a sub-category of licenses under platforms. For example, A10 Control SW MBU and TPS.
|
|
Start Date |
The date and time from when the license has been assigned. |
|
Name |
The name of the license is specified in GLM. This field is displayed when a license is exported using the GLM or ALM option. |
|
State |
Current status of the license. For more information about the available licenses, see License Validation Status. |
|
Expires |
The expiry date of the license. |
|
License Error |
The license error description. |
|
Product |
Name of the platform on which A10 Control is running. A10 Control ADO license can be assigned to TPS mitigator. A10 Control license can be assigned to non-TPS product. Example: ADC and CGN. RHEL Support Thunder and RHEL Support Virtual are available. |
|
Managed Bandwidth |
Bandwidth is in Gbps or Tbps. It can be modified after creating the license if required. Bandwidth is a shared pool of licenses. This field is not applicable for A10 Control ADO license. |
|
Managed Devices |
Devices that are associated with the license. Most licenses support unlimited devices. |
|
Billing Serial Numbers |
The billing serial numbers of the license. |
|
Export Node Count |
The number of nodes in the A10 Control deployments for which a license is exported. This helps GLM to track the number of nodes in the user's setup for Red Hat licenses. This field is displayed when a license is exported for the ALM option. |
|
Node Limit |
The maximum number of nodes that can be added to the A10 Control setup. This field is displayed only for A10 Control and A10 Control ADO licenses. |
|
Current Node Count |
The number of nodes deployed in A10 Control. This helps GLM to track the number of nodes in the setup and usage of Red Hat licenses. The maximum number of nodes supported is 9. |
|
Basic A10 Control (limited upgrade from HC/AG) |
Indicates whether a user has requested for a basic A10 Control license.
|
Click Capacity Update to modify the license capacity. For information, see Organization Scope License Tasks .
This option is applicable only for A10 Control license.

The following license validation statuses are available in the License Information tab:
| Status | Description |
|---|---|
|
Activated |
If the requested license is available and if you have chosen the right capacity, then the license state is activated. |
| Expiring | If the current license is about to expire, a message to renew the license is displayed one month before the expiry date. |
| Expired |
If the current license is expired and a message to renew the license is displayed. |
| Failed | If there is an error in license activation, the license is not available, or the request capacity does not match the criteria, the license state is failed. |
| Grace-Period | If the license has already expired, 30-day grace period is added to the license. You must renew the license before the grace period is over. You can associate or add devices, however you cannot update the license capacity in this period. After license renewal, the A10 Control MBU license will be updated in GLM with a new expiry date. The license expiry date is automatically updated during A10 Control. You do not need to add the token and devices again. |
| NOTE: | A warning message appears on the Licenses page three months before expiry, and on other pages four weeks before expiry. |