Filter
Top Products
Running Hardware Diagnostics
Page 36-9
Sample Command Lines
There are numerous ways to specify a test session through the test command. The following
are some sample command lines along with a description of what they test. The following
command:
test all 100 vram
would run the VRAM test on all the modules in the chassis that are capable of executing the
VRAM test for 100 times. In another example, the following command:
test 3 0 all
would run either all the static tests or the port test on the module in slot 3 infinitely. Finally,
the following command:
test 4 5
would run all tests (the default) on the module in slot 4 five (5) times.
Halting Diagnostic Tests in Progress
Depending on how many tests and repeat iterations you specify, a test session could take
some time to complete. If you need to halt in-progress tests, enter CTRL-C. This key sequence
pauses the testing and provides a test summary report. You will be prompted to resume or
terminate the testing after the pause.
♦ Note♦
During certain phases of diagnostic testing, the
CTRL-C
will not be immediately processed. This delay may last
several seconds, or longer.
Port Tests
Because port-to-port cabling is required, port tests may not be available on some modules
with only one port, one daughtercard, or on some modules with mismatched daughtercards.
(For example, 100BaseTx modules cannot run port tests with single or mismatched daughter-
cards.) When a port test is run, packets are generated in the MPX and sent out to the switch-
ing module, externally looped, and sent back to the MPX. The MPX then inspects the packets.
The tables on the following pages provide specific cable/plug information.
♦ Important Note ♦
For VSD and VSA submodules, the
port test requires no
outside cabling. It is a combination of multiple static
tests for the submodule, rather than a traffic test.