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.

Buffer Full Condition<br />

When <strong>the</strong> trace ring buffer is full, <strong>the</strong> trace lines are saved as a file into <strong>the</strong> flash (e.g.<br />

hw_trace_RPM0CP.0). When <strong>the</strong> buffer fills <strong>for</strong> <strong>the</strong> second time, it is saved as hw_trace_RPM0CP.1, and<br />

so on until hw_trace_RPM0CP.4. From <strong>the</strong> sixth time onwards, when <strong>the</strong> trace buffer fills, <strong>the</strong> second trace<br />

file (hw_trace_RPM0CP.1) is overwritten.<br />

Trace file hw_trace_RPM0CP.0 is not overwritten so that chassis bootup message are preserved.<br />

<strong>FTOS</strong> uses a similar approach to saving <strong>the</strong> various trace messages <strong>for</strong> CP and all LPs.<br />

The CP and LP trace file names are:<br />

Note: Line card 1 is taken as <strong>the</strong> example <strong>for</strong> <strong>the</strong> following filenames.<br />

• CP [SW trace] : sw_trace_RPM0CP.0, sw_trace_RPM0CP.1, sw_trace_RPM0CP.2,<br />

sw_trace_RPM0CP.3 and sw_trace_RPM0CP.4<br />

• CP [HW trace] : hw_trace_RPM0CP.0, hw_trace_RPM0CP.1, hw_trace_RPM0CP.2,<br />

hw_trace_RPM0CP.3 and hw_trace_RPM0CP.4<br />

• LP [SW trace] : sw_trace_LPX.0, sw_trace_LP1.1, sw_trace_LP1.2, sw_trace_LP1.3 and<br />

sw_trace_LP1.4<br />

• LP [HW trace] : hw_trace_LPX.0, hw_trace_LP1.1, hw_trace_LP1.2, hw_trace_LP1.3 and<br />

hw_trace_LP1.4<br />

Trace files are saved in <strong>the</strong> directory flash:/TRACE_LOG_DIR/TRACE_CURR_BOOT. Upon a system<br />

reload this directory is renamed flash:/TRACE_LOG_DIR/TRACE_LAST_BOOT, and a fresh empty<br />

flash:/TRACE_LOG_DIR/TRACE_CURR_BOOT directory is created.<br />

Manual Reload Condition<br />

When <strong>the</strong> chassis is reloaded manually (through <strong>the</strong> CLI), trace messages in all of <strong>the</strong> buffers (software and<br />

hardware) in CP and linecards are saved to <strong>the</strong> flash as reload_traceRPM0_CP and reload_traceLP1 in<br />

flash:/TRACE_LOG_DIR/TRACE_CURR_BOOT. After reload, you can see <strong>the</strong>se files in flash:/<br />

TRACE_LOG_DIR/TRACE_LAST_BOOT..<br />

When <strong>the</strong> trace messages are being saved on reload, Message 29 is displayed.<br />

Message 29 Saving Trace Messages<br />

Starting to save trace messages… Done.<br />

The CP and LP trace file names at chassis reload are:<br />

• CP: reload_traceRPM0_CP<br />

• LP: reload_traceLP1<br />

698 C-<strong>Series</strong> Debugging and Diagnostics

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

Saved successfully!

Ooh no, something went wrong!