|
|
Table Of Contents
Online Offline Diagnostics—Field Diagnostics on Cisco 10000 Series Routers User's Guide
Field Diagnostic Image Information
Field Diagnostic Test Information
Things to Do Before Running a Field Diagnostic Test
Downloading the Required Software for Field Diagnostic Testing
Downloading a Field Diagnostic Image
Running a Field Diagnostic Test
Verifying a Line Card Is Supported by the Field Diagnostic Image
Deciding Which Field Diagnostic Tests to Run
Loading the Field Diagnostic Image onto a Line Card and Starting a Field Diagnostic Test
Removing a Field Diagnostic Image from a Line Card and Resuming Normal Line Card Operation
Stopping an In-Progress Field Diagnostic Test
diagnostic ondemand action-on-failure
diagnostic ondemand iterations
show diagnostic ondemand settings
Online Offline Diagnostics—Field Diagnostics on Cisco 10000 Series Routers User's Guide
The purpose of this document is to explain how to use Online Offline Field Diagnostics on Cisco 10000 series routers.
This document contains the following sections:
•
Benefits
•
•
•
•
Field Diagnostics Overview
The Online Offline Diagnostics (OOD) feature introduces a Field Diagnostic tool that provides customers with a method of testing and verifying line card hardware problems.
If you would like to perform a hardware diagnostic test on any line card in your Cisco 10000 series router, an OOD Field Diagnostic image can be downloaded free of charge from Cisco Systems and used to test whether the line card problems are indeed due to faulty hardware. The test results will verify whether or not the hardware is faulty.
Note
Field Diagnostic Image Information
A Field Diagnostic image is used to run diagnostic tests on a line card. The Field Diagnostic image is loaded from the TFTP server onto the line card in order to perform Field Diagnostic tests. Once Field Diagnostic testing is complete, the Field Diagnostic image must be unloaded off the line card to resume normal line card operation.
A few notes regarding Field Diagnostic images:
•
•
Field Diagnostic Test Information
The individual Field Diagnostic tests themselves as well as per-port tests are not currently relevant for troubleshooting purposes unless Field Diagnostic tests have already been run. If you want to run Field Diagnostic tests, we recommend selecting the all, basic, or default tests. The following explanations provide an overview of each test:
•
•
•
The estimates for the amount of time required to run each type of line card are given in the Field Diagnostics release notes.
Individual tests are useful for verification testing purposes. For instance, if a default test suite is run and all of the tests pass except test 5, test 5 can be run individually to confirm the test result of fail without having to run an entire test suite.
Benefits
On-Site Fault Detection
Field Diagnostics is used to verify if a line card problem is due to a hardware fault; therefore, Field Diagnostics can be used to confirm if a problem is indeed hardware-related and a line card needs to be returned.
Additional Uptime
Field Diagnostics can increase network uptime by ensuring that line cards are not mistakenly taken offline when a problem is elsewhere.
System Requirements
For information on the software and hardware requirements for Field Diagnostic images, see the Release Notes for the Field Diagnostic image.
Things to Do Before Running a Field Diagnostic Test
Console logging is often disabled on Cisco 10000 series routers for reasons unrelated to Field Diagnostics. Field Diagnostic testing can still occur when console logging is disabled, but it is important to note that some Field Diagnostic messages may not be seen because of the console logging setting.
A Field Diagnostic image will take the line card offline, meaning the line card cannot receive and transmit packets as usual when a Field Diagnostic image is loaded onto the line card. Therefore, you may want to schedule downtime for the line card being tested before performing Field Diagnostic tests.
Before perfuming any Field Diagnostic test, we recommend unplugging all cables on the device that connect to other interfaces. If the cables that connect interfaces are not unplugged, some Field Diagnostic tests may send packets to connected devices. Although these packets are harmless and will not impact network performance, packet counters on the receiving interfaces will be incremented when receiving these packets.
Downloading the Required Software for Field Diagnostic Testing
The following sections provide instructions on downloading the software required to run Field Diagnostic tests. It covers the following topics:
•
Downloading a Field Diagnostic Image
Note
A Field Diagnostic image first must be downloaded to a TFTP server in order to run a Field Diagnostic test on a line card.
Downloading the Field Diagnostic image to a TFTP server can be accomplished by completing the following steps:
Step 1
http://www.cisco.com/cgi-bin/tablebuild.pl/10000fdi
Step 2
Step 3
Running a Field Diagnostic Test
The following sections provide the instructions for running a Field Diagnostic test on a line card after the Cisco IOS image has been successfully loaded on the router and a Field Diagnostic image has been loaded onto the TFTP server.
This section covers the following topics:
•
•
•
•
•
Verifying a Line Card Is Supported by the Field Diagnostic Image
To see which line cards in your chassis support Field Diagnostic testing on the Cisco 10000 ESR series router, enter the show diagnostic status command.
In the following example, show diagnostic status is used to see if the line cards support Field Diagnostic testing. The support for the Field Diagnostic image is listed in the FDiag Support column of the show diagnostic status output:
Note
This information becomes important when specifying line cards for other commands; if you want to specify that a full-slot line card in a slot be tested, you can specify slot number in many of the diagnostic commands (an example in the following output would be slot 1). If you want to specify a half-slot line card, subslot number must be specified (the lone example in the following output is subslot 3/0).Router# show diagnostic status==== ======================== ======= ========== =========== ==============FDiag Loaded Overall CurrentSlot Card Description Support Image Type Diag Result Card State---- ------------------------ ------- ---------- ----------- --------------A Primary PRE1-RP NO IOS N/A ONLINEB Secondary PRE1-RP NO N/A N/A OFFLINE1 6oc3pos-1 YES LCDOS N/A ONLINE2 6oc3pos-1 YES Field Diag PASS DIAG READY3/0 1gigethernet-hh-1 YES LCDOS N/A ONLINE6 6cht3-1 YES LCDOS N/A ONLINE==== ======================== ======= ========== =========== ==============Deciding Which Field Diagnostic Tests to Run
The default test suite should be the selected test suite in most testing cases. The all test suite should only be used if all of the ports on the line card are ready for external loopback tests (in most cases, this means that all of the ports have been cabled using external loopback cables), and the basic test suite should only be used if time is critical and the line card cannot be down for more than a couple of extra minutes (in most cases, the default test only takes less than 5 extra minutes to run and it provides more complete testing coverage). To see the approximate time required to run each type of test, see the Release Notes for your Field Diagnostic image.
If you are unsure of which test suite to run, use the default test suite.
Loading the Field Diagnostic Image onto a Line Card and Starting a Field Diagnostic Test
To begin Field Diagnostic testing on a line card, the Field Diagnostic image must be loaded from the TFTP server onto the line card that will be tested. The following steps are required to download the Field Diagnostic image to the line card:
Note
http://www.cisco.com/cgi-bin/tablebuild.pl/10000fdi
The show diag command can be used to see the current Field Diagnostic image version (Note that this is the show diag command, not the show diagnostic command. The show diag and show diagnostic commands will produce completely different outputs).
Step 1
Step 2
Note
For additional information on when to specify slot or subslot, see the "Verifying a Line Card Is Supported by the Field Diagnostic Image" section.a.
Note
See the "Running a Per-Port or All Test" section section of this document for information on running per-port and all tests.In the following example, the Field Diagnostic image would be downloaded from the assigned TFTP server to the line card in slot 2 and the full Field Diagnostic test suite would be run:
Router# diagnostic load slot 2 tftp://126.1.1.1/myfolder/c10k-fdiagslc-mz.1.1.bin autostart test defaultb.
The following example shows the Field Diagnostic image is loaded from the TFTP server to the line card in slot 6. Note that the Field Diagnostic image has only been loaded onto the line card; Field Diagnostic testing has not begun.
Router# diagnostic load slot 6 tftp://126.1.1.1/mytftpfolder/c10k-fdiagslc-mz.1.1.bin
Note
Step 3
Note
See the "Reviewing Test Results" section of this document for information on running per-port and all tests.In the following example, a Field Diagnostic test with the default test suite is started on slot 6. The example assumes that a Field Diagnostic image has been loaded onto the line card in slot 6.
Router# diagnostic start slot 6 test default
Note
Checking the Testing Process
Some individual tests take longer to run than others and the the lack of feedback on the console for a period of time may be worrisome even though the tests are running properly.
If you are unsure if Field Diagnostic tests are still running, the show diagnostic status target detail command can be used to verify if the Field Diagnostic testing is running.
Interpreting Test Results
Note
After running a Field Diagnostic test, an overall test result for the selected tests is displayed on the console. The overall test result is either pass or fail.
Note
Pass: All of the Field Diagnostic tests passed.
Minor Error: This result is only seen with per-port and all tests. This error indicates that the tested interface is faulty but the other interfaces on the line card are not necessarily faulty.
Major Error: This result indicates a hardware problem with the entire line card and the line card should not be used.
Use the recommendations based on the last test results below when deciding how to proceed after running any OOD Field Diagnostic test.•
If the test fails again, copy any messages on the console exactly as they appear and gather the outputs of show diagnostic result and show diagnostic result detail and contact a customer support representative with the gathered information.
•
Note
To see if external loopback testing is supported on an interface, enter the show diagnostic content command and see if the L attribute is available for an individual test. For information on running an external loopback test, proceed to the next section.Default Test Pass
–
Basic Test Pass
–
All Test Pass
–
Running a Per-Port or All Test
The external loopback test is supported on most, but not all, interfaces.
To see if external loopback testing is supported on an interface, enter the show diagnostic content command and see if the L attribute is available for an individual test.For information on cabling DB-15 and RJ-45 connections for external loopback tests, see the Hard Plug Loopback Tests for E1 Lines document. Refer to other Cisco documentation regarding loopback cabling for particular cables and connector types.
A per-port Field Diagnostic test is used to test a specific port for hardware problems. A per-port test should only be run after a default test has been run and no problems were found on the other line card components. The all test suite is a test suite that includes the default test as well as all of the per-port tests. The all test suite should only be run if all of the interfaces are cabled with external loopback cables.
Per-port tests utilize external loopbacks to test the interface hardware. In most, but not all, cases, the interfaces to be tested need to be cabled with external loopback cables before per-port or all testing can begin. It is important to note that not all interfaces support external loopback testing.
In the following example, a per-port test is run on port 1 of the line card in slot 2:
Router# diagnostic start slot 2 test per-port port 1In the following example, all tests including all per-port diagnostic tests will be run on the line card in slot 2:
Router# diagnostic start slot 2 test allReviewing Test Results
After completing a Field Diagnostic test, a message will appear on the console indicating your overall test results. Additional show commands must be entered to gather test results and events information, however.
For additional information on diagnostic events and results, enter one of the following commands:
Table 1 Field Diagnostic show Commands for Viewing Test Results
The following example is the show diagnostic result output for the last Field Diagnostic test run on the line card in slot 2. The output reveals which tests passed, failed, and were not run (untested).
Router# show diagnostic result slot 2Slot 2: 6oc3pos-1, 6 portsOverall diagnostic result: PASSTest results: (. = Pass, F = Fail, U = Untested)1) MPC8260 Register Test ---------------------> .2) MPC8260 Timer Test ------------------------> .3) 6P OC3 POS MPC8260 Port I/O Test ----------> .4) march_dram_64 -----------------------------> .5) bus_float_dram_64 -------------------------> .6) data_pins_dram_64 -------------------------> .7) SDRAM ECC Test ----------------------------> .8) SRAM Test ---------------------------------> .9) CPLD Register Test ------------------------> .10) BariumRegTest -----------------------------> .11) BariumIntTest -----------------------------> .12) FIBRegTest_pm -----------------------------> .13) FIBIntTest_pm -----------------------------> .14) FIBSdramMemTest_pm ------------------------> .15) FIBChanMemTest_pm -------------------------> .16) FIBStatMemTest_pm -------------------------> .17) FIBDescMemTest_pm -------------------------> .18) TIBRegTest_pm -----------------------------> .19) TIBIntTest_pm -----------------------------> .20) TIBSdramMemTest_pm ------------------------> .21) TIBChanMemTest_pm -------------------------> .22) TIBStatMemTest_pm -------------------------> .23) TIBCtrlMemTest_pm -------------------------> .24) TIBSdramParityTest_pm ---------------------> .25) TIBCtrlParityTest_pm ----------------------> .26) PM5351RegTest_1 ---------------------------> .27) PM5351IntTest_1 ---------------------------> .28) PM5351RegTest_2 ---------------------------> .29) PM5351IntTest_2 ---------------------------> .30) PMBariumLpbkTest --------------------------> .31) BariumCRCTest -----------------------------> .32) PMParallelLpbkTest ------------------------> .33) PMSerialLpbkTest --------------------------> .34) PMExternalLpbkTest:Port 0 1 2 3 4 5----------------------U U U U U UThe following output shows detailed information for each Field Diagnostic test:
Router# show diagnostic result slot 2 detailSlot 2: 6oc3pos-1, 6 portsOverall diagnostic result: PASSTest results: (. = Pass, F = Fail, U = Untested)___________________________________________________________________________1) MPC8260 Register Test ---------------------> .Error code ----------------------------> 0 (DIAG_SUCCESS)Total run count -----------------------> 4Last test execution time --------------> Apr 02 2003 12:36:25First test failure time ---------------> n/aLast test failure time ----------------> n/aLast test pass time -------------------> Apr 02 2003 12:36:25Total failure count -------------------> 0Consecutive failure count -------------> 0___________________________________________________________________________2) MPC8260 Timer Test ------------------------> .Error code ----------------------------> 0 (DIAG_SUCCESS)Total run count -----------------------> 4Last test execution time --------------> Apr 02 2003 12:36:26First test failure time ---------------> n/aLast test failure time ----------------> n/aLast test pass time -------------------> Apr 02 2003 12:36:26Total failure count -------------------> 0Consecutive failure count -------------> 0...(Additional display text omitted from this example)The following example provides sample show diagnostic events output. This output provides a list of previous diagnostic events with a brief description of each event.
Router# show diagnostic eventsDiagnostic events (storage for 500 events, 122 events recorded)Event Type (ET): I - Info, W - Warning, E - ErrorTime Stamp ET [Card] Event Message------------------ -- --------------------------------------------------------04/02 06:50:19.903 I [3/0] Card detected: 1gigethernet-hh-1, S/N:cab061406qc04/02 06:50:23.907 I [2] Card detected: 6oc3pos-1, S/N:CAB0531JXEF04/02 06:50:25.207 I [1] Card detected: 6oc3pos-1, S/N:CAB0531JXEE04/02 06:50:55.419 I [6] Card detected: 6cht3-1, S/N:N/A04/02 06:51:36.935 I [2] Loading Field Diag image into 6oc3pos-104/02 06:52:12.435 I [2] Field Diag image is loaded and booting04/02 06:52:14.575 I [2] Test list retrieval is completed04/02 06:58:45.551 I [2] Starting MPC8260 Register Test {ID=1}04/02 06:58:45.599 I [2] MPC8260 Register Test {ID=1} passed04/02 06:58:45.755 I [2] Field Diag passed for selected tests04/02 06:59:06.207 I [2] Field Diag image is unloaded04/02 06:59:24.107 I [2] Card detected: 6oc3pos-1, S/N:CAB0531JXEF04/02 12:24:02.662 I [2] Loading Field Diag image into 6oc3pos-104/02 12:24:38.570 I [2] Field Diag image is loaded and booting04/02 12:24:40.706 I [2] Test list retrieval is completed04/02 12:28:51.638 I [2] Starting MPC8260 Register Test {ID=1}04/02 12:28:51.686 I [2] MPC8260 Register Test {ID=1} passed04/02 12:28:51.742 I [2] Starting MPC8260 Timer Test {ID=2}...(Additional display text omitted from this example)Removing a Field Diagnostic Image from a Line Card and Resuming Normal Line Card Operation
Note
The diagnostic unload {slot slot-number | subslot slot-number/subslot-number} command can be used to unload a Field Diagnostic image as long as a Field Diagnostic test is not in progress. If you want to unload a Field Diagnostic image while a test is in progress, use the diagnostic stop {slot slot-number | subslot slot-number/subslot-number} command to stop the test, followed by the diagnostic unload {slot slot-number | subslot slot-number/subslot-number} command to unload the Field Diagnostic image.
Normal line card operation should resume after removing the Field Diagnostic image from the line card.
In the following example, the Field Diagnostic image is unloaded off the line card in slot 2 and normal line card operation will resume. Note that the Field Diagnostic image unloading process does not begin until y is entered at the prompt to verify the operation.
Router# diagnostic unload slot 2******************************************************************************WARNING:All Field Diagnostics test results and information will beunavailable to both the "show diagnostic result <target>" and"show diagnostic content <target>" commands.To save the test results, cancel the unloading process and enterthe "show diagnostic result <target>" command. Copy the outputinto a file, then re-enter the "diagnostic unload <target>" commandto restore normal line card operation.******************************************************************************% Are you sure that you want to perform this operation? [no]:yFDIAG [slot 2]> Unloading the Field Diagnostics image and restoring the original run-time image, please wait ...FDIAG [slot 2]> Field Diagnostics image was successfully unloadedSpecifying Testing Options
The following table provides a list of optional commands that can be entered before performing a Field Diagnostic test. None of these commands have to be entered to perform a Field Diagnostic test and most Field Diagnostic test cases will not require these commands.
See the "Command Reference" section of this document for additional information on any of these commands:
Table 2 Field Diagnostics Pre-Testing Options
The following example shows how to change the size of the event table to 250. Note that the event table size is changed in global configuration mode.
Router# configure terminalRouter(config)# diagnostic event-log size 250The following example shows how to change diagnostic on-demand settings and then verify the changed diagnostic ondemand settings.
Router# diagnostic ondemand iterations 2Router# diagnostic ondemand action-on-failure stopRouter# show diagnostic ondemand settingsTest iterations = 2Action on test failure = stopStopping an In-Progress Field Diagnostic Test
To stop an in-progress Field Diagnostic test, enter the diagnostic stop {slot slot-number | subslot slot-number/subslot-number} command while a test is in progress.
Note
The following example shows a diagnostic test being started and then stopped:
Router# diagnostic start slot 2 test basicRouter#FDIAG [slot 2]> Test ID(s) selected: 1-2,4,7,9-29,32-33FDIAG [slot 2]> Running Field Diagnostics [Iteration #1] ...FDIAG [slot 2]> Running MPC8260 Register Test {ID=1} ...FDIAG [slot 2]> MPC8260 Register Test {ID=1} passedFDIAG [slot 2]> Running MPC8260 Timer Test {ID=2} ...FDIAG [slot 2]> MPC8260 Timer Test {ID=2} passedFDIAG [slot 2]> Running march_dram_64 {ID=4} ...Router# diagnostic stop slot 2FDIAG [slot 2]> march_dram_64 {ID=4} passedFDIAG [slot 2]> Testing is being abortedFDIAG [slot 2]> Total testing time = 00:00:05.500Router#FDIAG [slot 2]> Field Diagnostics was successfully stoppedLimitations and Restrictions
•
If you would like to perform a Field Diagnostic test on a card in an APS configuration, unconfigure APS using the following commands before downloading the Field Diagnostic image to one of the line cards.
Router(config)#redundancy
Router(config-r)# no associate slot slot-numberFor additional information on disabling APS, see the "Disabling Redundancy to Disable SONET APS" section of Configuring Automatic Protection Switching.
•
•
•
Command Reference
This section documents the new commands introduced with Field Diagnostics on the Cisco 10000 series router. All other commands used with this feature are documented in the Cisco IOS Release 12.2 command reference publications.
•
•
•
diagnostic event-log size
To set the size of the event table, use the diagnostic event-log size command.
diagnostic event-log size event-size
Syntax Description
Defaults
The default event-size is 500.
Command Modes
Global configuration
Command History
Usage Guidelines
The diagnostic event-log size command sets the number of events that are saved in the event log. The event log can be viewed by entering the show diagnostic events command.
Examples
In the following example, the event table size is expanded to 501 events.
Router(config)# diagnostic event-log size 501Related Commands
diagnostic load
To load a Field Diagnostic image to the line card for Field Diagnostic testing, enter the diagnostic load command.
diagnostic load {slot slot-number | subslot slot-number/subslot-number} image-url [autostart test {all [port port-number | WORD]}| basic | default | per-port port-number}]
Syntax Description
Defaults
If the autostart option is entered but no test is specified, the default test suite is the suite used to test the line card.
Command Modes
Priviliged EXEC
Command History
Usage Guidelines
Entering this command and successfully downloading the Field Diagnostic image will disrupt normal line card operation. To remove the Field Diagnostic image from a line card and restore normal line card operation, use the diagnostic unload command.
If the autostart option is not specified, diagnostic tests can be run on the line card after the Field Diagnostic image has been loaded by entering the diagnostic start command.
Examples
In the following example, the diagnostic load command is used to download the Field Diagnostic image in TFTP server 127.1.1.1/mytftpfolder to the line card in slot 2. If yes is entered at the prompt below, the router will be placed in Field Diagnostic mode.
Router# diagnostic load slot 2 tftp://127.1.1.1/mytftpfolder/c10k-fdiagslc-mz.1.1.bin******************************************************************************WARNING:The specified line card will be taken offline, please ensure thatall traffic has been redirected before executing this command.NOTE:The "diagnostic unload <target>" command must be used after diagnostictesting to resume normal line card operation.******************************************************************************Field Diagnostics Image Loading Parameters==============================================================================Slot:2 (6oc3pos-1)Image URL:tftp://127.1.1.1/mytftpfolder/c10k-fdiagslc-mz.1.1.binAuto-Start:disabled==============================================================================% Are you sure that you want to perform this operation? [no]:Related Commands
diagnostic ondemand action-on-failure
To set an error count limit or to stop testing once a diagnostic error event is detected, use the diagnostic ondemand action-on-failure command.
diagnostic ondemand action-on-failure [continue failure-limit | stop]
Syntax Description
Defaults
If this command is not entered, a default failure-limit of 0 is used. Therefore, testing will continue regardless of the number of errors unless the diagnostic ondemand action-on-failure command is used to change the default setting.
Command Modes
Priviliged EXEC
Command History
Usage Guidelines
The diagnostic ondemand action-on-failure settings cannot be saved to an IOS configuration file. Therefore, the diagnostic ondemand action-on-failure command will need to be re-entered each time a router is reset or power cycled if the action-on-failure settings should be maintained.
The show diagnostic ondemand settings command can be used to verify the diagnostic ondemand action-on-failure setting.
The show diagnostic events event-type error command can be used to gather additional information about an error event.
Examples
In the following example, the diagnostic on-demand iteration and action-on-failure settings are changed using diagnostic ondemand iterations and diagnostic ondemand action-on-failure. The changed settings are then confirmed using show diagnostic ondemand settings.
Router# diagnostic ondemand iterations 2Router# diagnostic ondemand action-on-failure stopRouter# show diagnostic ondemand settingsTest iterations = 2Action on test failure = stopRelated Commands
diagnostic ondemand iterations
To set the number of times a diagnostic tests or set of tests will be run when the diagnostic start command is entered, enter the diagnostic ondemand iterations command.
diagnostic ondemand iterations iteration-count
Syntax Description
Defaults
The default iteration-count is 1.
Command Modes
Priviliged EXEC
Command History
Usage Guidelines
The diagnostic ondemand iterations settings cannot be saved to an IOS configuration file. Therefore, the diagnostic ondemand iterations command will need to be re-entered each time a router is reset or power cycled if a nondefault setting needs to be maintained.
The show diagnostic ondemand settings command can be used to verify the diagnostic ondemand iterations setting.
Examples
In the following example, the diagnostic on-demand iteration and action-on-failure settings are changed using diagnostic ondemand iterations and diagnostic ondemand action-on-failure. The changed settings are then confirmed using show diagnostic ondemand settings.
Router# diagnostic ondemand iterations 2Router# diagnostic ondemand action-on-failure stopRouter# show diagnostic ondemand settingsTest iterations = 2Action on test failure = stopIn the following example, the diagnostic ondemand iterations command is first used to change the number of iterations per test to 2. Therefore, a Field Diagnostic test is run twice (note that the output of the diagnostic start command reflects the test being run twice).
After the initial test, the iteration-count is then changed to 3 and the same test is run. Note that the output of diagnostic start shows each test being run three times as opposed to two after the iteration-count was changed using the diagnostic ondemand iterations 3 command.
Router# diagnostic ondemand iterations 2Router# diagnostic start slot 8 test 1Slot 8: Running test(s) 1 may generate packets out of the card interface.Do you want to run the selected test(s)? [no]: yRouter#FDIAG [slot 8]> Running Field Diagnostics [Iteration #1] ...FDIAG [slot 8]> Running MPC860 Register Test {ID=1} ...FDIAG [slot 8]> MPC860 Register Test {ID=1} passedFDIAG [slot 8]> Running Field Diagnostics [Iteration #2] ...FDIAG [slot 8]> Running MPC860 Register Test {ID=1} ...FDIAG [slot 8]> MPC860 Register Test {ID=1} passedFDIAG [slot 8]> Total testing time = 00:00:00.500FDIAG [slot 8]> Field Diagnostics passed with the selected test(s)*Jun 13 16:05:48.987: %DIAG_C10K-5-TESTING_PASSED: Field Diagnostics passed with the selected test(s) for card in slot 8Router# diagnostic ondemand iterations 3Router# diagnostic start slot 8 test 1Slot 8: Running test(s) 1 may generate packets out of the card interface.Do you want to run the selected test(s)? [no]: yRouter#FDIAG [slot 8]> Running Field Diagnostics [Iteration #1] ...FDIAG [slot 8]> Running MPC860 Register Test {ID=1} ...FDIAG [slot 8]> MPC860 Register Test {ID=1} passedFDIAG [slot 8]> Running Field Diagnostics [Iteration #2] ...FDIAG [slot 8]> Running MPC860 Register Test {ID=1} ...FDIAG [slot 8]> MPC860 Register Test {ID=1} passedFDIAG [slot 8]> Running Field Diagnostics [Iteration #3] ...FDIAG [slot 8]> Running MPC860 Register Test {ID=1} ...FDIAG [slot 8]> MPC860 Register Test {ID=1} passedFDIAG [slot 8]> Total testing time = 00:00:00.600FDIAG [slot 8]> Field Diagnostics passed with the selected test(s)*Jun 13 16:06:07.291: %DIAG_C10K-5-TESTING_PASSED: Field Diagnostics passed with the selected test(s) for card in slot 8Related Commands
diagnostic start
To begin a Field Diagnostic test after downloading the Field Diagnostic image to the line card, enter the diagnostic start command.
diagnostic start {{slot slot-number | subslot slot-number/subslot-number} test {all [port port-number | WORD | all]} | basic | default | per-port port-number | test-id-number | WORD}
Syntax Description
Defaults
No default behavior or values.
Command Modes
Priviliged EXEC
Command History
Usage Guidelines
This command can only be entered successfully if a Field Diagnostic image has already been loaded onto the line card that will be tested. The diagnostic load command is used to load a diagnostic image onto a line card.
The show diagnostic content command can be used to see which tests are run when basic or all is specified as the testing option. The show diagnostic content command also displays the tests that are available on a particular line card and their associated test numbers.
Examples
In the following example, the default test list is run for the line card in slot 2. The final lines of the output are shown to show that the line card passed the Field Diagnostic test.
Note
Router# diagnostic start slot 2 test defaultRouter#FDIAG [slot 2]> Test ID(s) selected: 1-33FDIAG [slot 2]> Running Field Diagnostics [Iteration #1] ...FDIAG [slot 2]> Running MPC8260 Register Test {ID=1} ...FDIAG [slot 2]> MPC8260 Register Test {ID=1} passedFDIAG [slot 2]> Running MPC8260 Timer Test {ID=2} ...FDIAG [slot 2]> MPC8260 Timer Test {ID=2} passedFDIAG [slot 2]> Running 6P OC3 POS MPC8260 Port I/O Test {ID=3} ...FDIAG [slot 2]> 6P OC3 POS MPC8260 Port I/O Test {ID=3} passedFDIAG [slot 2]> Running march_dram_64 {ID=4} ...FDIAG [slot 2]> march_dram_64 {ID=4} passedFDIAG [slot 2]> Running bus_float_dram_64 {ID=5} ...FDIAG [slot 2]> bus_float_dram_64 {ID=5} passedFDIAG [slot 2]> Running data_pins_dram_64 {ID=6} ...FDIAG [slot 2]> data_pins_dram_64 {ID=6} passedFDIAG [slot 2]> Running SDRAM ECC Test {ID=7} ...FDIAG [slot 2]> SDRAM ECC Test {ID=7} passed(Additional display text ommitted)Related Commands
diagnostic stop
To stop an in-progress Field Diagnostic test, enter the diagnostic stop command.
diagnostic stop {slot slot-number | subslot slot-number/subslot-number}
Syntax Description
Defaults
No default behavior or values.
Command Modes
Priviliged EXEC
Command History
Usage Guidelines
The diagnostic stop command can be entered at any time, even if a prompt is not present because the console is displaying diagnostic testing events. However, hitting Enter on your keyboard while a test is in progress will give you a router prompt and will make entering the diagnostic stop command easier.
This command is used to stop a diagnostic test that had been started previously using the diagnostic start command or was started automatically when the autostart option was entered when using the diagnostic load command. This command only stops the test; it does not remove the Field Diagnostic image from the line card. If you want to stop the Field Diagnostic test and put the line card online, use diagnostic unload after entering diagnostic stop.
Examples
In the following example, a diagnostic test on the line card in slot 6 is started and then stopped using the diagnostic stop command.
Router# diagnostic start slot 6 test allSlot 6: Running test(s) 1-31 may disrupt normal system operationDo you want to run disruptive tests? [no]: yRouter#FDIAG [slot 6]> Running Field Diagnostics [Iteration #1] ...FDIAG [slot 6]> Running MPC860 Register Test {ID=1} ...FDIAG [slot 6]> MPC860 Register Test {ID=1} passedFDIAG [slot 6]> Running MPC860 Register2 Test {ID=2} ...FDIAG [slot 6]> MPC860 Register2 Test {ID=2} passedFDIAG [slot 6]> Running MPC860 Timer Test {ID=3} ...FDIAG [slot 6]> MPC860 Timer Test {ID=3} passedFDIAG [slot 6]> Running OC12 POS MPC860 Port IO Test {ID=4} ...FDIAG [slot 6]> OC12 POS MPC860 Port IO Test {ID=4} passedFDIAG [slot 6]> Running march_dram_1 {ID=5} ...Router# diagnostic stop slot 6FDIAG [slot 6]> march_dram_1 {ID=5} stoppedFDIAG [slot 6]> Total testing time = 00:00:07.500*May 14 11:16:47.489: %DIAG-6-DIAG_STOPPED: Slot 6: Diagnostic is stopped.Related Commands
diagnostic unload
To unload the Field Diagnostic on the line card and resume normal line card operation, enter the diagnostic unload command.
diagnostic unload {slot slot-number | subslot slot-number/subslot-number}
Syntax Description
Defaults
No default behavior or values.
Command Modes
Priviliged EXEC
Command History
Usage Guidelines
The show diagnostic result output will be lost once a Field Diagnostic image is successfully unloaded off a line card. If you want to retain the results of the Field Diagnostic test, enter show diagnostic result and copy the output into a separate file before entering diagnostic unload to unload the Field Diagnostic image off the line card.
Entering this command successfully will resume normal line card operation.
If a line card needs to be placed back online immediately and a Field Diagnostic test is in progress, enter diagnostic stop to stop the in-progress Field Diagnostic test before entering diagnostic unload to unload the Field Diagnostic image off the line card.
Examples
In the following example, the Field Diagnostic image is unloaded off of the line card in slot 2. Note that the command is not successfully executed until confirmed at the screen prompt.
Router# diagnostic unload slot 2******************************************************************************WARNING:All Field Diagnostics test results and information will beunavailable to both the "show diagnostic result <target>" and"show diagnostic content <target>" commands.To save the test results, cancel the unloading process and enterthe "show diagnostic result <target>" command. Copy the outputinto a file, then re-enter the "diagnostic unload <target>" commandto restore normal line card operation.******************************************************************************% Are you sure that you want to perform this operation? [no]:yFDIAG [slot 2]> Unloading the Field Diagnostics image and restoring the original run-time image, please wait ...FDIAG [slot 2]> Field Diagnostics image was successfully unloadedRelated Commands
show diagnostic content
To show the Field Diagnostic test list for a line card with a loaded Field Diagnostic image, use the show diagnostic content command.
show diagnostic content {all | slot slot-number | subslot slot-number/subslot-number}
Syntax Description
Defaults
No default behavior or values.
Command Modes
EXEC and priviliged EXEC modes
Command History
Usage Guidelines
It is important to note that the show diag and show diagnostic commands produce completely different outputs. Therefore, the show diagnostic output cannot be gathered using show diag because the autocomplete function will generate the show diag, not the show diagnostic, output. If you want to abbreviate the show diagnostic command, the shortest possible abbreviation is show diagn.
The output for the show diagnostic content command varies based on whether a Field Diagnostic image is or is not loaded onto a line card. If the line card contains a loaded Field Diagnostic image, the available test list will be presented in the show diagnostic content output. If the line card does not contain a loaded Field Diagnostic image, the output will indicate that a Field Diagnostic image is not available and will also contain a note regarding Field Diagnostic testing availability for the particular line card.
Examples
The following show diagnostic content output occurs when no Field Diagnostic image is loaded onto the line card in slot 2.
Router# show diagnostic content slot 2Diagnostic[Slot 2]: Diagnostic is not available.NOTE: The Field Diagnostic test suite is supported for this line card.To run Field Diagnostic tests, download the Field Diagnostic image fromcisco.com to a TFTP server or a flash card and enter the "diagnosticload" command.The following show diagnostic content output occurs when a Field Diagnostic image is loaded onto the line card in slot 2. Note that the output assigns a test number to each test and reveals if the test is run when basic testing coverage is specified.
Router#show diagnostic content slot 2Slot 2: 6oc3pos-1, 6 portsDiagnostics test suite attributes:B/* - Basic ondemand test / NAP/V/* - Per port test / Per device test / NAD/N/* - Disruptive test / Non-disruptive test / NAS/* - Only applicable to standby unit / NAU/* - Default non-intervention test / NAL/* - External loopback test / NAID Test Name Attributes==== ============================================ ============1) MPC8260 Register Test ---------------------> B***U*2) MPC8260 Timer Test ------------------------> B***U*3) 6P OC3 POS MPC8260 Port I/O Test ----------> ****U*4) MarchingPattern DRAM (64 Bit Access) ------> B***U*5) BusFloat DRAM (64 Bit Access) -------------> ****U*6) DataPins DRAM (64 Bit Access) -------------> ****U*7) SDRAM ECC Test ----------------------------> B***U*8) SRAM Test ---------------------------------> ****U*9) CPLD Register Test ------------------------> B***U*10) Barium Register Test ----------------------> B***U*11) Barium Interrupt Test ---------------------> B***U*12) FIB Register Test -------------------------> B***U*13) FIB Interrupt Test ------------------------> B***U*14) FIB SDRAM Memory Test ---------------------> B***U*15) FIB Channel Memory Test -------------------> B***U*16) FIB Statistic Memory Test -----------------> B***U*17) FIB Descriptor Memory Test ----------------> B***U*18) TIB Register Test -------------------------> B***U*19) TIB Interrupt Test ------------------------> B***U*20) TIB SDRAM Memory Test ---------------------> B***U*21) TIB Channel Memory Test -------------------> B***U*22) TIB Statistics Memory Test ----------------> B***U*23) TIB Control Memory Test -------------------> B***U*24) TIB SDRAM Parity Test ---------------------> B***U*25) TIB Control Parity Test -------------------> B***U*26) PM5351 1 Register Test --------------------> B***U*27) PM5351 1 Interrupt Test -------------------> B***U*28) PM5351 2 Register Test --------------------> B***U*29) PM5351 2 Interrupt Test -------------------> B***U*30) Barium Lpbk Datapath Test -----------------> ****U*31) Barium CRC Test ---------------------------> ****U*32) Parallel Lpbk Datapath Test ---------------> B***U*33) Serial Lpbk Datapath Test -----------------> B***U*34) External Lpbk Datapath Test ---------------> *P***LTable 3 describes the significant fields shown in the display.
Related Commands
show diagnostic events
To display the history of all Field Diagnostic events since the last system reload, enter the show diagnostic events command.
show diagnostic events [event-type {error | info | warning} | {slot slot-number | subslot slot-number/subslot-number}]
Syntax Description
Defaults
No default behavior or values.
Command Modes
EXEC and priviliged EXEC mode
Command History
Usage Guidelines
It is important to note that the show diag and show diagnostic commands produce completely different outputs. Therefore, the show diagnostic output cannot be gathered using show diag because the autocomplete function will generate the show diag, not the show diagnostic, output. If you want to abbreviate the show diagnostic command, the shortest possible abbreviation is show diagn.
Examples
In the following example, a listing of error-type events is provided:
Router# show diagnostic events event-type errorDiagnostic events (storage for 500 events, 135 events recorded)Event Type (ET): I - Info, W - Warning, E - ErrorTime Stamp ET [Card] Event Message------------------ -- --------------------------------------------------------05/14 00:34:43.491 E [6/0] Timeout waiting for Field Diag image response05/14 10:11:08.133 E [8/0] Failed to load Field Diag image for 4oc3atm-105/14 11:29:20.545 E [6/0] Minor Error Detected05/14 11:31:57.677 E [6/0] Minor Error Detected05/14 11:34:18.017 E [6/0] Minor Error Detected05/14 11:34:49.353 E [6/0] Minor Error Detected05/14 11:41:10.629 E [6/0] Minor Error Detected05/14 11:41:55.793 E [6/0] Minor Error DetectedIn the following example, a listing of info-type events is provided:
Router# show diagnostic events event-type infoDiagnostic events (storage for 500 events, 135 events recorded)Event Type (ET): I - Info, W - Warning, E - ErrorTime Stamp ET [Card] Event Message------------------ -- --------------------------------------------------------05/14 00:34:33.739 I [6/0] Loading Field Diag image in 1oc12pos-105/14 00:35:28.311 I [6/0] Field Diag image is loaded and running05/14 10:10:45.665 I [8/0] Loading Field Diag image in 4oc3atm-105/14 10:23:24.797 I [6/0] MPC860 Register Test Passed05/14 10:23:24.909 I [6/0] MPC860 Register2 Test Passed05/14 10:23:25.373 I [6/0] MPC860 Timer Test Passed05/14 10:23:59.065 I [6/0] march_dram_1 Passed05/14 10:23:59.201 I [6/0] Sky4302RegTest_1 Passed...(Additional display text omitted from this example)In the following example, a listing of warning-type events is provided:
Router# show diagnostic events event-type warningDiagnostic events (storage for 500 events, 135 events recorded)Event Type (ET): I - Info, W - Warning, E - ErrorTime Stamp ET [Card] Event Message------------------ -- --------------------------------------------------------No diagnostic log entry matches specified search criteriaRouter#show diagnostic events slot 6Diagnostic events (storage for 500 events, 135 events recorded)Event Type (ET): I - Info, W - Warning, E - ErrorTime Stamp ET [Card] Event Message------------------ -- --------------------------------------------------------05/14 00:34:33.739 I [6/0] Loading Field Diag image in 1oc12pos-105/14 00:34:43.491 E [6/0] Timeout waiting for Field Diag image response05/14 00:35:28.311 I [6/0] Field Diag image is loaded and running05/14 10:23:24.797 I [6/0] MPC860 Register Test Passed05/14 10:23:24.909 I [6/0] MPC860 Register2 Test Passed05/14 10:23:25.373 I [6/0] MPC860 Timer Test Passed05/14 10:23:59.065 I [6/0] march_dram_1 Passed...(Additional display test omitted from this example)
Related Commands
show diagnostic ondemand settings
To display the diagnostic on-demand settings, such as the run iteration and the action-on-failure settings, enter the show diagnostic ondemand settings command.
show diagnostic ondemand settings
Syntax Description
No keywords or variables.
Defaults
No default behavior or values.
Command Modes
EXEC and priviliged EXEC modes
Command History
Usage Guidelines
It is important to note that the show diag and show diagnostic commands produce completely different outputs. Therefore, the show diagnostic output cannot be gathered using show diag because the autocomplete function will generate the show diag, not the show diagnostic, output. If you want to abbreviate the show diagnostic command, the shortest possible abbreviation is show diagn.
To change an on-demand setting, use the diagnostic ondemand command.
When viewing the output from this command, it is important to note that diagnostic on-demand settings are not saved to a configuration file. Therefore, if the diagnostic on-demand settings do not match a previous configuration, a likely reason is that the router has been reloaded since the settings were last configured. The desired settings can be set again using the diagnostic ondemand command.
Examples
In the following example, the diagnostic on-demand iteration and action-on-failure settings are changed using diagnostic ondemand iterations and diagnostic ondemand action-on-failure. The changed settings are then confirmed using show diagnostic ondemand settings.
Router# diagnostic ondemand iterations 2Router# diagnostic ondemand action-on-failure stopRouter# show diagnostic ondemand settingsOndemand Run Iterations = 2Ondemand Action-on-Failure = STOP
Related Commands
show diagnostic result
To show the results of the Field Diagnostic tests, use the show diagnostic result command.
show diagnostic result [{slot slot-number | subslot slot-number/subslot-number}] [detail]
Syntax Description
Defaults
No default behavior or values.
Command Modes
EXEC and priviliged EXEC mode
Command History
Usage Guidelines
The show diagnostic result command only generates output if the Field Diagnostic image is still loaded onto the line card. If the Field Diagnostic image has been unloaded from the line card, the show diagnostic result command will not display any test result output. If you want to unload the Field Diagnostic image from the line card and retain the diagnostic test results, enter show diagnostic result and copy and paste the output into a separate file before entering diagnostic unload to unload the Field Diagnostic image off the line card.
If a Field Diagnostic image has not been loaded onto a line card and show diagnostic result is entered, the show diagnostic result command output will indicate that a Field Diagnostic image has not been downloaded and a note will be generated that states whether the line card is supported by a Field Diagnostic image.
It is important to note that the show diag and show diagnostic commands produce completely different outputs. Therefore, the show diagnostic output cannot be gathered using show diag because the autocomplete function will generate the show diag, not the show diagnostic, output. If you want to abbreviate the show diagnostic command, the shortest possible abbreviation is show diagn.
Examples
In the following example, a diagnostic test has already been run on the line card in slot 6 and the results are now being viewed using the show diagnostic result command.
Router# show diagnostic result slot 6Slot 6: 1oc12pos-1, 1 portOverall diagnostic result: PASSTest results: (. = Pass, F = Fail, U = Untested)1) MPC860 Register Test ----------------------------> .2) MPC860 Register2 Test ---------------------------> .3) MPC860 Timer Test -------------------------------> .4) OC12 POS MPC860 Port IO Test --------------------> .5) march_dram_1 ------------------------------------> .6) bus_float_dram_1 --------------------------------> .7) data_pins_dram_1 --------------------------------> .8) Sky4302ResetTest_1 ------------------------------> .9) Sky4302RegTest_1 --------------------------------> .10) Sky4302AISTest_1 --------------------------------> .11) Sky4302InterruptTest_1 --------------------------> .12) IbFpgaResetTest_fib -----------------------------> .13) FIBRegTest_fib ----------------------------------> .14) march_packet_mem_fib ----------------------------> .15) OC12POSIbFpgaInterruptTest_fib ------------------> .16) OC12POSIbFpgaParityTest_fib ---------------------> .17) IbFpgaResetTest_tib -----------------------------> .18) TIBRegTest_tib ----------------------------------> .19) march_packet_mem_tib ----------------------------> .20) OC12POSIbFpgaInterruptTest_tib ------------------> .21) OC12POSIbFpgaParityTest_tib ---------------------> .22) diag_plx_reset_0 --------------------------------> .23) diag_plx_rw_0 -----------------------------------> .24) diag_plx_int_0 ----------------------------------> .25) diag_barium_reset_1 -----------------------------> .26) diag_barium_rw_1 --------------------------------> .27) OC12POSBariumInterruptTest_1 --------------------> .28) OC12POSInternalLoopbackTest_1 -------------------> .29) OC12POSTerminalLoopbackTest_1 -------------------> .30) OC12POSSystembusLoopbackTest_1 ------------------> .31) OC12POSBariumBpLoopbackTest_1 -------------------> .
The following output shows detailed information for each Field Diagnostic test:
Router# show diagnostic result slot 6 detailSlot 6: 4oc3atm-1, 4 portsOverall diagnostic result: PASSTest results: (. = Pass, F = Fail, U = Untested)___________________________________________________________________________1) MPC8260 Register Test ---------------------------> .Error code ----------------------------------> 0 (DIAG_SUCCESS)Total run count -----------------------------> 1Last test execution time --------------------> Jan 30 2003 16:33:04First test failure time ---------------------> n/aLast test failure time ----------------------> n/aLast test pass time -------------------------> Jan 30 2003 16:33:04Total failure count -------------------------> 0Consecutive failure count -------------------> 0___________________________________________________________________________2) MPC8260 Timer Test ------------------------------> .Error code ----------------------------------> 0 (DIAG_SUCCESS)Total run count -----------------------------> 1Last test execution time --------------------> Jan 30 2003 16:33:05First test failure time ---------------------> n/aLast test failure time ----------------------> n/aLast test pass time -------------------------> Jan 30 2003 16:33:05Total failure count -------------------------> 0Consecutive failure count -------------------> 0...(Additional display text omitted from this example)
In the following example, the Field Diagnostic image is not loaded onto a line card and therefore produces a different output:
Router# show diagnostic result slot 2Diagnostic[Slot 2]: Diagnostic is not available.NOTE: The Field Diagnostic test suite is supported for this line card.To run Field Diagnostic tests, download the Field Diagnostic image fromcisco.com to a TFTP server or a flash card and enter the "diagnosticload" command.Related Commands
show diagnostic status
To display status information, such as the line card slot and name, Field Diagnostic image status, and overall results from previous diagnostic tests, enter the show diagnostic status command.
show diagnostic status [slot slot-number | subslot slot-number/subslot-number] [detail]
Syntax Description
Defaults
No default behavior or values.
Command Modes
EXEC and priviliged EXEC mode
Command History
Usage Guidelines
The show diagnostic status output reveals if a line card supports Field Diagnostic testing and if the line card has already downloaded a Field Diagnostic image. Therefore, the show diagnostic status command is useful as a reference before loading the Field Diagnostic image onto the line card.
It is important to note that the show diag and show diagnostic commands produce completely different outputs. Therefore, the show diagnostic output cannot be gathered using show diag because the autocomplete function will generate the show diag, not the show diagnostic, output. If you want to abbreviate the show diagnostic command, the shortest possible abbreviation is show diagn.
Examples
In the following example, the show diagnostic status command is used to view status information of the line card.
Router# show diagnostic status==== ======================== ======= ========== =========== ==============FDiag Loaded Overall CurrentSlot Card Description Support Image Type Diag Result Card State---- ------------------------ ------- ---------- ----------- --------------A Secondary PRE1-RP NO IOS N/A OFFLINEB Primary PRE1-RP NO IOS N/A ONLINE2 6cht3-1 YES LCDOS N/A ONLINE3/1 1gigethernet-hh-1 YES Field Diag PASS DIAG READY6 4oc3atm-1 YES LCDOS N/A ONLINE==== ======================== ======= ========== =========== ==============
In the following example, the show diagnostic status command detailed results are shown.
Router# show diagnostic status slot 2 detailDetail testing progress for card in slot 2:Current card state:RUNNING DIAGTestID Test Name [Selected To Run (Y/N)] Status==== ============================================== =======1) MPC8260 Register Test .................... [Y] Passed2) MPC8260 Timer Test ....................... [Y] Passed3) 6P OC3 POS MPC8260 Port I/O Test ......... [Y] Passed4) march_dram_64 ............................ [Y] Running5) bus_float_dram_64 ........................ [Y] Not Run6) data_pins_dram_64 ........................ [Y] Not Run7) SDRAM ECC Test ........................... [Y] Not Run8) SRAM Test ................................ [Y] Not Run9) CPLD Register Test ....................... [Y] Not Run10) BariumRegTest ............................ [Y] Not Run11) BariumIntTest ............................ [Y] Not Run12) FIBRegTest_pm ............................ [Y] Not Run13) FIBIntTest_pm ............................ [Y] Not Run14) FIBSdramMemTest_pm ....................... [Y] Not Run15) FIBChanMemTest_pm ........................ [Y] Not Run16) FIBStatMemTest_pm ........................ [Y] Not Run17) FIBDescMemTest_pm ........................ [Y] Not Run18) TIBRegTest_pm ............................ [Y] Not Run19) TIBIntTest_pm ............................ [Y] Not Run20) TIBSdramMemTest_pm ....................... [Y] Not Run21) TIBChanMemTest_pm ........................ [Y] Not Run22) TIBStatMemTest_pm ........................ [Y] Not Run23) TIBCtrlMemTest_pm ........................ [Y] Not Run24) TIBSdramParityTest_pm .................... [Y] Not Run25) TIBCtrlParityTest_pm ..................... [Y] Not Run26) PM5351RegTest_1 .......................... [Y] Not Run27) PM5351IntTest_1 .......................... [Y] Not Run28) PM5351RegTest_2 .......................... [Y] Not Run29) PM5351IntTest_2 .......................... [Y] Not Run30) PMBariumLpbkTest ......................... [Y] Not Run31) BariumCRCTest ............................ [Y] Not Run32) PMParallelLpbkTest ....................... [Y] Not Run33) PMSerialLpbkTest ......................... [Y] Not Run34) PMExternalLpbkTest ....................... [N] -------==== ============================================== =======
Related Commands
Posted: Fri Feb 2 07:05:10 PST 2007
All contents are Copyright © 1992--2007 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.
