<?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: netflow behavior in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/netflow-behavior/m-p/220771#M63648</link>
    <description>&lt;P&gt;That is expected behavior.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Before the session ends, the values for things like duration and bytes would not be accurate later if you needed to investigate a particular flow. There wouldn't be an easy way to do delta calculations on the same session since that would require keeping a table of the various active sessions that were still active before, which would probably too much overhead.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;You're right in that there is a delta reporting for your configured interval, but that serves to buffer requests and provide cadence. Since the session still didn't end in that interval, the firewall won't use that session until it is actually completed.&lt;/P&gt;</description>
    <pubDate>Thu, 05 Jul 2018 21:40:11 GMT</pubDate>
    <dc:creator>gwesson</dc:creator>
    <dc:date>2018-07-05T21:40:11Z</dc:date>
    <item>
      <title>netflow behavior</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/netflow-behavior/m-p/220633#M63637</link>
      <description>&lt;P&gt;Is the session is long live ( some applications like nfs,panorama) will start and last till 1 month.&lt;/P&gt;&lt;P&gt;As we have configured log at session end, the log entry will be created once the session is ended.&lt;/P&gt;&lt;P&gt;However we have configured netflow as well.&lt;/P&gt;&lt;P&gt;Netflow is also reporting data to netflow server once the session ended on firewall ( which is 1 month later)&lt;/P&gt;&lt;P&gt;Is this beghavior correct for netflow, I was think it used to report every session information based on interval configured which around 30 min.&lt;/P&gt;&lt;P&gt;We are getting this information on netflow only after session ends. This is affecting for long duration sessions like 1 month.&lt;/P&gt;&lt;P&gt;Is there any parameters to tweak this behavior&lt;/P&gt;</description>
      <pubDate>Thu, 05 Jul 2018 14:53:45 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/netflow-behavior/m-p/220633#M63637</guid>
      <dc:creator>Roby_Sreejith</dc:creator>
      <dc:date>2018-07-05T14:53:45Z</dc:date>
    </item>
    <item>
      <title>Re: netflow behavior</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/netflow-behavior/m-p/220771#M63648</link>
      <description>&lt;P&gt;That is expected behavior.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Before the session ends, the values for things like duration and bytes would not be accurate later if you needed to investigate a particular flow. There wouldn't be an easy way to do delta calculations on the same session since that would require keeping a table of the various active sessions that were still active before, which would probably too much overhead.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;You're right in that there is a delta reporting for your configured interval, but that serves to buffer requests and provide cadence. Since the session still didn't end in that interval, the firewall won't use that session until it is actually completed.&lt;/P&gt;</description>
      <pubDate>Thu, 05 Jul 2018 21:40:11 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/netflow-behavior/m-p/220771#M63648</guid>
      <dc:creator>gwesson</dc:creator>
      <dc:date>2018-07-05T21:40:11Z</dc:date>
    </item>
  </channel>
</rss>

