Table Of Contents

Diagnostics Commands on Cisco IOS XR Software

diagnostic bootup level

diagnostic load

diagnostic monitor

diagnostic monitor interval

diagnostic monitor syslog

diagnostic monitor threshold

diagnostic ondemand action-on-failure

diagnostic ondemand iterations

diagnostic schedule

diagnostic start

diagnostic stop

diagnostic unload

ping (administration EXEC)

show diag

show diagnostic bootup level

show diagnostic content

show diagnostic ondemand settings

show diagnostic result

show diagnostic schedule

show diagnostic status

show diags

show hw-module subslot brief

Diagnostics Commands on Cisco IOS XR Software

---

This module describes the commands used to manage diagnostics on a router running Cisco IOS XR software.

diagnostic bootup level

To configure the diagnostic for booting a card, use the diagnostic bootup level command in administration configuration mode. To remove the specified command from the configuration file and restore the system to its default condition, use the no form of this command.

diagnostic bootup level {bypass | complete | minimal} location node-id

no diagnostic bootup level {bypass | complete | minimal} location node-id

Syntax Description

bypass	Specifies bypassing diagnostics at bootup.
complete	Specifies running full diagnostics at bootup.
minimal	Specifies running minimal diagnostics at bootup.
location node-id	Specifies a card. The node-id argument is entered in the rack/slot/module notation.

Defaults

The default bootup diagnostics level is minimal.

Command Modes

Administration configuration

Command History

Release	Modification
Release 3.4.0	This command was introduced on the Cisco CRS-1.
Release 3.5.0	No modification.

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.

---

Note There are no bootup diagnostic tests available in Release 3.5. Both the minimal and complete bootup diagnostic test levels contain no tests.

---

Use the diagnostic bootup level command to specify the level of diagnostics to be run when a card is booted.

The new level takes effect at the next reload or the next time that an online insertion and removal is performed.

You can set the bootup diagnostics level as minimal or complete, or you can bypass the bootup diagnostics entirely. Use the complete keyword to run a complete set of bootup diagnostic tests; use the minimal keyword to run the minimal set of bootup diagnostic tests. Use the bypass keyword to bypass all diagnostic tests.

---

Note To specify a physical layer interface module (PLIM) node using the node-id argument, use the following notation: rack/PLslot-number/SP. For example, 0/PL1/SP. PLIM diagnostic tests are supported on the Cisco CRS-1 router.

---

Task ID

Task ID	Operations
diag	read, write

Examples

The following example shows how to configure minimal bootup diagnostics for 0/1/cpu0:

RP/0/RP0/CPU0:router(admin-config)# diagnostic bootup level minimal location 0/1/cpu0 

Related Commands

Command	Description
show diagnostic bootup level	Displays the current bootup level configured for the specified location.
show diagnostic content	Displays test information including test ID, test attributes, and supported coverage test levels for each test and for all components.

diagnostic load

To load an offline diagnostic image for integrated field diagnostics, use the diagnostic load command in administration EXEC mode.

diagnostic load location node-id [autostart {basic | all}]

Syntax Description

location node-id	Loads an offline diagnostic image for a specified location. The node-id argument is entered in the rack/slot/module notation. All modules in the specified slot are loaded with the offline diagnostic image.
autostart {basic | all}	(Optional) Starts running the diagnostic tests after the image has loaded. The following options are available: •basic—Runs basic tests •all—Runs all tests.

Defaults

No default behavior or values

Command Modes

Administration EXEC

Command History

Release	Modification
Release 3.3.0	This command was introduced on the Cisco CRS-1.
Release 3.4.0	No modification.
Release 3.5.0	No modification.

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.

Use the diagnostic load command to load an offline diagnostic image used for integrated field diagnostics. Loading a diagnostic image places the specified card out of service.

The time it takes to load a diagnostic image varies depending on the card. Use the show platform command to determine if the image has been loaded and if the card has been placed out of service.

---

