A-34
Cisco 7600 Series Router Cisco IOS Software Configuration Guide, Release 12.2SX
OL-4266-08
Appendix A Online Diagnostic Tests
Critical Recovery Tests
TestEobcStressPing
The TestEobcStressPing test stress tests a module’s EOBC link with the supervisor engine. The test is
started when the supervisor engine initiates a number of sweep-ping processes (the default is one). The
sweep-ping process pings the module with 20,000 SCP-ping packets. The test passes if all 20,000
packets respond before each packet-ping timeout, which is two seconds. If unsuccessful, the test allows
five retries to account for traffic bursts on the EOBC bus during the test.
Critical Recovery Tests
The critical recovery tests consist of the following tests:
•
TestL3HealthMonitoring, page A-34
•
TestTxPathMonitoring, page A-35
•
TestSynchedFabChannel, page A-35
The TestFabricCh0Health and TestFabricCh1Health tests are also considered critical recovery tests. See
the
“Fabric Tests” section on page A-26
for a description of these tests.
TestL3HealthMonitoring
The TestL3HealthMonitoring test triggers a set of diagnostic tests involving IPv4 and IPv6 packet
switching on a local DFC whenever the system tries to self-recover from a detected hardware fault. The
tests shut down the front panel port (usually port 1) for testing purposes. If the diagnostic tests are not
passing, it is an indication that the hardware fault cannot be fixed and a self-recovery sequence will be
applied again
Table A-60
TestEobcStressPing Test Attributes
Attribute
Description
Disruptive/Nondisruptive
Disruptive. Disruption is several minutes.
Recommendation
Use this test to qualify hardware before installing it in your
network.
Default
Off.
Release
12.2(18)SXD.
Corrective action
Not applicable.
Hardware support
Supervisor Engine 720 and Supervisor Engine 32.
Table A-61
TestL3HealthMonitoring Test Attributes
Attribute
Description
Disruptive/Nondisruptive
Disruptive. Disruption is typically less than one second.
Duration of the disruption depends on the configuration of
looped-back port (for example, Spanning Tree Protocol).
Forwarding and port functions are disrupted during the test.