<?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 ASA State Table in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/asa-state-table/m-p/3697978#M12612</link>
    <description>&lt;P&gt;Dear All,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I have a doubt on working with timeouts and state table.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Below is the Same output&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;PRE&gt;ASA# &lt;STRONG&gt;show conn protocol tcp&lt;/STRONG&gt;&lt;BR /&gt;101 in use, 5589 most used&lt;BR /&gt;TCP outside 10.23.232.59:5223 inside 192.168.1.3:52419, idle 0:00:11, bytes 0, flags saA&lt;BR /&gt;TCP outside 192.168.3.5:80 dmz 172.16.103.221:57646, idle 0:00:29, bytes 2176, flags UIO&lt;BR /&gt;TCP outside 10.23.232.217:5223 inside 192.168.1.3:52425, idle 0:00:10, bytes 0, flags saA&lt;BR /&gt;TCP outside 10.23.232.217:443 inside 192.168.1.3:52427, idle 0:01:02, bytes 4504, flags UIO&lt;BR /&gt;TCP outside 10.23.232.57:5223 inside 192.168.1.3:52412, idle 0:00:23, bytes 0, flags saA&lt;BR /&gt;TCP outside 10.23.232.116:5223 inside 192.168.1.3:52408, idle 0:00:23, bytes 0, flags saA&lt;BR /&gt;TCP outside 10.23.232.60:5223 inside 192.168.1.3:52413, idle 0:00:23, bytes 0, flags saA&lt;BR /&gt;TCP outside 10.23.232.96:5223 inside 192.168.1.3:52421, idle 0:00:11, bytes 0, flags saA&lt;BR /&gt;TCP outside 10.23.232.190:5223 inside 192.168.1.3:52424, idle 0:00:10, bytes 0, flags saA&lt;/PRE&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;In the Mentioned output of the command show conn.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;What does idle mean ? and how does it works.&lt;/P&gt;</description>
    <pubDate>Fri, 21 Feb 2020 16:10:07 GMT</pubDate>
    <dc:creator>SivaVigneshKumar</dc:creator>
    <dc:date>2020-02-21T16:10:07Z</dc:date>
    <item>
      <title>ASA State Table</title>
      <link>https://community.cisco.com/t5/network-security/asa-state-table/m-p/3697978#M12612</link>
      <description>&lt;P&gt;Dear All,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I have a doubt on working with timeouts and state table.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Below is the Same output&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;PRE&gt;ASA# &lt;STRONG&gt;show conn protocol tcp&lt;/STRONG&gt;&lt;BR /&gt;101 in use, 5589 most used&lt;BR /&gt;TCP outside 10.23.232.59:5223 inside 192.168.1.3:52419, idle 0:00:11, bytes 0, flags saA&lt;BR /&gt;TCP outside 192.168.3.5:80 dmz 172.16.103.221:57646, idle 0:00:29, bytes 2176, flags UIO&lt;BR /&gt;TCP outside 10.23.232.217:5223 inside 192.168.1.3:52425, idle 0:00:10, bytes 0, flags saA&lt;BR /&gt;TCP outside 10.23.232.217:443 inside 192.168.1.3:52427, idle 0:01:02, bytes 4504, flags UIO&lt;BR /&gt;TCP outside 10.23.232.57:5223 inside 192.168.1.3:52412, idle 0:00:23, bytes 0, flags saA&lt;BR /&gt;TCP outside 10.23.232.116:5223 inside 192.168.1.3:52408, idle 0:00:23, bytes 0, flags saA&lt;BR /&gt;TCP outside 10.23.232.60:5223 inside 192.168.1.3:52413, idle 0:00:23, bytes 0, flags saA&lt;BR /&gt;TCP outside 10.23.232.96:5223 inside 192.168.1.3:52421, idle 0:00:11, bytes 0, flags saA&lt;BR /&gt;TCP outside 10.23.232.190:5223 inside 192.168.1.3:52424, idle 0:00:10, bytes 0, flags saA&lt;/PRE&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;In the Mentioned output of the command show conn.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;What does idle mean ? and how does it works.&lt;/P&gt;</description>
      <pubDate>Fri, 21 Feb 2020 16:10:07 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-state-table/m-p/3697978#M12612</guid>
      <dc:creator>SivaVigneshKumar</dc:creator>
      <dc:date>2020-02-21T16:10:07Z</dc:date>
    </item>
    <item>
      <title>Re: ASA State Table</title>
      <link>https://community.cisco.com/t5/network-security/asa-state-table/m-p/3698014#M12614</link>
      <description>&lt;P&gt;Hi there,&lt;/P&gt;
&lt;P&gt;Each line represents a seperate connection and the idle timer indicates the elpased time since a packet relevant to that connection has passed through the ASA.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;cheers,&lt;/P&gt;
&lt;P&gt;Seb.&lt;/P&gt;</description>
      <pubDate>Thu, 30 Aug 2018 15:29:34 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-state-table/m-p/3698014#M12614</guid>
      <dc:creator>Seb Rupik</dc:creator>
      <dc:date>2018-08-30T15:29:34Z</dc:date>
    </item>
    <item>
      <title>Re: ASA State Table</title>
      <link>https://community.cisco.com/t5/network-security/asa-state-table/m-p/3698035#M12615</link>
      <description>&lt;P&gt;Thanks Seb,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Let us consider the&amp;nbsp;UDP packet crossed the firewall and there is no reply from destination and my TCP timeout is 2 Mins and i have configured embryonic timeout to be 40 mins and idle time out as 1 hr so in this will the connection table will exists till 1 hour or will be cleared after 2 Mins.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Configuration.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;class Default_class&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;&amp;nbsp; set connection embryonic-conn-max 3000&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;&amp;nbsp; set connection timeout embryonic 0:40:00 idle 1:00:00&lt;/STRONG&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 30 Aug 2018 16:04:09 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-state-table/m-p/3698035#M12615</guid>
      <dc:creator>SivaVigneshKumar</dc:creator>
      <dc:date>2018-08-30T16:04:09Z</dc:date>
    </item>
    <item>
      <title>Re: ASA State Table</title>
      <link>https://community.cisco.com/t5/network-security/asa-state-table/m-p/3698208#M12619</link>
      <description>&lt;P&gt;UDP and TCP are handled differently. There is no state with UDP so no concept of being embryonic (half-open).&lt;/P&gt;
&lt;P&gt;UDP connections are cleared by configuring the UDP idle timeout:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;PRE&gt;!
timeout udp &amp;lt;hh:mm:ss&amp;gt; 
!&lt;/PRE&gt;
&lt;P&gt;&lt;A href="https://www.cisco.com/c/en/us/td/docs/security/asa/asa96/configuration/firewall/asa-96-firewall-config/conns-connlimits.html#ID-2068-0000003c" target="_blank"&gt;https://www.cisco.com/c/en/us/td/docs/security/asa/asa96/configuration/firewall/asa-96-firewall-config/conns-connlimits.html#ID-2068-0000003c&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;cheers,&lt;/P&gt;
&lt;P&gt;Seb.&lt;/P&gt;</description>
      <pubDate>Thu, 30 Aug 2018 19:57:24 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-state-table/m-p/3698208#M12619</guid>
      <dc:creator>Seb Rupik</dc:creator>
      <dc:date>2018-08-30T19:57:24Z</dc:date>
    </item>
  </channel>
</rss>

