<?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: Sessions aging , scaling , app tricking etc in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/sessions-aging-scaling-app-tricking-etc/m-p/23486#M17132</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;STRONG style="text-decoration: underline;"&gt;Accelerated aging threshold and Scaling Factor&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Once the session table reaches the Accelerated Aging Threshold (% full), the scaling factor will be applied to all sessions.&lt;/P&gt;&lt;P&gt;The session's idle time will be calculated as the actual idle time * scaling factor.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For example, if a scaling factor of 10 were used, a session that would normally time-out after 3600 seconds will instead time-out after 360 seconds.&lt;/P&gt;&lt;P&gt;Accelerated aging is performed across the full session table.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 30 Apr 2013 05:17:57 GMT</pubDate>
    <dc:creator>UhMayYeah</dc:creator>
    <dc:date>2013-04-30T05:17:57Z</dc:date>
    <item>
      <title>Sessions aging , scaling , app tricking etc</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/sessions-aging-scaling-app-tricking-etc/m-p/23485#M17131</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Could someone briefly describe the significance of these values shown in the output for "show sessions info" and how they may be tweaked from a performance perspective ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-&lt;/P&gt;&lt;P&gt;Session accelerated aging:&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; True&lt;/P&gt;&lt;P&gt;&amp;nbsp; Accelerated aging threshold:&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 80% of utilization&lt;/P&gt;&lt;P&gt;&amp;nbsp; Scaling factor:&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 2 X&lt;/P&gt;&lt;P&gt;--------------------------------------------------------------------------------&lt;/P&gt;&lt;P&gt;Session setup&lt;/P&gt;&lt;P&gt;&amp;nbsp; TCP - reject non-SYN first packet:&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; True&lt;/P&gt;&lt;P&gt;&amp;nbsp; Hardware session offloading:&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; True&lt;/P&gt;&lt;P&gt;&amp;nbsp; IPv6 firewalling:&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; True&lt;/P&gt;&lt;P&gt;--------------------------------------------------------------------------------&lt;/P&gt;&lt;P&gt;Application trickling scan parameters:&lt;/P&gt;&lt;P&gt;&amp;nbsp; Timeout to determine application trickling:&amp;nbsp;&amp;nbsp;&amp;nbsp; 10 secs&lt;/P&gt;&lt;P&gt;&amp;nbsp; Resource utilization threshold to start scan:&amp;nbsp; 80%&lt;/P&gt;&lt;P&gt;&amp;nbsp; Scan scaling factor over regular aging:&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 8&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;Sunil tricking &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 29 Apr 2013 10:43:40 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/sessions-aging-scaling-app-tricking-etc/m-p/23485#M17131</guid>
      <dc:creator>sunilsadanandan</dc:creator>
      <dc:date>2013-04-29T10:43:40Z</dc:date>
    </item>
    <item>
      <title>Re: Sessions aging , scaling , app tricking etc</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/sessions-aging-scaling-app-tricking-etc/m-p/23486#M17132</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;STRONG style="text-decoration: underline;"&gt;Accelerated aging threshold and Scaling Factor&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Once the session table reaches the Accelerated Aging Threshold (% full), the scaling factor will be applied to all sessions.&lt;/P&gt;&lt;P&gt;The session's idle time will be calculated as the actual idle time * scaling factor.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For example, if a scaling factor of 10 were used, a session that would normally time-out after 3600 seconds will instead time-out after 360 seconds.&lt;/P&gt;&lt;P&gt;Accelerated aging is performed across the full session table.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 30 Apr 2013 05:17:57 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/sessions-aging-scaling-app-tricking-etc/m-p/23486#M17132</guid>
      <dc:creator>UhMayYeah</dc:creator>
      <dc:date>2013-04-30T05:17:57Z</dc:date>
    </item>
    <item>
      <title>Re: Sessions aging , scaling , app tricking etc</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/sessions-aging-scaling-app-tricking-etc/m-p/23487#M17133</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;SPAN style="text-decoration: underline;"&gt;&lt;STRONG style=": ; color: #000000; font-size: 12px; background-color: #ffffff; font-family: Arial, Helvetica, sans-serif; text-decoration: underline;"&gt;Application trickling&lt;/STRONG&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: 'Lucida Grande', 'Helvetica Neue', Helvetica, Arial, sans-serif; font-size: 12.222222328186035px; background-color: #ffffff;"&gt;&lt;SPAN style="color: #000000; font-family: Arial, Helvetica, sans-serif; font-size: 12px; background-color: #ffffff;"&gt;Is basically a &lt;/SPAN&gt; resource-protection mechanism. As application-layer processing is resource-intensive, when resource (packet buffer etc) utilization exceeds configured threshold, software will start scanning sessions and if a session has been inactive longer than the trickling threshold configured, the buffering resource occupied by this session will be freed.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: 'Lucida Grande', 'Helvetica Neue', Helvetica, Arial, sans-serif; font-size: 12.222222328186035px; background-color: #ffffff;"&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 30 Apr 2013 05:22:13 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/sessions-aging-scaling-app-tricking-etc/m-p/23487#M17133</guid>
      <dc:creator>UhMayYeah</dc:creator>
      <dc:date>2013-04-30T05:22:13Z</dc:date>
    </item>
  </channel>
</rss>

