Splunk® Enterprise

Admin Manual

Download manual as PDF

Download topic as PDF

Swap the license master

This procedure assumes that you have already configured a license pool. What if you want to turn one of your license slaves into your pool's license master?

This topic spells out the steps to do that. Big picture, first you promote a slave to master. Then you demote the old master to a slave. Details follow.

1. Remove the new license master from the licensing pool and set it up as a master.

2. On the new license master, add the license keys. Check that the license keys match up to the old license master.

3. Make the other license slaves in the pool point to the new license master.

  • On each of the slaves, navigate to Settings > Licensing.
  • Change the master license server URI to refer to the new license master and click Save.
  • Restart Splunk on the license slave whose entry you just updated.

4. Check that one of the license slaves is connected to the new license master.

5. Demote the old license master to a slave:

  • On the old license master, navigate to Settings > Licensing > Change to slave.
  • Ignore the restart prompt.
  • On the "Change to slave" screen, point the new slave to the new license master by clicking Designate a different Splunk Enterprise instance as the master license server.

6. On the new license slave, stop Splunk Enterprise and delete the old license file(s) under the /opt/splunk/etc/licenses/enterprise/ folder. (Otherwise you'll have duplicate licenses and will get errors and/or warnings.)

7. On the new license slave, start Splunk Enterprise and confirm that it connects to the new license master.

About license violations
About the Splunk Enterprise license usage report view

This documentation applies to the following versions of Splunk® Enterprise: 6.0, 6.0.1, 6.0.2, 6.0.3, 6.0.4, 6.0.5, 6.0.6, 6.0.7, 6.0.8, 6.0.9, 6.0.10, 6.0.11, 6.0.12, 6.0.13, 6.0.14, 6.1, 6.1.1, 6.1.2, 6.1.3, 6.1.4, 6.1.5, 6.1.6, 6.1.7, 6.1.8, 6.1.9, 6.1.10, 6.1.11, 6.1.12, 6.1.13, 6.2.0, 6.2.1, 6.2.2, 6.2.3, 6.2.4, 6.2.5, 6.2.6, 6.2.7, 6.2.8, 6.2.9, 6.2.10, 6.2.11, 6.2.12, 6.2.13, 6.2.14, 6.3.0, 6.3.1, 6.3.2, 6.3.3, 6.3.4, 6.3.5, 6.3.6, 6.3.7, 6.3.8, 6.3.9, 6.3.10, 6.3.11, 6.3.12, 6.3.13, 6.4.0, 6.4.1, 6.4.2, 6.4.3, 6.4.4, 6.4.5, 6.4.6, 6.4.7, 6.4.8, 6.4.9, 6.4.10, 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.6.0, 6.6.1, 6.6.2, 6.6.3, 6.6.4, 6.6.5, 6.6.6, 6.6.7, 7.0.0, 7.0.1, 7.0.2, 7.0.3, 7.1.0


Because of the pass4SymmKey from the general section of server.conf, this doesn't work as a process.
You'd need to set the general pass4SymmKey on the new license master (via conf file and reboot, there doesn't seem to be any cli or GUI options). Then do the same on each client (indexers etc), before attempting to set the new license master. Then reboot again.

March 6, 2017

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