FTOS Configuration Guide for the C-Series - Force10 Networks

Diagnostics are invoked from the FTOS CLI. While diagnostics are running, the status can be monitored
via the CLI. The tests results are written to a file in flash memory and can be displayed on screen. Detailed
statistics for all tests are collected. These statistics include:
• last execution time
• first and last test pass time
• first and last test failure time
• total run count
• total failure count
• consecutive failure count
• error code.
The diagnostics tests are grouped into three levels:
• Level 0 checks the device inventory and verifies the existence of the devices (e.g., device ID test).
• Level 1 verifies that the devices are accessible via designated paths (e.g., line integrity tests) and tests
the internal parts (e.g., registers) of the devices.
• Level 2 performs on-board loopback tests on various data paths (e.g., data port pipe and Ethernet).
Configuration Task List
Note: This procedure assumes you have already loaded an FTOS image. These instructions illustrates
the process of running offline diagnostics using line cards, but the process is the same for RPMs. Only the
command keyword linecard must change to rpm. See the Command Line Reference Guide for details.
1. Take the line card offline. page 707.
2. Run offline diagnostics. page 707.
3. View offline diagnostic test results. page 707.
4. Bring the line card back online. page 711.
Important Points to Remember
• Offline diagnostics can only be run on offline line cards and on the standby route processor module
(RPM). The primary RPM cannot be not tested.
• Diagnostics test only connectivity, not the entire data path.
• The complete diagnostics test suite normally runs for 4 to 6 minutes; the 48-port 1-Gigabit line card
takes slightly longer than the 4-port 10-Gigabit line card.
706 C-Series Debugging and Diagnostics