<?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 what wrong about my 7507 in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/what-wrong-about-my-7507/m-p/261494#M1060101</link>
    <description>&lt;P&gt;a pos interface of my 7507, it's line protocol has become "up" and "down" for some minutes.&lt;/P&gt;&lt;P&gt;This is the show log text:&lt;/P&gt;&lt;P&gt;Apr 14 14:41:17 cst: %RSP-3-ERROR: MD error 0000008000002000&lt;/P&gt;&lt;P&gt;-Traceback= 60332754 60332E70 60332FA8 603339A4 6030D3AC&lt;/P&gt;&lt;P&gt;Apr 14 14:41:17 cst: %RSP-3-ERROR:   SRAM parity error (bytes 0:7) 02&lt;/P&gt;&lt;P&gt;-Traceback= 60332830 60332E70 60332FA8 603339A4 6030D3AC&lt;/P&gt;&lt;P&gt;Apr 14 14:41:17 cst: %VIP4-80 RM7000-3-MSG: slot5 VIP-3-MVIP_CYBUSERROR_INTERRUPT: A Cybus Error occurred.&lt;/P&gt;&lt;P&gt;Apr 14 14:41:18 cst: %VIP4-80 RM7000-3-MSG: slot5 VIP-3-SVIP_RELOAD: SVIP Reload is called. &lt;/P&gt;&lt;P&gt;Apr 14 14:41:18 cst: %VIP4-80 RM7000-3-MSG: slot5 VIP-3-SYSTEM_EXCEPTION: VIP System Exception occurred sig=22, &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;code=0x0, context=0x605FE788&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;Apr 14 14:41:19 cst: %DBUS-3-CXBUSERR: Slot 5, CBus Error&lt;/P&gt;&lt;P&gt;Apr 14 14:41:19 cst: %DBUS-3-DBUSINTERRSWSET: Slot 5, Internal Error due to VIP crash&lt;/P&gt;&lt;P&gt;Apr 14 14:41:19 cst: %RSP-3-ERROR: End of MEMD error interrupt processing&lt;/P&gt;&lt;P&gt;-Traceback= 60332F40 60332FA8 603339A4 6030D3AC&lt;/P&gt;&lt;P&gt;Apr 14 14:41:19 cst: %DBUS-3-CXBUSERR: Slot 5, CBus Error&lt;/P&gt;&lt;P&gt;Apr 14 14:41:19 cst: %DBUS-3-DBUSINTERRSWSET: Slot 5, Internal Error due to VIP crash&lt;/P&gt;&lt;P&gt;Apr 14 14:41:20 cst: %CBUS-3-CMDTIMEOUT: Cmd timed out, CCB 0x5800FF30, slot 1, cmd code 2&lt;/P&gt;&lt;P&gt;-Traceback= 6037B100 6037B5EC 603734A4 603714DC 602BE770 602BE9A0 602E0FC4 602E0FB0&lt;/P&gt;&lt;P&gt;Apr 14 14:41:20 cst: %CBUS-3-CMDTIMEOUT: Cmd timed out, CCB 0x5800FF60, slot 4, cmd code 2&lt;/P&gt;&lt;P&gt;-Traceback= 6037B100 6037B5EC 603734A4 603714DC 602BE770 602BE9A0 602E0FC4 602E0FB0&lt;/P&gt;&lt;P&gt;Apr 14 14:41:21 cst: %CBUS-3-CMDTIMEOUT: Cmd timed out, CCB 0x5800FF20, slot 0, cmd code 2&lt;/P&gt;&lt;P&gt;-Traceback= 6037B100 6037B5EC 603734A4 603714DC 602BE770 602BE9A0 602E0FC4 602E0FB0&lt;/P&gt;&lt;P&gt;Apr 14 14:41:21 cst: %IPC_RSP_CBUS-3-NOBUF: No more IPC memd buffers to transmit IPC message&lt;/P&gt;&lt;P&gt;Apr 14 14:41:22 cst: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/0, changed state to down  &lt;/P&gt;</description>
    <pubDate>Fri, 21 Feb 2020 07:20:34 GMT</pubDate>
    <dc:creator>admin_2</dc:creator>
    <dc:date>2020-02-21T07:20:34Z</dc:date>
    <item>
      <title>what wrong about my 7507</title>
      <link>https://community.cisco.com/t5/network-security/what-wrong-about-my-7507/m-p/261494#M1060101</link>
      <description>&lt;P&gt;a pos interface of my 7507, it's line protocol has become "up" and "down" for some minutes.&lt;/P&gt;&lt;P&gt;This is the show log text:&lt;/P&gt;&lt;P&gt;Apr 14 14:41:17 cst: %RSP-3-ERROR: MD error 0000008000002000&lt;/P&gt;&lt;P&gt;-Traceback= 60332754 60332E70 60332FA8 603339A4 6030D3AC&lt;/P&gt;&lt;P&gt;Apr 14 14:41:17 cst: %RSP-3-ERROR:   SRAM parity error (bytes 0:7) 02&lt;/P&gt;&lt;P&gt;-Traceback= 60332830 60332E70 60332FA8 603339A4 6030D3AC&lt;/P&gt;&lt;P&gt;Apr 14 14:41:17 cst: %VIP4-80 RM7000-3-MSG: slot5 VIP-3-MVIP_CYBUSERROR_INTERRUPT: A Cybus Error occurred.&lt;/P&gt;&lt;P&gt;Apr 14 14:41:18 cst: %VIP4-80 RM7000-3-MSG: slot5 VIP-3-SVIP_RELOAD: SVIP Reload is called. &lt;/P&gt;&lt;P&gt;Apr 14 14:41:18 cst: %VIP4-80 RM7000-3-MSG: slot5 VIP-3-SYSTEM_EXCEPTION: VIP System Exception occurred sig=22, &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;code=0x0, context=0x605FE788&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;Apr 14 14:41:19 cst: %DBUS-3-CXBUSERR: Slot 5, CBus Error&lt;/P&gt;&lt;P&gt;Apr 14 14:41:19 cst: %DBUS-3-DBUSINTERRSWSET: Slot 5, Internal Error due to VIP crash&lt;/P&gt;&lt;P&gt;Apr 14 14:41:19 cst: %RSP-3-ERROR: End of MEMD error interrupt processing&lt;/P&gt;&lt;P&gt;-Traceback= 60332F40 60332FA8 603339A4 6030D3AC&lt;/P&gt;&lt;P&gt;Apr 14 14:41:19 cst: %DBUS-3-CXBUSERR: Slot 5, CBus Error&lt;/P&gt;&lt;P&gt;Apr 14 14:41:19 cst: %DBUS-3-DBUSINTERRSWSET: Slot 5, Internal Error due to VIP crash&lt;/P&gt;&lt;P&gt;Apr 14 14:41:20 cst: %CBUS-3-CMDTIMEOUT: Cmd timed out, CCB 0x5800FF30, slot 1, cmd code 2&lt;/P&gt;&lt;P&gt;-Traceback= 6037B100 6037B5EC 603734A4 603714DC 602BE770 602BE9A0 602E0FC4 602E0FB0&lt;/P&gt;&lt;P&gt;Apr 14 14:41:20 cst: %CBUS-3-CMDTIMEOUT: Cmd timed out, CCB 0x5800FF60, slot 4, cmd code 2&lt;/P&gt;&lt;P&gt;-Traceback= 6037B100 6037B5EC 603734A4 603714DC 602BE770 602BE9A0 602E0FC4 602E0FB0&lt;/P&gt;&lt;P&gt;Apr 14 14:41:21 cst: %CBUS-3-CMDTIMEOUT: Cmd timed out, CCB 0x5800FF20, slot 0, cmd code 2&lt;/P&gt;&lt;P&gt;-Traceback= 6037B100 6037B5EC 603734A4 603714DC 602BE770 602BE9A0 602E0FC4 602E0FB0&lt;/P&gt;&lt;P&gt;Apr 14 14:41:21 cst: %IPC_RSP_CBUS-3-NOBUF: No more IPC memd buffers to transmit IPC message&lt;/P&gt;&lt;P&gt;Apr 14 14:41:22 cst: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/0, changed state to down  &lt;/P&gt;</description>
      <pubDate>Fri, 21 Feb 2020 07:20:34 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/what-wrong-about-my-7507/m-p/261494#M1060101</guid>
      <dc:creator>admin_2</dc:creator>
      <dc:date>2020-02-21T07:20:34Z</dc:date>
    </item>
    <item>
      <title>Re: what wrong about my 7507</title>
      <link>https://community.cisco.com/t5/network-security/what-wrong-about-my-7507/m-p/261495#M1060102</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Please review the following page for troubleshooting IPC error messages :&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-custom" href="http://www.cisco.com/warp/public/63/ipcnobuff_21165.html" target="_blank"&gt;http://www.cisco.com/warp/public/63/ipcnobuff_21165.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Distributed CEF uses IPC (inter process communications) to update CEF table on the VIPS.&lt;/P&gt;&lt;P&gt;In some occasions, where a lot of routing updates are received or when we have to delete&lt;/P&gt;&lt;P&gt;an important amount of routes, we may be running&lt;/P&gt;&lt;P&gt;short on IPC buffers causing distributed CEF to be disabled on the linecards. It has to reenabled&lt;/P&gt;&lt;P&gt;again via "ip distributed cef". The number of IPC buffers has been made tunable to deal with that&lt;/P&gt;&lt;P&gt;situation.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I would recommend you configure : "ipc cache 5000" in global configuration mode and you should&lt;/P&gt;&lt;P&gt;get rid of this problem.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Having said that, you're also getting a traceback which implies a software bug, but I can't decode it without a "sho ver" output.  I would suggest that if increasing the ipc buffers doesn't help, open a TAC case and include a "sho tech" output from this router.  They'll be able to figure it out then.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 16 Apr 2004 05:22:52 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/what-wrong-about-my-7507/m-p/261495#M1060102</guid>
      <dc:creator>gfullage</dc:creator>
      <dc:date>2004-04-16T05:22:52Z</dc:date>
    </item>
  </channel>
</rss>

