<?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 CSS 11000 flow port timeout in Application Networking</title>
    <link>https://community.cisco.com/t5/application-networking/css-11000-flow-port-timeout/m-p/414297#M7470</link>
    <description>&lt;P&gt;We have some CSS 11000 running 6.1 and need to protect some long lived tcp connections.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I would like some advice on which port_numbers to include in a&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;flow port port_number timeout value&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;command, in order to ensure neither front end or backend flows get reclaimed by garbage collection within the inactivity timeout period.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We have a one armed configuration with source groups and a port defined in both the content rule and the service definitions.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So if we are port mapping the destination port in the content rule (say 389) with a destination port in the backend service (say 23456) which do we include a flow port timeout for, 389, 23456 or both?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I assume we do not worry about the source ports on either the front end or back end connections?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Many thanks.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Andrew T&lt;/P&gt;</description>
    <pubDate>Wed, 01 Jun 2005 13:59:01 GMT</pubDate>
    <dc:creator>andrew.thomson</dc:creator>
    <dc:date>2005-06-01T13:59:01Z</dc:date>
    <item>
      <title>CSS 11000 flow port timeout</title>
      <link>https://community.cisco.com/t5/application-networking/css-11000-flow-port-timeout/m-p/414297#M7470</link>
      <description>&lt;P&gt;We have some CSS 11000 running 6.1 and need to protect some long lived tcp connections.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I would like some advice on which port_numbers to include in a&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;flow port port_number timeout value&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;command, in order to ensure neither front end or backend flows get reclaimed by garbage collection within the inactivity timeout period.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We have a one armed configuration with source groups and a port defined in both the content rule and the service definitions.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So if we are port mapping the destination port in the content rule (say 389) with a destination port in the backend service (say 23456) which do we include a flow port timeout for, 389, 23456 or both?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I assume we do not worry about the source ports on either the front end or back end connections?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Many thanks.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Andrew T&lt;/P&gt;</description>
      <pubDate>Wed, 01 Jun 2005 13:59:01 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/css-11000-flow-port-timeout/m-p/414297#M7470</guid>
      <dc:creator>andrew.thomson</dc:creator>
      <dc:date>2005-06-01T13:59:01Z</dc:date>
    </item>
    <item>
      <title>Re: CSS 11000 flow port timeout</title>
      <link>https://community.cisco.com/t5/application-networking/css-11000-flow-port-timeout/m-p/414298#M7471</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;The CSS uses and automatic garbage-collector for removing inactive flows. This is not customizable&lt;/P&gt;&lt;P&gt;sofar. To avoid the garbage collection to be performed for specific TCP ports you should then use this&lt;/P&gt;&lt;P&gt;command:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;(config) flow permanent&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;To define a set of TCP ports that will have permanent connections and not be reclaimed by the CSS&lt;/P&gt;&lt;P&gt;when they are inactive, use the flow permanent command. You can define up to four ports. Use the no&lt;/P&gt;&lt;P&gt;form of this command to disable a &lt;/P&gt;&lt;P&gt;permanent connection by setting its port number to 0.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;flow permanent [port1|port2|port3|port4] port_number&lt;/P&gt;&lt;P&gt;no flow permanent [port1|port2|port3|port4]&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Syntax Description &lt;/P&gt;&lt;P&gt;port_number is the number of the port. Enter an integer from 0 to 65535. The default is 0 which&lt;/P&gt;&lt;P&gt;disables the port.&lt;/P&gt;&lt;P&gt;On the CSS the user can configure up to 10 permanent ports which will never be garbage collected.&lt;/P&gt;&lt;P&gt;The problem of course is that the CSS can then run out of FCBs (Flow Control Blocks) if flows are&lt;/P&gt;&lt;P&gt;not properly terminated. I recommend running a cmd-sched script with the perm ports so that&lt;/P&gt;&lt;P&gt;periodically then can be removed and the older flows cleaned up. This script should consist of 2&lt;/P&gt;&lt;P&gt;scheduled commands, one for removing the flow permanent on the ports that you configured and another one one tha re-enables it after 10 minutes (to allow the CSS to delete all flows).&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 07 Jun 2005 11:32:02 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/css-11000-flow-port-timeout/m-p/414298#M7471</guid>
      <dc:creator>thomas.chen</dc:creator>
      <dc:date>2005-06-07T11:32:02Z</dc:date>
    </item>
  </channel>
</rss>

