Can't find what you need?


• Ask the Community
• Create a Case
Reset Search
 

 

Article

Securestack: Reset caused by nim_events.c(213): Error code 0x0000BADD and NIM: Timeout event for component IGMP_SNOOPING

« Go Back

Information

 
TitleSecurestack: Reset caused by nim_events.c(213): Error code 0x0000BADD and NIM: Timeout event for component IGMP_SNOOPING
Symptoms
Crash with sysDmp file

IGMP snooping task may be high 
b96ab20   snoopTask   91.20% 90.89% 91.64%

the following errors are seen in the sys logs :  
160>Nov 4 12:39:15 172.28.226.56-1 NIM[116507952]: nim_events.c(213) 728 
%% NIM: Timeout event(DOT1X_PORT_AUTHORIZED) on unit(1) slot(0) port(18)(intIfNum(18)) for components(IGMP_SNOOPING)

followed by 
 
<110> NOV 04 13:40:53 2014 STK1 BOOT[140620832]: edb_bxs_api.c(807) 322 
%% Last switch reset caused by nim_events.c(213): Error code 0x0000BADD, after 1009117 seconds
Environment
  • Securestack
  • C3-Series
  • C5-Series
  • B5-Series
  • Firmware 06.61.12.0005
  • IGMP Snooping
Cause
Snooping task queue was full, when NIM tried to add a new message to queue 
 
Resolution
Upgrade to 6.61.15.0003
Additional notes

Feedback

 

Was this article helpful?


   

Feedback

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

Characters Remaining: 255