<?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 Re: High Xlate Count in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/high-xlate-count/m-p/952014#M940095</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Brian&lt;/P&gt;&lt;P&gt;  Please open your PDM or ASDM syslog and check if any critical logs appear. Copy and paste one if any.&lt;/P&gt;&lt;P&gt;  And please copy and paste a part of "show xlate debug" output. &lt;/P&gt;&lt;P&gt;  If this is a DOS attack, that supposed to be outside oriented. Then we would apply a max session limit to the static you created.&lt;/P&gt;&lt;P&gt;  If this is an attempt from inside, most probably the xlate or syslog outputs will show one or two public IP addresses that inside host try to connect. Then we would stop this with an ACL to inside interface.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 31 Mar 2008 14:48:22 GMT</pubDate>
    <dc:creator>Alan Huseyin Kayahan</dc:creator>
    <dc:date>2008-03-31T14:48:22Z</dc:date>
    <item>
      <title>High Xlate Count</title>
      <link>https://community.cisco.com/t5/network-security/high-xlate-count/m-p/952012#M940085</link>
      <description>&lt;P&gt;I have a PIX 515E 6.3(5). Our network is obviously being attacked by viruses and the xlate count is skyrocketing to &amp;gt; 50,000 which basically shuts down our internet. Is there anything I can do on the PIX to block traffic to prevent this from happening. Any advice?&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 12:24:36 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/high-xlate-count/m-p/952012#M940085</guid>
      <dc:creator>b.calsing</dc:creator>
      <dc:date>2019-03-11T12:24:36Z</dc:date>
    </item>
    <item>
      <title>Re: High Xlate Count</title>
      <link>https://community.cisco.com/t5/network-security/high-xlate-count/m-p/952013#M940091</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;can you please send configuration file.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 31 Mar 2008 02:13:26 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/high-xlate-count/m-p/952013#M940091</guid>
      <dc:creator>ray_stone</dc:creator>
      <dc:date>2008-03-31T02:13:26Z</dc:date>
    </item>
    <item>
      <title>Re: High Xlate Count</title>
      <link>https://community.cisco.com/t5/network-security/high-xlate-count/m-p/952014#M940095</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Brian&lt;/P&gt;&lt;P&gt;  Please open your PDM or ASDM syslog and check if any critical logs appear. Copy and paste one if any.&lt;/P&gt;&lt;P&gt;  And please copy and paste a part of "show xlate debug" output. &lt;/P&gt;&lt;P&gt;  If this is a DOS attack, that supposed to be outside oriented. Then we would apply a max session limit to the static you created.&lt;/P&gt;&lt;P&gt;  If this is an attempt from inside, most probably the xlate or syslog outputs will show one or two public IP addresses that inside host try to connect. Then we would stop this with an ACL to inside interface.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 31 Mar 2008 14:48:22 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/high-xlate-count/m-p/952014#M940095</guid>
      <dc:creator>Alan Huseyin Kayahan</dc:creator>
      <dc:date>2008-03-31T14:48:22Z</dc:date>
    </item>
    <item>
      <title>Re: High Xlate Count</title>
      <link>https://community.cisco.com/t5/network-security/high-xlate-count/m-p/952015#M940098</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I've had that happen before, and here is a quick work around, it does'nt fix your problem with machines on teh inside having virus's, but it stops them from tying up the outside interface and using up xlate's.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;what you need to do is do a show xlate from the CLI, you will start to see a pattern of what internal IP's are using up the xlate sessions, you then SHUN those ip's , this will  stop them from accessing the internet, you then do a clear xlate, this disconnects all the current sessions,(interupst FTP's and streaming connections also).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This will buy you some time in order to download the latest DAT's and fix the virus' on the machines you shunned.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope this helps..&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 31 Mar 2008 16:54:56 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/high-xlate-count/m-p/952015#M940098</guid>
      <dc:creator>bmanderson</dc:creator>
      <dc:date>2008-03-31T16:54:56Z</dc:date>
    </item>
  </channel>
</rss>

