Configure a license master
This topic discusses configuring a Splunk instance as a license master. Before you proceed, you may want to review these topics:
- Read How Splunk licensing works in this manual for an introduction to Splunk licensing.
- Read Groups, stacks, pools, and other terminology in this manual for more information about Splunk license terminology.
Kinds of license masters
There are two types of license master:
- Standalone license master, for a deployment consisting of a single indexer.
- Central license master, for a distributed deployment with multiple indexers.
Standalone license master
If you have a single Splunk indexer, it serves as its own license manager, once you install one or more Enterprise licenses on it. You do not need to further configure it as a license master.
Note: When you first download and install Splunk Enterprise, it includes a 500 MB 60-day Enterprise Trial license. This instance is automatically configured as a standalone license master, and you cannot create a pool or define any license slaves for this type of license. If you want to create one or more stacks or pools and assign multiple indexers to them, you must purchase and install an Enterprise license. To install a license, follow the instructions in Install a license.
Central license master
If you have more than one indexer and you want to manage their access to purchased license capacity from a central location, you must configure a central license master and add the indexers to it as license slaves.
Deploy the central license master
Where to put the license master
The central license master does not usually need to run on a dedicated Splunk Enterprise instance. Instead, you can colocate it on an instance that is also performing other tasks:
- A monitoring console. See Which instance should host the console? in Monitoring Splunk Enterprise for a description of the circumstances under which a monitoring console and a license master can colocate.
- A deployment server. See Deployment server and other roles in Updating Splunk Enterprise Instances for a description of the circumstances under which a deployment server and a license master can colocate.
- An indexer cluster master node. See Additional roles for the master node in Managing Indexers and Clusters of Indexers for a description of the circumstances under which an indexer cluster master node and a license master can colocate.
- A search head cluster deployer. See Deployer requirements in Distributed Search.
- A search head.
- An indexer. If the license master is located on an indexer, it will be that indexer's license master as well.
For a general discussion of management component colocation, see Components that help to manage your deployment in the Distributed Deployment Manual.
License master and slave version compatibility
Compatibility between the master and its slaves requires that their versions follow all of these rules:
- A license master must be of an equal or later version than its license slaves.
- The master version must be at least 6.1.
- The slave version must be at least 6.0.
- A 7.1 master is compatible with 6.0, 6.1, 6.2, 6.3, 6.4, 6.5, 6.6, 7.0, and 7.1 slaves.
- A 6.5 master is compatible with 6.0, 6.1, 6.2, 6.3, 6.4, and 6.5 slaves.
Configure a central license master
To configure the central license master:
- Install one or more Enterprise licenses. See Install a license.
- Create one or more pools to access the installed license. See Create a license pool.
- Configure one or more license slaves. See Configure a license slave.
Now you can manage your licenses from the central license master.
Install a license
Configure a license slave
This documentation applies to the following versions of Splunk® Enterprise: 7.0.0, 7.0.1, 7.0.2, 7.0.3, 7.0.4, 7.1.0