<?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 tcp-map queue-limit in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/tcp-map-queue-limit/m-p/2604640#M198162</link>
    <description>&lt;P&gt;I had a connection to a business partner.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We were working with TAC on a recent firewall implementation.&lt;/P&gt;&lt;P&gt;The tech advised us to change a couple of settings as follows:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;tcp-map&lt;/P&gt;&lt;P&gt;&amp;nbsp; queue-limit&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;policy-map global_policy&lt;BR /&gt;&amp;nbsp;class BusinessPartner_1&lt;BR /&gt;&amp;nbsp; set connection timeout tcp 80:00:00&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Since these changes were made, the Business partner has had to restart their connection every morning. Proior to this, the connection remianed alive continuously.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Anyone have any insight into this?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Tue, 12 Mar 2019 05:18:10 GMT</pubDate>
    <dc:creator>Steve Coady</dc:creator>
    <dc:date>2019-03-12T05:18:10Z</dc:date>
    <item>
      <title>tcp-map queue-limit</title>
      <link>https://community.cisco.com/t5/network-security/tcp-map-queue-limit/m-p/2604640#M198162</link>
      <description>&lt;P&gt;I had a connection to a business partner.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We were working with TAC on a recent firewall implementation.&lt;/P&gt;&lt;P&gt;The tech advised us to change a couple of settings as follows:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;tcp-map&lt;/P&gt;&lt;P&gt;&amp;nbsp; queue-limit&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;policy-map global_policy&lt;BR /&gt;&amp;nbsp;class BusinessPartner_1&lt;BR /&gt;&amp;nbsp; set connection timeout tcp 80:00:00&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Since these changes were made, the Business partner has had to restart their connection every morning. Proior to this, the connection remianed alive continuously.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Anyone have any insight into this?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 12 Mar 2019 05:18:10 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/tcp-map-queue-limit/m-p/2604640#M198162</guid>
      <dc:creator>Steve Coady</dc:creator>
      <dc:date>2019-03-12T05:18:10Z</dc:date>
    </item>
    <item>
      <title>When you say they have to</title>
      <link>https://community.cisco.com/t5/network-security/tcp-map-queue-limit/m-p/2604641#M198164</link>
      <description>&lt;P&gt;When you say they have to restart, what exactly does it means? What the tech did there was to leave the connection open for 80:00:00 hrs, after the timeout is reached the connection would be closed.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Personally, I would never do that.&lt;/P&gt;&lt;P&gt;What connection are we talking about? Is it SQL? What protocol are you using?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Mike.&lt;/P&gt;</description>
      <pubDate>Mon, 05 Jan 2015 23:18:24 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/tcp-map-queue-limit/m-p/2604641#M198164</guid>
      <dc:creator>Maykol Rojas</dc:creator>
      <dc:date>2015-01-05T23:18:24Z</dc:date>
    </item>
  </channel>
</rss>

