Running Diagnostics on the Cisco 12012

Field diagnostics are available for the Cisco 12012 to help you isolate faulty hardware without disrupting of the operation of the system.

The Cisco 12012 diagnostics have the following features:

Diagnostics take the line card under test offline. The rest of the line cards remain online and continue to pass traffic normally. The diagnostics will not affect system performance.
You can run diagnostics concurrently on multiple line cards that have been taken offline or are not passing traffic.
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 being tested, diagnostics stop on the failing card; testing continues on the other cards.
There are over 80 diagnostic tests for line cards, which include the following:
- Processor tests
- Memory tests
- Component tests
- Major data path tests
The field diagnostics software image is bundled with the Cisco IOS software and is downloaded from the GRP to the target card prior to testing. While diagnostics are running, the line card being tested is controlled by the diagnostic software.

When testing is finished, a pass/fail message displays on the console as well as on the alphanumeric LED display on the card being tested.

Diagnostic Testing Sequence

When testing a card, the Cisco 12012 diagnostics perform the following sequence of operations:

Halts the normal operation of the card. The card is no longer available for network traffic.
Downloads a diagnostic image from the GRP Flash memory to the line card prior to 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.
Sends and receives messages to/from the card under test via the MBus. During the testing process, messages are passed from the line card under test to the GRP for display at the console. 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), a minimum number of messages are displayed at the console.
Displays pass/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. The pass/fail message is also sent to the alphanumeric LEd display on the card being tested where it is displayed until the Cisco IOS image is booted following the completion of testing.
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.

Using the diag Command

The diagnostic test command has the following format:

diag slot [previous | post] [verbose] [wait]

where:

slot	Specifies which upper card cage slot to test. The diagnostic software determines the type of card in the slot and downloads the appropriate tests.
previous	(Optional) Allows you to examine the last test results on the card specified by the slot parameter.
post	(Optional) Initiates EPROM-based extended power-on self-test (EPOST) only. The EPOST test suite is not as comprehensive as the field diagnostics, and the pass/fail message is the only message returned to the system console.
verbose	(Optional) Turns on the maximum 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, installed in the slot, and reconfigured manually.

To stop diagnostic testing at any time, use the following command:

diag slot halt

Loading and Running Diagnostics

This section provides the procedures for loading and running diagnostic tests on a card in the Cisco 12012. Included are sample console display messages. Diagnostic tests are run from the system console in privileged EXEC mode.

To load and run diagnostics on a card, perform the following steps:

Step 1 From the EXEC prompt (Router>), type enable to enter enable mode:

Router> enable

Password:

Step 2 Enter the password for the system.

The prompt changes to the privileged EXEC prompt:

Router#

Step 3 Determine the slot number of the card you want to run diagnostics on and enter the diag command:

Router# diag slot

The diagnostic tests are downloaded and executed. Test status and administrative messages are returned to the system console. At the end of testing, a pass/fail message is displayed on the console. The quantity of messages displayed depends on the setting of the verbosity option.

To see how the verbose option changes the messages from the diagnostics to the console, refer to the following two examples.

In the first example, diagnostics are run on a line card installed in slot 3 in the upper card cage. The diagnostics are run without the verbose option set (minimum messaging).

The console displays the following messages showing the progress of the diagnostic testing:

Router# diag 3
Runnning Diags will halt ALL activity on the requested slot.
[confirm]
Router#
Launching a Field Diagnostic for slot 3
Running DIAG config check
Running DIAG download to slot 3 (timeout set to 400 sec.)
sending cmd FDIAG_DOALL to fdiag in slot 3
(total/indiv. timeout set to 600/220 sec.)
Field Diagnostic ****PASSED**** for slot 3
Field Diag eeprom values: run 159 fail mode 0 (PASS) slot 3
   last test failed was 0, error code 0
sending SHUTDOWN FDIAG_QUIT to fdiag in slot 3
Board will reload
Router#

The messages on lines 1 through 8 indicate that the diagnostics software checked the card type and status, determined that the card installed in slot 3 could run diagnostics, downloaded the diagnostic software image to the card, and gave it the command to run all diagnostic tests.

The message on line 9 shows 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 the maximum amount of time allowed for any one diagnostic test to run.

