02.10.2013 Views

FTOS Configuration Guide for the C-Series - Force10 Networks

FTOS Configuration Guide for the C-Series - Force10 Networks

FTOS Configuration Guide for the C-Series - Force10 Networks

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

CP Software Exceptions<br />

When a RPM resets due to a software exception, <strong>the</strong> linecard trace files are saved to flash:/<br />

TRACE_LOG_DIR directory.<br />

The CP and LP trace file names in <strong>the</strong> case of a software exception are:<br />

• CP: failure_trace_RPM1_CP<br />

• LP: failure_trace_RPM1_LP1<br />

With a dual RPM system, linecard trace logs are saved in <strong>the</strong> case of a CP, RP1 or RP2 crash. Linecard<br />

trace logs are saved in <strong>the</strong> new primary RPM. Here <strong>the</strong> name of <strong>the</strong> line card trace file helps in identifying<br />

a failed RPM. That is, if RPM0 fails, <strong>the</strong>n <strong>the</strong> trace files are saved in RPM1 with filename<br />

failure_trace_RPM0_LP1. This is because <strong>the</strong> failover happens be<strong>for</strong>e <strong>the</strong> linecard traces are saved.<br />

Viewing Trace Buffer Content<br />

The command-history trace feature captures all commands entered by all users of <strong>the</strong> system with a time<br />

stamp and writes <strong>the</strong>se messages to a dedicated trace log buffer. The system generates a trace message <strong>for</strong><br />

each executed command. No password in<strong>for</strong>mation is saved to <strong>the</strong> file.<br />

To view <strong>the</strong> command-history trace, use <strong>the</strong> show command-history command, as shown in Figure 493.<br />

C300-TAC-B6#show command<br />

[12/5 10:57:8]: CMD-(CLI):service password-encryption<br />

[12/5 10:57:12]: CMD-(CLI):hostname <strong>Force10</strong><br />

[12/5 10:57:12]: CMD-(CLI):ip telnet server enable<br />

[12/5 10:57:12]: CMD-(CLI):line console 0<br />

[12/5 10:57:12]: CMD-(CLI):line vty 0 9<br />

[12/5 10:57:13]: CMD-(CLI):boot system rpm0 primary flash://<strong>FTOS</strong>-CB-1.1.1.2E2.bin<br />

Figure 493 show command-history Command Example<br />

Writing <strong>the</strong> Contents of <strong>the</strong> Trace Buffer<br />

The trace logs are saved to automatically but you can save <strong>the</strong> contents of a buffer manually via <strong>the</strong> CLI.<br />

To manually write <strong>the</strong> contents of a trace buffer on CP to a file on <strong>the</strong> flash:<br />

Step Task Command Syntax<br />

1 Write <strong>the</strong> buffered trace log to flash. upload trace-log cp [cmd-history |<br />

hw-trace | sw-trace]<br />

To manually write <strong>the</strong> contents of a trace buffer on LP to a file on <strong>the</strong> flash:<br />

Command<br />

Mode<br />

EXEC privilege<br />

<strong>FTOS</strong> <strong>Configuration</strong> <strong>Guide</strong>, version 7.7.1.0 699

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!