[c-nsp] SYSTEM_CONTROLLER / Cisco 7606

[Ahmed Hilmy]

Hello Expert,



I have 7606 router, got crashed today and i noticed these logs:



*Mar 15 09:58:01 UTC: %SYSTEM_CONTROLLER-3-MISTRAL_RESET: System Controller
is reset:Normal Operation continues*

**
Mar 15 09:58:30 UTC: %CPU_MONITOR-2-NOT_RUNNING: CPU_MONITOR messages have
not been sent for 30 seconds [*Sched* 1%/1% (00:00:31.228 92%/92%)] [IP
SLAs Event Processor 00:13:04.660] [ACCT Periodic Proc 00:01:34.336] [IP
SLAs Event Processor 00:06:17.848]


Mar 15 09:58:30 UTC: %CPU_MONITOR-2-NOT_RUNNING_TB: CPU_MONITOR traceback:
428284A8 427C6AB4 4193DA54 4193DC88 41F01354 42AD9CC4 42AE3128 42CC9070


Mar 15 09:59:00 UTC: %CPU_MONITOR-2-NOT_RUNNING: CPU_MONITOR messages have
not been sent for 60 seconds [*Sched* 1%/1% (00:01:01.228 96%/96%)] [IP
SLAs Event Processor 00:13:34.660] [ACCT Periodic Proc 00:01:34.336] [IP
SLAs Event Processor 00:06:17.848]


Mar 15 09:59:00 UTC: %CPU_MONITOR-2-NOT_RUNNING_TB: CPU_MONITOR traceback:
428284A8 427C6AB4 4193DA54 4193DC88 41F01354 42AD9CC4 42AE3128 42CC9070


Mar 15 09:59:30 UTC: %CPU_MONITOR-2-NOT_RUNNING: CPU_MONITOR messages have
not been sent for 90 seconds [*Sched* 1%/1% (00:01:31.228 97%/97%)] [IP
SLAs Event Processor 00:14:04.660] [ACCT Periodic Proc 00:01:34.336] [IP
SLAs Event Processor 00:06:17.848]


Mar 15 09:59:30 UTC: %CPU_MONITOR-2-NOT_RUNNING_TB: CPU_MONITOR traceback:
428284A8 427C6AB4 4193DA54 4193DC88 41F01354 42AD9CC4 42AE3128 42CC9070
Mar 15 10:00:00 UTC: %CPU_MONITOR-2-NOT_RUNNING: CPU_MONITOR messages have
not been sent for 120 seconds [*Sched* 1%/1% (00:02:01.228 98%/98%)] [IP
SLAs Event Processor 00:14:34.660] [ACCT Periodic Proc 00:01:34.336] [IP
SLAs Event Processor 00:06:17.848]
Mar 15 10:00:00 UTC: %CPU_MONITOR-2-NOT_RUNNING_TB: CPU_MONITOR traceback:
428284A8 427C6AB4 4193DA54 4193DC88 41F01354 42AD9CC4 42AE3128 42CC9070


Mar 15 10:00:30 UTC: %CPU_MONITOR-2-NOT_RUNNING: CPU_MONITOR messages have
not been sent for 150 seconds [*Sched* 1%/1% (00:02:31.228 98%/98%)] [IP
SLAs Event Processor 00:15:04.660] [ACCT Periodic Proc 00:01:34.336] [IP
SLAs Event Processor 00:06:17.848]


Mar 15 10:00:30 UTC: %CPU_MONITOR-2-NOT_RUNNING_TB: CPU_MONITOR traceback:
428284AC 427C6AB4 4193DA54 4193DC88 41F01354 42AD9CC4 42AE3128 42CC9070


Mar 15 10:00:33 UTC: %CPU_MONITOR-3-PEER_FAILED: CPU_MONITOR peer process
has failed to receive heartbeats, reset by [5/0]



*%Software-forced reload*



10:00:33 UTC Fri Mar 15 2013: Breakpoint exception, CPU signal 23, PC =
0x4278D310





Based on the information i got , it seems it is normal and it is related  tothe
Mistral ASIC, which is the ASIC used to connect the MSFC with the

Pinnacle on the Supervisor and with the EOBC bus (so to communicate
with the Supervisor in general, both for control and data path).



Would you please share your experience about this issue.




Regards,

Ahmed