The message on line 10 indicates that the diagnostic tests run on the card in slot 3 passed successfully.

If you set the verbose option, the diagnostics messages stream to the console changes. As an example, running diagnostics on the line card in slot 3 with the verbose option set produces the following message stream to the console (a partial list of messages is shown):

Launching a Field Diagnostic for slot 3
Running DIAG config check
Running DIAG download to slot 3 (timeout set to 400 sec.)
sending cmd FDIAG_DOALL to fdiag in slot 3 (total/indiv. timeout set to 600/220 sec.)
Field Diags: FDIAG_STAT_IN_PROGRESS: test #1 R5K Internal Cache
Field Diags: FDIAG STAT_PASS test_num 1
Field Diags: FDIAG_STAT_IN_PROGRESS: test #2 Subblock Ordering
Field Diags: FDIAG_STAT_PASS test_num 2
Field Diags: FDIAG_STAT_IN_PROGRESS: test #3 Dram Datapins
Field Diags: FDIAG_STAT_PASS test_num 3
Field Diags: FDIAG_STAT_IN_PROGRESS: test #4 L3FE Dram Access
Field Diags: FDIAG_STAT_PASS test_num 4
Field Diags: FDIAG_STAT_IN_PROGRESS: test #5 L3FE P4 Timeout
Field Diags: FDIAG_STAT_PASS test_num 5
Field Diags: FDIAG_STAT_IN_PROGRESS: test #6 L3FE Asic General Purpose Counter
Field Diags: FDIAG_STAT_PASS test_num 6
Field Diags: FDIAG_STAT_IN_PROGRESS: test #7 L3FE Asic Real Time Interrupt
Field Diags: FDIAG_STAT_PASS test_num 7
Field Diags: FDIAG_STAT_IN_PROGRESS: test #8 L3FE ToFab BMA SDram Read Around Write
Field Diags: FDIAG_STAT_PASS test_num 8
Field Diags: FDIAG_STAT_IN_PROGRESS: test #9 L3FE FrFab BMA SDram Read Around Write
Field Diags: FDIAG_STAT_PASS test_num 9
Field Diags: FDIAG_STAT_IN_PROGRESS: test #10 L3FE Dram Read Around Write
.
.
.
Field Diags: FDIAG_STAT_IN_PROGRESS: test #30 From Fabric (TX) BMA PLIM Buffers
Field Diags: FDIAG_STAT_PASS test_num 30
Field Diags: FDIAG_STAT_IN_PROGRESS: test #31 From Fabric (TX) BMA Micro Sequencer Ins^@
Field Diags: FDIAG_STAT_PASS test_num 31
Field Diags: FDIAG_STAT_IN_PROGRESS: test #32 From Fabric (TX) BMA Q Manager SRAM Busf@
Field Diags: FDIAG_STAT_PASS test_num 32
Field Diags: FDIAG_STAT_IN_PROGRESS: test #33 From Fabric (TX) BMA Q Manager SRAM Data@0.0c81.ee2a has
  been chosen.  Ensure that this address is unique, or specify MAC
  addresses for commands (such as 'novell routing') that allow the
  use of this address as a default.
