<?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: Splunk Architecture with two IP addresses in Splunk Search</title>
    <link>https://community.splunk.com/t5/Splunk-Search/Splunk-Architecture-with-two-IP-addresses/m-p/254812#M189411</link>
    <description>&lt;P&gt;Hi.. As long as you have needed flexibility from Networking  and Systems administration side, the above setup can be done. I don't think there would be big performance advantages (assuming your network is overall well managed) by this. However from a process/implementation standpoint I can see how this might make things better regulated for certain environments. I would imagine this naturally adds a bit to administrative overhead and will also add additional factors to consider when trouble shooting issues (clustering/data loss).&lt;/P&gt;</description>
    <pubDate>Thu, 01 Oct 2015 13:36:53 GMT</pubDate>
    <dc:creator>Yasaswy</dc:creator>
    <dc:date>2015-10-01T13:36:53Z</dc:date>
    <item>
      <title>Splunk Architecture with two IP addresses</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Splunk-Architecture-with-two-IP-addresses/m-p/254811#M189410</link>
      <description>&lt;P&gt;Hi to everyone&lt;/P&gt;

&lt;P&gt;It makes sense to have a Splunk Architecture, with machines with two addresses?&lt;/P&gt;

&lt;P&gt;For example:&lt;/P&gt;

&lt;UL&gt;
&lt;LI&gt;1 Indexer with 1 address for web access, and another address for receive syslog&lt;/LI&gt;
&lt;/UL&gt;

&lt;P&gt;Another example:&lt;/P&gt;

&lt;UL&gt;
&lt;LI&gt;1 indexer with 1 address for web access, and another address for index replication&lt;/LI&gt;
&lt;/UL&gt;

&lt;P&gt;Thanks in advance&lt;/P&gt;

&lt;P&gt;Regards&lt;/P&gt;</description>
      <pubDate>Thu, 01 Oct 2015 12:56:22 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Splunk-Architecture-with-two-IP-addresses/m-p/254811#M189410</guid>
      <dc:creator>rubeniturrieta</dc:creator>
      <dc:date>2015-10-01T12:56:22Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk Architecture with two IP addresses</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Splunk-Architecture-with-two-IP-addresses/m-p/254812#M189411</link>
      <description>&lt;P&gt;Hi.. As long as you have needed flexibility from Networking  and Systems administration side, the above setup can be done. I don't think there would be big performance advantages (assuming your network is overall well managed) by this. However from a process/implementation standpoint I can see how this might make things better regulated for certain environments. I would imagine this naturally adds a bit to administrative overhead and will also add additional factors to consider when trouble shooting issues (clustering/data loss).&lt;/P&gt;</description>
      <pubDate>Thu, 01 Oct 2015 13:36:53 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Splunk-Architecture-with-two-IP-addresses/m-p/254812#M189411</guid>
      <dc:creator>Yasaswy</dc:creator>
      <dc:date>2015-10-01T13:36:53Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk Architecture with two IP addresses</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Splunk-Architecture-with-two-IP-addresses/m-p/254813#M189412</link>
      <description>&lt;P&gt;Ok, thanks you Yasaswy&lt;/P&gt;</description>
      <pubDate>Thu, 01 Oct 2015 13:59:50 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Splunk-Architecture-with-two-IP-addresses/m-p/254813#M189412</guid>
      <dc:creator>rubeniturrieta</dc:creator>
      <dc:date>2015-10-01T13:59:50Z</dc:date>
    </item>
  </channel>
</rss>