Note The distributed route processor (DRP) does not support the automatic running of tests when the image is loaded for CPU0 and CPU1. After the diagnostic image is loaded, use the diagnostic start location node-id test {id | all | basic | non-disruptive} command to execute the tests.

---

For more information about running Cisco IOS XR diagnostics, refer to Cisco IOS XR Diagnostics.

Task ID

Task ID	Operations
diag	execute

Examples

The following example shows how to load an offline diagnostic image:

RP/0/RP0/CPU0:router# admin

RP/0/RP0/CPU0:router(admin)# diagnostic load location 0/0/CPU0 autostart basic

diagnostic load will bring requested slot out of service. [confirm(y/n)] y

User has confirmed diagnostic load request

Preparing UUT for Diagnostics software.

Downloading IDS diagnostics image /pkg/ucode/hfr-diag-l3sp-fdiags

Downloading IDS diagnostics image /pkg/ucode/hfr-diag-l3-fdiags

Please wait for UUT image downloading ...

diagnostic load in progress.

RP/0/RP0/CPU0:router(admin)#

Related Commands

Command	Description
diagnostic unload	Unloads a diagnostic test.
show platform	Displays information and status of each node in the system.

diagnostic monitor

To configure the health-monitoring diagnostic testing for a specified location, use the diagnostic monitor command in administration configuration mode. To remove the specified command from the configuration file and restore the system to its default condition, use the no form of this command.

diagnostic monitor location node-id test {id | test-name} [disable]

no diagnostic monitor location node-id test {id | test-name} [disable]

Syntax Description

node-id	Location to enable diagnostic monitoring. The node-id argument is entered in the rack/slot/module notation.
test {id | test-name}	Specifies diagnostic test selection. The following test selections are available: •id—Test ID, as shown in the show diagnostic content command. •test-name—Name of the test.
disable	Disables diagnostic monitoring for a specified location.

Defaults

To view the default value for each test, use the show diagnostic content command when the diagnostic image is first installed. The default may be different for each test.

Command Modes

Administration configuration

Command History

Release	Modification
Release 3.4.0	This command was introduced on the Cisco CRS-1.
Release 3.5.0	No modification.

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.

Use the diagnostic monitor command to enable or disable health-monitoring diagnostic testing for a specified test at the specified location.

Use the disable keyword to disable a health-monitoring diagnostic test that is enabled by default. For example, if test 1 is enabled by default, the disable keyword disables the diagnostic test. If the no form of the command is used, the test is set to the default condition, which is enabled.

---

Note To specify a physical layer interface module (PLIM) node using the node-id argument, use the following notation: rack/PLslot-number/SP. For example, 0/PL1/SP. PLIM diagnostic tests are supported on the Cisco CRS-1 router.

---

Task ID

Task ID	Operations
diag	read, write

Examples

The following example shows how to enable health-monitoring diagnostic testing for 0/1/cpu0:

RP/0/RP0/CPU0:router(admin-config)# diagnostic monitor location 0/1/cpu0 test 1 

Related Commands

Command	Description
show diagnostic content	Displays test information including test ID, test attributes, and supported coverage test levels for each test and for all components.

diagnostic monitor interval

To configure the health-monitoring diagnostic testing for a specified interval for a specified location, use the diagnostic monitor interval command in administration configuration mode. To remove the specified command from the configuration file and restore the system to its default condition, use the no form of this command.

diagnostic monitor interval location node-id test {id | test-name} number-of-days hour:minutes:seconds.milliseconds

no diagnostic monitor interval location node-id test {id | test-name} number-of-days hour:minutes:seconds.milliseconds

Syntax Description

location node-id	Specifies a location. The node-id argument is entered in the rack/slot/module notation.
test {id | test-name}	Specifies diagnostic test selection. The following test selections are available: •id—Test ID. •test-name—Test name, as shown in the show diagnostic content command.
number-of-days hour:minutes:seconds. milliseconds	Interval between each test run. The number-of-days argument specifies the number of days between testing. The hour:minutes:seconds.milliseconds argument specifies the interval, where hour is a number in the range from 0 through 23, minutes is a number in the range from 0 through 59, seconds is a number in the range from 0 through 59, and milliseconds is a number in the range from 0 through 999.

