<?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 FWSM idle connection issues? in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/fwsm-idle-connection-issues/m-p/1897124#M437331</link>
    <description>&lt;P&gt;Hey all,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We are experiencing an odd issue that may be related to our FWSM. Our DBAs are experiencing timeout issues when running Oracle SQLNet queries for connections that are anywhere between 30 minutes and 60 minutes idle. I can say with certainty that after 60 minutes the connection is lost, less than that I do not have concrete evidence yet. We have run some packet captures and analyzed the data using a third party analysis tool with their engineers and have found very little to say it is network. The DBAs say it isn't the database a setting on the clients and that the issue appears to have begun back when we implemented performance modifcations on our FWSM - upping the default mss from 1380 to 1460 and disabling TCP sequence randomization.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I saw another post on here that appeared to be similar, but I didn't; quite understand the "Correct Answer" solution or how to use it as it was quite generic.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We are running FWSM code 3.1(9)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Here is a listing of our timeouts and policies:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;timeout xlate 3:00:00&lt;/P&gt;&lt;P&gt;timeout conn 4:00:00 half-closed 0:10:00 udp 0:02:00 icmp 0:00:02&lt;/P&gt;&lt;P&gt;timeout sunrpc 0:10:00 h323 0:05:00 h225 1:00:00 mgcp 0:05:00&lt;/P&gt;&lt;P&gt;timeout mgcp-pat 0:05:00 sip 0:30:00 sip_media 0:02:00&lt;/P&gt;&lt;P&gt;timeout uauth 0:05:00 absolute&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;class-map sqltraffic&lt;/P&gt;&lt;P&gt; match access-list sqltraffic&lt;/P&gt;&lt;P&gt;class-map TCP&lt;/P&gt;&lt;P&gt; match port tcp range 1 65535&lt;/P&gt;&lt;P&gt;class-map class_sip_tcp&lt;/P&gt;&lt;P&gt; match port tcp eq sip&lt;/P&gt;&lt;P&gt;class-map inspection_default&lt;/P&gt;&lt;P&gt; match default-inspection-traffic&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;policy-map global_policy&lt;/P&gt;&lt;P&gt; class inspection_default&lt;/P&gt;&lt;P&gt;&amp;nbsp; inspect ftp&lt;/P&gt;&lt;P&gt;&amp;nbsp; inspect h323 h225&lt;/P&gt;&lt;P&gt;&amp;nbsp; inspect h323 ras&lt;/P&gt;&lt;P&gt;&amp;nbsp; inspect rsh&lt;/P&gt;&lt;P&gt;&amp;nbsp; inspect sunrpc&lt;/P&gt;&lt;P&gt;&amp;nbsp; inspect ils&lt;/P&gt;&lt;P&gt;&amp;nbsp; inspect icmp&lt;/P&gt;&lt;P&gt; class class_sip_tcp&lt;/P&gt;&lt;P&gt;&amp;nbsp; inspect sip&lt;/P&gt;&lt;P&gt; class sqltraffic&lt;/P&gt;&lt;P&gt;&amp;nbsp; inspect sqlnet&lt;/P&gt;&lt;P&gt; class TCP&lt;/P&gt;&lt;P&gt;&amp;nbsp; set connection random-sequence-number disable&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;sysopt connection tcpmss 1460&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We plan to take the tcpmss back to default of 1380 and remove the class TCP to re-enable random-sequence-number &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;However I am curious if just having the class TCP in there, does this override the global timeout connection of 4:00:00 (4hr) ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-dan&lt;/P&gt;</description>
    <pubDate>Mon, 11 Mar 2019 23:04:54 GMT</pubDate>
    <dc:creator>Daniel Foerst</dc:creator>
    <dc:date>2019-03-11T23:04:54Z</dc:date>
    <item>
      <title>FWSM idle connection issues?</title>
      <link>https://community.cisco.com/t5/network-security/fwsm-idle-connection-issues/m-p/1897124#M437331</link>
      <description>&lt;P&gt;Hey all,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We are experiencing an odd issue that may be related to our FWSM. Our DBAs are experiencing timeout issues when running Oracle SQLNet queries for connections that are anywhere between 30 minutes and 60 minutes idle. I can say with certainty that after 60 minutes the connection is lost, less than that I do not have concrete evidence yet. We have run some packet captures and analyzed the data using a third party analysis tool with their engineers and have found very little to say it is network. The DBAs say it isn't the database a setting on the clients and that the issue appears to have begun back when we implemented performance modifcations on our FWSM - upping the default mss from 1380 to 1460 and disabling TCP sequence randomization.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I saw another post on here that appeared to be similar, but I didn't; quite understand the "Correct Answer" solution or how to use it as it was quite generic.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We are running FWSM code 3.1(9)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Here is a listing of our timeouts and policies:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;timeout xlate 3:00:00&lt;/P&gt;&lt;P&gt;timeout conn 4:00:00 half-closed 0:10:00 udp 0:02:00 icmp 0:00:02&lt;/P&gt;&lt;P&gt;timeout sunrpc 0:10:00 h323 0:05:00 h225 1:00:00 mgcp 0:05:00&lt;/P&gt;&lt;P&gt;timeout mgcp-pat 0:05:00 sip 0:30:00 sip_media 0:02:00&lt;/P&gt;&lt;P&gt;timeout uauth 0:05:00 absolute&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;class-map sqltraffic&lt;/P&gt;&lt;P&gt; match access-list sqltraffic&lt;/P&gt;&lt;P&gt;class-map TCP&lt;/P&gt;&lt;P&gt; match port tcp range 1 65535&lt;/P&gt;&lt;P&gt;class-map class_sip_tcp&lt;/P&gt;&lt;P&gt; match port tcp eq sip&lt;/P&gt;&lt;P&gt;class-map inspection_default&lt;/P&gt;&lt;P&gt; match default-inspection-traffic&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;policy-map global_policy&lt;/P&gt;&lt;P&gt; class inspection_default&lt;/P&gt;&lt;P&gt;&amp;nbsp; inspect ftp&lt;/P&gt;&lt;P&gt;&amp;nbsp; inspect h323 h225&lt;/P&gt;&lt;P&gt;&amp;nbsp; inspect h323 ras&lt;/P&gt;&lt;P&gt;&amp;nbsp; inspect rsh&lt;/P&gt;&lt;P&gt;&amp;nbsp; inspect sunrpc&lt;/P&gt;&lt;P&gt;&amp;nbsp; inspect ils&lt;/P&gt;&lt;P&gt;&amp;nbsp; inspect icmp&lt;/P&gt;&lt;P&gt; class class_sip_tcp&lt;/P&gt;&lt;P&gt;&amp;nbsp; inspect sip&lt;/P&gt;&lt;P&gt; class sqltraffic&lt;/P&gt;&lt;P&gt;&amp;nbsp; inspect sqlnet&lt;/P&gt;&lt;P&gt; class TCP&lt;/P&gt;&lt;P&gt;&amp;nbsp; set connection random-sequence-number disable&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;sysopt connection tcpmss 1460&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We plan to take the tcpmss back to default of 1380 and remove the class TCP to re-enable random-sequence-number &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;However I am curious if just having the class TCP in there, does this override the global timeout connection of 4:00:00 (4hr) ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-dan&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 23:04:54 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/fwsm-idle-connection-issues/m-p/1897124#M437331</guid>
      <dc:creator>Daniel Foerst</dc:creator>
      <dc:date>2019-03-11T23:04:54Z</dc:date>
    </item>
  </channel>
</rss>

