<?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 Trouble with TA-Juniper in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Trouble-with-TA-Juniper/m-p/33120#M5916</link>
    <description>&lt;P&gt;I have a Juniper firewall that forwards syslog/udp:514 data from a forwarder to an indexer in one of my 2 production data centers (DC1 and DC2)&lt;/P&gt;

&lt;P&gt;I have installed the TA-Juniper app on each of the indexers thru a deployment server and they are setup identically.&lt;/P&gt;

&lt;P&gt;However the app is working correctly in DC1 and &lt;STRONG&gt;NOT&lt;/STRONG&gt; in DC2.&lt;/P&gt;

&lt;P&gt;The app exists in the same location and there are no networking issues between the forwarder/indexer or search head.&lt;/P&gt;

&lt;P&gt;On the indexer that is &lt;STRONG&gt;NOT&lt;/STRONG&gt; working I've run:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;./splunk cmd btool transforms list --debug | grep TA-juniper | more./splunk cmd btool transforms list --debug | grep TA-juniper | more
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;and confirmed that the transforms are in place and the app is enabled.&lt;/P&gt;

&lt;P&gt;Data from the forwarder in DC2 is being received at the indexer but is defaulting to the syslog sourcetype. It's like the indexer is completely ignoring the TA-juniper app?&lt;/P&gt;

&lt;P&gt;I've restarted the indexer a couple of times with no change in behavior.&lt;/P&gt;</description>
    <pubDate>Mon, 12 Dec 2011 16:11:15 GMT</pubDate>
    <dc:creator>Kate_Lawrence-G</dc:creator>
    <dc:date>2011-12-12T16:11:15Z</dc:date>
    <item>
      <title>Trouble with TA-Juniper</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Trouble-with-TA-Juniper/m-p/33120#M5916</link>
      <description>&lt;P&gt;I have a Juniper firewall that forwards syslog/udp:514 data from a forwarder to an indexer in one of my 2 production data centers (DC1 and DC2)&lt;/P&gt;

&lt;P&gt;I have installed the TA-Juniper app on each of the indexers thru a deployment server and they are setup identically.&lt;/P&gt;

&lt;P&gt;However the app is working correctly in DC1 and &lt;STRONG&gt;NOT&lt;/STRONG&gt; in DC2.&lt;/P&gt;

&lt;P&gt;The app exists in the same location and there are no networking issues between the forwarder/indexer or search head.&lt;/P&gt;

&lt;P&gt;On the indexer that is &lt;STRONG&gt;NOT&lt;/STRONG&gt; working I've run:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;./splunk cmd btool transforms list --debug | grep TA-juniper | more./splunk cmd btool transforms list --debug | grep TA-juniper | more
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;and confirmed that the transforms are in place and the app is enabled.&lt;/P&gt;

&lt;P&gt;Data from the forwarder in DC2 is being received at the indexer but is defaulting to the syslog sourcetype. It's like the indexer is completely ignoring the TA-juniper app?&lt;/P&gt;

&lt;P&gt;I've restarted the indexer a couple of times with no change in behavior.&lt;/P&gt;</description>
      <pubDate>Mon, 12 Dec 2011 16:11:15 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Trouble-with-TA-Juniper/m-p/33120#M5916</guid>
      <dc:creator>Kate_Lawrence-G</dc:creator>
      <dc:date>2011-12-12T16:11:15Z</dc:date>
    </item>
    <item>
      <title>Re: Trouble with TA-Juniper</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Trouble-with-TA-Juniper/m-p/33121#M5917</link>
      <description>&lt;P&gt;Kate,&lt;/P&gt;

&lt;P&gt;When you say "I have a Juniper firewall that forwards syslog/udp:514 data from a forwarder", are you using a full forwarder? If so, then you will need to deploy TA-Juniper at the forwarder. I recognize that this would not explain why one indexer is working and the other is not but may be contributing to the problem.&lt;/P&gt;

&lt;P&gt;If this is not the case, could you please open a ticket with support and provide diags? This will make it much easier for Splunk to get a handle on the root cause.&lt;/P&gt;</description>
      <pubDate>Mon, 12 Dec 2011 21:15:30 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Trouble-with-TA-Juniper/m-p/33121#M5917</guid>
      <dc:creator>LukeMurphey</dc:creator>
      <dc:date>2011-12-12T21:15:30Z</dc:date>
    </item>
  </channel>
</rss>

