Monitoring Splunk

How to configure a license slave when the GUI won't allow access to Settings?

grantlindley
New Member

Splunk Community Edit: 

Institutionalized bias is the concept that people and organizations unintentionally support negative stereotypes through their behavior. Institutionalized bias has no place in our products, our documentation, our language or our actions. We know that words have meanings beyond their dictionary definitions, and organizations must also strive to consider the experiences of everyone. 

Back in June 2020, Splunk announced our commitment to removing biased language in our products, documentation and language. You may see older posts in the Splunk Community or other Splunk properties that may refer to older versions of Splunk and may contain biased terminology which has since been removed or replaced. These pages are made available solely for the purpose of preserving Splunk knowledge that users may still find useful or provide historical context. Splunk is still committed to using our words and actions to help promote equity wherever we can.

More Resources:

------------------

This is for splunk 7.3.3 enterprise on Win 2012 server.

In order to connect a slave to a license manager, an admin user would normally go to Settings > Licensing and select Change to Slave.

However, my splunk instance has an expired license, and won't allow access to anything from the GUI, giving only options to Add License or Get License. And neither of these options allows the configuration of a slave.

If it was Splunk LIght, I could get a free license, then switch to the license manager. Since it is Enterprise, I do not have that option.

Labels (1)
0 Karma
1 Solution

MuS
Legend

Hi grantlindley,

the easiest option would be to modify server.conf on that server and restart Splunk. See the docs for details https://docs.splunk.com/Documentation/Splunk/latest/admin/serverconf#License_manager_settings_for_co...

or use the CLI command splunk edit licenser-localslave -master_uri https://YourLicenseMaster:8089 see the docs https://docs.splunk.com/Documentation/Splunk/latest/Admin/CLIadmincommands#Commands.2C_objects.2C_an... for details

Hope this helps ...

cheers, MuS

View solution in original post

MuS
Legend

Hi grantlindley,

the easiest option would be to modify server.conf on that server and restart Splunk. See the docs for details https://docs.splunk.com/Documentation/Splunk/latest/admin/serverconf#License_manager_settings_for_co...

or use the CLI command splunk edit licenser-localslave -master_uri https://YourLicenseMaster:8089 see the docs https://docs.splunk.com/Documentation/Splunk/latest/Admin/CLIadmincommands#Commands.2C_objects.2C_an... for details

Hope this helps ...

cheers, MuS

grantlindley
New Member

The CLI did the trick. Thanks!

0 Karma
Get Updates on the Splunk Community!

Splunk Observability Cloud’s AI Assistant in Action Series: Analyzing and ...

This is the second post in our Splunk Observability Cloud’s AI Assistant in Action series, in which we look at ...

Elevate Your Organization with Splunk’s Next Platform Evolution

 Thursday, July 10, 2025  |  11AM PDT / 2PM EDT Whether you're managing complex deployments or looking to ...

Splunk Answers Content Calendar, June Edition

Get ready for this week’s post dedicated to Splunk Dashboards! We're celebrating the power of community by ...