Step 1 | diagnostic
ondemand
Example:
Router# diagnostic ondemand iteration 50
|
Configures the ondemand diagnostic parameters such as
iteration-count and action-on-error. These parameters signify the number of
times the test is run and the execution action when a failure is detected.
These parameters are used when the command
diagnostic
start is executed. In the given example, the
iteration count to the same ondemand diagnostic test again is configured as 50.
Note
| By default, iteration-count is 1, action-on-error is continue,
and error count is 0.
|
|
Step 2 | show
diagnostic
ondemand
settings
Example:
Router# show diagnostic ondemand settings
|
Displays the ondemand diagnostic settings configured using the
command
diagnostic
ondemand.
|
Step 3 | diagnostic
start
{bay
slot/bay |
slot
slot-no}
test {test-id |
test-id-range |
all |
complete |
minimal |
non-disruptive}
Example:
Router# diagnostic start bay 1/0 test 1 all
|
Starts an ondemand diagnostic test.
- bay
slot/bay—Indicates the card slot and
bay number where the diagnostic test is executed. The bay keyword is used to
refer a SPA on the router. The valid range for the slot number is from 1 to 8
and 0 to 3 for the bay number.
- slot
slot-no—Indicates the slot number of
the full-height line card where the diagnostic test is executed. The slot
keyword is used to refer a full-height line card on the router. The valid range
for slot is from 1 to 8.
- subslot
slot/sub-slot—Indicates the slot and
subslot number of half-height line card where the diagnostic test is executed.
The subslot keyword is used to refer a half-height line card on the router. The
valid range for the slot number is from 1 to 8 and 0 to 1 for the subslot
number.
- test— Specifies a test to run.
- test-id—Identification number for the
test to run.
- test-id-range—Range of identification
numbers for tests to run.
- minimal—Runs minimal bootup
diagnostic tests.
- complete—Runs complete bootup
diagnostic tests.
- non-disruptive—Runs the non
disruptive health-monitoring tests.
- all—Runs all diagnostic tests.
|
Step 4 | show
diagnostic
content
Example:
Router# show diagnostic content
|
Displays the registered tests, attributes, and the configured
interval at which the test runs.
Note
| To view the registered test details for a specific SPA,
full-height line card, or half-height line-card, use the keywords bay, slot, or
subslot.
|
|
Step 5 | show
diagnostic
result
Example:
Router# show diagnostic result
|
Displays the diagnostic test results for a SPA, full-height line
card, or half-height line card.
|
Step 6 | show
diagnostic
events
Example:
Router# show diagnostic events
|
Displays the diagnostic event log details for all the SPAs,
full-height line card, and half-height line cards installed on the Cisco
UBR10012 Router.
|
Step 7 | diagnostic
stop
{bay
slot/bay |
slot
slot-no}
test {test-id |
test-id-range |
all |
complete |
minimal |
non-disruptive}
Example:
Router# diagnostic stop bay 1/0 all
|
Stops the ondemand diagnostic test.
|
Step 8 | configure
terminal
Example:
Router# configure terminal
|
Enters global configuration mode.
|
Step 9 | diagnostic
bootup
level {minimal |
complete}
Example:
Router(config)# diagnostic bootup level complete
|
Configures the bootup diagnostic level.
- minimal—Specifies minimal
diagnostics.
- complete—Specifies complete
diagnostics.
|
Step 10 | show
diagnostic
bootup
level
Example:
Router# show diagnostic bootup
|
Displays the configured bootup diagnostic level.
|
Step 11 | diagnostic
event-log
size
size
Example:
Router(config)# diagnostic event log size 10000
|
Modifies the diagnostic event log size dynamically.
- size—Diagnostic event-log sizes. The
valid values range from 1 to 10000 entries.
|
Step 12 | diagnostic
monitor
interval {bay
slot/bay |
slot
slot-no} |
subslot
slot/subslot}
test {test-id |
test-id-range |
all}
hh:mm:ss
milliseconds
days
Example:
Router(config)# diagnostic monitor interval bay 1/0 test 2 06:00:00 100 20
|
Configures the health monitoring diagnostic test interval to
rerun the tests.
- hh:mm:ss—Hours, minutes, and seconds
interval configured to run the test again.
- milliseconds—Number of milliseconds
between tests.
- days—Number of days between tests.
The valid range is from 0 to 20.
|
Step 13 | diagnostic
schedule
module
{module-number | slot/subslot}
test {test-id |
all |
complete |
minimal |
non-disruptive |
per-port}
Example:
Router(config)# diagnostic schedule slot 1 test complete daily 08:00
|
Schedules the online diagnostic test to run at a designated time,
or on daily, weekly or monthly basis.
- module-number—Specifies the module
number.
- per-port—Selects the per-port test
suite.
|
Step 14 | show
diagnostic
schedule
Example:
Router# show diagnostic schedule
|
Displays the current scheduled diagnostic tests.
|