1178 | C-Series Debugging and Diagnosticsw w w . d e l l . c o m | s u p p o r t . d e l l . c o m When the trace messages are being saved on reload, Message 9 is displayed.The CP and LP trace file names at chassis reload are:• CP: reload_traceRPM0_CP• LP: reload_traceLP[0-7]Figure 60-8. TRACE_LAST_BOOT Directory exampleCP software exceptionsWhen a RPM resets due to a software exception, the linecard trace files are saved to flash:/TRACE_LOG_DIR directory.The CP and LP trace file names in the case of a software exception are:• CP: failure_trace_RPM1_CP• LP: failure_trace_RPM1_LP[0-7]For systems with a single RPM, the linecard traces are saved on the failed RPM itself.For systems with dual RPM, linecard trace logs are saved when the CP, RP1, or RP2 crashes. The linecardtrace logs are saved on the new Primary RPM. The linecard trace file name identifies the failed RPM. Forexample, if RPM0 fails the trace files saved in RPM1 with filename as failure_trace_RPM0_LP1.Command historyThe command-history trace feature captures all commands entered by all users of the system with a timestamp and writes these messages to a dedicated trace log buffer. When the show command-historycommand is entered, the system displays a trace message for each executed command. No passwordinformation is saved to the file. The trace messages are not saved to a file or directory on the internalsystem flash.To view the command-history trace, use the show command-history command, as shown in Figure 60-9.Message 9 Saving Trace MessagesStarting to save trace messages… Done.FTOS#cd /flash/TRACE_LOG_DIR/TRACE_LAST_BOOTFTOS#dirhw_traceLP0.0 hw_traceLP2.3 hw_traceRPM0_CP.3 reload_traceLP6hw_traceLP0.1 hw_traceLP2.4 hw_traceRPM0_CP.4 reload_traceRPM0_CPhw_traceLP2.0 hw_traceRPM0_CP.0 reload_traceLP0hw_traceLP2.1 hw_traceRPM0_CP.1 reload_traceLP2hw_traceLP2.2 hw_traceRPM0_CP.2 reload_traceLP3
