<?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: Universal forwarder is not working as an intermediate forwarder. in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Universal-forwarder-is-not-working-as-an-intermediate-forwarder/m-p/93627#M19456</link>
    <description>&lt;P&gt;It works. So it's just the CLI bug. Thanks.&lt;/P&gt;</description>
    <pubDate>Thu, 02 Feb 2012 14:19:35 GMT</pubDate>
    <dc:creator>asingla</dc:creator>
    <dc:date>2012-02-02T14:19:35Z</dc:date>
    <item>
      <title>Universal forwarder is not working as an intermediate forwarder.</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Universal-forwarder-is-not-working-as-an-intermediate-forwarder/m-p/93623#M19452</link>
      <description>&lt;P&gt;I have the below deployment topology&lt;/P&gt;

&lt;P&gt;Program -&amp;gt; Universal Forwarder (UF1) -&amp;gt; Universal Forwarder (UF2) (Intermediate) -&amp;gt; Main Indexer&lt;/P&gt;

&lt;P&gt;'-&amp;gt;' the flow of TCP message originated from the Program.&lt;/P&gt;

&lt;P&gt;I don't see the messages reaching to the main indexer.&lt;/P&gt;

&lt;P&gt;Main Indexer is installed on host3 and listening on 44444.&lt;/P&gt;

&lt;P&gt;I used command lines to configure the universal forwarders as below&lt;/P&gt;

&lt;P&gt;UF2  in installed on host2 and configure to listen on 33333 for tcp messages and forwarding to main indexer.&lt;/P&gt;

&lt;P&gt;1) splunk add tcp 33333&lt;/P&gt;

&lt;P&gt;2) splunk add forwarder-server host3:44444&lt;/P&gt;

&lt;P&gt;UF1 is installed on host1 and configure to listen on 22222 for tcp messages and forwarding to universal forwarder installed on host2.&lt;/P&gt;

&lt;P&gt;1) splunk add tcp 22222&lt;/P&gt;

&lt;P&gt;2) splunk add forwarder-server host2:33333&lt;/P&gt;

&lt;P&gt;My program is sending tcp message to UF1 and I don't see that message reaching all the way to main indexer. FYI, If I configure UF1/UF2 to directly send messages to main indexer , that works for me.&lt;/P&gt;</description>
      <pubDate>Tue, 18 Oct 2011 15:24:34 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Universal-forwarder-is-not-working-as-an-intermediate-forwarder/m-p/93623#M19452</guid>
      <dc:creator>asingla</dc:creator>
      <dc:date>2011-10-18T15:24:34Z</dc:date>
    </item>
    <item>
      <title>Re: Universal forwarder is not working as an intermediate forwarder.</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Universal-forwarder-is-not-working-as-an-intermediate-forwarder/m-p/93624#M19453</link>
      <description>&lt;P&gt;You need to make UF2 a receiver for data getting forwarded from UF1.  To enable it, use this command:&lt;/P&gt;

&lt;P&gt;./splunk enable listen &lt;PORT&gt; -auth &lt;USERNAME&gt;:&lt;PASSWORD&gt;&lt;/PASSWORD&gt;&lt;/USERNAME&gt;&lt;/PORT&gt;&lt;/P&gt;

&lt;P&gt;In your case, &lt;PORT&gt; would be 33333.&lt;/PORT&gt;&lt;/P&gt;

&lt;P&gt;See this topic for more details:&lt;/P&gt;

&lt;P&gt;&lt;A href="http://docs.splunk.com/Documentation/Splunk/latest/Deploy/Enableareceiver"&gt;http://docs.splunk.com/Documentation/Splunk/latest/Deploy/Enableareceiver&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 18 Oct 2011 18:04:57 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Universal-forwarder-is-not-working-as-an-intermediate-forwarder/m-p/93624#M19453</guid>
      <dc:creator>Steve_G_</dc:creator>
      <dc:date>2011-10-18T18:04:57Z</dc:date>
    </item>
    <item>
      <title>Re: Universal forwarder is not working as an intermediate forwarder.</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Universal-forwarder-is-not-working-as-an-intermediate-forwarder/m-p/93625#M19454</link>
      <description>&lt;P&gt;That's what I tired at the first place. &lt;BR /&gt;
./splunk enable listen 33333&lt;/P&gt;

&lt;P&gt;Bit I got a command error:&lt;/P&gt;

&lt;P&gt;Command error: The subcommand 'listen' is not valid for command 'enable'.&lt;/P&gt;

&lt;P&gt;Looks like this command is not supported in Universal Forwarder.&lt;/P&gt;

&lt;P&gt;So I thought that I would just add a tcp listener instead.&lt;/P&gt;</description>
      <pubDate>Tue, 18 Oct 2011 18:21:00 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Universal-forwarder-is-not-working-as-an-intermediate-forwarder/m-p/93625#M19454</guid>
      <dc:creator>asingla</dc:creator>
      <dc:date>2011-10-18T18:21:00Z</dc:date>
    </item>
    <item>
      <title>Re: Universal forwarder is not working as an intermediate forwarder.</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Universal-forwarder-is-not-working-as-an-intermediate-forwarder/m-p/93626#M19455</link>
      <description>&lt;P&gt;Try adding this stanza to the inputs.conf file on UF2: &lt;/P&gt;

&lt;P&gt;[splunktcp://33333]&lt;/P&gt;</description>
      <pubDate>Tue, 18 Oct 2011 18:59:02 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Universal-forwarder-is-not-working-as-an-intermediate-forwarder/m-p/93626#M19455</guid>
      <dc:creator>Steve_G_</dc:creator>
      <dc:date>2011-10-18T18:59:02Z</dc:date>
    </item>
    <item>
      <title>Re: Universal forwarder is not working as an intermediate forwarder.</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Universal-forwarder-is-not-working-as-an-intermediate-forwarder/m-p/93627#M19456</link>
      <description>&lt;P&gt;It works. So it's just the CLI bug. Thanks.&lt;/P&gt;</description>
      <pubDate>Thu, 02 Feb 2012 14:19:35 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Universal-forwarder-is-not-working-as-an-intermediate-forwarder/m-p/93627#M19456</guid>
      <dc:creator>asingla</dc:creator>
      <dc:date>2012-02-02T14:19:35Z</dc:date>
    </item>
  </channel>
</rss>

