<?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 IDSM2 IDM not accessible in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/idsm2-idm-not-accessible/m-p/789432#M85967</link>
    <description>&lt;P&gt;Hi all&lt;/P&gt;&lt;P&gt;I have one IDSM2 version 5.1(6)E1 running promiscuous mode monitoring 2 vlans. The IDSM2 is monitored by a MARS50 with "Pull IP log" activated and the IDSM2 has the options "overrides log-pair-packets" and "overrides produce-verbose-alert" activated as described in the MARS manual.&lt;/P&gt;&lt;P&gt;My guess is that these settings caused the MARS to overload the web server on the IDSM because now the MARS can't fetch any new events from the IDSM2 and I can't access the web interface.&lt;/P&gt;&lt;P&gt;Any ideas how to fix this? I can't find any option to "reboot" the web service on the sernsor. I guess rebooting the sensor itself is one option but I'd rahter not do that.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Fredrik Hofgren&lt;/P&gt;</description>
    <pubDate>Sun, 10 Mar 2019 10:45:01 GMT</pubDate>
    <dc:creator>hoffa2000</dc:creator>
    <dc:date>2019-03-10T10:45:01Z</dc:date>
    <item>
      <title>IDSM2 IDM not accessible</title>
      <link>https://community.cisco.com/t5/network-security/idsm2-idm-not-accessible/m-p/789432#M85967</link>
      <description>&lt;P&gt;Hi all&lt;/P&gt;&lt;P&gt;I have one IDSM2 version 5.1(6)E1 running promiscuous mode monitoring 2 vlans. The IDSM2 is monitored by a MARS50 with "Pull IP log" activated and the IDSM2 has the options "overrides log-pair-packets" and "overrides produce-verbose-alert" activated as described in the MARS manual.&lt;/P&gt;&lt;P&gt;My guess is that these settings caused the MARS to overload the web server on the IDSM because now the MARS can't fetch any new events from the IDSM2 and I can't access the web interface.&lt;/P&gt;&lt;P&gt;Any ideas how to fix this? I can't find any option to "reboot" the web service on the sernsor. I guess rebooting the sensor itself is one option but I'd rahter not do that.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Fredrik Hofgren&lt;/P&gt;</description>
      <pubDate>Sun, 10 Mar 2019 10:45:01 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/idsm2-idm-not-accessible/m-p/789432#M85967</guid>
      <dc:creator>hoffa2000</dc:creator>
      <dc:date>2019-03-10T10:45:01Z</dc:date>
    </item>
    <item>
      <title>Re: IDSM2 IDM not accessible</title>
      <link>https://community.cisco.com/t5/network-security/idsm2-idm-not-accessible/m-p/789433#M85971</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;A full IDSM2 reset solved the problem but I had hoped there would be an option to restart just the web service.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 17 Aug 2007 06:20:28 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/idsm2-idm-not-accessible/m-p/789433#M85971</guid>
      <dc:creator>hoffa2000</dc:creator>
      <dc:date>2007-08-17T06:20:28Z</dc:date>
    </item>
  </channel>
</rss>

