<?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 for NetApp - Mount NFS in All Apps and Add-ons</title>
    <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/Splunk-for-NetApp-Mounting-NFS/m-p/24581#M69440</link>
    <description>&lt;P&gt;I experienced some challenges with bringing in Netapp object auditing events (not ONTAP events), so I thought I’d share if anyone else can be spared some of the pain.&lt;/P&gt;

&lt;P&gt;In my case, the Netapp events were written to XML files stored on a Windows file share.  The forwarder was installed on a Windows VM that had access to this share.  The account running the Splunk service also was set up with access to this share.  Here are my working config files.&lt;/P&gt;

&lt;P&gt;&lt;STRONG&gt;Inputs.conf&lt;/STRONG&gt;&lt;BR /&gt;
[monitor://\\servername\auditlogs]&lt;/P&gt;

&lt;H1&gt;NOTE:  The file path is: 2 forward slashes, 4 backslashes, server name, backslash, share  name&lt;/H1&gt;

&lt;H1&gt;FS FS BS BS BS BS server name BS share name&lt;/H1&gt;

&lt;P&gt;index = netapp&lt;BR /&gt;
sourcetype = object_auditing&lt;BR /&gt;
disabled = 0&lt;BR /&gt;
whitelist = .*last.xml&lt;BR /&gt;
initCrcLength=512&lt;/P&gt;

&lt;P&gt;&lt;STRONG&gt;props.conf&lt;/STRONG&gt;&lt;BR /&gt;
[object_auditing]&lt;BR /&gt;
KV_MODE=xml&lt;BR /&gt;
SHOULD_LINEMERGE=true&lt;BR /&gt;
LINE_BREAKER= &amp;gt;(\s+)&lt;/P&gt;</description>
    <pubDate>Tue, 29 Sep 2020 08:57:21 GMT</pubDate>
    <dc:creator>dfrankekcg</dc:creator>
    <dc:date>2020-09-29T08:57:21Z</dc:date>
    <item>
      <title>Splunk for NetApp - Mounting NFS?</title>
      <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/Splunk-for-NetApp-Mounting-NFS/m-p/24579#M69438</link>
      <description>&lt;P&gt;All,&lt;/P&gt;
&lt;P&gt;Step 3, mounting the NFS share for Splunk to digest isn't going to work for us. Can't we get the same data via syslog?&lt;/P&gt;
&lt;P&gt;".&lt;BR /&gt;Create an NFS mount to the system partition of your filer(s). Copy local/inputs.conf.sample to inputs.conf and edit this file. Specify path to the system log path. For example:&lt;/P&gt;
&lt;P&gt;[monitor:///opt/netapp_logs/10.160.114.230/etc/log]"&lt;/P&gt;</description>
      <pubDate>Mon, 24 Apr 2023 14:47:27 GMT</pubDate>
      <guid>https://community.splunk.com/t5/All-Apps-and-Add-ons/Splunk-for-NetApp-Mounting-NFS/m-p/24579#M69438</guid>
      <dc:creator>daniel333</dc:creator>
      <dc:date>2023-04-24T14:47:27Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk for NetApp - Mount NFS</title>
      <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/Splunk-for-NetApp-Mounting-NFS/m-p/24580#M69439</link>
      <description>&lt;P&gt;Yes, actually I had planned on obsoleting the NFS file monitor entirely in favor of syslog. You will see this in an upcoming release. Not that it will be drastic, but I have not yet started on the work to change the dashboard panels on the overview page. It should be trivial if you want to have a go. Click on the "view results" link on those first two panels and you'll see what needs to be edited. For example:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;index=netapp sourcetype="*messages*" OR sourcetype="*syslog*" 
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;This is what the NFS messages are coming in as presently. Just replace that with how to find your syslog messages and it might "just work".&lt;/P&gt;</description>
      <pubDate>Fri, 08 Feb 2013 04:39:01 GMT</pubDate>
      <guid>https://community.splunk.com/t5/All-Apps-and-Add-ons/Splunk-for-NetApp-Mounting-NFS/m-p/24580#M69439</guid>
      <dc:creator>halr9000</dc:creator>
      <dc:date>2013-02-08T04:39:01Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk for NetApp - Mount NFS</title>
      <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/Splunk-for-NetApp-Mounting-NFS/m-p/24581#M69440</link>
      <description>&lt;P&gt;I experienced some challenges with bringing in Netapp object auditing events (not ONTAP events), so I thought I’d share if anyone else can be spared some of the pain.&lt;/P&gt;

&lt;P&gt;In my case, the Netapp events were written to XML files stored on a Windows file share.  The forwarder was installed on a Windows VM that had access to this share.  The account running the Splunk service also was set up with access to this share.  Here are my working config files.&lt;/P&gt;

&lt;P&gt;&lt;STRONG&gt;Inputs.conf&lt;/STRONG&gt;&lt;BR /&gt;
[monitor://\\servername\auditlogs]&lt;/P&gt;

&lt;H1&gt;NOTE:  The file path is: 2 forward slashes, 4 backslashes, server name, backslash, share  name&lt;/H1&gt;

&lt;H1&gt;FS FS BS BS BS BS server name BS share name&lt;/H1&gt;

&lt;P&gt;index = netapp&lt;BR /&gt;
sourcetype = object_auditing&lt;BR /&gt;
disabled = 0&lt;BR /&gt;
whitelist = .*last.xml&lt;BR /&gt;
initCrcLength=512&lt;/P&gt;

&lt;P&gt;&lt;STRONG&gt;props.conf&lt;/STRONG&gt;&lt;BR /&gt;
[object_auditing]&lt;BR /&gt;
KV_MODE=xml&lt;BR /&gt;
SHOULD_LINEMERGE=true&lt;BR /&gt;
LINE_BREAKER= &amp;gt;(\s+)&lt;/P&gt;</description>
      <pubDate>Tue, 29 Sep 2020 08:57:21 GMT</pubDate>
      <guid>https://community.splunk.com/t5/All-Apps-and-Add-ons/Splunk-for-NetApp-Mounting-NFS/m-p/24581#M69440</guid>
      <dc:creator>dfrankekcg</dc:creator>
      <dc:date>2020-09-29T08:57:21Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk for NetApp - Mount NFS</title>
      <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/Splunk-for-NetApp-Mounting-NFS/m-p/641109#M78989</link>
      <description>&lt;P&gt;Hi, where did you find the solution , documentation about mounting the NFS under Splunk ?&lt;BR /&gt;thanks&lt;/P&gt;</description>
      <pubDate>Mon, 24 Apr 2023 11:08:05 GMT</pubDate>
      <guid>https://community.splunk.com/t5/All-Apps-and-Add-ons/Splunk-for-NetApp-Mounting-NFS/m-p/641109#M78989</guid>
      <dc:creator>printul77700</dc:creator>
      <dc:date>2023-04-24T11:08:05Z</dc:date>
    </item>
  </channel>
</rss>

