Information About Configuring Online Diagnostics

Online Diagnostics

With online diagnostics, you can test and verify the hardware functionality of the switch while the switch is connected to a live network.

The online diagnostics contain packet switching tests that check different hardware components and verify the data path and the control signals.

The online diagnostics detect problems in these areas:

Hardware components

Interfaces (Ethernet ports and so forth)

Solder joints

Online diagnostics are categorized as on-demand, scheduled, or health-monitoring diagnostics. On-demand diagnostics run from the CLI; scheduled diagnostics run at user-designated intervals or at specified times when the switch is connected to a live network; and health-monitoring runs in the background with user-defined intervals. By default, the health-monitoring test runs for every 30 seconds.

After you configure online diagnostics, you can manually start diagnostic tests or display the test results. You can also see which tests are configured for the switch or switch stack and the diagnostic tests that have already run.

The
switchnumber keyword is supported only on stacking
switches. The range is from 1 to 4.

When specifying
the tests to be scheduled, use these options:

name—Name of the test that appears in the
show diagnostic
content command output.

test-id—ID number of the test that appears in the
show diagnostic
content command output.

test-id-range—ID numbers of the tests that appear
in the
show diagnostic
content command output.

all—All test IDs.

basic—Starts the basic on-demand diagnostic tests.

complete—Starts the complete test suite.

minimal—Starts the minimal bootup test suite.

non-disruptive—Starts the non-disruptive test
suite.

per-port—Starts the per-port test suite.

You can schedule
the tests as follows:

Daily—Use
the
dailyhh:mm parameter.

Specific day
and time—Use the
onmm dd yyyy hh:mm parameter.

Weekly—Use
the
weeklyday-of-week hh:mm parameter.

Configuring
Health-Monitoring Diagnostics

You can configure
health-monitoring diagnostic testing on a switch while it is connected to a
live network. You can configure the execution interval for each
health-monitoring test, enable the switch to generate a syslog message because
of a test failure, and enable a specific test.

Use the
no form of this command to disable testing.

By default, health
monitoring is disabled, but the switch generates a syslog message when a test
fails.

The
switchnumber keyword is supported only on stacking
switches. The range is from 1 to 9.

When
specifying the tests, use one of these parameters:

name—Name of the test that appears in the
show diagnostic
content command output.

test-id—ID number of the test that appears in the
show diagnostic
content command output.

test-id-range—ID numbers of the tests that appear
in the
show diagnostic
content command output.

all—All of the diagnostic tests.

Step 6

end

Example:

Controller(config)# end

Returns to
privileged EXEC mode.

Use the
no diagnostic monitor interval
testtest-id |
test-id-range } global configuration command
to change the interval to the default value or to zero. Use the
no diagnostic monitor syslog command to
disable generation of syslog messages when a health-monitoring test fails. Use
the
diagnostic monitor threshold
testtest-id |
test-id-range }failure countcommand
to remove the failure threshold.

This example shows how to display the description for a diagnostic test:

Controller# show diagnostic description switch 1 test all
DiagGoldPktTest :
The GOLD packet Loopback test verifies the MAC level loopback
functionality. In this test, a GOLD packet, for which doppler
provides the support in hardware, is sent. The packet loops back
at MAC level and is matched against the stored packet. It is a non
-disruptive test.
DiagThermalTest :
This test verifies the temperature reading from the sensor is below the yellow
temperature threshold. It is a non-disruptive test and can be run as a health monitoring test.
DiagFanTest :
This test verifies all fan modules have been inserted and working properly on the board
It is a non-disruptive test and can be run as a health monitoring test.
DiagPhyLoopbackTest :
The PHY Loopback test verifies the PHY level loopback
functionality. In this test, a packet is sent which loops back
at PHY level and is matched against the stored packet. It is a
disruptive test and cannot be run as a health monitoring test.
DiagScratchRegisterTest :
The Scratch Register test monitors the health of application-specific
integrated circuits (ASICs) by writing values into registers and reading
back the values from these registers. It is a non-disruptive test and can
be run as a health monitoring test.
DiagPoETest :
This test checks the PoE controller functionality. This is a disruptive test
and should not be performed during normal switch operation.
DiagStackCableTest :
This test verifies the stack ring loopback functionality
in the stacking environment. It is a disruptive test and
cannot be run as a health monitoring test.
DiagMemoryTest :
This test runs the exhaustive ASIC memory test during normal switch operation
NG3K utilizes mbist for this test. Memory test is very disruptive
in nature and requires switch reboot after the test.
Controller#