<?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: Inactive CS-MARS reporting device (again) in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/inactive-cs-mars-reporting-device-again/m-p/676200#M92353</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I vaguely recall reading something about not being able to use a drop rule to prevent these.  You have to inactivate the rule.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 19 Sep 2006 16:53:37 GMT</pubDate>
    <dc:creator>mhellman</dc:creator>
    <dc:date>2006-09-19T16:53:37Z</dc:date>
    <item>
      <title>Inactive CS-MARS reporting device (again)</title>
      <link>https://community.cisco.com/t5/network-security/inactive-cs-mars-reporting-device-again/m-p/676199#M92351</link>
      <description>&lt;P&gt;I created a drop rule, dest and src ip's are "ANY", and the hostnames as seen in MARS.  I chose to "drop" as action...not "log to db only".  The event is "Inactive CS-MARS reporting device, device is "ANY",  severity is "ANY", time range is "ANY"  I clicked apply, submit and activate.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;How come on my Summary | dashboard screen I still see these incidences.  I was hoping this would stop.  Is this expected behavior, or have I done something incorrectly?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Bob&lt;/P&gt;</description>
      <pubDate>Sun, 10 Mar 2019 10:13:53 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/inactive-cs-mars-reporting-device-again/m-p/676199#M92351</guid>
      <dc:creator>laamidd2003</dc:creator>
      <dc:date>2019-03-10T10:13:53Z</dc:date>
    </item>
    <item>
      <title>Re: Inactive CS-MARS reporting device (again)</title>
      <link>https://community.cisco.com/t5/network-security/inactive-cs-mars-reporting-device-again/m-p/676200#M92353</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I vaguely recall reading something about not being able to use a drop rule to prevent these.  You have to inactivate the rule.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 19 Sep 2006 16:53:37 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/inactive-cs-mars-reporting-device-again/m-p/676200#M92353</guid>
      <dc:creator>mhellman</dc:creator>
      <dc:date>2006-09-19T16:53:37Z</dc:date>
    </item>
    <item>
      <title>Re: Inactive CS-MARS reporting device (again)</title>
      <link>https://community.cisco.com/t5/network-security/inactive-cs-mars-reporting-device-again/m-p/676201#M92356</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I've solved that problem including "ANY" and "0.0.0.0" in the source address. CS-MARS doesn't understand that ANY must include 0.0.0.0. &lt;/P&gt;&lt;P&gt;Concerning to the dashboard you'll see the events for a time, and previous incidents will be saved in the incident list. Since you add "0.0.0.0" in source address, you won't see any inactive cs-mars event. The most important issue filtering that event is that it is a very high amount of events and all reports must be created using "!=Inactive CS-MARS reporting device". &lt;/P&gt;&lt;P&gt;As I told you, from now you won't see that event any more.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Good luck!!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;ps: Please, rate the post.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 20 Sep 2006 05:34:22 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/inactive-cs-mars-reporting-device-again/m-p/676201#M92356</guid>
      <dc:creator>JUCETA</dc:creator>
      <dc:date>2006-09-20T05:34:22Z</dc:date>
    </item>
    <item>
      <title>Re: Inactive CS-MARS reporting device (again)</title>
      <link>https://community.cisco.com/t5/network-security/inactive-cs-mars-reporting-device-again/m-p/676202#M92358</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks Juceta,&lt;/P&gt;&lt;P&gt;That seems to have solved the problem, no new incidences for the last couple of hours.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Bob&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 20 Sep 2006 12:00:30 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/inactive-cs-mars-reporting-device-again/m-p/676202#M92358</guid>
      <dc:creator>laamidd2003</dc:creator>
      <dc:date>2006-09-20T12:00:30Z</dc:date>
    </item>
    <item>
      <title>Re: Inactive CS-MARS reporting device (again)</title>
      <link>https://community.cisco.com/t5/network-security/inactive-cs-mars-reporting-device-again/m-p/676203#M92360</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Here is the bug id.  It appears to have been fixed now based on your results.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-custom" href="http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCsc49248&amp;amp;cco_product=Cisco+Security+Monitoring,+Analysis+and+Response+System&amp;amp;fset=&amp;amp;swver=&amp;amp;keyw=reporting&amp;amp;target=&amp;amp;train" target="_blank"&gt;http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCsc49248&amp;amp;cco_product=Cisco+Security+Monitoring,+Analysis+and+Response+System&amp;amp;fset=&amp;amp;swver=&amp;amp;keyw=reporting&amp;amp;target=&amp;amp;train&lt;/A&gt;=&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 20 Sep 2006 13:34:35 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/inactive-cs-mars-reporting-device-again/m-p/676203#M92360</guid>
      <dc:creator>mhellman</dc:creator>
      <dc:date>2006-09-20T13:34:35Z</dc:date>
    </item>
  </channel>
</rss>

