<?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: Fortinet Fortigate log direct ingest into Splunk in Deployment Architecture</title>
    <link>https://community.splunk.com/t5/Deployment-Architecture/Fortinet-Fortigate-log-direct-ingest-into-Splunk/m-p/441119#M20935</link>
    <description>&lt;P&gt;As per Splunk's best practice, for syslog data sources, its advised to setup a syslog server [ rsyslog/syslog-ng] for a production environment. This can be low spec server or a Virtual machine, based on the volume of data ingested. This then will send the logs using  a UF to the indexer clusters in round robin. The Replication factor setting can be used to ensure a copy resides always on the origin and other indexer.&lt;/P&gt;

&lt;P&gt;If for some reasons, this can not be done, then you can deply an app to both the Indexers in the cluster [with UDP port, should be higher than 1024 for non-root account used to run splunk]. The syslog can go to one of the indexers [ as you may need to provide a IP in the fortinet, unless you can have a DNS record which can round-robin the syslog to both the indexers] and in case of that indexer failure, you would need to manually change the IP on the fortinet to the other working indexers.. [ you may also have cluster issues to handle, when one node goes down in a 2 node cluster]. Make a note of all pros/cons and decide on the approach that suits your need.&lt;/P&gt;</description>
    <pubDate>Tue, 07 May 2019 10:56:33 GMT</pubDate>
    <dc:creator>lakshman239</dc:creator>
    <dc:date>2019-05-07T10:56:33Z</dc:date>
    <item>
      <title>Fortinet Fortigate log direct ingest into Splunk</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/Fortinet-Fortigate-log-direct-ingest-into-Splunk/m-p/441118#M20934</link>
      <description>&lt;P&gt;Hi Guys, &lt;/P&gt;

&lt;P&gt;Can i just check is it possible for me to direct ingest the Fortigate Fortinet logs in to my Splunk environment ?&lt;BR /&gt;
Meaning without using Forwarder + syslog server (method), like the following guide for a standalone environment from fortinet :&lt;BR /&gt;
&lt;A href="https://www.fortinet.com/content/dam/fortinet/assets/alliances/Fortinet-Splunk-Deployment-Guide.pdf"&gt;https://www.fortinet.com/content/dam/fortinet/assets/alliances/Fortinet-Splunk-Deployment-Guide.pdf&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;My current environment setup are as follows :&lt;BR /&gt;
1 x Search Head/Node Master role Server.&lt;BR /&gt;
2 x Cluster Indexer Server.&lt;/P&gt;

&lt;P&gt;If direct ingest method is possible in my environment, how should i go about configuring it to ensure both my indexer have a replicated copy of the data that was ingested from Fortinet ?&lt;/P&gt;

&lt;P&gt;Thanks in advance!&lt;/P&gt;</description>
      <pubDate>Tue, 07 May 2019 09:46:22 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/Fortinet-Fortigate-log-direct-ingest-into-Splunk/m-p/441118#M20934</guid>
      <dc:creator>christay</dc:creator>
      <dc:date>2019-05-07T09:46:22Z</dc:date>
    </item>
    <item>
      <title>Re: Fortinet Fortigate log direct ingest into Splunk</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/Fortinet-Fortigate-log-direct-ingest-into-Splunk/m-p/441119#M20935</link>
      <description>&lt;P&gt;As per Splunk's best practice, for syslog data sources, its advised to setup a syslog server [ rsyslog/syslog-ng] for a production environment. This can be low spec server or a Virtual machine, based on the volume of data ingested. This then will send the logs using  a UF to the indexer clusters in round robin. The Replication factor setting can be used to ensure a copy resides always on the origin and other indexer.&lt;/P&gt;

&lt;P&gt;If for some reasons, this can not be done, then you can deply an app to both the Indexers in the cluster [with UDP port, should be higher than 1024 for non-root account used to run splunk]. The syslog can go to one of the indexers [ as you may need to provide a IP in the fortinet, unless you can have a DNS record which can round-robin the syslog to both the indexers] and in case of that indexer failure, you would need to manually change the IP on the fortinet to the other working indexers.. [ you may also have cluster issues to handle, when one node goes down in a 2 node cluster]. Make a note of all pros/cons and decide on the approach that suits your need.&lt;/P&gt;</description>
      <pubDate>Tue, 07 May 2019 10:56:33 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/Fortinet-Fortigate-log-direct-ingest-into-Splunk/m-p/441119#M20935</guid>
      <dc:creator>lakshman239</dc:creator>
      <dc:date>2019-05-07T10:56:33Z</dc:date>
    </item>
    <item>
      <title>Re: Fortinet Fortigate log direct ingest into Splunk</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/Fortinet-Fortigate-log-direct-ingest-into-Splunk/m-p/441120#M20936</link>
      <description>&lt;P&gt;Thanks for the advice, appreciate that. &lt;/P&gt;</description>
      <pubDate>Thu, 09 May 2019 02:58:10 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/Fortinet-Fortigate-log-direct-ingest-into-Splunk/m-p/441120#M20936</guid>
      <dc:creator>christay</dc:creator>
      <dc:date>2019-05-09T02:58:10Z</dc:date>
    </item>
  </channel>
</rss>

