- Preface
- Chapter 1 - Product Overview
- Chapter 2 - Preparing for Installation
- Chapter 3 - Installing the Router
- Chapter 4 - Troubleshooting the Installation
- Chapter 5 - Field Diagnostics for the Cisco 12000 Series Router
- Chapter 6 - Maintaining the Router
- Appendix A - Technical Specifications
- Appendix B - Repackaging the Router
Cisco 12006 and Cisco 12406 Router Installation and Configuration Guide
Chapter: Chapter 5 - Field Diagnostics for the Cisco 12000 Series Router
Field Diagnostics for the Cisco 12000 Series Router
Field diagnostics are available for all Cisco 12000 Series Routers to help you isolate faulty hardware to the level of a field-replaceable unit (FRU), without disrupting the operation of the system. After you identify the faulty unit, you can replace it with a spare unit.
Field diagnostics are not designed to identify specific components within the router. They simply determine whether a particular card is operational or defective.
Note 
Starting with Cisco IOS Release 12.0(22)S, the line card field diagnostics image is unbundled from the main Cisco IOS image. Line card field diagnostics are now stored and maintained as a separate image that must be available on a Flash memory card or TFTP boot server before the diagnostics commands can be used. Route processor and switch fabric card field diagnostics continue to be bundled and do not need to be launched from a separate image.
Unbundled field diagnostics offer the following benefits:
•In-service testing—Field diagnostics can be run on an in-service router running Cisco IOS and only take the card being tested out of service. If the tested card passes the diagnostic tests, it is returned to normal operation. If there is a hardware fault, the card remains out of service after the testing is completed.
•Smaller Cisco IOS image—To accommodate customers with 20-MB Flash memory cards, the line card field diagnostics are stored and maintained as a separate image that must be available on a Flash memory card or a TFTP boot server.
•Easy access to the most current diagnostics software—Since the field diagnostics software is now maintained as a separate image, the most recent version is always available on Cisco.com, without regard to the Cisco IOS software version currently in use.
The remainder of this chapter contains the following sections:
Diagnostics Overview
There are more than 100 diagnostic operations for each Cisco 12000 Series Router line card, in addition to diagnostics for the switch fabric and route processor cards. These operations include the following:
•Processor tests
•Memory tests
•Component tests
•Major data path tests
•Field-programmable gate array (FPGA) image updates (on some line cards)
Note When using Cisco IOS Release 12.0(21)S or 12.0(21)ST or later, the default download method changes from the MBus to the switch fabric. It takes about 1 minute to obtain test results from the switch fabric, compared to 15 minutes to obtain test results from the MBus.
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. Diagnostics do not affect system performance.
Diagnostic testing stops when all the tests are completed, when testing is terminated by the user, or by default 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.
FPGA Overview
Some Cisco 12000 Series Router line cards store hardware information as software code in the form of a field-programmable gate array (FPGA). This code is permanently placed on Flash memory directly on the line card. Occasionally, this Flash memory code needs to be updated with a different FPGA code for feature enhancements or code improvements.
Some FPGA images are bundled within the Cisco IOS image and are updated along with a new release and do not require Flash memory storage. These FPGAs are likely to be those that are being developed and expanded within Cisco IOS feature sets. Others that are unlikely to undergo change are permanently stored in the Flash memory of the line card. Upon booting the line card, Cisco IOS may use an image bundled within itself, or it may access and use the FPGA image stored in Flash memory on the line card.
When the FPGA code resides on Flash memory and the Cisco IOS code checks the revision, you may be informed by the Cisco IOS boot process that an FPGA upgrade is necessary.
The following sample Cisco IOS boot text shows an FPGA upgrade message in bold text.
*Aug 19 14:51:06 UTC: %MBUS-6-FABCONFIG: Switch Cards 0x1F (bitmask)
Primary Clock is CSC_1
Fabric Clock is Redundant
Bandwidth Mode : Full Bandwidth
*Aug 19 14:51:23 UTC: %MBUS-6-NO_FPGA_IMG: FPGA image is not
appropriate or corrupted for slot 0. Please run Field Diagnostics
image on slot 0 to upgrade the FPGA image.
*Aug 19 14:51:31 UTC: %GRPGE-6-SYNC_LOSS: Interface GigabitEthernet2/0: Loss of Sync
*Aug 19 14:51:31 UTC: %GRPGE-6-RX_LOS: Interface GigabitEthernet2/0: Detected RX Loss of Signal
SLOT 2:00:00:12: %SYS-5-RESTART: System restarted --
Cisco Internetwork Operating System Software
IOS (tm) GS Software (GLC1-LC-M), Experimental Version 12.0(20030605:093502) [mliflian-25-thr-work-nog-lke 115]
Copyright (c) 1986-2003 by cisco Systems, Inc.
Compiled Tue 19-Aug-03 17:33 by mliflian
When this message is received, the Cisco 12000 Series Router field diagnostics are used to update the Flash memory with the new image. When using field diagnostics to update the FPGA, no actual test is initiated, only an update to the FPGA code. See the "Upgrade the FPGA Image on a Line Card" section.
When field diagnostics run, the target line card stops passing traffic, but the rest of the router continues passing traffic normally. The line card is loaded with the field diagnostics program, the Flash memory update is run, and, if successful, the card reboots to Cisco IOS. The entire process takes approximately 2 minutes per line card and must be done one line card at a time. It is a good practice to wait about 30 seconds after Cisco IOS reloads on the line card before updating the next line card. This gives the router a chance to synchronize all its internal functions. The following sample output shows the process involved in updating the FPGA code on a line card in slot 0.
router# diag 0 verbose update-fpgas
Running DIAG config check
Fabric Download for Field Diags chosen: If timeout occurs, try 'mbus' option.
Verbose mode: Test progress and errors will be displayed
UUT will update FPGA's flash
Running Diags will halt ALL activity on the requested slot.[confirm]
Router#
Launching a Field Diagnostic for slot 0
Loading muckier/award/c12k-fdiagsbflc-mz.conn_isp from 223.255.254.254 (via Ethernet0): !!!!!( stuff deleted)
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
[OK - 8452824 bytes]
FD 0> *****************************************************
FD 0> GSR Field Diagnostics V6.14
FD 0> Compiled by award on Mon Sep 22 14:05:20 PDT 2003
FD 0> view: award-conn_isp.Field_Diag_Release
FD 0> *****************************************************
Executing all diagnostic tests in slot 0
(total/indiv. timeout set to 3000/600 sec.)
FD 0> BFR_CARD_TYPE_OC12_4P_ATM_E48 testing...
FD 0> Available test types 2
FD 0> 1
FD 0> 3
FD 0> 11
FD 0> Completed f_diags_board_discovery() (0x2f)
FD 0> Verbosity now (0x00000211) TESTSDISP FATL IDSPRINTF
FD 0> Test list selection received: Test ID 3, Device 0
FD 0> running in slot 0 (1 tests from test list ID 3)
FD 0> Skipping MBUS_FDIAG command from slot 5
FD 0> Just into idle state
FDIAG_STAT_IN_PROGRESS(0): test #1 Pinnacle FPGA Upgrade
FD 0> Same version of IOB FPGA in flash and bundle: rev A0.79
FD 0> IOB FPGA completed
FD 0> MICKEY FPGA completed
FD 0> Same version of MOUSE FPGA in flash and bundle: rev A0.11
FD 0> MOUSE FPGA completed
FD 0> Lower version of SAF FPGA being programmed over flash bundle: Bundle rev B0.0A flash rev B1.10
FD 0> SAF FPGA completed
FD 0> Magic number indicates first use of this sector in flash for CPK FPGA
FD 0> WARNING: Not all devices flashed successfully: fail_flag=0x0010
FD 0> CPK FPGA completed
FD 0> Displaying environmental information
FD 0> 3.3V 5V MBUS 5V Hot Sensor Inlet Sensor
FD 0> (mv) (mv) (mv) (deg C) (deg C)
FD 0> 3288 2568 5048 45.0 34.5
FDIAG_STAT_DONE(0)
FD 0> Changed current_status to FDIAG_STAT_IDLE
Field Diagnostic ****PASSED**** for slot 0
Field Diag eeprom values: run 8 fail mode 0 (PASS) slot 0
last test failed was 0, error code 0
Shutting down diags in slot 0
Board will reload
Router#
Router#
Router#
SLOT 0:00:00:42: %SYS-5-RESTART: System restarted --
Cisco Internetwork Operating System Software
IOS (tm) GS Software (GLC1-LC-M), Experimental Version 12.0(20030909:221642) [hsiang-conn3 108]
Copyright (c) 1986-2003 by cisco Systems, Inc.
Compiled Thu 11-Sep-03 15:19 by hsiang
Using Diagnostics
Before proceeding with any diagnostics procedures, review the following:
•Obtain and Place the Diagnostics Image
•Upgrade the FPGA Image on a Line Card
Obtain and Place the Diagnostics Image
Before you can use the line card field diagnostics commands, you must obtain and place a valid diagnostics image on a separate Flash memory card installed in the router or on a TFTP boot server.
Field diagnostics images are approximately 18 MB in size. Cisco IOS images are slightly larger. A single 64-MB Flash memory card can contain both images, or these images can be stored individually on two 20-MB memory cards inserted into in card slot 0 and slot 1 on the RP. To accommodate future feature releases, it is recommended that you use larger Flash memory disks.
The diagnostics image is named c12k-fdiagsbflc-mz.120-25.S and is always available on Cisco.com. 120-25.S is the version number of the image that corresponds to the Cisco IOS image, in this example, Cisco IOS Release 12.0(25)S.
Note All Cisco Systems field diagnostics images available on Cisco.com are backward and forward compatible with any Cisco IOS 12.0(22)S software release and later. Cisco strongly recommends always using the latest available field diagnostics image from Cisco.com for testing and verifying line cards.
Upgrade the FPGA Image on a Line Card
If a line card does not boot and you receive an error message indicating that there is a problem with the FPGA image, or if the line card alphanumeric LED display remains frozen in IOS STRT state, you need to upgrade the FPGA image using the diag command.
Note When the Cisco IOS image boots, it verifies that a compatible FPGA image is running on the router. The major version number of the FPGA image must be the same as that expected by the Cisco IOS image; the minor version number on the FPGA image must be the same as or greater than the minor version number expected by the Cisco IOS image. For example, if the Cisco IOS image expects a minimum FPGA image of 03.02, the software verifies that the actual major version number of the FPGA image in the line card bootflash is 03, and that the minor version number is 02 or above.
To upgrade the FPGA image on a line card, follow these steps:
Step 1 Enter privileged EXEC mode by entering the enable command followed by the password.
Step 2 Update the Flash memory with FPGA image(s) from the current field diagnostics download image by entering the diag command in this form:
diag slot-number update-fpga source {tftp | flash} source-path
The name of the image file is c12k-fdiagsbflc-mz.120-25.S, where 120-25.S is the Cisco IOS Release number.
•For Flash memory cards, the source path would typically be slot0:c12k-fdiagsbflc-mz.120-25.S or slot1:c12k-fdiagsbflc-mz.120-25.S.
•For TFTP boot servers, the source path would typically be tftp://tftp_server_ip_address/my_directory/c12k-fdiagsbflc-mz.120-25.S.
Do not unplug the line card or terminate the field diagnostics session during this test.
Using the diag Command
To perform field diagnostics on a line card, route processor (RP) (including both the performance route processor [PRP] and gigabit route processor [GRP]), switch fabric card (SFC), or clock and scheduler card (CSC), use the diag command in privileged EXEC configuration mode. To halt a running field diagnostic session on a line card or RP, use the diag halt form of this command.
Some line cards include components that are unable to isolate internal line card testing traffic from customer premise connections. When testing these line cards, you are warned and notified to disconnect any connections to these line cards before testing to achieve the most reliable results and minimize traffic disruption.
Cisco 12000 Series Router Line Cards
The following command examples apply to line card field diagnostics.
diag slot-number source {tftp | flash} source-path [verbose] [wait] [full] [coe] [dl-timeout-plus <1-2000>] [device] [messaging]
diag slot-number previous
diag slot-number halt
diag slot-number update-fpga source {tftp | flash} source-path [dl-timeout-plus <1-2000>]
Note Starting with Cisco IOS Release 12.0(22)S, the line card field diagnostics image is unbundled from the main Cisco IOS image. Line card field diagnostics are now stored and maintained as a separate image that must be available on a Flash memory card or TFTP boot server before the diagnostics commands can be used. Route processor and switch fabric card field diagnostics continue to be bundled and do not need to be launched from a separate image.
Cisco 12000 Series Router RPs
The following command examples apply to GRP and PRP field diagnostics:
diag slot-number [verbose] [wait] [full] [coe]
diag slot-number previous
diag slot-number halt
Cisco 12000 Series Router SFCs and CSCs
The following command example applies to SFC and CSC field diagnostics:
diag slot-number [verbose]
diag Command Reference
Table 5-1 lists the diag command options and their descriptions.
In some cases when field diagnostics indicates a card FAILURE, you may want to bring the line card back on line manually. In this case the microcode reload command may be used.
Performing field diagnostics on a line card stops all activity on the line card. Before the
diag command begins running diagnostics, you are prompted to confirm the request to perform field diagnostics on the line card.
In normal mode, if a test fails, the title of the failed test is displayed on the console. However, not all tests that are performed are displayed. To view all performed tests, use the verbose keyword.
After all diagnostic tests are completed on the line card, a PASSED or TEST FAILURE message is displayed. If the line card sends a PASSED message, the Cisco IOS software image on the line card is automatically reloaded unless the wait keyword is specified. If the line card sends a TEST FAILURE message, the Cisco IOS software image on the line card is not automatically reloaded.
If you want to reload the line card after it fails diagnostic testing, use the microcode reload slot global configuration command.
Note When you stop the field diagnostic test using the diag halt command, the line card remains down (in other words, in an unbooted state). Generally, you would stop testing in order to remove or replace the line card. If this is not the case, and you need to bring the line card back up (online), use the microcode reload global configuration command or power cycle the line card.
If the line card fails the test, the line card is defective and should be replaced. Under certain circumstances, Cisco Technical Assistance Center (TAC) engineers may direct you to replace field-replaceable memory modules and then retest. For example, if the DRAM test fails, you might only need to replace the DRAM on the line card. However, this should only be done under the guidance of a TAC engineer and only when observing tightly controlled static-sensitive device handling procedures. Do NOT replace memory components without proper body grounding and board grounding.
Output Examples
The following example shows the output when field diagnostics are performed on the line card in slot 7. After the line card passes all field diagnostic tests, the
Cisco IOS software automatically reloads on the card. Before starting the diagnostic tests, you must confirm the request to perform these tests on the line card because all activity on the line card is halted. The total/indiv. timeout set to 2000/600 sec. message indicates that 2000 seconds are allowed to perform all field diagnostics tests, and that no single test should exceed 600 seconds to complete.
Router# diag 7 source tftp
tftp://192.164.5.4/images/c12k-fdiagsbflc-mz.120-25.S
Running DIAG config check
Fabric Download for Field Diags chosen: If timeout occurs, try 'mbus' option.
Running Diags will halt ALL activity on the requested slot. [confirm]
award-rp-slot0#
Launching a Field Diagnostic for slot 7
Downloading diagnostic tests to slot 7 via fabric (timeout set to 300 sec.)
5d20h: %GRP-4-RSTSLOT: Resetting the card in the slot: 7,Event: EV_ADMIN_FDIAG
Loading images/award/c12k-fdiagsbflc-mz from 192.164.1.1 (via Ethernet0): !!!!!
5d20h: Downloading diags from tftp file tftp://192.164.1.1/images/award/c12k-fdiagsbflc-mz
!!!!![OK - 13976524 bytes]
FD 7> *****************************************************
FD 7> GSR Field Diagnostics V6.05
FD 7> Compiled by award on Tue Jul 30 13:00:41 PDT 2002
FD 7> view: award-conn_isp.FieldDiagRelease
FD 7> *****************************************************
Executing all diagnostic tests in slot 7
(total/indiv. timeout set to 2000/600 sec.)
FD 7> BFR_CARD_TYPE_OC12_4P_POS testing...
FD 7> Available test types 2
FD 7> 1
FD 7> Completed f_diags_board_discovery() (0x1)
FD 7> Test list selection received: Test ID 1, Device 0
FD 7> running in slot 7 (30 tests from test list ID 1)
FD 7> Skipping MBUS_FDIAG command from slot 2
FD 7> Just into idle state
Field Diagnostic ****PASSED**** for slot 7
Shutting down diags in slot 7
Board will reload
5d20h: %GRP-4-RSTSLOT: Resetting the card in the slot: 7,Event: EV_ADMIN_FDIAG
SLOT 7:00:00:09: %SYS-5-RESTART: System restarted --
Cisco Internetwork Operating System Software
IOS (tm) GS Software (GLC1-LC-M), Experimental Version 12.0(20020509:045149) [award-conn_isp.f_diag_new 337]
Copyright (c) 1986-2002 by cisco Systems, Inc.
Compiled Tue 25-Jun-02 15:51 by award
The following example shows the output of a line card test with the verbose option specified (highly recommended).
Router# diag 7 verbose tftp
tftp://192.164.1.1/images/award/c12k-fdiagsbflc-mz.120-25.S
Running DIAG config check
Fabric Download for Field Diags chosen: If timeout occurs, try 'mbus' option.
Verbose mode: Test progress and errors will be displayed
Runnning Diags will halt ALL activity on the requested slot. [confirm]
Router#
Launching a Field Diagnostic for slot 7
Downloading diagnostic tests to slot 7 via fabric (timeout set to 300 sec.)
00:07:41: %GRP-4-RSTSLOT: Resetting the card in the slot: 7,Event: EV_ADMIN_FDIAG
Loading images/award/c12k-fdiagsbflc-mz from 192.164.1.1 (via Ethernet0): !!!!!! (...)
00:08:24: Downloading diags from tftp file tftp://192.164.1.1/images/award/c12k-fdiagsbflc-mz
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!
[OK - 13976524 bytes]
FD 7> *****************************************************
FD 7> GSR Field Diagnostics V6.05
FD 7> Compiled by award on Tue Jul 30 13:00:41 PDT 2002
FD 7> view: award-conn_isp.FieldDiagRelease
FD 7> *****************************************************
Executing all diagnostic tests in slot 7
(total/indiv. timeout set to 2000/600 sec.)
FD 7> BFR_CARD_TYPE_OC12_4P_POS testing...
FD 7> Available test types 2
FD 7> 1
FD 7> Completed f_diags_board_discovery() (0x1)
FD 7> Verbosity now (0x00000011) TESTSDISP FATL
FD 7> Test list selection received: Test ID 1, Device 0
FD 7> running in slot 7 (30 tests from test list ID 1)
FD 7> Just into idle state
FDIAG_STAT_IN_PROGRESS(7): test #1 Dram Marching Pattern
FDIAG_STAT_IN_PROGRESS(7): test #2 Dram Datapins
FDIAG_STAT_IN_PROGRESS(7): test #3 Dram Busfloat
FDIAG_STAT_IN_PROGRESS(7): test #4 RBM SDRAM Marching Pattern
FDIAG_STAT_IN_PROGRESS(7): test #5 RBM SDRAM Datapins
FDIAG_STAT_IN_PROGRESS(7): test #6 RBM SSRAM Marching Pattern
FDIAG_STAT_IN_PROGRESS(7): test #7 RBM SSRAM Datapins Memory
FDIAG_STAT_IN_PROGRESS(7): test #8 TBM SDRAM Marching Pattern
FDIAG_STAT_IN_PROGRESS(7): test #9 TBM SDRAM Datapins
FDIAG_STAT_IN_PROGRESS(7): test #10 TBM SSRAM Marching Pattern
FDIAG_STAT_IN_PROGRESS(7): test #11 TBM SSRAM Datapins Memory
FDIAG_STAT_IN_PROGRESS(7): test #12 PSA TLU SDRAM Marching Pattern
FDIAG_STAT_IN_PROGRESS(7): test #13 PSA TLU SDRAM Datapins
FDIAG_STAT_IN_PROGRESS(7): test #14 PSA PLU SDRAM Marching Pattern
FDIAG_STAT_IN_PROGRESS(7): test #15 PSA PLU SDRAM Datapins
FDIAG_STAT_IN_PROGRESS(7): test #16 PSA SRAM Marching Pattern
FDIAG_STAT_IN_PROGRESS(7): test #17 PSA SRAM Datapins
FDIAG_STAT_IN_PROGRESS(7): test #18 To Fabric SOP FIFO SRAM Memory
FDIAG_STAT_IN_PROGRESS(7): test #19 From Fabric SOP FIFO SRAM Memory
FDIAG_STAT_IN_PROGRESS(7): test #20 RBM to SALSA Packet
FDIAG_STAT_IN_PROGRESS(7): test #21 TBM to SALSA Packet
FDIAG_STAT_IN_PROGRESS(7): test #22 RBM to TBM SLI Packet Loopback
FDIAG_STAT_IN_PROGRESS(7): test #23 TBM to PSA Packet - Framer Loopback
FDIAG_STAT_IN_PROGRESS(7): test #24 TBM to TX SOP Packet
FDIAG_STAT_IN_PROGRESS(7): test #25 TBM to RX SOP Packet - 4302 Terminal Loopback
FDIAG_STAT_IN_PROGRESS(7): test #26 TBM to RX SOP Packet - Framer System Bus Loop
FDIAG_STAT_IN_PROGRESS(7): test #27 RBM to TBM Fabric Packet Loopback
FDIAG_STAT_IN_PROGRESS(7): test #28 TBM to RBM Packet, RBM page crossing
FDIAG_STAT_IN_PROGRESS(7): test #29 TBM to TX SOP Packet Simultaneous
FDIAG_STAT_IN_PROGRESS(7): test #30 TBM to PSA Multicast Packets - Framer Loopback
FDIAG_STAT_DONE(7)
FD 7> Changed current_status to FDIAG_STAT_IDLE
Field Diagnostic ****PASSED**** for slot 7
Field Diag eeprom values: run 62 fail mode 0 (PASS) slot 7
last test failed was 0, error code 0
Shutting down diags in slot 7
Board will reload
Following is an example of a test FAILURE condition on a GRP card. This card would need to be replaced and returned to Cisco for repair:
Field Diag download COMPLETE for slot 7
FD 3> *****************************************************
FD 3> GSR Field Diagnostics V6.01
FD 3> Compiled by award on Tue Apr 9 07:22:53 PDT 2002
FD 3> view: award-conn_isp.f_diag_new
FD 3> *****************************************************
Diagnostics have been downloaded to slot 7
Executing all diagnostic tests in slot 7
(total/indiv. timeout set to 2000/600 sec.)
FD 3> BFRP w/ECC testing...
FD 3> Secondary Discovery found ID 2
FD 3> BFR_CARD_TYPE_BFRP_CARD w/ ECC testing...
FD 3> Available test types 2
FD 3> 1
FD 3> Completed f_diags_board_discovery() (0x1)
FD 3> Verbosity now (0x00000011) TESTSDISP FATL
FD 3> Test list selection received: Test ID 1, Device 0
FD 3> running in slot 7 (24 tests from test list ID 1)
FDIAG_STAT_IN_PROGRESS(3): test #1 BFRP Dram Datapins Test
FDIAG_STAT_IN_PROGRESS(3): test #2 Dram Marching Pattern Test
FDIAG_STAT_IN_PROGRESS(3): test #3 DataPins_Sram
FDIAG_STAT_IN_PROGRESS(3): test #4 March_Sram
FDIAG_STAT_IN_PROGRESS(3): test #5 High Memory DRAM Marching Pattern
FDIAG_STAT_IN_PROGRESS(3): test #6 diags_csar_regtest
FDIAG_STAT_IN_PROGRESS(3): test #7 diags_test_p4_csar_int
FDIAG_STAT_IN_PROGRESS(3): test #8 NVRAM Memory Test
FD 3> 32 bit data compare error. Wrote 0xcccccccc, read back 0xcc41cccc at location 0xbe03fff0
FDIAG_STAT_DONE_FAIL(3) test_num 8, error_code 1
COMPLETED Field Diags: pid 128, status 5, test_num 8, error_code 1
Field Diagnostic: ****TEST FAILURE**** slot 7: first test failed: 8,
NVRAM Memory Test, error 1
Field Diag results from eeprom before updating slot 7, run# 0x5000042 were 0x0
previous field diag eeprom values: run 66 fail mode 5 (DOWNLOAD FAILURE)
last test failed was 0, error code 0
Field Diag eeprom values: run 67 fail mode 1 (TEST FAILURE) slot 7
last test failed was 8, error code 1
Shutting down diags in slot 7
slot 7 done, will not reload automatically
The following example shows the previous test results of a line card. Diagnostics had been run 64 times on this line card. Because the board PASSED the last field diagnostics session, the fail mode was 0 as was the last test that failed.
Router # diag 7 prev
Field Diag eeprom values: run 64 fail mode 0 (PASS) slot 7
last test failed was 0, error code 0
The following example shows the output of a line card test with the update-fpga option specified.
Router# diag 7 verbose source tftp
tftp://223.255.254.254/c12k-fdiagsbflc-mz.120-25.S update-fpga
Running DIAG config check
Fabric Download for Field Diags chosen: If timeout occurs, try 'mbus' option.
Verbose mode: Test progress and errors will be displayed
UUT will update FPGA's flash
Runnning Diags will halt ALL activity on the requested slot. [confirm]
Router#
PID of f_diag_run is 121, set test_pid[3]
gdb slot is 0
Launching a Field Diagnostic for slot 7
Loading c12k-fdiagsbflc-mz.new_fpga from 223.255.254.254 (via Ethernet0):
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Calling enable_slot_and_type_on_fabric(DISABLE) for slot 7
Calling enable_slot_and_type_on_fabric(ENABLE) for slot 7
FD 3> *****************************************************
FD 3> GSR Field Diagnostics V6.9
FD 3> Compiled by ckhuong on Fri Jan 17 15:51:36 PST 2003
FD 3> view: ckhuong-conn_isp.inti4
FD 3> *****************************************************
Diagnostics have been downloaded to slot 7
Executing all diagnostic tests in slot 7
(total/indiv. timeout set to 2000/600 sec.)
FD 3> BFR_CARD_TYPE_4P_GE_E48 testing...
FD 3> Available test types 2
FD 3> 1
FD 3> 3
FD 3> 11
FD 3> Completed f_diags_board_discovery() (0x32)
FD 3> Verbosity now (0x00000011) TESTSDISP FATL
FD 3> Test list selection received: Test ID 3, Device 0
FD 3> running in slot 7 (1 tests from test list ID 3)
FD 3> Just into idle state
FDIAG_STAT_IN_PROGRESS(3): test #1 Tetra Flash Mem Upgrading
FD 3> Upgraded FPGA image in Flash from version 0xcc53 to 0xcc54
Calling enable_slot_and_type_on_fabric(DISABLE) for slot 7
Calling enable_slot_and_type_on_fabric(ENABLE) for slot 7
FDIAG_STAT_DONE(3)
FD 3> Changed current_status to FDIAG_STAT_IDLE
COMPLETED Field Diags: pid 121, status 6, test_num 1, error_code 0
Field Diagnostic ****PASSED**** for slot 7
Field Diag results from eeprom before updating slot 7, run# 0x10 were 0x0
previous field diag eeprom values: run 16 fail mode 0 (PASS)
last test failed was 0, error code 0
Field Diag eeprom values: run 17 fail mode 0 (PASS) slot 7
last test failed was 0, error code 0
Shutting down diags in slot 7
Board will reload
Router#
Feedback