<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: connecting to license master from CLI in Splunk Enterprise Security</title>
    <link>https://community.splunk.com/t5/Splunk-Enterprise-Security/connecting-to-license-master-from-CLI/m-p/505726#M8951</link>
    <description>I believe Splunk must be running for the 'edit' command to work.&lt;BR /&gt;I usually do that by putting server.conf in an org_all_license_client app and deploying that app to the new instance.</description>
    <pubDate>Tue, 23 Jun 2020 12:41:06 GMT</pubDate>
    <dc:creator>richgalloway</dc:creator>
    <dc:date>2020-06-23T12:41:06Z</dc:date>
    <item>
      <title>connecting to license master from CLI</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise-Security/connecting-to-license-master-from-CLI/m-p/505718#M8949</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;I'm installing a new splunk instance and need to connect it to our master license server. I used to do this from the web admin page, and learned that it is also possible to do from CLI like&lt;/P&gt;&lt;PRE&gt;splunk edit licenser-localslave -master_uri 'https://master:port'&lt;/PRE&gt;&lt;P&gt;&amp;nbsp;now the question: can I do this before starting splunk first time? The aim is fully automatize the installation, so no manual intervention would be required. What I also have in mind is keeping this setting in server.conf which I feed to splunk after the (rpm) installation and before starting it, but I feel that using CLI is more proper way to do this.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks!&lt;/P&gt;&lt;P&gt;Andrei&lt;/P&gt;</description>
      <pubDate>Tue, 23 Jun 2020 11:54:08 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise-Security/connecting-to-license-master-from-CLI/m-p/505718#M8949</guid>
      <dc:creator>akazarov</dc:creator>
      <dc:date>2020-06-23T11:54:08Z</dc:date>
    </item>
    <item>
      <title>Re: connecting to license master from CLI</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise-Security/connecting-to-license-master-from-CLI/m-p/505726#M8951</link>
      <description>I believe Splunk must be running for the 'edit' command to work.&lt;BR /&gt;I usually do that by putting server.conf in an org_all_license_client app and deploying that app to the new instance.</description>
      <pubDate>Tue, 23 Jun 2020 12:41:06 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise-Security/connecting-to-license-master-from-CLI/m-p/505726#M8951</guid>
      <dc:creator>richgalloway</dc:creator>
      <dc:date>2020-06-23T12:41:06Z</dc:date>
    </item>
    <item>
      <title>Re: connecting to license master from CLI</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise-Security/connecting-to-license-master-from-CLI/m-p/505727#M8952</link>
      <description>&lt;P&gt;Howdy. The CLI requires Splunk to be on.&amp;nbsp;&amp;nbsp;&lt;BR /&gt;Your thought on server.conf is the better way to automate. Since you've seen the cli, just grab the server.conf line that was created and have your script write that out. That way, when you start Splunk, the license master is already set.&lt;/P&gt;</description>
      <pubDate>Tue, 23 Jun 2020 12:42:05 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise-Security/connecting-to-license-master-from-CLI/m-p/505727#M8952</guid>
      <dc:creator>The_Simko</dc:creator>
      <dc:date>2020-06-23T12:42:05Z</dc:date>
    </item>
  </channel>
</rss>

