• Improved Troubleshooting. Field diagnostics verifies whether a line card problem is hardware-related or not. If the problem is software-related, the Field Diagnostic image allows customer to quickly rule out hardware related cause and focus on fixing the software issue causing the problem.

• Pre-installation Line Card Hardware Verification. Field diagnostics verifies whether a line card has hardware problems before installing the line card in a Cisco cBR Series router.

• Onsite Fault Detection. Field diagnostics helps to confirm if the problem is hardware-related and if it is necessary to replace the line card.

• Additional Uptime. Field diagnostics ensures that line cards are not mistakenly taken offline if the problem is not hardware-related, thereby increasing network uptime.

• Before running the OOD Field Diagnostic tests on the working (active) line card in an N + 1 redundancy setup, it is advisable to switch over to the protect (standby) line card before loading the Field Diagnostic image to the line card to avoid service interruption.

• After an OOD Field Diagnostic image is loaded to the line card, the line card goes offline. Therefore, schedule a downtime for the line card to be tested before performing field diagnostic tests.

• Before performing any field diagnostic test, unplug 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, which increments packet counters on the receiving interfaces.

• When accessing a router through Telnet while running an OOD Field Diagnostic test, testing progress messages do not appear on the screen.

• If supervisor switchover occurs during a field diagnostic test, the test stops immediately and the line card run-time image automatically replaces the Field Diagnostic image on the line card.

• This feature is supported on CBR-CCAP-LC-40G line card in Cisco IOS-XE release 3.18.0S and later releases.

• It is suggested to run OOD on one line card at a time to avoid service impact.

• To run OOD on multiple line cards, leave 5 to 10 minutes gap before loading the OOD image to the next line card.

To load the field diagnostic image and start field diagnostic test, complete the following procedure:

copy tftp:image-file {harddisk: | bootflash: | flash:} 
request platform hardware diagnostic load slot slot-id image-file autostart 

To verify whether the field diagnostic tests are running, use the show platform hardware diagnostic status slot slot-id command as shown in the example below:

Router# show platform hardware diagnostic status slot 0
Online Offline Diagnostic Status (P=Passed, F=Failed, U=Untested) 
State                 Overall Test Num        Test Done Num          Test Result            
---------------------------------------------------------------------------------
Running Auto Test     75                      70                     P:69 F:1 U:5  

Note	If the test result shows that the failed test number is not 0, please copy the full log and contact Cisco TAC team for support. You can use dir harddisk:ood/ command to list the log files.

To unload the Field Diagnostic image, use the request platform hardware diagnostic unload slot slot-id command as below:

request platform hardware diagnostic unload slot slot-id 

Then the line card will be reloaded to run-time image.

Note

To retain the results of a diagnostic test, copy and paste the show platform hardware diagnostic status slot command output into a separate file before unloading the Field Diagnostic image. The output of the show platform hardware diagnostic status slot command cannot be gathered after unloading the Field Diagnostic image from the line card.