Dell Force10 E600i FTOS Version 8.4.1.5 Configuration Guide for ExaScale - Page 1096

www.dell.com | support.dell.com CP software exceptions When 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_LP1 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 linecard trace logs are saved on the new Primary RPM. The linecard trace file name identifies the failed RPM. For example, if RPM0 fails the trace files saved in RPM1 with filename as failure_trace_RPM0_LP1. View trace buffer content The command-history trace feature captures all commands entered by all users of the system with a time stamp and writes these messages to a dedicated trace log buffer. The system generates a trace message for each executed command. No password information is saved to the file. To view the command-history trace, use the show command-history command. FTOS#show command-history [12/5 10:57:8]: CMD-(CLI):service password-encryption [12/5 10:57:12]: CMD-(CLI):hostname Force10 [12/5 10:57:12]: CMD-(CLI):ip telnet server enable [12/5 10:57:12]: CMD-(CLI):line console 0 [12/5 10:57:12]: CMD-(CLI):line vty 0 9 [12/5 10:57:13]: CMD-(CLI):boot system rpm0 primary flash://FTOS-CB-1.1.1.2E2.bin Write the contents of the trace buffer The trace logs are saved to automatically but you can save the contents of a buffer manually via the CLI. To manually write the contents of a trace buffer on CP to a file on the flash: Step 1 Task Command Syntax Write the buffered trace log to flash. upload trace-log cp [cmd-history | hw-trace | sw-trace] Command Mode EXEC Privilege 1096 | E-Series TeraScale Debugging and Diagnostics