Defaults

To view the default value for each test, use the show diagnostic content command when the diagnostic image is first installed. The default may be different for each test.

Command Modes

Administration configuration

Command History

Release	Modification
Release 3.4.0	This command was introduced on the Cisco CRS-1.
Release 3.5.0	No modification.

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.

Use the diagnostic monitor interval command to set the health-monitoring interval of a specified test at the specified location. The no version of the command resets the interval to the default setting. The diagnostic monitor command is used to enable health-monitoring.

---

Note To specify a physical layer interface module (PLIM) node using the node-id argument, use the following notation: rack/PLslot-number/SP. For example, 0/PL1/SP. PLIM diagnostic tests are supported on the Cisco CRS-1 router.

---

Task ID

Task ID	Operations
diag	read, write

Examples

The following example shows how to set the health-monitoring diagnostic testing at an interval of 1 hour, 2 minutes, 3 seconds, and 4 milliseconds for 0/1/cpu0:

RP/0/RP0/CPU0:router(admin-config)# diagnostic monitor interval location 0/1/cpu0 test 1 0 
1:2:3.4 

Related Commands

Command	Description
diagnostic monitor	Enables or disables health-monitoring diagnostic testing for a specified test at a specified location.
show diagnostic content	Displays test information including test ID, test attributes, and supported coverage test levels for each test and for all components.

diagnostic monitor syslog

To enable the generation of a syslog message when any health monitoring test fails, use the diagnostic monitor syslog command in administration configuration mode. To remove the specified command from the configuration file and restore the system to its default condition, use the no form of this command.

diagnostic monitor syslog

no diagnostic monitor syslog

Syntax Description

This command has no arguments or keywords.

Defaults

Syslog is disabled.

Command Modes

Administration configuration

Command History

Release	Modification
Release 3.4.0	This command was introduced on the Cisco CRS-1.
Release 3.5.0	No modification.

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.

Use the diagnostic monitor syslog command to enable the generation of a syslog message when a health-monitoring test fails.

Task ID

Task ID	Operations
diag	read, write

Examples

The following example shows how to enable the generation of syslog messages:

RP/0/RP0/CPU0:router(admin-config)# diagnostic monitor syslog 

Related Commands

Command	Description
show diagnostic content	Displays test information including test ID, test attributes, and supported coverage test levels for each test and for all components.

diagnostic monitor threshold

To configure the health-monitoring diagnostic testing failure threshold, use the diagnostic monitor threshold command in administration configuration mode. To remove the specified command from the configuration file and restore the system to its default condition, use the no form of this command.

diagnostic monitor threshold location node-id test {id | test-name} failure count failures

no diagnostic monitor threshold location node-id test {id | test-name} failure count failures

Syntax Description

location node-id	Specifies a location. The node-id argument is entered in the rack/slot/module notation.
test {id | test-name}	Specifies diagnostic test selection. The following test selections are available: •id—Test ID. •test-name—Test name, as shown in the show diagnostic content command.
failure count failures	Specifies the number of allowable test failures. Range is 1 to 99.

Defaults

To view the default value for each test, use the show diagnostic content command when the diagnostic image is first installed. The default can be different for each test.

Command Modes

Administration configuration

Command History

Release	Modification
Release 3.4.0	This command was introduced on the Cisco CRS-1.
Release 3.5.0	No modification.

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.

Use the diagnostic monitor threshold command to specify health-monitoring diagnostic testing failure threshold.

---

Note To specify a physical layer interface module (PLIM) node using the node-id argument, use the following notation: rack/PLslot-number/SP. For example, 0/PL1/SP. PLIM diagnostic tests are supported on the Cisco CRS-1 router.

---

Task ID

