Cisco Catalyst 4500 Series, Software Configuration Manual

Page: 1971 / 2086

80-7
Catalyst 4500 Series Switch, Cisco IOS Software Configuration Guide - Cisco IOS XE 3.9.xE and IOS 15.2(5)Ex
Chapter 80 Performing Diagnostics
Last test failure time ------> n/a
Last test pass time ---------> Dec 20 2009 22:30:41
Total failure count ---------> 0
Consecutive failure count ---> 0
___________________________________________________________________________
Switch#
Displaying Data Path Online Diagnostics Test Results
A data path online diagnostic test verifies that the data paths between the supervisor engine and the
linecards (defined as a number of stub ASICs) are functioning correctly. There is a direct connection
between each stub ASIC on a line card and the supervisor engine. Error counters on the supervisor
engine (supervisor-rx-trends) and each stub ASIC on a line card (stub-rx-trends) are monitored
periodically. Error counters that continually increase indicate malfunctioning hardware in the data path
and cause the test to fail. Data path online diagnostic tests are non-destructure and the error counters are
polled every minute.
Errors on the stub end of the data path are reported as errors in traffic egressing to the line card from
the supervisor engine switching ASICs. Some initial errors might be revealed as links are brought
up, but they should not increase. An increasing count indicates a poor connection between the
supervisor engine and a line card. If only one line card is affected, the cause is likely an incorrectly
seated or faulty line card. The error counts include idle frames, so detection can occur when traffic
is not flowing.
Errors on the supervisor end of the data path are reported as errors in traffic ingressing to the
supervisor engine from linecards. The error counts should not increase and the detection includes
idle frames. If the error counts increase for more than one line card, the likely cause is a faulty
supervisor engine or chassis. If only one stub or line card is affected, the likely cause is a faulty line
card or a defective mux buffer (for a redundant chassis).
In addition to running periodically, data path online diagnostics can be also be invoked on-demand in the
following way:
Switch# diagnostic start module 1 test stub-rx-errors
*Apr 1 09:25:14.211: %DIAG-6-TEST_RUNNING: module 1: Running stub-rx-errors{ID=3} ...
*Apr 1 09:25:14.211: %DIAG-6-TEST_OK: module 1: stub-rx-errors{ID=3} has completed
Switch# diagnostic start module 1 test supervisor-rx-errors
*Apr 1 09:25:26.503: %DIAG-6-TEST_RUNNING: module 1: Running supervisor-rx-errors{ID=4}
...
*Apr 1 09:25:26.503: %DIAG-6-TEST_OK: module 1: supervisor-rx-errors{ID=4} has completed
successfully
Detailed information about the test results can be viewed as follows:
Switch# show diagnostic result module 1 test stub-rx-errors detail
Current bootup diagnostic level: minimal
Test results: (. = Pass, F = Fail, U = Untested)
___________________________________________________________________________
3) stub-rx-errors ------------------> .
Error code ------------------> 0 (DIAG_SUCCESS)
Total run count -------------> 7
Last test testing type ------> OnDemand
Last test execution time ----> Apr 01 2010 09:25:14
First test failure time -----> n/a
Last test failure time ------> n/a