Dell Networking S6000 System, Справочное руководство

Страница: 504 / 1510

Offline Diagnostic Commands
The offline diagnostics test suite is useful for isolating faults and debugging hardware. While tests are
running, Dell Networking OS results are saved as a text file (TestReport-SU-X.txt) in the flash directory.
This
show file
command is available only on master and standby.
Important Points to Remember
• Offline diagnostics can only be run when the unit is offline.
• You can only run offline diagnostics on a unit to which you are connected via the console. In other
words, you cannot run diagnostics on a unit to which you are connected to via a stacking link.
• Diagnostic results are printed to the screen. Dell Networking OS does not write them to memory.
• Diagnostics only test connectivity, not the entire data path.
diag stack-unit
Run offline diagnostics on a stack unit.
S6000
Syntax
diag stack-unit number [alllevels | level0 | level1 | level2]
verbose testname
Parameters
number
Enter the stack-unit id.
Range from 0 to 5.
alllevels Enter the keyword
alllevels
to run the complete set of
offline diagnostic tests.
level0 Enter the keyword
level0
to run Level 0 diagnostics. Level
0 diagnostics check for the presence of various components
and perform essential path verifications. In addition, they
verify the identification registers of the components on the
board.
level1 Enter the keyword
Level1
to run Level 1 diagnostics. Level 1
diagnostics is a smaller set of diagnostic tests with support
for automatic partitioning. They perform status/self test for
all the components on the board and test their registers for
appropriate values. In addition, they perform extensive tests
on memory devices (for example, SDRAM, flash, NVRAM,
EEPROM, and CPLD) wherever possible. There are no tests
on 10G links. At this level, stack ports are shut down
automatically.
level2 Enter the keyword
level2
to run Level 2 diagnostics. Level 2
diagnostics are a full set of diagnostic tests with no support
for automatic partitioning. Level 2 diagnostics are used
primarily for on-board loopback tests and more extensive
component diagnostics. Various components on the board
are put into Loopback mode and test packets are transmitted
through those components. These diagnostics also perform
504
Debugging and Diagnostics