<?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: idsm2 reboot unexpectedly in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/idsm2-reboot-unexpectedly/m-p/1562790#M66099</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I would first check if the module is properly seated in the slot, chaning the slot can also sometimes help.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If the above fail, most probably seems to be a RMA candidate. The best option is to open a TAC Case, and they will generate the RMA for you automatically if that is the only solution&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Please rate if helpful&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Farrukh&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 22 Nov 2010 13:03:34 GMT</pubDate>
    <dc:creator>Farrukh Haroon</dc:creator>
    <dc:date>2010-11-22T13:03:34Z</dc:date>
    <item>
      <title>idsm2 reboot unexpectedly</title>
      <link>https://community.cisco.com/t5/network-security/idsm2-reboot-unexpectedly/m-p/1562789#M66098</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We have one Catalyst 6509 with IDSM2, and the IDSM2 reboot unexpectedly. The error message is :&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Nov 17 22:32:47: %OIR-SP-3-PWRCYCLE: Card in module 9, is being power-cycled off (Module not responding to Keep Alive polling)&lt;BR /&gt;Nov 17 22:32:48: %C6KPWR-SP-4-DISABLED: power to module in slot 9 set off (Module not responding to Keep Alive polling)&lt;BR /&gt;Nov 17 22:36:21: %DIAG-SP-6-RUN_MINIMUM: Module 9: Running Minimum Diagnostics...&lt;BR /&gt;Nov 17 22:36:22: %MLS_RATE-4-DISABLING: The Layer2 Rate Limiters have been disabled.&lt;BR /&gt;Nov 17 22:36:22: %DIAG-SP-6-DIAG_OK: Module 9: Passed Online Diagnostics&lt;BR /&gt;Nov 17 22:36:23: %OIR-SP-6-INSCARD: Card inserted in slot 9, interfaces are now online&lt;/P&gt;&lt;P&gt;Nov 20 18:47:26: %OIR-SP-3-PWRCYCLE: Card in module 9, is being power-cycled off (Module not responding to Keep Alive polling)&lt;BR /&gt;Nov 20 18:47:26: %C6KPWR-SP-4-DISABLED: power to module in slot 9 set off (Module not responding to Keep Alive polling)&lt;BR /&gt;Nov 20 18:51:00: %DIAG-SP-6-RUN_MINIMUM: Module 9: Running Minimum Diagnostics...&lt;BR /&gt;Nov 20 18:51:01: %MLS_RATE-4-DISABLING: The Layer2 Rate Limiters have been disabled.&lt;BR /&gt;Nov 20 18:51:01: %DIAG-SP-6-DIAG_OK: Module 9: Passed Online Diagnostics&lt;BR /&gt;Nov 20 18:51:01: %OIR-SP-6-INSCARD: Card inserted in slot 9, interfaces are now online&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It occured several times before 11/17 and I have tried to reseat the module before, but the IDSM2 reboot again. The IOS version of supervisor engine is s72033-ps-mz.122-18.SXD5.bin, The IDSM2 software version is 6.0(5)E2. Please help to diagnosis this problem. Shall I upgrade IOS of supervisor engine or IDSM or need RMA?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Best Regards,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Jackson Ku&lt;/P&gt;</description>
      <pubDate>Sun, 10 Mar 2019 12:11:19 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/idsm2-reboot-unexpectedly/m-p/1562789#M66098</guid>
      <dc:creator>jackson.ku</dc:creator>
      <dc:date>2019-03-10T12:11:19Z</dc:date>
    </item>
    <item>
      <title>Re: idsm2 reboot unexpectedly</title>
      <link>https://community.cisco.com/t5/network-security/idsm2-reboot-unexpectedly/m-p/1562790#M66099</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I would first check if the module is properly seated in the slot, chaning the slot can also sometimes help.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If the above fail, most probably seems to be a RMA candidate. The best option is to open a TAC Case, and they will generate the RMA for you automatically if that is the only solution&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Please rate if helpful&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Farrukh&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 22 Nov 2010 13:03:34 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/idsm2-reboot-unexpectedly/m-p/1562790#M66099</guid>
      <dc:creator>Farrukh Haroon</dc:creator>
      <dc:date>2010-11-22T13:03:34Z</dc:date>
    </item>
    <item>
      <title>Re: idsm2 reboot unexpectedly</title>
      <link>https://community.cisco.com/t5/network-security/idsm2-reboot-unexpectedly/m-p/1562791#M66100</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;/P&gt;&lt;DIV&gt;&lt;P&gt;Agreed, this likely needs to have a TAC case opened for an RMA -- especially if a re-seat of the module has already been attempted.&amp;nbsp; Any time you're seeing the switch cut off power to the module over multiple insertions, that's not a good thing.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I just had this happen to a FWSM last week, and re-seating the module didn't work for me, either.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You can read more about the error message here:&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.cisco.com/en/US/partner/products/hw/switches/ps700/products_tech_note09186a00801b42bf.shtml"&gt;http://www.cisco.com/en/US/partner/products/hw/switches/ps700/products_tech_note09186a00801b42bf.shtml&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;PRE __jive_macro_name="quote" class="jive_text_macro jive_macro_quote"&gt;&lt;P&gt;&lt;STRONG style="text-decoration: underline; "&gt;Workaround&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;A simple reseat of the module corrects this issue 90 percent of the time. If you reseat the module, it realigns the switch fabric and ensures a firm connection to the backplane.&lt;/P&gt;&lt;DIV&gt; &lt;/DIV&gt;&lt;/PRE&gt;&lt;/DIV&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 23 Nov 2010 01:28:51 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/idsm2-reboot-unexpectedly/m-p/1562791#M66100</guid>
      <dc:creator>mikecrowe4ICS_2</dc:creator>
      <dc:date>2010-11-23T01:28:51Z</dc:date>
    </item>
  </channel>
</rss>

