Configure a license master
This topic discusses configuring a Splunk Enterprise instance as a license master. Before you proceed, you may want to review these topics:
- Read How Splunk licensing works for an introduction to Splunk licensing.
- Read Allocate license volume for general information about allocating license volume across Splunk Enterprise instances.
Kinds of license masters
There are two types of license master:
- Standalone license master, for a deployment consisting of a single Splunk Enterprise instance.
- Central license master, for a distributed deployment consisting of multiple Splunk Enterprise instances.
Standalone license master
If you have a single Splunk Enterprise instance, it serves as its own license manager, once you install an Enterprise license on it. You do not need to further configure it as a license master.
Central license master
If you have multiple Splunk Enterprise instances, you usually want to manage their license access from a central location.To do this, you must configure one instance as a central license master. You then designate each of the remaining Splunk Enterprise instances as license slaves of the license master.
Deploy the central license master
Where to put the license master
The 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.
Compatibility is significant at the major/minor release level, but not at the maintenance level. For example, a 6.3 license master is not compatible with a 6.4 license slave, because the 6.3 license master is at a lower minor release level than the 6.4 license slave. However, a 6.3.1 license master is compatible with a 6.3.3 license slave, despite the lower maintenance release level of the license master.
Configure a license master
To configure the license master:
- Install Enterprise licenses. See Install a license.
- Configure license slaves. See Configure a license slave.
- Create pools to allocate the installed license. See Create a license pool.
Now you can manage your licenses from the 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.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.1.7, 7.2.0, 7.2.1, 7.2.2, 7.2.3, 7.2.4, 7.2.5, 7.2.6