Reset Search
 

 

Article

210-Series switch randomly crashes with Task Name nim_t

« Go Back

Information

 
Title210-Series switch randomly crashes with Task Name nim_t
Symptoms
  • 210-Series Switch random crashes with "Task Name: num_t"
  • The "debug crash and kernel logs" within the tech-support file displays the following crash dump information:
*************** Debug crashlog 0 unit 1 ******** 
Displaying FASTPATH Crash Dump 0 
For kernel Crash Dump - osapiDebugCrashDumpDisplay(x,1) 

*************************************************** 
* Start FASTPATH Stack Information * 
*************************************************** 
pid: 1432 
TID: 0xb4c854c0 
Task Name:	nim_t 
si_signo: 11 
si_errno: 0 
si_code: 1 
si_addr: (nil) 
Date/Time:	6/6/2019 8:04:37 
SW ver: 1.2.6.9 

------------ CALL STACK INFO ------------ 
$001c4f44$ log_error_code + 0x60 
$001c821c$ l7_log_error_opt_reset + 0x50 
$001d91d4$ nimDoNotify + 0x45c 
$001d9e88$ nimNotifyUserOfIntfChange + 0xc3c 
$001da750$ nimTask + 0x1d0 
$0071a2fc$ osapi_task_wrapper + 0xb4 
/lib/libpthread.so.0 [0xb6e667e8] 
----------------------------------------- 
Stack Size: 36864 Bytes 
Stack Base Address: 0xB4C7D000
  • Buffered log messages: 
<185> Jun  6 08:05:23 192.168.1.1-1 SIM[SimAddrConflict]: sim.c(4648) 497 % Failed to read conflicting ARP packet from stack - errno Resource temporarily unavailable
<189> Jun  6 08:04:27 192.168.1.1-1 TRAPMGR[nim_t]: traputil.c(763) 496 % Cold Start: Unit: 0
<184> Jun  6 08:04:27 192.168.1.1-1 LOG[nim_t]: log_cnfgr.c(1264) 495 % The system is restarting due to inconsistent state.
<187> Jun  6 08:04:26 192.168.1.1-1 NIM[nim_t]: nim_events.c(212) 494 % NIM: Timeout event(L7_DOWN), interface(0/19) remainingMask =  0x00000000  0x00000000  0x00000000  0x00000000  0x00080000  0x00000000

<187> Jun  6 08:04:26 192.168.1.1-1 NIM[nim_t]: nim_events.c(204) 493 % NIM:DOT1X component not responding. Internal timeout may indicate system instability. Recommend checking interface in next message.

 
Environment
  • 210-Series
  • 1.2.6.9
Cause
Resolution
  1. Gather the tech-support and core dump (if available) files of the affected unit(s). 
  2. Open a case with the Global Technical Assistance Center (GTAC) team of Extreme Networks. 
Additional notes

Feedback

 

Was this article helpful?


   

Feedback

Please tell us how we can make this article more useful.

Characters Remaining: 255