Task ID	Operations
diag	read, write

Examples

The following example shows how to set the failure threshold to 35 test failures for all tests for 0/1/cpu0:

RP/0/RP0/CPU0:router(admin-config)# diagnostic monitor threshold location 0/1/cpu0 test 
all failure count 35 

Related Commands

Command	Description
show diagnostic content	Displays test information including test ID, test attributes, and supported coverage test levels for each test and for all components.

diagnostic ondemand action-on-failure

To set when to stop test execution for a diagnostic start command, use the diagnostic ondemand action-on-failure command in administration EXEC mode. This command is used in conjunction with the diagnostic ondemand iteration command.

diagnostic ondemand action-on-failure {continue failure-count | stop}

Syntax Description

continue failure-count	Specifies that test execution continue until the number of failures reaches the specified failure-count. Range is 0 to 65534. A failure-count of 0 indicates to not stop execution until all iterations are complete, no matter how many failures are encountered.
stop	Stops execution immediately when the first test failure occurs.

Defaults

failure-count: 0

Command Modes

Administration EXEC

Command History

Release	Modification
Release 3.5.0	This command was introduced on the Cisco CRS-1.

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.

Use the diagnostic ondemand action-on-failure command to specify whether or when to stop test execution if a test fails. This command is used in conjunction with the diagnostic ondemand iterations command.

Task ID

Task ID	Operations
diag	read, write

Examples

The following example shows how to set the test failure action to stop:

RP/0/RP0/CPU0:router(admin)# diagnostic ondemand action-on-failure stop 

Related Commands

Command	Description
diagnostic ondemand iterations	Specifies the number of times to run the specified tests when the diagnostic start command is entered.
diagnostic start	Runs specified diagnostic tests for the number of iterations set by the diagnostic ondemand iteration command.

diagnostic ondemand iterations

To set the number of iterations to repeat execution of the tests specified by the diagnostic start command, use the diagnostic ondemand iterations command in administration EXEC mode.

diagnostic ondemand iterations count

Syntax Description

count

Number of times to repeat the specified on-demand tests. Range is 1 to 999.

Defaults

count: 1

Command Modes

Administration EXEC

Command History

Release	Modification
Release 3.5.0	This command was introduced on the Cisco CRS-1.

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.

Use the diagnostic ondemand iterations command to specify the number of times the specified on-demand tests run. The on-demand tests are specified using the diagnostic start command.

Task ID

Task ID	Operations
diag	read, write

Examples

The following example shows how to set the number of iterations to 12:

RP/0/RP0/CPU0:router(admin)# diagnostic ondemand iterations 12 

Related Commands

Command	Description
diagnostic ondemand action-on-failure	Specifies whether or when to stop execution if there is failure.
diagnostic start	Runs specified diagnostic tests for the number of iterations set by the diagnostic ondemand iteration command.

diagnostic schedule

To configure the diagnostic schedule, use the diagnostic schedule command in administration configuration mode. To disable the diagnostic schedule, use the no form of this command.

diagnostic schedule location node-id test {id | all | basic | non-disruptive} {daily | on month day year | weekly day-of-week} hour:minute

no diagnostic schedule location node-id test {id | all} {daily | on month day year | weekly day-of-week} hour:minute

Syntax Description

location node-id	Schedules a diagnostic test for a specified location. The node-id argument is entered in the rack/slot/module notation.
test	Specifies a specific diagnostic test, or all diagnostic tests.
id	Test ID or list of test IDs, as shown in the show diagnostic content command. Multiple tests can be listed if separated by semicolons (;) as follows: •x;y-z (for example: 1; 3-4 or 1;3;4)
all	Specifies all tests.
basic	Specifies the basic on-demand test suite [Attribute = B].
non-disruptive	Specifies the nondisruptive test suite [Attribute = N].
daily	Specifies a daily schedule.
on month day year	Schedules an exact date.
weekly day-of-week	Specifies a weekly schedule with a set day of the week. Enter the name of a day of the week or a number that specifies a day of the week in the range from 0 through 6.
hour:minute	Scheduled start time, where hour is a number in the range from 0 through 23, and minute is a number in the range from 0 through 59.

