<?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 Hi Alex,The above messages in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/asa5520-tcp-reset-i/m-p/2760895#M171243</link>
    <description>&lt;P&gt;Hi Alex,&lt;BR /&gt;&lt;BR /&gt;The above messages correlate to building and tearing down of the state connections on the ASA which is the expected behavior.&lt;BR /&gt;You might want to take packet captures to narrow down the issue.&lt;BR /&gt;Example :- capture &amp;lt;capture name&amp;gt; interface &amp;lt;ingress interface&amp;gt; match ip host &amp;lt;server1 IP&amp;gt; host &amp;lt;server2 IP&amp;gt;&lt;/P&gt;&lt;P&gt;Verify the output via :-&amp;nbsp;show capture &amp;lt;capture name&amp;gt;&amp;nbsp;&lt;BR /&gt;Ref:-&amp;nbsp;&lt;A href="https://supportforums.cisco.com/document/69281/asa-using-packet-capture-troubleshoot-asa-firewall-configuration-and-scenarios"&gt;https://supportforums.cisco.com/document/69281/asa-using-packet-capture-troubleshoot-asa-firewall-configuration-and-scenarios&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;Dinesh Moudgil&lt;BR /&gt;&lt;BR /&gt;P.S. Please rate helpful posts.&lt;/P&gt;</description>
    <pubDate>Tue, 27 Oct 2015 05:20:38 GMT</pubDate>
    <dc:creator>Dinesh Moudgil</dc:creator>
    <dc:date>2015-10-27T05:20:38Z</dc:date>
    <item>
      <title>ASA5520 TCP Reset-I</title>
      <link>https://community.cisco.com/t5/network-security/asa5520-tcp-reset-i/m-p/2760894#M171242</link>
      <description>&lt;P&gt;I get this TCP Reset-I when some of my servers sending syslog information to my splunk server.&amp;nbsp; I am not sure what the root cause is since I am able to send syslog on a number of devices to this server.&amp;nbsp; Please assist.&amp;nbsp;&lt;/P&gt;&lt;P&gt;6&amp;nbsp;Oct 26 2015&amp;nbsp;15:25:52&amp;nbsp;302013&amp;nbsp;10.1.106.50&amp;nbsp;44550&amp;nbsp;xxx.xxx.82.9&amp;nbsp;514&amp;nbsp;Built inbound TCP connection 256105191 for Outside:10.1.106.50/44550 (10.1.106.50/44550) to Vlan2000-Security:xxx.xxx.82.9/514 (xxx.xxx.82.9/514)&lt;/P&gt;&lt;P&gt;6&amp;nbsp;Oct 26 2015&amp;nbsp;15:25:52&amp;nbsp;302014&amp;nbsp;10.1.106.50&amp;nbsp;44550&amp;nbsp;xxx.xxx.82.9&amp;nbsp;514&amp;nbsp;Teardown TCP connection 256105191 for Outside:10.1.106.50/44550 to Vlan2000-Security:xxx.xxx.82.9/514 duration 0:00:00 bytes 0 TCP Reset-I&lt;/P&gt;</description>
      <pubDate>Tue, 12 Mar 2019 06:47:39 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa5520-tcp-reset-i/m-p/2760894#M171242</guid>
      <dc:creator>alexvietle</dc:creator>
      <dc:date>2019-03-12T06:47:39Z</dc:date>
    </item>
    <item>
      <title>Hi Alex,The above messages</title>
      <link>https://community.cisco.com/t5/network-security/asa5520-tcp-reset-i/m-p/2760895#M171243</link>
      <description>&lt;P&gt;Hi Alex,&lt;BR /&gt;&lt;BR /&gt;The above messages correlate to building and tearing down of the state connections on the ASA which is the expected behavior.&lt;BR /&gt;You might want to take packet captures to narrow down the issue.&lt;BR /&gt;Example :- capture &amp;lt;capture name&amp;gt; interface &amp;lt;ingress interface&amp;gt; match ip host &amp;lt;server1 IP&amp;gt; host &amp;lt;server2 IP&amp;gt;&lt;/P&gt;&lt;P&gt;Verify the output via :-&amp;nbsp;show capture &amp;lt;capture name&amp;gt;&amp;nbsp;&lt;BR /&gt;Ref:-&amp;nbsp;&lt;A href="https://supportforums.cisco.com/document/69281/asa-using-packet-capture-troubleshoot-asa-firewall-configuration-and-scenarios"&gt;https://supportforums.cisco.com/document/69281/asa-using-packet-capture-troubleshoot-asa-firewall-configuration-and-scenarios&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;Dinesh Moudgil&lt;BR /&gt;&lt;BR /&gt;P.S. Please rate helpful posts.&lt;/P&gt;</description>
      <pubDate>Tue, 27 Oct 2015 05:20:38 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa5520-tcp-reset-i/m-p/2760895#M171243</guid>
      <dc:creator>Dinesh Moudgil</dc:creator>
      <dc:date>2015-10-27T05:20:38Z</dc:date>
    </item>
    <item>
      <title>Hi Alex,</title>
      <link>https://community.cisco.com/t5/network-security/asa5520-tcp-reset-i/m-p/2760896#M171244</link>
      <description>&lt;P&gt;Hi Alex,&lt;/P&gt;
&lt;P&gt;'TCP Reset-I' means that the Reset is coming from Higher Security Zone. From the capture also you would see that Inside host(or server) is sending a Reset.&amp;nbsp; Check if three way handshake is getting completed or not or some password mismatch or something.&lt;/P&gt;
&lt;P&gt;Also there could be any proxy or any thing on the higher security zone which might be sending it if not or main server. Track down the host with mac-address it is coming with the help of capture one hop down everytime.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Regards,&lt;/P&gt;
&lt;P&gt;Akshay Rastogi&lt;/P&gt;</description>
      <pubDate>Sun, 01 Nov 2015 07:31:21 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa5520-tcp-reset-i/m-p/2760896#M171244</guid>
      <dc:creator>Akshay Rastogi</dc:creator>
      <dc:date>2015-11-01T07:31:21Z</dc:date>
    </item>
  </channel>
</rss>

