<?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: Can an IDSM2 Bring Down a 6513 ?? in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/can-an-idsm2-bring-down-a-6513/m-p/407421#M100191</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;There is nothing in the module itself or in the IPS code that could bring the network down when running promiscuous mode.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;However, there could be something in the switch code and how it interacts with the module.  It would be a switch bug and not an IPS software bug.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have heard of some issues with spanning tree and the msfc autostate on the supervisor when the IDSM-2 interfaces go down and up.&lt;/P&gt;&lt;P&gt;I am not sure what the state of those DDTS Issues are.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It is possible that there is an issue on the IDSM-2 that causes it to bring it's ports down and up, which could then trigger a spanning tree or msfc autostate issue on the switch itself.  So one issue on the IDSM-2 could trigger a separate issue on the switch.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you were going to attempt further debugging you would want to concentrate on what is happening to both the IDSM-2 and the switch.  &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You may also want to check what version is running on your switch.  You may want to ensure you are running the latest IOS version.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 25 Jul 2005 15:29:09 GMT</pubDate>
    <dc:creator>marcabal</dc:creator>
    <dc:date>2005-07-25T15:29:09Z</dc:date>
    <item>
      <title>Can an IDSM2 Bring Down a 6513 ??</title>
      <link>https://community.cisco.com/t5/network-security/can-an-idsm2-bring-down-a-6513/m-p/407420#M100159</link>
      <description>&lt;P&gt;We have had 2 instances in the past 2 months where our 'network' came to a crawl/stop. It is related to our IDSM2 blade in our 6513 via&lt;/P&gt;&lt;P&gt;  a) Moments before stoppage, could not ping management intf of IDSM2&lt;/P&gt;&lt;P&gt;  b) After issuing reset via the 6513&lt;/P&gt;&lt;P&gt;by the command: &lt;/P&gt;&lt;P&gt;   hw-module module 11 reset&lt;/P&gt;&lt;P&gt;   The Network returned to normal.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;notes: 1) The IDSM2 is a 4.1 sensor with the latest software 4.1.g.&lt;/P&gt;&lt;P&gt;       2) There is no TCP Reset or Blocking being done.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I opened a TAC case after the first instance, but a top engineer did not &lt;/P&gt;&lt;P&gt;think a IDSM2 could bring down a 6513.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks for any thoughts ! &lt;/P&gt;&lt;P&gt;&lt;/P&gt;</description>
      <pubDate>Sun, 10 Mar 2019 09:33:18 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/can-an-idsm2-bring-down-a-6513/m-p/407420#M100159</guid>
      <dc:creator>davidculp</dc:creator>
      <dc:date>2019-03-10T09:33:18Z</dc:date>
    </item>
    <item>
      <title>Re: Can an IDSM2 Bring Down a 6513 ??</title>
      <link>https://community.cisco.com/t5/network-security/can-an-idsm2-bring-down-a-6513/m-p/407421#M100191</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;There is nothing in the module itself or in the IPS code that could bring the network down when running promiscuous mode.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;However, there could be something in the switch code and how it interacts with the module.  It would be a switch bug and not an IPS software bug.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have heard of some issues with spanning tree and the msfc autostate on the supervisor when the IDSM-2 interfaces go down and up.&lt;/P&gt;&lt;P&gt;I am not sure what the state of those DDTS Issues are.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It is possible that there is an issue on the IDSM-2 that causes it to bring it's ports down and up, which could then trigger a spanning tree or msfc autostate issue on the switch itself.  So one issue on the IDSM-2 could trigger a separate issue on the switch.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you were going to attempt further debugging you would want to concentrate on what is happening to both the IDSM-2 and the switch.  &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You may also want to check what version is running on your switch.  You may want to ensure you are running the latest IOS version.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 25 Jul 2005 15:29:09 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/can-an-idsm2-bring-down-a-6513/m-p/407421#M100191</guid>
      <dc:creator>marcabal</dc:creator>
      <dc:date>2005-07-25T15:29:09Z</dc:date>
    </item>
  </channel>
</rss>

