Configure License Manager

In A10 Control, the License Manager defines how licenses are activated, synchronized, and managed.

Depending on your deployment, you can configure one of the following:

• Global License Manager (GLM)
• A10 Control License Manager (ALM)
• Remote A10 Control instance as the Primary License Manager

To configure the license manager:

1. Navigate to A10 Control home page > Controller scope > Platform > License Management > License Manager.

2. Click Edit.

   The License Manager page is displayed.

3. Select and configure one of the following options:
   
   Global License Manager (GLM)

   This is a default option for license management. Licenses are directly retrieved and synchronized with the GLM portal.

   1. Select the following:

      Field	Description
      Device License Config
      Use Management Port	Select to allow all management traffic (license activation, GLM communication, NTP, DNS, SMTP) to flow through the dedicated management interface.

   2. Click Save to confirm the changes.
   A10 Control License Manager (ALM)

   This option is used when you want A10 Control to act as a local license manager.

   1. Following fields are available.

      Field	Description
      License Manager UUID	A unique identifier for the license manager instance. This UUID is used during ALM activation process in GLM. Copy the License Manager UUID.
      Activation String	It is used to activate the ALM in A10 Control. To obtain the Activation String and use it here, see Obtain the Activation String.

   2. Obtain the Activation String: Keep both the GLM Portal and A10 Control instances open and then perform the following steps:

      

      1. Sign in to GLM (ELM Activation page).
      2. In the Activate ELM page, add the following details and click Activate.
         

         Field	Description
         Organization	Select your Organization.
         ELM UUID	Paste the License Manager UUID copied from A10 Control.
         Name	Add the Name.

      3. Navigate to ELM option, click the Copy icon to copy the Activation string or click the Download icon to download the string file.

      4. Return to A10 Control, and on the License Manager page, paste the string into the Activation String field.

   3. Click Activate to enable this license manager.

      A confirmation message, ALM activation is successful, appears.
      After activation, the ALM is ready to import and manage licenses locally.

   4. On the License Manager page, click Edit once again, then click Save to finalize the configuration.

   Use remote A10 Control as Primary License Manager

   This option allows licenses to be centrally managed from a single A10 Control instance when multiple instances are deployed.

   Ensure that at least one A10 Control instance is already configured and activated with ALM. This ALM-enabled instance will act as the Primary License Manager.

   1. Select A10 Control License Manager (ALM) and provide the following:

      • License Manager UUID
      • Activation String
   2. Click Activate to enable this license manager.
   3. On the License Manager page, click Edit once again.
   4. Select Use remote A10 Control as Primary License Manager.

   5. Enter or select the following:

      Field	Description
      Host	IPv4 or IPv6 address of the central license-managing A10 Control instance.
      Port	Communication port of the central license manager (default is typically 443 unless customized).
      Device License Config
      Use Management Port	When selected, all management traffic (license activation, GLM communication, NTP, DNS, SMTP) flows through the dedicated management interface.

   6. Click Save to save the changes.

   Once configured, this instance acts as the primary license manager. It allows multiple A10 Control instances to connect through this host. It centrally handles license distribution and automatically reclaims unused capacity when devices are removed or become inactive.

   NOTE:

   When this option is configured, no license string is stored locally. The A10 Control instances fully depend on the primary license manager instance for all license activations and capacity tracking.

   If successful, a floating notification appears, and the imported license is displayed in the License section.