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	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.

The show diag command displays detailed information on the hardware components for each node, and on the status of the software running on each node.

Task ID

Task ID	Operations
sysmgr	read

Examples

The following example shows partial sample output from the show diag details command on a Cisco CRS-1 router:

RP/0/RP1/CPU0:router# show diag details

NODE 0/0/SP : MSC(SP)

  MAIN:  board type 500060

         0-0-00 rev 00

         dev N/A

         S/N SAD072102RS

  PCA:   73-7648-04 rev 08

  PID:    rev 00

  VID:   V00

  CLEI:

  ECI:   0

  Board State : IOS-XR RUN

  PLD:   Motherboard: 0x0025, Processor: 0xda13, Power: N/A

  MONLIB: QNXFFS Monlib Version 3.0

  ROMMON: Version 1.19(20040603:013227)  [CRS-1 ROMMON]

  SPEED: OSC Speed:  100 Mhz, CPU Speed:  800 Mhz

         BUS Speed:  100 Mhz, MEM Speed:  100 Mhz

  MEM Size: 2048 Mbytes

  RMA:   Test Hist: ab, RMA#: 00-00-00, RMA Hist: 00

  DIAGNOSTICS RESULTS:

    ENTRY 1: 0

      TIMESTAMP: 00/00/0000 00:00:00

      VERSION: v0.0

      PARAM1: 0      PARAM2: n/a

      TESTNUM: 0

      RESULT: 0 (PASS)

      ERRCODE: 0

    ENTRY 2: 0

      TIMESTAMP: 00/00/0000 00:00:00

      VERSION: v0.0

      PARAM1: 0      PARAM2: n/a

      TESTNUM: 0

      RESULT: 0 (PASS)

      ERRCODE: 0

    ENTRY 3: 0

      TIMESTAMP: 00/00/0000 00:00:00

      VERSION: v0.0

      PARAM1: 0      PARAM2: n/a

      TESTNUM: 0

      RESULT: 0 (PASS)

      ERRCODE: 0

--More--

Table 1 describes the significant fields shown in the display.

Table 1 show diag Field Descriptions 

Field	Description
MAIN	Provides the following general information about the hardware: •Board type •Revision •Device identifier •S/N
PCA	Cisco PCA1 hardware and revision number.
PID	Displays the PID2 revision for the specified node.
VID	Displays the VID3 for the specified node.
CLEI	Displays the CLEI4 for the specified node.
ECI	Displays the ECI5 for the specified node.
Board State	Displays the current software on the board (in this case, Cisco IOS XR software) and whether or not the board is running.
PLD	Displays the information about the following PLD6 components on the current module: •Processor •Power •MONLIB
SPEED	Displays speed information for the various components of the specified node, in Mhz.
MEM Size	Displays the memory size of the specified node, in megabytes.
RMA	Displays RMA7 information for the specified node.
DIAGNOSTICS RESULTS	Provides the following information about the last diagnostics test that was run on the specified node: •ENTRY 1 •TIMESTAMP—Time stamp for the last diagnostic test that was run on the node. •VERSION •PARAM1 •PARAM2 •TESTNUM—Identifies the test that was run on the node. •RESULT—Displays whether the last diagnostic test passed or failed. •ERRCODE

1. printed circuit assembly

2. product identifier

3. version identifier

4. common language equipment identifier

5. equipment catalog item

6. programmable logic device

7. returned material adjustment

Related Commands

Command	Description
show platform	Displays information and status for each node in the system.
show version	Displays details on the hardware and software status of the system.

show diagnostic bootup level

To display the current diagnostic bootup level, use the show diagnostic bootup level command in administration EXEC mode.

show diagnostic bootup level location node-id

Syntax Description

location node-id

Specifies a card. 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.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 show diagnostic bootup level command to display the current diagnostic bootup level for 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.

---

Task ID

Task ID	Operations
diag	read

Examples

The following example shows how to display the current diagnostic bootup level for 0/1/cpu0:

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