Defaults

No default behavior or values

Command Modes

Administration configuration

Command History

Release	Modification
Release 3.3.0	This command was introduced on the Cisco CRS-1.
Release 3.4.0	No modification.
Release 3.5.0	No modification.

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.

Use the diagnostic schedule command to schedule diagnostic tests for a specific location.

---

Note To specify a physical layer interface module (PLIM) node using the node-id argument, use the following notation: rack/PLslot-number/SP. For example, 0/PL1/SP. PLIM diagnostic tests are supported on the Cisco CRS-1 router.

---

For more information about running Cisco IOS XR diagnostics, refer to Cisco IOS XR Diagnostics.

Task ID

Task ID	Operations
diag	read, write

Examples

The following example shows how to schedule a diagnostic test:

RP/0/RP0/CPU0:router# admin

RP/0/RP0/CPU0:router(admin)# configure

RP/0/RP0/CPU0:router(admin-config)# diagnostic schedule location 0/0/CPU0 test all daily 
12:30

Related Commands

Command	Description
show diagnostic schedule	Displays the diagnostic schedule for a specified location.

diagnostic start

To run a specified diagnostic test, use the diagnostic start command in administration EXEC mode.

diagnostic start location node-id test {id | all | basic | non-disruptive}

Syntax Description

location node-id	Runs diagnostic testing for a specified location. The node-id argument is entered in the rack/slot/module notation.
test	Specifies a specific diagnostic test, or all diagnostic tests.
id	Test ID or list of test IDs, as shown in the show diagnostic content command. Multiple tests can be listed if separated by semicolons (;) as follows: •x;y-z (for example: 1; 3-4 or 1;3;4)
all	Specifies all tests.
basic	Specifies the basic on-demand test suite [Attribute = B].
non-disruptive	Specifies the nondisruptive test suite [Attribute = N].

Defaults

No default behavior or values

Command Modes

Administration EXEC

Command History

Release	Modification
Release 3.3.0	This command was introduced on the Cisco CRS-1.
Release 3.4.0	No modification.
Release 3.5.0	No modification.

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.

Use the diagnostic start command to run a diagnostic test on a specified card.

---

Note To specify a physical layer interface module (PLIM) node using the node-id argument, use the following notation: rack/PLslot-number/SP. For example, 0/PL1/SP. PLIM diagnostic tests are supported on the Cisco CRS-1 router.

---

For more information about running Cisco IOS XR diagnostics, refer to Cisco IOS XR Diagnostics.

Task ID

Task ID	Operations
diag	execute

Examples

The following example shows how to run a suite of basic diagnostic tests for a specified location:

RP/0/RP0/CPU0:router# admin

RP/0/RP0/CPU0:router(admin)# diagnostic start location 0/0/CPU0 test basic

Related Commands

Command	Description
diagnostic stop	Stops a diagnostic test.

diagnostic stop

To stop the diagnostic testing in progress on a node, use the diagnostic stop command in administration EXEC mode.

diagnostic stop location node-id

Syntax Description

location node-id

Stops diagnostic testing for a specified location. The node-id argument is entered in the rack/slot/module notation.

Defaults

No default behavior or values

Command Modes

Administration EXEC

Command History

Release	Modification
Release 3.3.0	This command was introduced on the Cisco CRS-1.
Release 3.4.0	No modification.
Release 3.5.0	No modification.

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.

Use the diagnostic stop command to stop a diagnostic test on a specified node. The command is used for scheduled tests, a test that is causing errors, or a test that does not finish.

---

Note To specify a physical layer interface module (PLIM) node using the node-id argument, use the following notation: rack/PLslot-number/SP. For example, 0/PL1/SP. PLIM diagnostic tests are supported on the Cisco CRS-1 router.

