Running Hardware Diagnostics
Page 36-6

Running Hardware Diagnostics

The test command initiates one or more test routines on a switching module that you
specify. You can also optionally test all switching modules in one test session. Test status,
instructions, and a summary of results are provided as output. Start a diagnostic test session
using the following command syntax:
test <slot_number> [<repeat_count> [<test_name>]]
where
<slot_number> Indicates the slot number in the Omni Switch/Router for the module on
which you want to run tests. If you enter all for this parameter, then all
switching modules in the chassis will be tested. This parameter is required;
if you do not enter a slot number then the test session will not start.
<repeat_count> Indicates the number of times to run the specified tests on the module.
This value can be an integer between 0 and 999. A value of zero (0)
repeats the test infinitely. The default value is 1. This default will be
assumed if you do not enter a repeat_count.
<test_name> Indicates the test to be performed on the module. You can indicate the test
name or all to run all tests. You can enter only one test name or all. The
default is all. This default will be assumed if you do not enter a test_name.
♦ Note ♦
A combination of repeat_count set to 0 and test_name
set to all allows the user to run either the port test
infinitely or all off-board tests infinitely. If the user
chooses to run the port test when prompted, all the
static tests (memory and control/status register tests)
are run once, followed by an infinite run of the port
test. See Sample Command Lines on page 36-9 for
more information.
Descriptions of each test follows:
alpreg Tests the Alpine registers. Test the Alpine control logic, registers, and
data/address lines.
csr Tests the command/status registers. Includes testing management bus
buffers, management bus read/write control logic, reset and LED memory,
ID EEPROM, and reset circuitry.
gigareg Tests the Giga-Chip registers. Test the Giga-Chip control logic, registers,
and data/address lines.
hrexmem Tests the HRE-X’s local memory. Includes testing the HRE-X read/write
functions, data/address, and the memory.
hrexport Tests the HRE-X’s functions. Packets are generated by the MPX, sent out
to the port, and claimed by the HRE-X. The HRE-X will insert additional
routing information to the claimed packet and place it back on MVBUS to
be claimed and verified by the MPX. This test can be bypassed. See
Running Diagnostics on an Entire Chassis on page 36-20.
ilb Performs a port test using the internal loopback at the PHY or framer
interface. Packets are generated by the MPX and sent out to the port and
returned through an internal loopback within the PHY or framer. The MPX
verifies the packets on a bit by bit basis.