Field Diags: FDIAG_STAT_PASS test_num 33
Field Diags: FDIAG_STAT_IN_PROGRESS: test #34 From Fabric (TX) BMA Q Manager Sram Marc@ protocol on Interface POS0, changed state to down
SLOT 5:%LINEPROTO-5-UPDOWN: Line protocol on Interface POS1, changed state to down
SLOT 5:%LINEPROTO-5-UPDOWN: Line protocol on Interface POS
Field Diags: FDIAG_STAT_PASS test_num 34
Field Diags: FDIAG_STAT_IN_PROGRESS: test #35 From Fabric (TX) BMA Micro Sequencer Scr^@
Field Diags: FDIAG_STAT_PASS test_num 35
Field Diags: FDIAG_STAT_IN_PROGRESS: test #36 From Fabric (TX) BMA to L3FE Packet
Field Diags: FDIAG_STAT_PASS test_num 36
Field Diags: FDIAG_STAT_IN_PROGRESS: test #37 From Fabric (TX) BMA SDRAM Marching Patt^@
Field Diags: FDIAG_STAT_PASS test_num 37
Field Diags: FDIAG_STAT_IN_PROGRESS: test #38 From Fabric (TX) BMA SDRAM Datapins
Field Diags: FDIAG_STAT_PASS test_num 38
Field Diags: FDIAG_STAT_IN_PROGRESS: test #39 To Fabric FIA Asic Registers
Field Diags: FDIAG_STAT_PASS test_num 39
Field Diags: FDIAG_STAT_IN_PROGRESS: test #40 To Fabric FIA Asic Packet
Field Diags: FDIAG_STAT_PASS test_num 40
Field Diags: FDIAG_STAT_IN_PROGRESS: test #41 From Fabric FIA Asic Registers
Field Diags: FDIAG_STAT_DONE
Field Diagnostic PASSED for slot 3
UUT in slot 3 eeprom updated with Field Diag results: 0000002B00000000
Board will reload
sending SHUTDOWN FDIAG_QUIT to fdiag in slot 3MESSAGE from Slot 3 : 
System Bootstrap, Version 11.2
Copyright (c) 1994-1997 by cisco Systems, Inc.
MESSAGE from Slot 3 : mem_size = 4000000
MESSAGE from Slot 3 : memory combination register = 11
MESSAGE from Slot 3 : LINECARD processor with 65536 Kbytes of main memory
MESSAGE from Slot 3 : ROM location: Extended ROM
Download to 8 Duration 0.060 seconds
MESSAGE from Slot 3 : Get a launch message
SLOT 3:%LINK-4-NOMAC: A random default MAC address of 0000.0c81.ed28 has been chosen.  Ensure that this address is unique, or specify MAC addresses for commands (such as 'novell routing') that allow the wuse of this address as a default.
SLOT 3:%SYS-5-RESTART: System restarted --
Cisco Internetwork Operating System Software 
IOS (tm) GS Software (BFLC-BFLC1-M), Experimental Version 11.2(19970515:151701) [award-bfr_112.temp 436]
Copyright (c) 1986-1997 by cisco Systems, Inc.
SLOT 3:%LINEPROTO-5-UPDOWN: Line protocol on Interface POS0, changed state to down
SLOT 3:%LINEPROTO-5-UPDOWN: Line protocol on Interface POS1, changed state to down
SLOT 3:%LINEPROTO-5-UPDOWN: Line protocol on Interface POS2, changed state to up
SLOT 3:%LINEPROTO-5-UPDOWN: Line protocol on Interface POS3, changed state to up
SLOT 3:%LINEPROTO-5-UPDOWN: Line protocol on Interface POS2, changed state to down
SLOT 3:%LINEPROTO-5-UPDOWN: Line protocol on Interface POS3, changed state to down

Most of the information presented with the verbose option set is status messages indicating when tests start and when they are completed. At the end of the diagnostic tests, a message is displayed indicating if the card passed or failed the tests.

Note Individual test start and end messages might not appear on the console during testing. However, any test fail messages will be displayed on the console.

If diagnostics fails on a line card, testing halts at the failing test. The line card will not reload and come back online automatically.

The following is an example of a diagnostic message stream to the console for a line card, located in slot 8, which fails one of the diagnostic tests.

Router# diag 8
Runnning Diags will halt ALL activity on the requested slot.
[confirm]
Launching a Field Diagnostic for slot 8
Running DIAG config check
Running DIAG download to slot 8 (timeout set to 400 sec.)
Launching Field Diagnostics in slot 8
sending cmd FDIAG_DOALL to fdiag in slot 8
(total/indiv. timeout set to 600/220 sec.)
Field Diagnostic: ****TEST FAILURE**** slot 8: last test run 8,
FIA Asics Packet SLI Loopback, error 2
Field Diag eeprom values: run 244 fail mode 1 (TEST FAILURE) slot 8
   last test failed was 8, error code 2
sending SHUTDOWN FDIAG_QUIT to fdiag in slot 8
slot 8 done, will not reload automatically

Note The DRAM is the only serviceable component on a line card; therefore, if a diagnostic test fails, you must replace the line card.

Table of Contents