Splunk® Enterprise

Admin Manual

Download manual as PDF

Download topic as PDF

Manage licenses from the CLI

This topic describes how to use Splunk CLI commands to monitor and manage your licenses. It covers some of the main uses and options of the CLI licensing commands. The definitive reference to any CLI command is the command's online help.

For general information on the Splunk CLI, see "About the CLI".

For information on managing licenses through Splunk's REST API, refer to "Licenses" in the REST API Reference Manual.

CLI license commands and objects

You can use the CLI to add, edit, list, and remove licenses and license-related objects. The available commands are:

Command Object(s) Description
add licenses, licenser-pools Add a license or a pool of licenses to a license stack. This command is only available if you have an Enterprise license.
edit licenser-localslave, licenser-pools Edit the attributes of a license slave or a pool of licenses. This command is only available if you have an Enterprise license.
list licenser-groups, licenser-localslave, licenser-messages, licenser-pools, licenser-slaves, licenser-stacks, licenses Depending on the object specified, lists either the attributes of that object or members of that object.
remove licenser-pools, licenses Remove licenses or license pools from a license stack.

License-related objects are:

Object Description
licenser-groups the different license groups you can switch to.
licenser-localslave a local indexer's configuration.
licenser-messages the alerts or warnings about the state of your licenses.
licenser-pools a pool, or virtual license. A stack can be divided into various pools, with multiple slaves sharing the quota of each pool.
licenser-slaves all the slaves that have contacted the master.
licenser-stacks this object represents a stack of licenses. A stack contains licenses of the same type and are cumulative.
licenses all licenses for this Splunk instance.

Common licenser-related tasks

The following are examples of common licenser-related tasks.

Managing licenses

To add a new license to the license stack, specify the path to the license file:

./splunk add licenses /opt/splunk/etc/licenses/enterprise/enterprise.lic 

To list all the licenses in a license stack:

./splunk list licenses

List also displays the properties of each license, including the features it enables (features), the license group and stack it belongs to (group_id, stack_id), the indexing quote it allows (quota), and the license key that is unique for each license (license_hash).

If a license expires, you can remove it from the license stack. To remove a license from the license stack, specify the license's hash:

./splunk remove licenses BM+S8VetLnQEb1F+5Gwx9rR4M4Y91AkIE=781882C56833F36D

Managing license pools

You can create a license pool from one or more licenses in a license stack (if you have an Enterprise license). Basically, a license stack can be carved up into multiple licenser pools. Each pool can have more than one license slave sharing the quota of the pool.

To see all the license pools in all the license stacks:

./splunk list licenser-pools

To add a license pool to the stack, you need to: name the pool, specify the stack that you want to add it to, and specify the indexing volume allocated to that pool:

./splunk add licenser-pools pool01 -quota 10mb -slaves guid1,guid2 -stack_id enterprise

You can also specify a description for the pool and the slaves that are members of the pool (these are optional).

You can edit the license pool's description, indexing quota, and slaves:

./splunk edit licenser-pools pool01 -description "Test" -quota 15mb -slaves guid3,guid4 -append_slaves true

This basically adds a description for the pool, "Test", changes the quota from 10mb to 15mb, adds slaves guid3 and guid4 to the pool (instead of overwriting or replace guid1 and guid2).

To remove a license pool from a stack, specify the name:

./splunk remove licenser-pools pool01

Managing license slaves

A license slave is a member of one or more license pools. The license slaves access to license volume is controlled by its license master.

To list all the license slaves that have contacted the license master:

./splunk list licenser-slaves

To list all the properties of the local license slave:

./splunk list licenser-localslave

To add a license slave, edit the attributes of that local license slave node (specify the uri of the splunkd license master instance or 'self'):

./splunk edit licenser-localslave -master_uri 'https://master:port'

Monitoring license status

You can use the list command to view messages (alerts or warnings) about the state of your licenses.

./splunk list licenser-messages
Swap the license master
About license violations

This documentation applies to the following versions of Splunk® Enterprise: 6.5.0, 6.5.1, 6.5.1612 (Splunk Cloud only), 6.5.2, 6.5.3, 6.5.4, 6.5.5, 6.5.6, 6.5.7, 6.5.8, 6.5.9, 6.5.10, 6.6.0, 6.6.1, 6.6.2, 6.6.3, 6.6.4, 6.6.5, 6.6.6, 6.6.7, 6.6.8, 6.6.9, 6.6.10, 6.6.11, 6.6.12, 7.0.0, 7.0.1, 7.0.2, 7.0.3, 7.0.4, 7.0.5, 7.0.6, 7.0.7, 7.0.8, 7.0.9, 7.1.0, 7.1.1, 7.1.2, 7.1.3, 7.1.4, 7.1.5, 7.1.6, 7.2.0, 7.2.1, 7.2.2, 7.2.3, 7.2.4, 7.2.5

Was this documentation topic helpful?

Enter your email address, and someone from the documentation team will respond to you:

Please provide your comments here. Ask a question or make a suggestion.

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