The "TBC0719017300000" string is the rack number. This string should be present for every chassis. The number is burnt in by manufacturing.

Using ping and traceroute

For details on the ping and traceroute commands, see the "Basic Troubleshooting Commands" section inCisco IOS XR Getting Started Guide for the Cisco CRS-1 Router.

Using Debug Commands

For details on using debug commands, see Cisco IOS XR Using Debug Guide.

Using Diagnostic Commands

The Cisco IOS XR diagnostic tests verify control Ethernet and fabric data paths between nodes in a system using Cisco IOS XR software. If a diagnostic tests fails, it indicates a bad data path. The integrity of the covered data paths is verified when the diagnostic tests pass.

The system runs diagnostic tests automatically to verify control Ethernet and fabric data paths between nodes in the system. The integrity of the covered data paths is verified when the diagnostic tests pass. If a diagnostic tests fails, it indicates a bad data path and the system alerts you to the problem.

The diagnostic tests generally test data paths between multiple nodes, therefore you need to analyze error reports to narrow down the possible points of failure in a system. For example, if a diagnostic test fails on a fabric interface, the fabric cables in the path of failure would be a primary suspected cause of the failure.

All diagnostic tests run within the 1 second to 1 minute range.

This section contains the following additional topics related to diagnostics:

Online Diagnostics

You can start and stop diagnostic tests on specific nodes while the node is online and processing traffic. It is important to run test on both the active and standby RP; the standby RP is actually capable of running more fabric diagnostic tests than the active RP.

Examples:

The following example shows a set of diagnostic tests on the active RP (0/RP0/CPU0).

Transient Condition when Standby RP Becomes Active

If online diagnostics are performed within five minutes of the standby RP becoming active, some test cases will be skipped. Wait at least five minutes after the standby RP is ready before performing the online diagnostic test. If your system is set to perform diagnostic checks automatically, it might skip some tests during this five-minute period. Therefore, you should perform these tests manually after the standby RP has been active for at least five minutes.

To run a specified on-demand diagnostic test or series of tests, use the diagnostic start location command.

Examples:

Offline Diagnostics—FDIAG RUNNING State

You load the offline diagnostics with the command (admin)diagnostic load locationnode-id. The specified node remains in the "FDIAG RUNNING" state until you unload diagnostics with the command (admin)diagnostic unload locationnode-id.

Note In the "FDIAG RUNNING" state, the specified node is offline and cannot process traffic.

While a node is in "FDIAG RUNNING" state, tests are run in response to the optional autostart keyword of the diagnostic load locationnode-id command or the diagnostic start locationnode-id command. When an individual test completes, a message is printed and results are updated. The result can be read using the show diagnostic result locationnode-id command. When a test completes, a new diagnostic start locationnode-id command can be invoked since the card remains the "FDIAG RUNNING" state until it is explicitly unloaded using the diagnostic unload locationnode-id command.