<?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: IPS Alerting to multiple locations in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/ips-alerting-to-multiple-locations/m-p/1492826#M66660</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;If your sensor is not overloaded today, it's doubtfull that adding an additional SDEE feed will push it over the edge. But if you're already showing a missed packet percentage in your logs, then adding another event feed won't do your sensor any favors.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;- Bob&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 27 Aug 2010 18:15:03 GMT</pubDate>
    <dc:creator>rhermes</dc:creator>
    <dc:date>2010-08-27T18:15:03Z</dc:date>
    <item>
      <title>IPS Alerting to multiple locations</title>
      <link>https://community.cisco.com/t5/network-security/ips-alerting-to-multiple-locations/m-p/1492825#M66659</link>
      <description>&lt;P&gt;Will adding multiple alerting destinations have a dramatic CPU impact&lt;/P&gt;&lt;P&gt;over a single destination when under significant alerting load?&lt;/P&gt;</description>
      <pubDate>Sun, 10 Mar 2019 12:06:41 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ips-alerting-to-multiple-locations/m-p/1492825#M66659</guid>
      <dc:creator>cwmontgo</dc:creator>
      <dc:date>2019-03-10T12:06:41Z</dc:date>
    </item>
    <item>
      <title>Re: IPS Alerting to multiple locations</title>
      <link>https://community.cisco.com/t5/network-security/ips-alerting-to-multiple-locations/m-p/1492826#M66660</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;If your sensor is not overloaded today, it's doubtfull that adding an additional SDEE feed will push it over the edge. But if you're already showing a missed packet percentage in your logs, then adding another event feed won't do your sensor any favors.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;- Bob&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 27 Aug 2010 18:15:03 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ips-alerting-to-multiple-locations/m-p/1492826#M66660</guid>
      <dc:creator>rhermes</dc:creator>
      <dc:date>2010-08-27T18:15:03Z</dc:date>
    </item>
    <item>
      <title>Re: IPS Alerting to multiple locations</title>
      <link>https://community.cisco.com/t5/network-security/ips-alerting-to-multiple-locations/m-p/1492827#M66661</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;In addition to Bob's points, please be aware that Cisco's IPS sensors have a limit to five (5) open SDEE subscriptions; this equates to five (5) "alerting destinations". If you configure more than five (5) you may encounter subscription contention and inconsistent events being logged at each destination.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Scott&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 30 Aug 2010 11:00:03 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ips-alerting-to-multiple-locations/m-p/1492827#M66661</guid>
      <dc:creator>Scott Fringer</dc:creator>
      <dc:date>2010-08-30T11:00:03Z</dc:date>
    </item>
  </channel>
</rss>

