S/K-Series has MEM_FAIL Reset with Status 0x00000200

  • 0
  • 1
  • Article
  • Updated 5 years ago
  • (Edited)
Article ID: 14830 

Products
S-Series, firmware 7.11.01.0026 through 7.72.02.0004
K-Series, firmware 7.31.02.0008 through 7.72.02.0004 

Symptoms
Module reset. 

The fault logs ('show support') contain bcmStrat-originated messages forming a diagnostic sequence beginning with "MEM_FAIL interrupt", and the sequence matches one of the following two conditions: 

* With newer S/K-Series firmware 7.22.01.0002 and higher, "MEM_FAIL_INT_STAT=0x00000200" (and typically "IP1_INTR_STATUS=0x00000000"); for example: 

    For the S-Series...
==============================================================================
Message 4/197 Shutdown 07.41.02.0014 09/13/2012 03:06:30

Initiated - Reset
Shutdown process is starting.

==============================================================================
Message 5/197 Syslog Message 07.41.02.0014 09/13/2012 03:06:30
<0>bcmStrat[2.tNimIntr]Chip 0 has encountered a fatal error. ( 0x009deba
0 0x00a9d35c 0x00aa2174 0x00aa7004 0x00a9fc68 0x0044be38 0x0044de04 0x01
1541b4 0xeeeeeeee )

==============================================================================
Message 6/197 Syslog Message 07.41.02.0014 09/13/2012 03:06:30
<3>bcmStrat[2.tNimIntr]MEM_FAIL_INT_STAT=0x00000200, EP_INTR_STATUS=0x00
000000, IP0_INTR_STATUS=0x00000000, IP1_INTR_STATUS=0x00000000, IP2_INTR
_STATUS=0x00000000, IP3_INTR_STATUS=0x00000000

==============================================================================
Message 7/197 Syslog Message 07.41.02.0014 09/13/2012 03:06:30
<3>bcmStrat[2.tNimIntr]MEM_FAIL interrupt occurred on chip 0!
    For the K-Series...
==============================================================================
Message 57/211 Syslog Message 07.71.01.0010 10/17/2012 17:27:29

<3>System[11]Halting the line card in slot 5 ( KT2006-0224 pn 9404352, s
n 112613745745 ) due to a detected failure

==============================================================================
Message 58/211 Syslog Message 07.71.01.0010 10/17/2012 17:27:28
<3>bcmStrat[11.tLcIntr]MEM_FAIL_INT_STAT=0x00000200, EP_INTR_STATUS=0x00
000000, IP0_INTR_STATUS=0x00000000, IP1_INTR_STATUS=0x00000000, IP2_INTR
_STATUS=0x00000000, XQPORT_INTR_STATUS.xgport0=0x00000000, XQPORT_INTR_S
TATUS.xgport1=0x00000000

==============================================================================
Message 59/211 Syslog Message 07.71.01.0010 10/17/2012 17:27:28
<3>bcmStrat[11.tLcIntr]MEM_FAIL interrupt occurred on chip 4!

* With older S-Series firmware 7.11.01.0026 through 7.21.03.0003, "MEM_FAIL_INT_STAT=0x00000001" and "IP1_INTR_STATUS=0x00000200"; for example:
==============================================================================
Message 94/241 Shutdown 07.21.01.0015 06/11/2011 04:58:04

Initiated - Reset
Shutdown process is starting.

==============================================================================
Message 95/241 Syslog Message 07.21.01.0015 06/11/2011 04:58:04
<0>bcmStrat[1.tNimIntr]MEM_FAIL condition is fatal. ( 0x009337f0 0x009e8
194 0x004413fc 0x00441580 0x00f7a754 0xeeeeeeee )

==============================================================================
Message 96/241 Syslog Message 07.21.01.0015 06/11/2011 04:58:04
<3>bcmStrat[1.tNimIntr]MEM_FAIL_INT_STAT=0x00000001, IP0_INTR_STATUS=000
0000000, IP1_INTR_STATUS=0x00000200, IP2_INTR_STATUS=0000000000, IP3_INT
R_STATUS=0000000000, EP_INTR_STATUS=0000000000

==============================================================================
Message 97/241 Syslog Message 07.21.01.0015 06/11/2011 04:58:04
<3>bcmStrat[1.tNimIntr]MEM_FAIL interrupt occurred on chip 0!
Solution
For "MEM_FAIL interrupt" events which do not exactly match the above-stated status values, please use 13306 instead. 

Upgrade to firmware 7.73.01.0003 or higher. 

If the issue persists after upgrade, then please contact the GTAC for assistance.
Photo of FAQ User

FAQ User, Official Rep

  • 13,610 Points 10k badge 2x thumb

Posted 5 years ago

  • 0
  • 1

There are no replies.

This conversation is no longer open for comments or replies.