---

For more information about running Cisco IOS XR diagnostics, refer to Cisco IOS XR Diagnostics.

Task ID

Task ID	Operations
diag	execute

Examples

The following example shows how to stop the diagnostic test process:

RP/0/RP0/CPU0:router# admin

RP/0/RP0/CPU0:router(admin)# diagnostic stop location 0/0/CPU0

Related Commands

Command	Description
diagnostic start	Runs specified diagnostic tests for the number of iterations set by the diagnostic ondemand iteration command.

diagnostic unload

To unload an offline diagnostic image, use the diagnostic unload command in administration EXEC mode.

diagnostic unload location node-id

Syntax Description

location node-id

Unloads an offline diagnostic image for a specified location. The node-id argument is entered in the rack/slot/module notation. The diagnostic image is unloaded for all modules in the specified slot.

Defaults

No default behavior or values

Command Modes

Administration EXEC

Command History

Release	Modification
Release 3.3.0	This command was introduced on the Cisco CRS-1.
Release 3.4.0	No modification.
Release 3.5.0	No modification.

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.

Use the diagnostic unload command to unload an offline diagnostic image used for integrated field diagnostics. Unloading the image returns the specified card to service.

Use the show platform command to determine if the card has been placed back into service.

For more information about running Cisco IOS XR diagnostics, refer to Cisco IOS XR Diagnostics.

Task ID

Task ID	Operations
diag	execute

Examples

The following example shows how to unload a diagnostic image:

RP/0/RP0/CPU0:router# admin

RP/0/RP0/CPU0:router(admin)# diagnostic unload location 0/0/CPU0

Related Commands

Command	Description
diagnostic load	Loads a diagnostic test.
show platform	Displays information and status of each node in the system.

ping (administration EXEC)

To send internal echo messages from one node to another, use the ping command in administration EXEC mode.

ping {control-eth | fabric} location node-id [count pings | interval milliseconds | pattern random | retries number | size payload_size | timeout seconds]

Syntax Description

control-eth	Specifies a control ethernet ping test.
fabric	Specifies a fabric ping test.
count pings	(Optional) Number of pings to send each time the command is run. The test reports results and statistics after all pings have been sent and received (or timed out). Range is from 0 through 4294967295.
interval milliseconds	(Optional) Hold-off time between each ping in milliseconds. Range is from 0 through 4294967295. The total test time will be as follows: (count-1) * (RTT + interval) + RTT RTT = Round Trip Time for the ping.
pattern random	(Optional) Specifies a data pattern for the ping packet payload.
retries number	(Optional) Maximum number of times a failed ping transmission is sent before the packet transmission is considered a failure. Range is from 0 through 4294967295. Note Packet transmission failure is usually an indication of a server software transient. In this case, Cisco recommends that you run the ping command again.
size payload_size	(Optional) Specifies the payload size for each ping packet size. Range is from 0 through 4294967295 bytes. The maximum payload size allowed may be limited, depending on the transport type that is used (fabric or control-ethernet).
timeout seconds	(Optional) Specifies the maximum time to wait for response to a ping. Range is from 0 through 4294967295 seconds. If a ping does not receive a response before the configured timeout expires, the ping statistics reflect it as a discrepancy between the "Sent:" and "Rec'd:" packet count, and the test is considered failed. Because of this, Cisco recommends that you do not set the timeout to 0.

Defaults

No default behavior or values

Command Modes

Administration EXEC

Command History

Release	Modification
Release 3.3.0	This command was introduced on the Cisco CRS-1.
Release 3.4.0	No modification.
Release 3.5.0	No modification.

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.

When you enter the ping command, a ping is sent to the node at the specified location. The received response is compared byte-by-byte to the sent packet. If a ping response is not received before the specified time-out, or if the ping response does not match the transmitted ping, the ping is considered failed.

A node that is unreachable or intermittently working impacts the total run time for the test as follows:

(received_packet_count * RTT + lost_packet_count * timeout + (count-1) * interval)