Current bootup diagnostic level for LC 0/1/CPU0: minimal

Related Commands

Command	Description
diagnostic bootup level	Specifies the diagnostic bootup level.

show diagnostic content

To display test information including test ID, test attributes, and supported coverage test levels for each test and for all components, use the show diagnostic content command in administration EXEC mode.

show diagnostic content location node-id

Syntax Description

location node-id

Displays the diagnostic content 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	The command output has been modified.
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 show diagnostic content command to display diagnostic test information for a specific location. The test information includes the supported tests and attributes.

---

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

Examples

The following example shows how to display the test information for a specified location:

RP/0/RP0/CPU0:router# admin

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

LC 0/0/CPU0:

Diagnostics test suite attributes:

    M/C/* - Minimal bootup level test / Complete bootup level test / NA

      B/* - Basic ondemand test / NA

    P/V/* - Per port test / Per device test / NA

    D/N/* - Disruptive test / Non-disruptive test / NA

      S/* - Only applicable to standby unit / NA

      X/* - Not a health monitoring test / NA

      F/* - Fixed monitoring interval test / NA

      E/* - Always enabled monitoring test / NA

      A/I - Monitoring is active / Monitoring is inactive

                                                         Test Interval    Thre-

  ID   Test Name                          Attributes     (day hh:mm:ss.ms shold)

  ==== ================================== ============ ================= =====

    1) ControlEthernetPingTest ---------> *B*N****I       001 00:00:00.000 1

    2) SelfPingOverFabric --------------> *B*N****I       001 00:00:00.000 1

Table 69 describes the significant fields shown in the display.

Table 69 show diagnostic content Field Descriptions 

Field	Description
M/C/* - Minimal bootup level test / Complete bootup level test / NA	Minimal bootup test or complete bootup test.
B/* - Basic ondemand test / NA	Basic on-demand test.
P/V/* - Per port test / Per device test / NA	Test is per port or device.
D/N/* - Disruptive test / Non-disruptive test / NA	Test is disruptive or nondisruptive.
S/* - Only applicable to standby unit / NA	Test is available for standby node only.
X/* - Not a health monitoring test / NA	Test is not a health-monitoring test.
F/* - Fixed monitoring interval test / NA	Test is a fixed monitoring interval test.
E/* - Always enabled monitoring test / NA	Test is an always enabled monitoring test.
A/I - Monitoring is active / Monitoring is inactive	Test is active or inactive.
ID	ID of the test.
Test Name	Name of the test.
Attributes	Attributes for the test.
Test Interval	Interval of the test.
Threshold	Failure threshold of the text.

Related Commands

Command	Description
diagnostic bootup level	Specifies the diagnostic bootup level.
diagnostic load	Loads a diagnostic test.
diagnostic monitor interval	Specifies the diagnostic test interval.
diagnostic unload	Specifies the test failure threshold.
diagnostic schedule	Schedules a diagnostic test.
diagnostic start	Runs specified diagnostic tests for the number of iterations set by the diagnostic ondemand iteration command.

show diagnostic ondemand settings

To display the current on-demand settings, use the show diagnostic ondemand settings command in administration EXEC mode.

show diagnostic ondemand settings

Syntax Description

This command has no arguments or keywords.

Defaults

No default behavior or values

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.

Task ID

Task ID	Operations
diag	read

Examples

The following example shows how to display the on-demand settings:

RP/0/RP0/CPU0:router(admin)# show diagnostic ondemand settings 

Test iterations = 45

Action on test failure = continue until test failure limit reaches 25

show diagnostic result

To display diagnostic test results, use the show diagnostic result command in administration EXEC mode.

show diagnostic result location node-id [test {id | all}] [detail]

Syntax Description

location node-id	Displays the diagnostic test results for a specified location. The node-id argument is entered in the rack/slot/module notation.
test {id | all}	(Optional) Specifies diagnostic test selection. The following test selections are available: •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.
detail	(Optional) Specifies detailed results.

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	Current bootup diagnostic level display output was added.
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 show diagnostic result command to display diagnostic results 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

Examples

The following example shows how to display detailed diagnostic test results:

RP/0/RP0/CPU0:router(admin)# show diagnostic result location 0/3/CPU0 test 1 detail 

Test results: (. = Pass, F = Fail, U = Untested) 

___________________________________________________________________________ 

1 ) Control Ethernet Ping Test ------> . 

    Error code ------------------> 0 (DIAG_SUCCESS) 
    Total run count -------------> 1 
    Last test execution time ----> Thu Aug 11 18:13:38.918 2005 
    First test failure time -----> n/a 
    Last test failure time ------> n/a 
    Last test pass time ---------> Thu Aug 11 18:13:38.918 2005 
    Total failure count ---------> 0 
    Consecutive failure count ---> 0 
___________________________________________________________________________ 

Table 70 describes the significant fields shown in the display.

Table 70 show diagnostic result Field Descriptions 

Field	Description
Test results:	Test result options: •.—Pass •F—Fail •U—Untested
Error code	Code for the error. DIAG_SUCCESS is indicated if there were no code errors. DIAG_FAILURE is indicated for any failure. DIAG_SKIPPED is indicated if the test was stopped.
Total run count	Number of times the test has run.
Last test execution time	Last time the test was run.
First test failure time	First time the test failed.
Last test failure time	Last time the test failed.
Last test pass time	Last time the test passed.
Total failure count	Number of times the test has failed.
Consecutive failure count	Number of consecutive times the test has failed.

Related Commands

Command	Description
diagnostic load	Loads a diagnostic test.
diagnostic schedule	Schedules a diagnostic test.
diagnostic start	Runs specified diagnostic tests for the number of iterations set by the diagnostic ondemand iteration command.

show diagnostic schedule

To display the current scheduled diagnostic tasks, use the show diagnostic schedule command in administration EXEC mode.

show diagnostic schedule location node-id

Syntax Description

location node-id

Displays the diagnostic schedule 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 show diagnostic schedule command to display scheduled diagnostic tasks 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

Examples

The following example shows how to display scheduled diagnostic tasks:

RP/0/RP0/CPU0:router# admin

RP/0/RP0/CPU0:router(admin)# show diagnostic schedule location 0/3/CPU0

Current Time = Tue Sep 27 12:41:24 2005

Diagnostic for LC 0/3/CPU0:

Schedule #1:

        To be run daily 14:40

        Test ID(s) to be executed: 1 .

Table 71 describes the significant fields shown in the display.

Table 71 show diagnostic schedule Field Descriptions 

Field	Description
Current Time	Current system time.
Diagnostic for	Card for which the diagnostic is scheduled.
Schedule	Schedule number.
To be run	Time at which the diagnostics are scheduled to run.
Test ID(s) to be executed	Tests to be run at scheduled time.

Related Commands

Command	Description
diagnostic schedule	Schedules a diagnostic test.

show diagnostic status

To display the current running tests, use the show diagnostic status command in administration EXEC mode.

show diagnostic status

Syntax Description

This command has no arguments or keywords.

Defaults

No default behavior or values

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.

Task ID

Task ID	Operations
diag	read

Examples

The following example shows how to display the current running tests:

RP/0/RP0/CPU0:router(admin)# show diagnostic status 

<BU> - Bootup Diagnostics, <HM> - Health Monitoring Diagnostics,

<OD> - OnDemand Diagnostics, <SCHD> - Scheduled Diagnostics

==================================== =============================== ======

Card   Description                   Current Running Test            Run by

------------------------------------ ------------------------------- ------

RP 0/RP0/CPU0                        N/A                             N/A   

------------------------------------ ------------------------------- ------

RP 0/RP1/CPU0                        N/A                             N/A   

------------------------------------ ------------------------------- ------

DRP 0/4/CPU1                         N/A                             N/A   

------------------------------------ ------------------------------- ------

DRP 0/4/CPU0                         SelfPingOverFabric              <OD>  

DRP-ACC 0/PL4/SP                     N/A                             N/A   

------------------------------------ ------------------------------- ------

MSC 0/1/CPU0                         N/A                             N/A   

JACKET CARD 0/PL1/SP                 N/A                             N/A   

------------------------------------ ------------------------------- ------

MSC 0/6/CPU0                         N/A                             N/A   

JACKET CARD 0/PL6/SP                 N/A                             N/A   

------------------------------------ ------------------------------- ------

FC/S 0/SM0/SP                        N/A                             N/A   

------------------------------------ ------------------------------- ------

FC/S 0/SM3/SP                        N/A                             N/A   

------------------------------------ ------------------------------- ------

FC/S 0/SM2/SP                        N/A                             N/A   

------------------------------------ ------------------------------- ------

FC/S 0/SM1/SP                        N/A                             N/A   

------------------------------------ ------------------------------- ------

DRP 0/4/SP                           N/A                             N/A   

------------------------------------ ------------------------------- ------

MSC 0/1/SP                           N/A                             N/A   

------------------------------------ ------------------------------- ------

MSC 0/6/SP                           N/A                             N/A   

==================================== =============================== ======

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

show diags

To display details about the hardware and software on each node in a router, use the show diags command in EXEC mode or Administration EXEC mode.

show diags [slot [details | summary] | chassis-info | details | summary]

Syntax Description

slot	Identifies the slot that hosts the node on which you want to run diagnostics. Replace slot-number with a slot number. Range is from 0 through 22. To display detailed diagnostics information for the slot, follow the slot argument with the details keyword. To display summarized diagnostics results for the slot, follow the slot argument with the summary keyword.
details	(Optional) Displays detailed diagnostics information for the current node.
summary	(Optional) Displays summarized diagnostics results for all nodes in the system.
chassis-info	(Optional) Displays information about the chassis.

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 XR 12000 Series Router.
Release 3.0	No modification.
Release 3.2	No modification.
Release 3.3.0	The chassis-info keyword was added to the show diags command syntax on the Cisco XR 12000 Series Router.
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.

The show diags command displays detailed information on the hardware components for each node, and on the status of the software running on each node.

Task ID

Task ID	Operations
sysmgr	read

Examples

The following example shows sample output from the show diags command on a Cisco XR 12000 Series Router. In this example, the show diags command is entered without any of the optional parameters. Diagnostic test results are displayed for all nodes in the router:

RP/0/0/CPU0:router# show diags

SLOT 0  (RP/LC 0 ): Route Processor

  MAIN: type 19,  800-2427-01 rev J0

        Deviation: 0

        HW config: 0xFF    SW key: FF-FF-FF

  PCA:  73-2170-03 rev G0 ver 3

        Design Release 1.4  S/N CAB040879NN

  MBUS: MBUS Agent (1)  73-2146-07 rev B0 dev 0

        HW version 1.2  S/N CAB040877IM

        Test hist: 0xFF    RMA#: FF-FF-FF    RMA hist: 0xFF

  DIAG: Test count: 0xFFFFFFFF    Test results: 0xFFFFFFFF

  FRU:  Linecard/Module: GRP=

        Route Memory: MEM-GRP-512=

  MBUS Agent Software version 1.100 (RAM) (ROM version is 2.9)

  ROM Monitor version 181 (old numbering scheme)

  Primary clock is CSC 1

  Board State is IOS Running  ACTIVE (ACTV  RP )

  Insertion time: 00:00:04 (5d01h ago)

  DRAM size: 536870912 bytes

Table 72 describes the significant fields shown in the display.

Table 72 show diags Field Descriptions

Field	Description
SLOT	Physical slot number of the line card.
MAIN	General information about the hardware.
PCA	Cisco PCA1 hardware and revision number.
MBUS	Provides version information for the Mbus agent.
DIAG	Results of the last diagnostics test, in hexadecimal format.
FRU	Information about the FRUs2 associated with the nodes that are installed in the router.
MBUS Agent Software version	Mbus agent software version currently running on the router.
ROM monitor version	Version of monitor library used by ROMMON.
Primary clock	Primary clock source configured on the router.
Board State	Current software on the board (in this case, Cisco IOS XR software), and whether or not the board is running.
Insertion time	Time at which the last diagnostics test was executed.
DRAM size	DRAM3 size in bytes.

1. protection channel access

2. Field-replaceable units

3. dynamic random-access memory

Related Commands

Command	Description
show platform	Displays information and status for each node in the system.
show version	Displays details on the hardware and software status of the system.

show hw-module subslot brief

To display summary diagnostic information about internal hardware devices for a shared port adapter (SPA), use the show hw-module subslot brief command in EXEC mode.

show hw-module subslot [node-id] brief [device [device-index [device-subindex]]]

Syntax Description

node-id	(Optional) Location for which to display the specified information. The node-id argument is entered in the rack/slot/module notation.
device	(Optional) Internal hardware device for which to display the specified information. Valid devices include: •analog-digital-converter—Displays analog-to-digital converter information. •c2w—Displays Cisco-to-wire bus device information. •fpga—Displays shared port adapter (SPA) field-programmable gate array information. •framer—Displays SONET framer information. (Not applicable to Ethernet SPAs.) •l2-tcam—Displays SPA Layer 2 ternary content addressable memory information. (Not applicable to POS SPAs.) •mac—Displays SPA MAC information. (Not applicable to POS SPAs.) •pluggable-optics—Displays pluggable-optics module information. •power-margining—Displays power-margining device information. •sdcc—Displays section data communications channel device information. (Not applicable to Ethernet SPAs.) •serdes—Displays SPA serializer/deserializer information. •spi4—Displays system packet interface level 4.2 bus device information. •temperature-sensor—Displays temperature sensor information.
device-index	(Optional) Index of the specific device if there are multiple devices of the same type.
device-subindex	(Optional) Subindex of the specific device if there are multiple devices of the same device index.

Defaults

No default behavior or values

Command Modes

EXEC

Command History

Release	Modification
Release 3.2	This command was introduced on the Cisco CRS-1 and the Cisco XR 12000 Series Router.
Release 3.3.0	No modification.
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 command to display the nodes on the router.

You can enter a partially qualified location specifier by using the wildcard (*) character. For example, 0/1/* would display information for all modules on slot 1 in rack 0.

Use the show hw-module subslot brief command to obtain summary diagnostic information about an interface on the SPA.

Task ID

Task ID	Operations
root-lr	read

Examples

The following is sample output for the show hw-module subslot brief command:

RP/0/RP1/CPU0:router# show hw-module subslot brief

BAY 0 brief info:

-------------------

SPA inserted: YES

SPA type:     1xOC192 POS/RPR HHSPA with XFP

SPA operational state: READY

SPA cfg admin up: YES

BAY 1 brief info:

-------------------

SPA inserted: YES

SPA type:     1xOC192 POS/RPR FHSPA

SPA operational state: READY

SPA cfg admin up: YES

Table 73 describes the significant fields shown in the display.

Table 73 show hw-module subslot brief Field Descriptions 

Field	Description
SPA inserted	Indicates if a SPA is currently detected in the subslot.
SPA type	Description of SPA including the technology type, number of ports, height of SPA (HHSPA—single height, FHSPA—double height), and optics type.
SPA operational state	Current state of the SPA module.
SPA cfg admin	Configured state of the SPA: YES—the SPA is not shut down, NO—the SPA is shut down.

The following is sample output for the show hw-module subslot brief command with the c2w option:

RP/0/RP1/CPU0router# show hw-module subslot 0/2/cpu0 brief c2w

 SPA device c2w index 0 subindex 0 info:

Auxiliary C2W (0x0803bfbc), name AUX C2W (busywait), state 4

SPA device c2w index 0 subindex 0 info:

Auxiliary C2W (0x080638c4), name AUX C2W (busywait), state 4

Related Commands

Command	Description
show controllers	Displays the controller type and other information.