Creating and Managing Licensing Pools

 

Starting with ArubaOS 8.0.1, centralized licensing is supported on standalone controllers, and is enabled by default. Standalone controllers running ArubaOS 8.0.0 require that licenses are directly to that individual controller using the license add command.

Before you Begin

If your network includes a controller running an earlier version of ArubaOS that supported the installation of licenses directly on that device, make a note of the licenses installed on that legacy device before you upgrade to ArubaOS 8.0 or later. If you add that controller as a managed device under a Mobility Master, those locally installed licenses will become inactive and you will need to regenerate those keys and reinstall them via the Mobility Master.

This section contains the following information:

Adding a Sharable License to the Global License Pool
Creating and Managing a Local License pool
Adding an Individual (non-Sharable) license to a Managed Device

Adding a Sharable License to the Global License Pool

The following steps describe the procedure to add a sharable license to the global licensing pool on a Mobility Master.

 

When adding a license, you must enable the global licensing pool in the WebUI, or issue the licensing-pool-profile-root command to enable licensing features using the command-line interface before that license can be used. For more information on the specific commands to enable individual license types, see Creating and Managing a Local License pool.

Using the WebUI

To add a license via the Mobility Master WebUI:

1. In the Mobility Master node hierarchy, navigate to Configuration > System > Licensing.
2. Click the Mobility Master Licenses subtab.
3. Click + below the Key table. The Install Licenses window appears.
4. In the Install Licenses window, enter the license keyfor one or more licenses. Each license key must be on a separate line.
5. Click OK.
6. Click Apply.
7. Click Pending Changes.
8. In the Pending Changes window, select the check box and click Deploy changes.

Using the CLI

From any configuration node, issue the command license add <key>.

Example:

(host)[mynode](config) #license add lnZSpC2vkLMlJw8KVYdgj2

Creating and Managing a Local License pool

When you add a local license pool to a configuration node, those licenses in that local pool are reserved for that configuration node, and usable only for managed devices at or below the level of configuration.

 

For an overview of global and local license pool usage, see Licensing Pools Overview.

Using the WebUI

1. In the Mobility Master node hierarchy, navigate to Configuration > System > Licensing.
2. Select the Usage sub-tab. The License Usage table appears, showing the numbers of licenses currently used for each Mobility Master configuration node.
3. Select the configuration node for which you want to create a local license pool.
4. Select Enable Local License Pool. Another table appears below the License Usage table, showing the numbers of sharable licenses currently allocated to that license pool. If this is the first time you have enabled a local license pool on this configuration node, this table shows zero allocated licenses for all license types.
5. Click the allocated licenses value for any license type to change the number of licenses in that license pool. The Allocate Licenses window opens, displaying the number of available licenses that are free to be allocated to a local pool.
6. Enter the number of permanent and/or evaluation licenses to be added to the selected pool, then click Done.
7. Repeat steps 6-7 as required to allocate licenses for other license types.

Figure 1  Allocating Licenses for a Global License Pool

8. Click Apply.
9. Click Pending Changes.
10. In the Pending Changes window, select the check box and click Deploy changes.

 

Starting with ArubaOS 8.0.1, the Global License Pool table displays license usage statistics for each configuration pool, as well as the license usage for the devices associated to those license pools. In ArubaOS 8.0.0, the Global license pool table does not display license usage data at the device level.

Using the CLI

Navigate to the configuration node for which you want to add a local configuration pool, and issue the following command:

license-pool-profile <node-path> [acr-licenses {eval key <key> <num>}|<num>][ap-licenses {eval key <key> <num>}|<num>][mm-license {eval key <key> <num>}|<num>][pefng-licenses {eval key <key> <num>}|<num>][rfp-licenses {eval key <key> <num>}|<num>][webcc-licenses {eval key <key> <num>}|{subscript key <key> <num>}][xsc-licenses [{eval key <key> <num>}|<num>]

Example:

(host)[mm] (config) #license-pool-profile /group/config

(host) [mm] (License pool profile "/group/config") #ap-licenses 64

 

After you create the license pool, you must issue the license-pool-profile-root command to enable shared license features within the global licensing pool.

(host) [mm](config) #license-pool-profile-root

(host) [mm](License root(/) pool profile) #acr-license-enable

 

The AP, Mobility Master (MM), virtual mobility controller (VMC) licenses are automatically for their specific device type. These licenses do not need to be enabled within the global licensing pool.

 

Adding an Individual (non-Sharable) license to a Managed Device

Non-sharable licenses are generated using the serial number of a specific device, and can only be assigned to the device for which they were created. A non-sharable license is associated to an individual managed device using the Mobility Master WebUI or command-line interfaces.

Using the WebUI

To add a license via the Mobility Master WebUI:

1. In the Mobility Master node hierarchy, navigate to Configuration > System > Licensing.
2. Select the Controller Licenses subtab.
3. Select the managed device to which you want to add a license.
4. The Licenses table appears, showing the licenses currently associated to that device.
5. Click + below the Licenses table.
6. Enter the serial number for one or more licenses. Each license key must be on a separate line.
7. Click OK.
8. Click Apply.
9. Click Pending Changes.
10. In the Pending Changes window, select the check box and click Deploy changes.

Using the CLI

Navigate to the configuration for the managed device for which you want to add a license, then issue the command license add <key>.

Example:

(host)[group/node/managed-node-14]#license add lnZSpC2vkLMlJw8KVYdgj2