|
|
Sections in this chapter include the following:
There are more than 80 diagnostic tests for line cards, including the following:
The field diagnostics software image is bundled with the Cisco IOS software and is downloaded from the GRP to the target card before testing. While diagnostics are running, the line card being tested is controlled by the diagnostic software.
Diagnostics take the line card under test offline. The diagnostics affect just the line card being tested; the rest of the line cards remain online and continue to pass traffic normally.
Except for the tests on the clock and scheduler cards (CSCs) and the switch fabric cards (SFCs), which temporarily drop throughput on those cards, the diagnostics do not affect system performance.
Diagnostic testing stops at the completion of all of the tests, when terminated by the user, or when an error is encountered. If multiple cards are specified for the test cycle, the diagnostics stop testing a card when it fails a test, but continue testing the remaining cards.
When testing is finished, a pass or fail message displays on the console, as well as on the alphanumeric LED display on the card being tested.
The diagnostic test command, issued at the privileged EXEC mode prompt on the system console, takes the following form:
diag slot [halt] [previous] [verbose] [wait]where:
slot | Specifies which card cage slot to test. The diagnostic software determines the type of card in the slot and downloads the appropriate tests. |
halt | (Optional) Stops the active diagnostic test. |
previous | (Optional) Allows you to examine the last test results on the card (EEPROM) specified by the slot parameter. |
verbose | (Optional) Turns on the status messaging capability of the diagnostics. The default is minimum messaging. |
wait | (Optional) Stops the diagnostics from reloading the Cisco IOS image following the completion of diagnostic testing. The card must be ejected from the slot, reinstalled in the slot, and reconfigured manually. |
When testing a card, the diagnostics perform the following operations in this sequence:
1. Halts the normal operation of the card. The card is no longer available for network traffic.
2. Downloads a diagnostic image from the GRP Flash memory to the line card before testing. The Cisco IOS software image is removed from the line card DRAM and is replaced with the diagnostic software image for the duration of the tests.
3. Sends and receives messages across the MBus to and from the card being tested. During the testing process, messages are passed from the line card under test to the GRP. If the verbose option is turned on, interim messages listing the start and completion of each test are displayed at the console. If the verbose option is not specified (default), the console displays the minimum number of messages.
4. Displays pass or fail test results. At the conclusion of the diagnostic tests, a pass or fail message is sent to the GRP, which passes the message to the console and to the alphanumeric LED display on the line card being tested. The message is displayed on the alphanumeric display until the Cisco IOS image is booted following the completion of testing. The pass or fail message is also stored in Flash memory for later factory analysis.
5. Reloads the Cisco IOS software image. If diagnostic testing was successful, and you do not specify the wait option, the Cisco IOS software image is loaded from the GRP to the card under test, bringing it back online.
This section describes the procedures for loading and running diagnostic tests on a card in the router, including sample console display messages. You must run diagnostic tests from the system console in privileged EXEC mode.
To load and run diagnostics on a card, follow these steps:
Step 1 From the EXEC prompt (Router>), type enable to enter privileged EXEC mode:
Router> enable
Password:
Step 2 Enter the password assigned to the system.
The prompt changes to the privileged EXEC prompt:
Router#
Step 3 Determine the slot number of the card on which you want to run diagnostics.
Step 4 Enter the diag command:
Router# diag slot
The diagnostic tests are downloaded and run. Test status and administrative messages are returned to the system console. At the end of testing, a pass or fail message is displayed on the console. The number of messages displayed depends on whether you included the verbose option in the command.
To see how the verbose option changes the messages from the diagnostics to the console, refer to the following examples.
In the first example, diagnostics are run on a line card installed in slot 2 in the card cage. The diagnostics are run without the verbose option set (minimum messaging).
The console displays a message sequence similar to the following, showing the progress of the diagnostic testing. In the following example message sequence, inserted comments describe the type of diagnostic activity by the messages.
Router#diag 2Running DIAG config checkRunning Diags will halt ALL activity on the requested slot.[confirm]Router#<Return>Launching a Field Diagnostic for slot 2Downloading diagnostic tests to slot 2 (timeout set to 400 sec.)Field Diag download COMPLETE for slot 2 FD 2> **************************************************** FD 2> GSR Field Diagnostics V3.0 FD 2> Compiled by award on Tue Aug 3 15:58:13 PDT 1999 FD 2> view: award-bfr_112.FieldDiagRelease FD 2> **************************************************** FD 2> BFR_CARD_TYPE_OC48_1P_POS_TTM testing... FD 2> running in slot 2 (73 tests) Executing all diagnostic tests in slot 2
The messages in the lines shown above indicate that the diagnostics software checked the card type and status, determined that the card installed in slot 2 could run diagnostics, downloaded the diagnostic software image to the card, and gave it the command to run all diagnostic tests.
(total/indiv. timeout set to 600/220 sec.)
The message in the line shown above indicates the two timeout values set for diagnostics. The first timeout is set to 600 seconds, which is the maximum amount of time allowed for all diagnostic tests to run. The second timeout is set to 220 seconds, which is the maximum amount of time allowed for any one diagnostic test to run.
Field Diagnostic ****PASSED**** for slot 2
The message in the line shown above indicates that the diagnostic tests run on the card in slot 2 all passed.
Shutting down diags in slot 2Board will reloadSLOT 2:%SYS-5-RESTART: System restarted -- Cisco Internetwork Operating System Software IOS (tm) GS Software (GSR-P-MZ), Released Version 12.0(n)GS Copyright (c) 1986-1999 by cisco Systems, Inc. Compiled Fri 17-Sep-99 17:58 by ...Router#
The messages in the lines shown above indicate that the diagnostics software is automatically terminated and the line card is reloaded and restarted.
If you set the verbose option, that changes the diagnostics message stream to the console. As an example, running diagnostics on the line card in slot 2 with the verbose option set produces a message stream to the console similar to the following (only a partial list of messages is shown). In the following example message sequence, inserted comments describe the type of diagnostic activity indicated by the messages.
Router#diag 2 verboseRunning DIAG config checkRunning Diags will halt ALL activity on the requested slot. [confirm] Router# <Return>Launching a Field Diagnostic for slot 2Downloading diagnostic tests to slot 2 (timeout set to 400 sec.)Field Diag download COMPLETE for slot 2 FD 2> **************************************************** FD 2> GSR Field Diagnostics V3.0 FD 2> Compiled by award on Tue Aug 3 15:58:13 PDT 1999 FD 2> view: award-bfr_112.FieldDiagRelease FD 2> **************************************************** FD 2> BFR_CARD_TYPE_OC48_1P_POS_TTM testing... FD 2> running in slot 2 (73 tests) Executing all diagnostic tests in slot 1 (total/indiv. timeout set to 600/220 sec.) FD 2> Verbosity now (0x00000001) TESTSDISP
Field diagnostics, verbose example (continued)
FDIAG_STAT_IN_PROGRESS: test #1 R5K Internal Cache FDIAG_STAT_IN_PROGRESS: test #2 Burst Operations FDIAG_STAT_IN_PROGRESS: test #3 Subblock Ordering FDIAG_STAT_IN_PROGRESS: test #4 Dram Marching Pattern FDIAG_STAT_IN_PROGRESS: test #5 Dram Datapins FDIAG_STAT_IN_PROGRESS: test #6 Dram Busfloat . . . FDIAG_STAT_IN_PROGRESS: test #73 SDRAM Traffic FDIAG_STAT_DONE Field Diagnostic ****PASSED**** for slot 2 Field Diag eeprom values: run 0 fail mode 0 (PASS) slot 2 last test failed was 0, error code 0 Shutting down diags in slot 2 Board will reload SLOT 2:%SYS-5-RESTART: System restarted -- Cisco Internetwork Operating System Software IOS (tm) GS Software (GSR-P-MZ), Released Version 12.0(n)GS Copyright (c) 1986-1999 by cisco Systems, Inc. Compiled Fri 17-Sep-99 17:58 by ... Router#
When you set the verbose option, most of the information returned by the diagnostic tests is status messages that indicate when tests start and when they are completed. At the end of the diagnostic tests, a message is displayed indicating whether the card passed or failed the tests.
If a diagnostic test fails on a line card, testing halts with that test. The line card will not reload and come back online automatically.
Router#diag 15 verboseRunning DIAG config checkRunning Diags will halt ALL activity on the requested slot.[confirm]Router# <Return>Launching a Field Diagnostic for slot 15Downloading diagnostic tests to slot 15 (timeout set to 400 sec.)Field Diag download COMPLETE for slot 15 FD 15> **************************************************** FD 15> GSR Field Diagnostics V3.0 FD 15> Compiled by award on Tue Aug 3 15:58:13 PDT 1999 FD 15> view: award-bfr_112.FieldDiagRelease FD 15> **************************************************** FD 15> BFR_CARD_TYPE_OC48_1P_POS testing... FD 15> running in slot 15 (128 tests) Executing all diagnostic tests in slot 15 (total/indiv. timeout set to 600/220 sec.) FD 15> Verbosity now (0x00000001) TESTSDISP FDIAG_STAT_IN_PROGRESS: test #1 R5K Internal Cache FDIAG_STAT_IN_PROGRESS: test #2 Burst Operations FDIAG_STAT_IN_PROGRESS: test #3 Subblock Ordering . . . FDIAG_STAT_IN_PROGRESS: test #21, error_code 5Field Diagnostic: ****TEST FAILURE**** slot 15: last test run 21,To Fabric SOP FIFO SRAM Memory, error 5Field Diag eeprom values:run 0 fail mode 1 (TEST FAILURE) slot 15 last test failed was 21, error code 5Shutting down diags in slot 15slot 15 done, will not reload automaticallyRouter#
Posted: Mon Jun 5 13:38:08 PDT 2000
Copyright 1989 - 2000©Cisco Systems Inc.