G/C5/C3/B5-Series f/w 6.42.10.0016 Reset from nim_t task with 'nimNotifyUserOfIntfChange' diagnostic

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

Products
G-Series, firmware 6.42.10.0016 through 6.61.09.0012
C5-Series, firmware 6.42.10.0016 through 6.61.09.0012
C3-Series, firmware 6.42.10.0016 through 6.61.09.0012
B5-Series, firmware 6.42.10.0016 through 6.61.09.0012

Symptoms
Unit reboot. 

With firmware 6.42.10.0016 and higher... 
The current.log (5487may display a single NIM Timeout event; for example (here from multiple systems): 
<160>Dec 13 09:00:07 20.1.6.1-4 NIM[145477336]: nim_events.c(213) 2013 %%
 NIM: Timeout event(DETACH) on unit(3) slot(0) port(1)(intIfNum(105)) for components(MACA)
<160>Mar 16 10:23:21 10.16.0.104-1 NIM[111002896]: nim_events.c(213) 1139 %%
 NIM: Timeout event(ATTACH) on unit(8) slot(0) port(6)(intIfNum(370)) for components(MACA)
<160>Aug 3 12:01:48 10.1.24.1-1 NIM[113894648]: nim_events.c(213) 513 %%
 NIM: Timeout event(DOWN) on unit(7) slot(0) port(44)(intIfNum(356)) for components(MACA)
<160>Dec 15 14:59:38 61.200.8.8-1 NIM[111002568]: nim_events.c(213) 617 %%
 NIM: Timeout event(VRRP_TO_MASTER) on unit(0) slot(2) port(5)(intIfNum(428)) for components(IGMP, DVMRP)
<160>Jun 5 14:16:06 0.0.0.0-1 NIM[159033376]: nim_events.c(213) 1185 %%
 NIM: Timeout event(VRRP_TO_MASTER) on unit(0) slot(2) port(2)(intIfNum(425)) for components(IGMP_SNOOPING)
<160>Aug 3 12:20:13 10.1.224.16-2 NIM[113894576]: nim_events.c(213) 213 %%
 NIM: Timeout event(ACTIVE) on unit(2) slot(0) port(15)(intIfNum(67)) for components(IGMP_SNOOPING)
With firmware 6.51.02.0018 and lower.. 
The current.log (5487) displays a "l7_prepareSystemDump" BackTrace with last reset cause "nim_events.c(213)" and error code "0x0000badd"; for example:
<57> MAR 23 15:25:35 2012 STK1 BOOT[268430624]: bootos.c(1398) 189 %%
Start of Code - Build:06.42.10.0016 Date:Mon Dec 12 14:31:02 2011
BackTrace-0x007870b4: sysReboot (0x7870b4) + 0x0
BackTrace-0x01048680: SwitchReset (0x10485e8) + 0x98
BackTrace-0x00b78ba8: l7_prepareSystemDump (0xb7810c) + 0xa9c
BackTrace-0x00b7914c: l7MonitorTask (0xb790a8) + 0xa4
BackTrace-0x01161bd8: vxTaskEntry (0x1161b7c) + 0x5c
BackTrace-r0 = 0x00000000 r1 = 0x00000000 r2 = 0x00000000
BackTrace-r3 = 0x00000000 r4 = 0x00000000 r5 = 0x00000000
BackTrace-r6 = 0x00000000 r7 = 0x00000000 r8 = 0x00000000
BackTrace-r9 = 0x00000000 r10 = 0x00000000 r11 = 0x00000000
BackTrace-r12 = 0x00000000 r13 = 0x00000000 r14 = 0x00000000
BackTrace-r15 = 0x00000000 r16 = 0x00000000 r17 = 0x00000000
BackTrace-r18 = 0x00000000 r19 = 0x00000000 r20 = 0x00000000
BackTrace-r21 = 0x00000000 r22 = 0x00000000 r23 = 0x00000000
BackTrace-r21 = 0x00000000 r22 = 0x00000000 r23 = 0x00000000
BackTrace-r24 = 0x00000000 r25 = 0x00000000 r26 = 0x00000000
BackTrace-r27 = 0x00000000 r28 = 0x00000000 r29 = 0x00000000
BackTrace-r30 = 0x00000000 r31 = 0x00000000
BackTrace-lr = 0x00000000 pc = 0x00000000 msr = 0x00000000
<110> MAR 23 15:26:01 2012 STK1 BOOT[141095848]: edb_bxs.c(1226) 208 %%
Last switch reset caused by nim_events.c(213): Error code 0x0000badd, after 5878055 seconds
With firmware 6.61.02.0007 and higher... 
The current.log (5487) displays a "Task nim_t(<address>) is suspended..." message; for example: 
Task nim_t(0x6c9e4f8) is suspended with error 2, creating file sysDmp2Aug0312.z
With firmware 6.61.02.0007 through 6.61.05.0009... 
The sysDmp (13650) file states "Task nim_t" and displays a "nimNotifyUserOfIntfChange" diagnostic; for example: 
Detailed erred task information 
---------------------------------
Calling Stack:

------------
Task ID: 0x8abced8
Task Name: nim_t
PC: 0x11dd33c
PendQ: 0xf945284
SP: 0x8abab80

0x11dd33c: taskSuspend (0x11dcf00) + 0x43c
0x101464c: log_error_nvram (0x10143a4) + 0x2a8
0x5f14b0: nimDoNotify (0x5f0bac) + 0x904
0x5f29e4: nimNotifyUserOfIntfChange (0x5f1798) + 0x124c
0x5f36e0: nimTask (0x5f33c0) + 0x320
x1131760: vxTaskEntry (0x1131704) + 0x5c
With firmware 6.61.06.0009... 
The sysDmp (13650) file states "Task nim_t" and displays a "_vx_offset_COPROC_DESC_next" diagnostic; for example: 
Detailed exception task information
---------------------------------

Calling Stack:
--------------
Task ID: 0x980d1c0
Task Name: nim_t
PC: 0x0
PendQ: 0x1fff86a4
SP: 0x0

0x0: _vx_offset_COPROC_DESC_next (0x0) + 0x0
Solution
For any affected product, upgrade to firmware 6.61.10.0008 or higher. 
For the C5/B5-Series, you may upgrade to firmware 6.71.03.0025 or higher. 
Release notes state, in the 'Firmware Changes and Enhancements' section:
18584    Addressed an issue in MAC Locking application that could result in a reset with the error message, "nim_events.c(213): Error code 0x0000BADD"
Photo of FAQ User

FAQ User, Official Rep

  • 13,620 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.