<?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 drop rate exceeded, exclude specific host in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/drop-rate-exceeded-exclude-specific-host/m-p/2437117#M268800</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you would like to stop the&lt;STRONG&gt;"drop rate-&lt;X&gt; exceeded" &lt;/X&gt;&lt;/STRONG&gt;messages for a specific host , that would not be possible on the ASA device. Depending on the configuration on the ASA device , if you have Scanning threat detecttion enabled and this server is being shunned , you would be able to exclude this host using &lt;STRONG&gt;threat-detection scanning-threat except &lt;/STRONG&gt;command on the ASA device.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks and Regards,&lt;/P&gt;&lt;P&gt;Vibhor&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Sat, 01 Mar 2014 20:37:27 GMT</pubDate>
    <dc:creator>Vibhor Amrodia</dc:creator>
    <dc:date>2014-03-01T20:37:27Z</dc:date>
    <item>
      <title>drop rate exceeded, exclude specific host</title>
      <link>https://community.cisco.com/t5/network-security/drop-rate-exceeded-exclude-specific-host/m-p/2437116#M268799</link>
      <description>&lt;P&gt;In our ASA 5520 we see a lot of messages with "drop rate-&amp;lt;x&amp;gt; exceeded". These messages are caused by our Zabbix server that is pinging to about 300 network routers in our nation wide retail network every 60 seconds.&lt;/P&gt;&lt;P&gt;I know that we can ignore these messages or change the threat-detection rate settings. But what we really want is just to exclude the thread-detection for our Zabbix host.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is it possible and how?&lt;/P&gt;</description>
      <pubDate>Tue, 12 Mar 2019 03:52:24 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/drop-rate-exceeded-exclude-specific-host/m-p/2437116#M268799</guid>
      <dc:creator>n.vd.coevering</dc:creator>
      <dc:date>2019-03-12T03:52:24Z</dc:date>
    </item>
    <item>
      <title>drop rate exceeded, exclude specific host</title>
      <link>https://community.cisco.com/t5/network-security/drop-rate-exceeded-exclude-specific-host/m-p/2437117#M268800</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you would like to stop the&lt;STRONG&gt;"drop rate-&lt;X&gt; exceeded" &lt;/X&gt;&lt;/STRONG&gt;messages for a specific host , that would not be possible on the ASA device. Depending on the configuration on the ASA device , if you have Scanning threat detecttion enabled and this server is being shunned , you would be able to exclude this host using &lt;STRONG&gt;threat-detection scanning-threat except &lt;/STRONG&gt;command on the ASA device.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks and Regards,&lt;/P&gt;&lt;P&gt;Vibhor&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 01 Mar 2014 20:37:27 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/drop-rate-exceeded-exclude-specific-host/m-p/2437117#M268800</guid>
      <dc:creator>Vibhor Amrodia</dc:creator>
      <dc:date>2014-03-01T20:37:27Z</dc:date>
    </item>
    <item>
      <title>drop rate exceeded, exclude specific host</title>
      <link>https://community.cisco.com/t5/network-security/drop-rate-exceeded-exclude-specific-host/m-p/2437118#M268801</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks Vibhor for confirming what I thought. We are still debating if we are going to enable shunning.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 02 Mar 2014 21:56:55 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/drop-rate-exceeded-exclude-specific-host/m-p/2437118#M268801</guid>
      <dc:creator>n.vd.coevering</dc:creator>
      <dc:date>2014-03-02T21:56:55Z</dc:date>
    </item>
    <item>
      <title>drop rate exceeded, exclude specific host</title>
      <link>https://community.cisco.com/t5/network-security/drop-rate-exceeded-exclude-specific-host/m-p/2437119#M268802</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;but you could enable shunning and disable shun for the zabix host, why not test this behavior ???&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 03 Mar 2014 17:47:01 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/drop-rate-exceeded-exclude-specific-host/m-p/2437119#M268802</guid>
      <dc:creator>INGENIERIA Y CONSULTORIAS WEBREDES LTDA</dc:creator>
      <dc:date>2014-03-03T17:47:01Z</dc:date>
    </item>
    <item>
      <title>drop rate exceeded, exclude specific host</title>
      <link>https://community.cisco.com/t5/network-security/drop-rate-exceeded-exclude-specific-host/m-p/2437120#M268803</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Yes, this is possible. But after enabling shunning and excluding the host, warning messages still keep appearing for his host.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 04 Mar 2014 10:49:25 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/drop-rate-exceeded-exclude-specific-host/m-p/2437120#M268803</guid>
      <dc:creator>n.vd.coevering</dc:creator>
      <dc:date>2014-03-04T10:49:25Z</dc:date>
    </item>
  </channel>
</rss>

