Enabling Diagnostics; Ignoring Diagnostic Test Failures - Juniper JUNOSE SOFTWARE FOR E SERIES 11.3.X - SYSTEM BASICS CONFIGURATION GUIDE 2010-10-04 Configuration Manual

JunosE 11.3.x System Basics Configuration Guide

Enabling Diagnostics

diag-level

Ignoring Diagnostic Test Failures

392
Use to restart the specified SRP module or line module and enable the system to
perform diagnostic tests on the module.
Use the force keyword to enable the system to manually confirm conflicting conditions
when the slot of the active SRP module is specified.
If you specify a slot on the E120 and E320 routers that contains an SRP module, you
can use the subsystem variable to perform diagnostic tests on a subsystem on the SRP
module. We recommend that you perform diagnostic tests on one subsystem at a time
to avoid interrupting network traffic transmitting through the fabric modules.
Use the srp keyword to perform diagnostic tests on the SC subsystem that resides
on a specified SRP module.
Use the fabric keyword to run diagnostic tests on the fabric slice that resides on the
specified SRP module.
Example 1—Enables warm restart diagnostics on a line module
host1#diag 3 force
Example 2—Enables warm restart diagnostics on the fabric subsystem of an active
SRP module on the E320 Router
host1#diag 6 fabric
There is no no version.
See diag.
Use the diag command to enable warm restart diagnostics on a module. Use the
diag-level command to set the diagnostics level on a module.
Use to set the diagnostics level on the active or standby SRP module to reduce the
boot time during a cold and a warm boot.
Use the normal keyword (default) to execute full diagnostics on the boot of the line
card.
Use the bypass keyword to skip diagnostic tests on the boot of the line card.
Example —Bypasses diagnostic tests
host1#diag—level bypass
There is no no version.
See diag-level.
You can ignore diagnostic test failures on the line module or SRP. This enables you to
categorize diagnostic failures and determine the impact on functional behavior.
Copyright © 2010, Juniper Networks, Inc.