Task ID

Task ID	Operations
diag	execute

Examples

The following example shows sample output from a control-ethernet ping to an SP node in slot 0/0:

RP/0/RP0/CPU0:router# admin

RP/0/RP0/CPU0:router(admin)# ping control-eth location 0/0/SP count 5

Src node:        529  :  0/RP0/CPU0

Dest node:         0  :  0/0/SP

Local node:      529  :  0/RP0/CPU0

Packet cnt:        5  Packet size:   128  Payload ptn type: default (0)

Hold-off (ms):   300  Time-out(s):     2  Max retries: 5

Destination node has MAC addr 5246.4800.0000

Running CE node ping. 

Please wait...

Src: 529:, Dest: 0, Sent: 5, Rec'd: 5, Mismatched: 0

Min/Avg/Max RTT: 0/200/1000

CE node ping succeeded for node: 0

The following example shows a fabric ping from the active RP to the active RP. In this example, the ping contains 72 packets of 1 kilobyte each. This command performs a good coverage test of the entire switch fabric:

RP/0/RP0/CPU0:router# admin

RP/0/RP0/CPU0:router(admin)# ping fabric location 0/RP0/CPU0 count 72 size 1024

Src node:        529  :  0/RP0/CPU0

Dest node:       529  :  0/RP0/CPU0

Local node:      529  :  0/RP0/CPU0

Packet cnt:       72  Packet size:  1024  Payload ptn type: default (0)

Hold-off (ms):   300  Time-out(s):     2  Max retries: 5

Running Fabric node ping. 

Please wait...

Src: 529:, Dest: 529, Sent: 72, Rec'd: 72, Mismatched: 0

Min/Avg/Max RTT: 3000/3013/4000

Fabric node ping succeeded for node: 529

The following example shows a ping to a control Ethernet node that has a problem or does not exist:

RP/0/RP0/CPU0:router# admin

RP/0/RP0/CPU0:router(admin)# ping control-eth location 0/1/CPU0 count 3 

Src node:        529  :  0/RP0/CPU0

Dest node:        17  :  0/1/CPU0

Local node:      529  :  0/RP0/CPU0

Packet cnt:        3  Packet size:   128  Payload ptn type: default (0)

Hold-off (ms):   300  Time-out(s):     2  Max retries: 5

Destination node has MAC addr 5246.4800.0011

Running CE node ping. 

Please wait...

Src: 529:, Dest: 17, Sent: 3, Rec'd: 0, Mismatched: 0

Requested ping failed for node: 17

show diag

To display details about the hardware and software on each node in a router, use the show diag command in the appropriate mode.

In EXEC mode.

show diag [node-id] [details | eeprom-info | power-regs | summary]

In administration EXEC mode:

show diag [node-id] [[chassis | fans | power-supply] [eeprom-info] | details | summary]

Syntax Description

node-id	(Optional) Identifies the node whose information you want to display. The node-id argument is expressed in the rack/slot/module notation. Follow the node-id argument with one of the following optional keywords to specify specific test results: •details •eeprom-info •power-regs •summary
details	(Optional) Displays detailed diagnostics information for the current node.
eeprom-info	(Optional) Displays field diagnostics results from the EEPROM.
power-regs	(Optional) Displays field diagnostics results from the power registers.
summary	(Optional) Displays summarized diagnostics results for all nodes in the system.
chassis-info	(Optional) Displays information about the chassis.
fans	(Optional) Displays information about the fans tray.
power-supply	(Optional) Displays information about the power supply.

Defaults

Diagnostics for all nodes installed in the router are displayed.

Command Modes

EXEC

Administration EXEC

Command History

Release	Modification
Release 2.0	This command was introduced on the Cisco CRS-1.
Release 3.0	No modification.
Release 3.2	The show diag command was modified to display the last diagnostic result for a card.
Release 3.3.0	The chassis and details keywords were removed from the show diag command.
Release 3.4.0	<