Splunk® Enterprise

Admin Manual

Download manual as PDF

Download topic as PDF

Swap the license master

You can change the license master by promoting a slave to master and demoting the old master to a slave.

  1. Promote a license slave to master:
    1. On the slave, navigate to Settings > Licensing.
    2. Follow the prompts to configure the instance as a license master.
    3. Restart the instance.
  2. On the new license master, add the license keys:
    1. See Install a license.
    2. Check that the license keys match those in the old license master.
  3. Point the other license slaves to the new license master: On each slave:
    1. Navigate to Settings > Licensing.
    2. Change the master license URI to point to the new license master.
    3. Click Save.
    4. Restart the slave instance..
  4. On one of the license slaves, confirm the connection to the new license master.
  5. Demote the old license master to a slave:
    1. Navigate to Settings > Licensing
    2. Click Change to slave.
    3. Ignore the restart prompt.
    4. Click Designate a different Splunk Enterprise instance as the master license server to point the instance to the new license master.
    5. Stop the instance.
    6. Delete the old license files under $SPLUNK_HOME/etc/licenses/enterprise/.
    7. Start the instance.
    8. Confirm that the instance connects as a slave to the new license master.
Retrieved from "https://docs.splunk.com/index.php?title=Documentation:Splunk:Admin:Swapthelicensemaster:6.0beta&oldid=1022148"
PREVIOUS
Manage your licenses 		  NEXT
Manage licenses from the CLI

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.0.15, 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.1.14, 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.2.15, 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.3.14, 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.4.11, 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.0.10, 7.0.11, 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.1.8, 7.2.0, 7.2.1, 7.2.2, 7.2.3, 7.2.4, 7.2.5, 7.2.6, 7.2.7, 7.2.8, 7.3.0, 7.3.1

Comments

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.

Alisterwhipp
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