<?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: Is it possible to have multiple license managers behind a load balancer? in Deployment Architecture</title>
    <link>https://community.splunk.com/t5/Deployment-Architecture/Is-it-possible-to-have-multiple-license-managers-behind-a-load/m-p/677354#M27903</link>
    <description>&lt;P&gt;I suspect multiple LMs will cause issues.&lt;/P&gt;&lt;P&gt;There's no real need for more than a single LM.&amp;nbsp; If the LM goes away, the clients will continue to function normally for a few days - which should be more than enough time to stand up a new LM.&lt;/P&gt;</description>
    <pubDate>Tue, 13 Feb 2024 00:51:36 GMT</pubDate>
    <dc:creator>richgalloway</dc:creator>
    <dc:date>2024-02-13T00:51:36Z</dc:date>
    <item>
      <title>Is it possible to have multiple license managers behind a load balancer?</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/Is-it-possible-to-have-multiple-license-managers-behind-a-load/m-p/677345#M27902</link>
      <description>&lt;P&gt;I wasn't sure if having multiple different license managers would cause any violations.&amp;nbsp; Ideally we really do not like the idea of having a single point of failure for our license manager, and are looking to implement redundancy.&amp;nbsp; Is this possible or will it cause issues?&lt;/P&gt;</description>
      <pubDate>Mon, 12 Feb 2024 22:08:23 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/Is-it-possible-to-have-multiple-license-managers-behind-a-load/m-p/677345#M27902</guid>
      <dc:creator>briancronrath</dc:creator>
      <dc:date>2024-02-12T22:08:23Z</dc:date>
    </item>
    <item>
      <title>Re: Is it possible to have multiple license managers behind a load balancer?</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/Is-it-possible-to-have-multiple-license-managers-behind-a-load/m-p/677354#M27903</link>
      <description>&lt;P&gt;I suspect multiple LMs will cause issues.&lt;/P&gt;&lt;P&gt;There's no real need for more than a single LM.&amp;nbsp; If the LM goes away, the clients will continue to function normally for a few days - which should be more than enough time to stand up a new LM.&lt;/P&gt;</description>
      <pubDate>Tue, 13 Feb 2024 00:51:36 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/Is-it-possible-to-have-multiple-license-managers-behind-a-load/m-p/677354#M27903</guid>
      <dc:creator>richgalloway</dc:creator>
      <dc:date>2024-02-13T00:51:36Z</dc:date>
    </item>
    <item>
      <title>Re: Is it possible to have multiple license managers behind a load balancer?</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/Is-it-possible-to-have-multiple-license-managers-behind-a-load/m-p/677378#M27906</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/207387"&gt;@briancronrath&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;&lt;P&gt;as&amp;nbsp;&lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/213957"&gt;@richgalloway&lt;/a&gt;&amp;nbsp;said, License Manager, as the other Splunk management consoles aren't Single Point of Failuer because the infrastructure will continue to run even if the License Manager is down.&lt;/P&gt;&lt;P&gt;You eventually can have a turned off copy in a disaster recovery site, if the down is longer but it isn't mandatory.&lt;/P&gt;&lt;P&gt;Ciao.&lt;/P&gt;&lt;P&gt;Giuseppe&lt;/P&gt;</description>
      <pubDate>Tue, 13 Feb 2024 09:31:22 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/Is-it-possible-to-have-multiple-license-managers-behind-a-load/m-p/677378#M27906</guid>
      <dc:creator>gcusello</dc:creator>
      <dc:date>2024-02-13T09:31:22Z</dc:date>
    </item>
  </channel>
</rss>

