<?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: Cluster question in Deployment Architecture</title>
    <link>https://community.splunk.com/t5/Deployment-Architecture/Cluster-question/m-p/354873#M13171</link>
    <description>&lt;P&gt;What you do see in Jacksonville? Do you see Omaha as Peer?&lt;/P&gt;</description>
    <pubDate>Tue, 14 Mar 2017 18:03:14 GMT</pubDate>
    <dc:creator>somesoni2</dc:creator>
    <dc:date>2017-03-14T18:03:14Z</dc:date>
    <item>
      <title>Cluster question</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/Cluster-question/m-p/354870#M13168</link>
      <description>&lt;P&gt;We have a server in Omaha and a server in Jacksonville.&lt;/P&gt;

&lt;P&gt;Currently all items are forwarded to Omaha so when I log into Omaha I can see Omaha and Jacksonville.  When I log into Jacksonville I cant see anything.&lt;/P&gt;

&lt;P&gt;How do I set it so that in Jacksonville I can see Jacksonville.  I don't want to replicate all Omaha indexes to Jacksonville, but I would like to be able to see Jacksonville when logged into Jacksonville.&lt;/P&gt;

&lt;P&gt;Thanks&lt;BR /&gt;
John&lt;/P&gt;</description>
      <pubDate>Tue, 14 Mar 2017 16:00:52 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/Cluster-question/m-p/354870#M13168</guid>
      <dc:creator>dolejh76</dc:creator>
      <dc:date>2017-03-14T16:00:52Z</dc:date>
    </item>
    <item>
      <title>Re: Cluster question</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/Cluster-question/m-p/354871#M13169</link>
      <description>&lt;P&gt;Does your search head has both Omaha and Jacksonville indexers added as Search Peer? &lt;/P&gt;</description>
      <pubDate>Tue, 14 Mar 2017 16:03:01 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/Cluster-question/m-p/354871#M13169</guid>
      <dc:creator>somesoni2</dc:creator>
      <dc:date>2017-03-14T16:03:01Z</dc:date>
    </item>
    <item>
      <title>Re: Cluster question</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/Cluster-question/m-p/354872#M13170</link>
      <description>&lt;P&gt;Logged into Omaha - I see Jax as a Peer, and Omaha as a search head.&lt;/P&gt;</description>
      <pubDate>Tue, 14 Mar 2017 17:41:58 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/Cluster-question/m-p/354872#M13170</guid>
      <dc:creator>dolejh76</dc:creator>
      <dc:date>2017-03-14T17:41:58Z</dc:date>
    </item>
    <item>
      <title>Re: Cluster question</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/Cluster-question/m-p/354873#M13171</link>
      <description>&lt;P&gt;What you do see in Jacksonville? Do you see Omaha as Peer?&lt;/P&gt;</description>
      <pubDate>Tue, 14 Mar 2017 18:03:14 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/Cluster-question/m-p/354873#M13171</guid>
      <dc:creator>somesoni2</dc:creator>
      <dc:date>2017-03-14T18:03:14Z</dc:date>
    </item>
    <item>
      <title>Re: Cluster question</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/Cluster-question/m-p/354874#M13172</link>
      <description>&lt;P&gt;If I log into Jax - I just see - Clustering: Peer Node and Jax.&lt;/P&gt;</description>
      <pubDate>Tue, 14 Mar 2017 18:12:07 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/Cluster-question/m-p/354874#M13172</guid>
      <dc:creator>dolejh76</dc:creator>
      <dc:date>2017-03-14T18:12:07Z</dc:date>
    </item>
    <item>
      <title>Re: Cluster question</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/Cluster-question/m-p/354875#M13173</link>
      <description>&lt;P&gt;Sounds like you need to add Omaha as a search peer on the Jax machine. &lt;/P&gt;</description>
      <pubDate>Wed, 15 Mar 2017 05:29:41 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/Cluster-question/m-p/354875#M13173</guid>
      <dc:creator>mrgibbon</dc:creator>
      <dc:date>2017-03-15T05:29:41Z</dc:date>
    </item>
    <item>
      <title>Re: Cluster question</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/Cluster-question/m-p/354876#M13174</link>
      <description>&lt;P&gt;Sounds to me like you are not indexing in Jacksonville, you are just forwarding events. &lt;/P&gt;

&lt;P&gt;You either need to index and forward events from Jacksonville, or you need setup distributed search from the Jacksonville instance(s).&lt;/P&gt;

&lt;P&gt;Read this : &lt;A href="https://docs.splunk.com/Documentation/Splunk/6.5.2/DistSearch/Configuredistributedsearch"&gt;https://docs.splunk.com/Documentation/Splunk/6.5.2/DistSearch/Configuredistributedsearch&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;What you want to do is add the Omaha indexer as a peer to Jacksonville. Be aware there are some bandwidth and latency issues to be considerate of...&lt;/P&gt;</description>
      <pubDate>Wed, 15 Mar 2017 05:45:10 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/Cluster-question/m-p/354876#M13174</guid>
      <dc:creator>esix_splunk</dc:creator>
      <dc:date>2017-03-15T05:45:10Z</dc:date>
    </item>
    <item>
      <title>Re: Cluster question</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/Cluster-question/m-p/354877#M13175</link>
      <description>&lt;P&gt;Ill take a look - thanks&lt;/P&gt;</description>
      <pubDate>Wed, 15 Mar 2017 13:03:14 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/Cluster-question/m-p/354877#M13175</guid>
      <dc:creator>dolejh76</dc:creator>
      <dc:date>2017-03-15T13:03:14Z</dc:date>
    </item>
  </channel>
</rss>

