<?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: traffic report -&amp;gt; wrong byte counts ? in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/traffic-report-gt-wrong-byte-counts/m-p/49399#M36388</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;!--[if gte mso 10]&gt;
&lt;style&gt;
 /* Style Definitions */
 table.MsoNormalTable
	{mso-style-name:"Table Normal";
	mso-tstyle-rowband-size:0;
	mso-tstyle-colband-size:0;
	mso-style-noshow:yes;
	mso-style-priority:99;
	mso-style-qformat:yes;
	mso-style-parent:"";
	mso-padding-alt:0in 5.4pt 0in 5.4pt;
	mso-para-margin:0in;
	mso-para-margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	mso-ascii-font-family:Calibri;
	mso-ascii-theme-font:minor-latin;
	mso-fareast-font-family:"Times New Roman";
	mso-fareast-theme-font:minor-fareast;
	mso-hansi-font-family:Calibri;
	mso-hansi-theme-font:minor-latin;
	mso-bidi-font-family:"Times New Roman";
	mso-bidi-theme-font:minor-bidi;}
&lt;/style&gt;
&lt;![endif]--&gt;&lt;SPAN style="font-size: 11pt; font-family: &amp;amp;quot;Calibri&amp;amp;quot;,&amp;amp;quot;sans-serif&amp;amp;quot;; color: #1f497d;"&gt;You might want to check the raw logs (log viewer) for the same address pair and if they happen to have the large byte count.&lt;BR /&gt;&lt;BR /&gt;This may be something that needs to have a case open with support.&amp;nbsp; There have been some issues with wrong byte counts in the past.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;&lt;BR /&gt;Oliver&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 13 Oct 2010 17:17:56 GMT</pubDate>
    <dc:creator>odaos</dc:creator>
    <dc:date>2010-10-13T17:17:56Z</dc:date>
    <item>
      <title>traffic report -&gt; wrong byte counts ?</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/traffic-report-gt-wrong-byte-counts/m-p/49398#M36387</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I recently created some scheduled custom report to list the top 25 byte-consumers for the last calender day.&lt;/P&gt;&lt;P&gt;This works well and provides a listing with source and dest zone, source and dest address and bytes.&lt;/P&gt;&lt;P&gt;But if I drill down, there is a massive discrepance between the amout that is displayed in the report ( e.g. 31,833,534,225 bytes )&lt;/P&gt;&lt;P&gt;and the detail-page for the same time-period, where only about 355 MBs are listed for the correspondinc address-pair.&lt;/P&gt;&lt;P&gt;This lower value corresponds to Netflow data, we are capturing.&lt;/P&gt;&lt;P&gt;The behaviour is the same if I run the report on demand and / or for different time periods&lt;/P&gt;&lt;P&gt;We are running a PAN-500 as a&amp;nbsp; Virtual Wire between netword and squid-proxy&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;any ideas ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Kind Regards&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Franz Leippert&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 07 Oct 2010 08:52:35 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/traffic-report-gt-wrong-byte-counts/m-p/49398#M36387</guid>
      <dc:creator>rfle.rz</dc:creator>
      <dc:date>2010-10-07T08:52:35Z</dc:date>
    </item>
    <item>
      <title>Re: traffic report -&gt; wrong byte counts ?</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/traffic-report-gt-wrong-byte-counts/m-p/49399#M36388</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;!--[if gte mso 10]&gt;
&lt;style&gt;
 /* Style Definitions */
 table.MsoNormalTable
	{mso-style-name:"Table Normal";
	mso-tstyle-rowband-size:0;
	mso-tstyle-colband-size:0;
	mso-style-noshow:yes;
	mso-style-priority:99;
	mso-style-qformat:yes;
	mso-style-parent:"";
	mso-padding-alt:0in 5.4pt 0in 5.4pt;
	mso-para-margin:0in;
	mso-para-margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	mso-ascii-font-family:Calibri;
	mso-ascii-theme-font:minor-latin;
	mso-fareast-font-family:"Times New Roman";
	mso-fareast-theme-font:minor-fareast;
	mso-hansi-font-family:Calibri;
	mso-hansi-theme-font:minor-latin;
	mso-bidi-font-family:"Times New Roman";
	mso-bidi-theme-font:minor-bidi;}
&lt;/style&gt;
&lt;![endif]--&gt;&lt;SPAN style="font-size: 11pt; font-family: &amp;amp;quot;Calibri&amp;amp;quot;,&amp;amp;quot;sans-serif&amp;amp;quot;; color: #1f497d;"&gt;You might want to check the raw logs (log viewer) for the same address pair and if they happen to have the large byte count.&lt;BR /&gt;&lt;BR /&gt;This may be something that needs to have a case open with support.&amp;nbsp; There have been some issues with wrong byte counts in the past.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;&lt;BR /&gt;Oliver&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 13 Oct 2010 17:17:56 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/traffic-report-gt-wrong-byte-counts/m-p/49399#M36388</guid>
      <dc:creator>odaos</dc:creator>
      <dc:date>2010-10-13T17:17:56Z</dc:date>
    </item>
  </channel>
</rss>

