<?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: Licensing issue in Installation</title>
    <link>https://community.splunk.com/t5/Installation/Licensing-issue/m-p/238851#M8970</link>
    <description>&lt;P&gt;Hi hunters,&lt;/P&gt;

&lt;P&gt;Thank you.&lt;BR /&gt;
May I know why cluster master not recommended as license master?&lt;/P&gt;

&lt;P&gt;kyawsoenaing&lt;/P&gt;</description>
    <pubDate>Wed, 18 Jan 2017 00:36:46 GMT</pubDate>
    <dc:creator>kyawsoenaing</dc:creator>
    <dc:date>2017-01-18T00:36:46Z</dc:date>
    <item>
      <title>Licensing issue</title>
      <link>https://community.splunk.com/t5/Installation/Licensing-issue/m-p/238849#M8968</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;

&lt;P&gt;I need some advise. &lt;/P&gt;

&lt;P&gt;Currently I in mid of migration and getting license issue in 3 new index servers.&lt;BR /&gt;
My environment as below.&lt;BR /&gt;
Current splunk server are stand alone with all in one. New splunk servers implement as one master node and 3 indexers.&lt;BR /&gt;
I have some servers data have been index to new 3 indexers. &lt;BR /&gt;
Currently i have add the search peer at Current server to new 3 indexers.&lt;BR /&gt;
I would like to assign license to new 3 indexers.&lt;BR /&gt;
Current I have 2 licenses. First one is using in current server and second one is not using yet(for future used for DR server). &lt;/P&gt;

&lt;P&gt;My question as below.&lt;BR /&gt;
- Should I add license manager role to new  master node server and add second license then create license pool to add current and 3 new indexers? After migration, I will put back first license.&lt;BR /&gt;
- Should I add license manager role to new  master node server and add second license then create license pool to add 3 new indexers?&lt;BR /&gt;
- Should I create license pool at current server and add in current server and 3 new index servers?&lt;BR /&gt;
-Any other way should I need to do?&lt;/P&gt;

&lt;P&gt;Thank you.&lt;/P&gt;</description>
      <pubDate>Sun, 15 Jan 2017 19:20:39 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Installation/Licensing-issue/m-p/238849#M8968</guid>
      <dc:creator>kyawsoenaing</dc:creator>
      <dc:date>2017-01-15T19:20:39Z</dc:date>
    </item>
    <item>
      <title>Re: Licensing issue</title>
      <link>https://community.splunk.com/t5/Installation/Licensing-issue/m-p/238850#M8969</link>
      <description>&lt;P&gt;Hi kyawsoenaing, &lt;/P&gt;

&lt;P&gt;Please note that all cluster members must share: &lt;BR /&gt;
- The same licensing pool&lt;BR /&gt;
- The same licensing configuration&lt;BR /&gt;
So, your cluster master and three indexers should be in the same licensing pool. &lt;BR /&gt;
Also, Splunk recommends that you dedicate a host for each role, but you can enable multiple Splunk server roles -  license master, deployer, deployment server - on a server with caveats. &lt;BR /&gt;
I suggest the following license migration steps: &lt;BR /&gt;
1. install a new Splunk instance on a server or VM as a dedicated license master. To add a license to a License Master, run: &lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;splunk add licenses {path_to_license_file}
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;OL&gt;
&lt;LI&gt;&lt;P&gt;Switch the license master and three indexers to a license slave. Run this command on each slave. &lt;/P&gt;

&lt;P&gt;splunk edit licenser-localslave -master_uri https://{Lic_Master:Mport}&lt;/P&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;P&gt;To check the list of license slaves, run this command on the license master: &lt;/P&gt;

&lt;P&gt;splunk list licenser-slaves&lt;/P&gt;&lt;/LI&gt;
&lt;/OL&gt;

&lt;P&gt;Of course, if you really want to also use the cluster master as a license master, I think you can, but it's not recommended. As to the second license, you can stack onto your first license on your license master. &lt;BR /&gt;
Hope this helps. Thanks! &lt;BR /&gt;
Hunter&lt;/P&gt;</description>
      <pubDate>Tue, 29 Sep 2020 12:23:10 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Installation/Licensing-issue/m-p/238850#M8969</guid>
      <dc:creator>hunters_splunk</dc:creator>
      <dc:date>2020-09-29T12:23:10Z</dc:date>
    </item>
    <item>
      <title>Re: Licensing issue</title>
      <link>https://community.splunk.com/t5/Installation/Licensing-issue/m-p/238851#M8970</link>
      <description>&lt;P&gt;Hi hunters,&lt;/P&gt;

&lt;P&gt;Thank you.&lt;BR /&gt;
May I know why cluster master not recommended as license master?&lt;/P&gt;

&lt;P&gt;kyawsoenaing&lt;/P&gt;</description>
      <pubDate>Wed, 18 Jan 2017 00:36:46 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Installation/Licensing-issue/m-p/238851#M8970</guid>
      <dc:creator>kyawsoenaing</dc:creator>
      <dc:date>2017-01-18T00:36:46Z</dc:date>
    </item>
    <item>
      <title>Re: Licensing issue</title>
      <link>https://community.splunk.com/t5/Installation/Licensing-issue/m-p/238852#M8971</link>
      <description>&lt;P&gt;Well, mostly for cluster master performance reasons. Actually, if you are planning a central license master, Splunk recommends that if you have a search head, you designate it as the license master.  See details here: &lt;A href="http://docs.splunk.com/Documentation/Splunk/6.5.1/Admin/Configurealicensemaster#Kinds_of_license_masters"&gt;http://docs.splunk.com/Documentation/Splunk/6.5.1/Admin/Configurealicensemaster#Kinds_of_license_masters&lt;/A&gt;. &lt;BR /&gt;
Thanks! &lt;/P&gt;</description>
      <pubDate>Wed, 18 Jan 2017 01:30:50 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Installation/Licensing-issue/m-p/238852#M8971</guid>
      <dc:creator>hunters_splunk</dc:creator>
      <dc:date>2017-01-18T01:30:50Z</dc:date>
    </item>
  </channel>
</rss>

