Splunk® Enterprise

Admin Manual

Create or edit a license pool

This topic describes how to create or edit a license pool. Before you proceed, read Allocate license volume for general information about allocating license volume across Splunk Enterprise instances.

Note: You can also perform these tasks through the CLI. See Manage licenses from the CLI.

The default license pool

When you first install an Enterprise license on a Splunk Enterprise instance, the instance becomes the license manager for that license. Several default configurations result:

  • The license resides in a license stack called Splunk Enterprise Stack
  • The stack has a default license pool called auto_generated_pool_enterprise.
  • Any license peer that connects to this license manager has access to the default pool.

You can change the set of pools. You can also configure access of license peers to stacks.

The following example shows the Settings > Licensing screen for an Enterprise license.

LicMgmt Note83.png

Edit an existing license pool

You can edit a license pool to change the pool's allocation or to change the set of indexers that have access to the pool.

  1. Next to the license pool that you want to edit, click Edit. The Edit license pool page is displayed.
  2. (Optional) Change the allocation for the pool. The allocation is how much of the stack's overall licensing volume is available for use by the indexers that access this pool. The allocation can be a specific value, or it can be the entire amount of indexing volume available in the stack, as long as it is not already allocated to any other pool.
  3. (Optional) Change the indexers that have access to the pool. The options are:
    1. Any indexer configured as a license peer can access the pool and use the license allocation within it.
    2. Only specific indexers can access the pool and use the license allocation within it. To allow a specific indexer to draw from the pool, click the plus sign next to the name of the indexer in the list of available indexers to move it into the list of associated indexers.
  4. Click Submit.

Once a license pool is created, there's no option to rename the pool using License Management in Splunk Web. To modify the license pool name, you can delete the old pool and create a new pool with the chosen name. Or you can edit the server.conf file, change the pool name in the [lmpool:] stanza, and restart Splunk Enterprise services.

Create a new license pool

Before you can create a new license pool from the default Enterprise stack, you must make some indexing volume available by either editing an existing pool and reducing its allocation, or by deleting an existing pool entirely. Click Delete next to the pool's name to delete it.

To create a new license pool:

  1. Click Add pool toward the bottom of the page. The Create new license pool page is displayed.
  2. Specify a name for the pool, and optionally add a description for the pool.
  3. Set the allocation for the pool. The allocation is how much of the stack's overall licensing volume is available for use by the indexers that access this pool. The allocation can be a specific value, or it can be the entire amount of indexing volume available in the stack, as long as it is not already allocated to any other pool.
  4. Specify the indexers that have access to the pool. The options are:
    1. Any indexer configured as a license peer can access the pool and use the license allocation within it.
    2. Only specific indexers can access the pool and use the license allocation within it. To allow a specific indexer to draw from the pool, click the plus sign next to the name of the indexer in the list of available indexers to move it into the list of associated indexers.
Last modified on 10 December, 2021
Configure a license peer   About Splunk Free

This documentation applies to the following versions of Splunk® Enterprise: 9.0.0, 9.0.1, 9.0.2, 9.0.3, 9.0.4, 9.0.5, 9.0.6, 9.0.7, 9.0.8, 9.0.9, 9.0.10, 9.1.0, 9.1.1, 9.1.2, 9.1.3, 9.1.4, 9.1.5, 9.1.6, 9.1.7, 9.2.0, 9.2.1, 9.2.2, 9.2.3, 9.2.4, 9.3.0, 9.3.1, 9.3.2, 9.4.0


Was this topic useful?







You must be logged into splunk.com in order to post comments. Log in now.

Please try to keep this discussion focused on the content covered in this documentation topic. If you have a more general question about Splunk functionality or are experiencing a difficulty with Splunk, consider posting a question to Splunkbase Answers.

0 out of 1000 Characters