Configuration manual

E-Series ExaScale Debugging and Diagnostics | 1261
When the trace messages are being saved on reload, Message 9 is displayed.
The trace file names at a chassis reload are:
• CP: reload_traceRPM[0|1]_CP
• LP: reload_traceLPnumber
CP/RP1/RP2 software exceptions
When an RPM resets due to an RP1 or RP2 software exception, the trace files are saved to flash:/
TRACE_LOG_DIR
directory.
The trace file names in the case of a software exception are:
• CP: failure_trace_RPM[0|1]_CP
• LP: failure_trace_RPM[0|1]_LPnumber
With a dual RPM system, trace logs are saved in the case of a CP, RP1 or RP2 crash. Trace logs are saved
in the new primary RPM. Here the name of the trace file helps in identifying a failed RPM. That is, if
RPM0 fails, then the trace files are saved in RPM1 with filename
failure_trace_RPM0_LP1. This is because
the failover happens before the traces are saved.
Recognize a high CPU condition
A high CPU condition exists when any of the messages in Message 10 appear.
Message 9 Saving Trace Messages
Starting to save trace messages… Done.
Message 10 High CPU Condition
Feb 13 13:56:16: %RPM1-S:CP %CHMGR-5-TASK_CPU_THRESHOLD: Cpu usage above threshold for task
"sysAdmTsk"(100.00%) in CP.
Feb 13 13:56:20: %RPM1-S:CP %CHMGR-5-CPU_THRESHOLD: Overall cp cpu usage above threshold.
Cpu5SecUsage (100)
Feb 13 13:56:20: %RPM1-S:CP %CHMGR-5-TASK_CPU_THRESHOLD_CLR: Cpu usage drops below threshold
for task "sysAdmTsk"(0.00%) in CP.