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 Allocate license volume for general information about allocating license volume across Splunk Enterprise instances.
Kinds of license masters
There are two basic styles of license master:
- Standalone license master
- If you have a single Splunk indexer and want to manage its licenses, you can run it as its own license master, install one or more Enterprise licenses on it and it will manage itself as a license slave.
- 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" in this manual.
- Central license master
- If you have more than one indexer and want to manage their access to purchased license capacity from a central location, configure a central license master and add the indexers to it as license slaves.
- If the license master is also an indexer, it will be its own license master as well, but Splunk recommends that if you have a search head, you designate it as the license master.
- If you have a large environment with multiple search heads, you might want to have some or all search heads that are not the license master distribute searches to the license master, for two reasons:
- You can run searches against the license logs.
- If an unusual condition occurs on the search head (for example you have a time-limited license and it will expire in 5 days), this condition will be visible on the search head when running a search, as part of the info messages attached to search results.
License master and slave compatibility
A license master must always be of equal or later version than its license slaves.
|License master version||Compatible license slave versions|
|6.1.x||5.x, 6.0.x, 6.1.x|
|6.2.x||5.x, 6.0.x, 6.1.x, 6.2.x|
|6.3.x||5.x, 6.0.x, 6.1.x, 6.2.x, 6.3.x|
|6.4.x||5.x, 6.0.x, 6.1.x, 6.2.x, 6.3.x, 6.4.x|
|6.5.x||5.x, 6.0.x, 6.1.x, 6.2.x, 6.3.x, 6.4.x, 6.5.x|
|6.6.x||5.x, 6.0.x, 6.1.x, 6.2.x, 6.3.x, 6.4.x, 6.5.x, 6.6.x|
Configure a central license master
By default, a standalone instance of Splunk is its own license master. To configure a central license master, install one or more Enterprise licenses.
Install a license
Configure a license slave
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