Information About Online Diagnostics
With online diagnostics, you can test and verify the hardware functionality of the switch while the switch is connected to a live network.
The online diagnostics contain packet switching tests that check different hardware components and verify the data path and control signals. Disruptive online diagnostic tests, such as the built-in self-test (BIST) and the disruptive loopback test, and nondisruptive online diagnostic tests, such as packet switching, run during bootup, module online insertion and removal (OIR), and system reset. The nondisruptive online diagnostic tests run as part of background health monitoring. Either disruptive or nondisruptive tests can be run at the user’s request (on-demand).
The online diagnostics detect problems in the following areas:
-
Hardware components
-
Interfaces (GBICs, Ethernet ports, and so forth)
-
Connectors (loose connectors, bent pins, and so forth)
-
Solder joints
-
Memory (failure over time)
Online diagnostics is one of the requirements for the high availability feature. High availability is a set of quality standards that seek to limit the impact of equipment failures on the network. A key part of high availability is detecting hardware failures and taking corrective action while the switch runs in a live network. Online diagnostics in high availability detect hardware failures and provide feedback to high availability software components to make switchover decisions.
Online diagnostics are categorized as bootup, on-demand, schedule, or health-monitoring diagnostics. Bootup diagnostics run during bootup; on-demand diagnostics run from the CLI; schedule diagnostics run at user-designated intervals or specified times when the switch is connected to a live network; and health-monitoring runs in the background.
How to Configure Online Diagnostics
Setting Bootup Online Diagnostics Level
You can set the bootup diagnostics level as minimal or complete or you can bypass the bootup diagnostics entirely. Enter the
complete
keyword to run all diagnostic tests; enter the
minimal
keyword to run only EARL tests and loopback tests for all ports in the switch. Enter the
no
form of the command to bypass all diagnostic tests. The default bootup diagnositcs level is minimal.
To set the bootup diagnostic level, perform this task:
|
|
|
Router(config)#
diagnostic bootup level
{
minimal
|
complete
}
|
Sets the bootup diagnostic level.
|
This example shows how to set the bootup online diagnostic level:
Router(config)# diagnostic bootup level complete
This example shows how to display the bootup online diagnostic level:
Router(config)# show diagnostic bootup level Current bootup diagnostic level: complete
Combined Legacy Diagnostic Tests
The following legacy diagnostic tests have been combined:
TestAclRedirectRBAcl
The legacy tests
TestRBAcl
and
TestAclRedirect
have been merged into this test.
The combined test will verify both the ACL redirect feature and the Role based ACL feature of the Layer 3 forwarding engine.
TestQosDQUP
The legacy tests
TestQos
and
TestDQUP
have been merged into this test.
The combined test will verify both the QoS input/output TCAM functionality and that DQUP/PUP packets can be generated when diagnostic packets hit QoS entry.
TestIngressEgressSpan
The legacy tests TestIngressSpan and TestEgressSpan have been merged into this test.
This combined test will ensure the port ASIC will be able to tag packets for ingress span and verify the egress span replication functionality of the ingress module replication engine.
New Diagnostic Tests
TestEobcStressPing
This test is designed to stress test the EOBC link of a line card with the supervisor.
In this test a large number (20,000) of ICMP packets are sent from the Supervisor to the line card along with varying the size of the ICMP packet. The test is declared pass when all the ICMP packets are responded to within the timeout (2 seconds).
The test can be run on-demand or scheduled as it is a disruptive test. It is possible the test will fail if the EOBC was already under heavy load and all packets are not responded to. No corrective action is needed.
TestVSActiveToStandbyLoopback
This test is a VSS system wide test and only permitted in on-demand mode.
During this test, the standby VSS supervisor’s uplink port is configured in loopback mode and a VLAN flood packet is sent from the Active VSS’s inband port to the standby VSS’s uplink port.
This is a disruptive test that can be run on-demand only. It doesn’t require a VSL link from Active to Standby supervisor. The uplink port cannot be specified. The test cannot be run on the Active Supervisor.
TestVslBridgeLink
This test verifies the bridge link data path between two fabric channel and rewrite engine based data path complexes for VSL configurable Supervisor or line card.
The packet is sent across the bridge link from the inband port on one data path complex to a good loopback port on another data path complex.
TestVslLocalLoopback
This test verifies the hardware functionality of each port on a VSL card before any VSL member link in the VSL port-channel group is up.
A diagnostic packet is sent from the local inband port of the VSL card to each port to run a loopback test.
TestVslStatus
This test reports the status change of the link detected by VSLP protocol.
If any link problem is detected by VSLP, the link status and result are updated. The loopback test to check the hardware status, as requested by VSLP is also triggered.
TestFabricLinkStatus
This test monitors the FEX fabric link on the FEX controller.
It will report failure if the fabric link port has lost connection to the associated FEX.
Configuring On-Demand Online Diagnostics
You can run the on-demand online diagnostic tests from the CLI. You can set the execution action to either stop or continue the test when a failure is detected or to stop the test after a specific number of failures occur by using the failure count setting. You can configure a test to run multiple times using the iteration setting.
You should run packet-switching tests before memory tests.
Note Do not use the diagnostic start all command until all of the following steps are completed.
Because some on-demand online diagnostic tests can affect the outcome of other tests, you should perform the tests in the following order:
1. Run the nondisruptive tests.
2. Run all tests in the relevant functional area.
3. Run the TestTrafficStress test.
4. Run the TestEobcStressPing test.
5. Run the exhaustive-memory tests.
To run on-demand online diagnostic tests, perform this task:
Step 1 Run the nondisruptive tests.
To display the available tests and their attributes, and determine which commands are in the nondisruptive category, enter the
show diagnostic content
command.
Step 2 Run all tests in the relevant functional area.
Packet-switching tests fall into specific functional areas. When a problem is suspected in a particular functional area, run all tests in that functional area. If you are unsure about which functional area you need to test, or if you want to run all available tests, enter the
complete
keyword.
Step 3 Run the TestTrafficStress test.
This is a disruptive packet-switching test. This test switches packets between pairs of ports at line rate for the purpose of stress testing. During this test all of the ports are shut down, and you may see link flaps. The link flaps will recover after the test is complete. The test takes several minutes to complete.
Disable all health-monitoring tests f before running this test by using the
no diagnostic monitor module
number
test all
command.
Step 4 Run the TestEobcStressPing test.
This is a disruptive test and tests the Ethernet over backplane channel (EOBC) connection for the module. The test takes several minutes to complete. You cannot run any of the packet-switching tests described in previous steps after running this test. However, you can run tests described in subsequent steps after running this test.
Disable all health-monitoring tests before running this test by using the
no diagnostic monitor module
number
test all
command. The EOBC connection is disrupted during this test and will cause the health-monitoring tests to fail and take recovery action.
Step 5 Run the exhaustive-memory tests.
Before running the exhaustive-memory tests, all health-monitoring tests should be disabled because the tests will fail with health monitoring enabled and the switch will take recovery action. Disable the health-monitoring diagnostic tests by using the
no diagnostic monitor module
number
test all
command.
Perform the exhaustive-memory tests in the following order:
1. TestFibTcamSSRAM
2. TestAclQosTcam
3. TestNetFlowTcam
4. TestAsicMemory
5. TestAsicMemory
You must reboot the after running the exhaustive-memory tests before it is operational again. You cannot run any other tests on the switch after running the exhaustive-memory tests. Do not save the configuration when rebooting as it will have changed during the tests. After the reboot, reenable the health-monitoring tests using the
diagnostic monitor module
number
test all
command.
To set the bootup diagnostic level, perform this task:
|
|
|
Router#
diagnostic ondemand
{
iteration
iteration_count
} | {
action-on-error {continue
|
stop
} [
error_count
]}
|
Configures on-demand diagnostic tests to run, how many times to run (iterations), and what action to take when errors are found.
|
This example shows how to set the on-demand testing iteration count:
Router# diagnostic ondemand iteration 3
This example shows how to set the execution action when an error is detected:
Router# diagnostic ondemand action-on-error continue 2
Scheduling Online Diagnostics
You can schedule online diagnostics to run at a designated time of day or on a daily, weekly, or monthly basis. You can schedule tests to run only once or to repeat at an interval. Use the
no
form of this command to remove the scheduling.
To schedule online diagnostics, perform this task:
|
|
|
Router(config)#
diagnostic schedule
module
number
test
{
test_id
|
test_id_range
|
all
} [
port
{
num
|
num_range
|
all
}] {
on
mm
dd
yyyy
hh
:
mm
} | {
daily
hh
:
mm
} | {
weekly
day_of_week
hh
:
mm
}
|
Schedules on-demand diagnostic tests on the specified module for a specific date and time, how many times to run (iterations), and what action to take when errors are found.
|
This example shows how to schedule diagnostic testing on a specific date and time for a specific port on module 1:
Router(config)# diagnostic schedule module 1 test 1,2,5-9 port 3 on january 3 2003 23:32
This example shows how to schedule diagnostic testing to occur daily at a certain time for a specific port:
Router(config)# diagnostic schedule module 1 test 1,2,5-9 port 3 daily 12:34
This example shows how to schedule diagnostic testing to occur weekly on a certain day for a specific port:
Router(config)# diagnostic schedule module 1 test 1,2,5-9 port 3 weekly friday 09:23
Configuring Health-Monitoring Diagnostics
You can configure health-monitoring diagnostic testing while the switch is connected to a live network. You can configure the execution interval for each health-monitoring test, the generation of a system message upon test failure, or the enabling or disabling an individual test. Use the
no
form of this command to disable testing.
To configure health-monitoring diagnostic testing, perform this task:
|
|
|
|
Step 1
|
Router(config)#
diagnostic monitor interval
module
number
test
{
test_id
|
test_id_range
|
all
} [
hour
hh
] [
min
mm
] [
second
ss
] [
millisec
ms
] [
day
day
]
|
Configures the health-monitoring interval of the specified tests. The
no
form of this command will change the interval to the default interval, or zero.
|
Step 2
|
Router(config)#[
no
]
diagnostic monitor
module
number
test
{
test_id
|
test_id_range
|
all
}
|
Enables or disables health-monitoring diagnostic tests.
|
This example shows how to configure the specified test to run every two minutes on module 1:
Router(config)# diagnostic monitor interval module 1 test 1 min 2
This example shows how to run the test if health monitoring has not previously been enabled:
Router(config)# diagnostic monitor module 1 test 1
This example shows how to enable the generation of a syslog message when any health-monitoring test fails:
Router(config)# diagnostic monitor syslog
How to Run Online Diagnostic Tests
Overview of Diagnostic Test Operation
After you configure online diagnostics, you can start or stop diagnostic tests or display the test results. You can also see which tests are configured and what diagnostic tests have already run.
-
Enable the logging console/monitor to see all warning messages before you enable any online diagnostics tests.
-
When you are running disruptive tests, run the tests when connected through the console. When disruptive tests are complete, a warning message on the console recommends that you reload the system to return to normal operation. Strictly follow this warning.
-
While tests are running, all ports are shut down because a stress test is being performed with ports configured to loop internally; external traffic might alter the test results. The switch must be rebooted to bring the switch to normal operation. When you issue the command to reload the switch, the system will ask you if the configuration should be saved. Do not save the configuration.
-
If you are running the tests on a supervisor engine, after the test is initiated and complete, you must reload or power down and then power up the entire system.
-
If you are running the tests on a switching module, rather than the supervisor engine, after the test is initiated and complete, you must reset the switching module.
Starting and Stopping Online Diagnostic Tests
After you configure diagnostic tests to run, you can use the
start
and
stop
to begin or end a diagnostic test. To start or stop an online diagnostic command, perform one of these tasks:
|
|
|
Router#
diagnostic start module
number
test
{
test_id
|
test_id_range
|
minimal
|
complete
|
basic
|
per-port
|
non-disruptive
| all} [port {
num
|
port#_range
| all}]
|
Starts a diagnostic test on a port or range of ports on the specified module.
|
Router#
diagnostic stop module
number
|
Stops a diagnostic test on the specified module.
|
This example shows how to start a diagnostic test on module 1:
Router# diagnostic start module 1 test 5 Module 1:Running test(s) 5 may disrupt normal system operation Do you want to run disruptive tests? [no]yes 00:48:14:Running OnDemand Diagnostics [Iteration #1] ... 00:48:14:%DIAG-SP-6-TEST_RUNNING:Module 1:Running TestNewLearn{ID=5} ... 00:48:14:%DIAG-SP-6-TEST_OK:Module 1:TestNewLearn{ID=5} has completed successfully 00:48:14:Running OnDemand Diagnostics [Iteration #2] ... 00:48:14:%DIAG-SP-6-TEST_RUNNING:Module 1:Running TestNewLearn{ID=5} ... 00:48:14:%DIAG-SP-6-TEST_OK:Module 1:TestNewLearn{ID=5} has completed successfully
This example shows how to stop a diagnostic test:
Router# diagnostic stop module 1
Running All Online Diagnostic Tests
You can run all diagnostic tests, disruptive and nondisruptive, at once with a single command. In this case, all test dependencies will be handled automatically.
Note • Running all online diagnostic tests will disrupt normal system operation. Reset the system after the diagnostic start system test all command has completed.
-
Do not insert, remove, or power down modules or the supervisor while the system test is running.
-
Do not issue any diagnostic command other than the
diagnostic stop system test all
command while the system test is running.
-
Make sure no traffic is running in background.
To start or stop all online diagnostic tests, perform one of these tasks:
|
|
|
Router#
diagnostic start system test all
|
Executes all online diagnostic tests.
|
Router#
diagnostic stop system test all
|
Stops the execution of all online diagnostic tests.
|
This example shows how to start all online diagnostic tests:
Router# diagnostic start system test all ************************************************************************* * 'diagnostic start system test all' will disrupt normal system * * operation. The system requires RESET after the command * * 'diagnostic start system test all' has completed prior to * * 1. DO NOT INSERT, OIR, or POWER DOWN Linecards or * * Supervisor while system test is running. * * 2. DO NOT ISSUE ANY DIAGNOSTIC COMMAND except * * "diagnostic stop system test all" while system test * * 3. PLEASE MAKE SURE no traffic is running in background. * ************************************************************************* Do you want to continue? [no]:
Displaying Online Diagnostic Tests and Test Results
You can display the online diagnostic tests that are configured and check the results of the tests using the following
show
commands:
-
show diagnostic content
-
show diagnostic health
To display the diagnostic tests that are configured, perform this task:
|
|
|
show diagnostic
{
bootup level
|
content
[
module
num
]
|
events
[
module
num
]
[
event-type
event-type
]
|
health
|
ondemand settings
|
result
[
module
num
]
[
detail
]
|
schedule
[
module
num
]}
|
Displays the test results of online diagnostics and lists supported test suites.
|
This example shows how to display the online diagnostics that are configured on switch 1 module 5:
Router# show diagnostic content switch 1 module 5 Switch 1 Module 5: Supervisor Engine 6T 10GE w/ CTS (Active) 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 R/* - Power-down line cards and need reload supervisor / NA K/* - Require resetting the line card after the test has completed / NA T/* - Shut down all ports and need reload supervisor / NA L/* - FEX switch will reload after test list completion / NA ID Test Name Attributes day hh:mm:ss.ms shold ==== ================================== ============ =============== ===== 1) TestTransceiverIntegrity --------> **PD*X**I**** not configured n/a 2) TestLoopback --------------------> M*PD*X**I**** not configured n/a 3) TestFexModeLoopback -------------> M*PD*X**I**** not configured n/a 4) TestVSActiveToStandbyLoopback ---> ***DSX**I**** not configured n/a 5) TestL2CTSLoopback ---------------> M*PD*X**I**** not configured n/a 6) TestL3CTSLoopback ---------------> M*PD*X**I**** not configured n/a 7) TestScratchRegister -------------> ***N****I**** 000 00:00:30.00 5 8) TestNewIndexLearn ---------------> M**N****I**** 000 00:00:15.00 10 9) TestDontConditionalLearn --------> M**N****I**** 000 00:00:15.00 10 10) TestBpduTrap --------------------> M**D*X**I**** not configured n/a 11) TestMatchCapture ----------------> M**D*X**I**** not configured n/a 12) TestProtocolMatchChannel --------> M**D*X**I**** not configured n/a 13) TestPortSecurity ----------------> M**D*X**I**** not configured n/a 14) TestIPv4FibShortcut -------------> M**N****I**** 000 00:00:15.00 10 15) TestL3Capture2 ------------------> M**D*X**I**** not configured n/a 16) TestIPv6FibShortcut -------------> M**N****I**** 000 00:00:15.00 10 17) TestMPLSFibShortcut -------------> M**N****I**** 000 00:00:15.00 10 18) TestNATFibShortcut --------------> M**N****I**** 000 00:00:15.00 10 19) TestAclPermit -------------------> M**N****I**** 000 00:00:15.00 10 20) TestAclDeny ---------------------> M**D*X**I**** not configured n/a 21) TestAclRedirectRBAcl ------------> M**N****I**** not configured n/a 22) TestQosDQUP ---------------------> M**D*X**I**** not configured n/a 23) TestL3VlanMet -------------------> M**D*X**I**** not configured n/a 24) TestIngressEgressSpan -----------> M**D*X**I**** not configured n/a 25) TestNetflowShortcut -------------> M**D*X**I**** not configured n/a 26) TestInbandEdit ------------------> M**D*X**I**** not configured n/a 27) TestFabricVlanLoopback ----------> M**D*X**I**** not configured n/a 28) TestTrafficStress ---------------> ***D*X**I**T* not configured n/a 29) TestL3TcamMonitoring ------------> ***N****I**** 000 00:00:15.00 10 30) TestFibTcam ---------------------> ***D*X**IR*** not configured n/a 31) TestAclQosTcam ------------------> ***D*X**IR*** not configured n/a 32) TestEarlMemOnBootup -------------> M**N*X**I**** not configured n/a 33) TestAsicMemory ------------------> ***D*X**IR*** not configured n/a 34) TestEobcStressPing --------------> ***D*X**I**** not configured n/a 35) TestFirmwareDiagStatus ----------> M**N****I**** 000 00:00:15.00 10 36) TestAsicSync --------------------> ***N****I**** 000 00:00:15.00 10 37) TestUnusedPortLoopback ----------> **PN****I**** 000 00:01:00.00 10 38) TestNonDisruptiveLoopback -------> **PN****I**** 000 00:00:10.00 10 39) TestFabricFlowControlStatus -----> ***N****I**** 000 00:00:15.00 10 40) TestPortTxMonitoring ------------> **PN****I**** 000 00:01:15.00 5 41) TestOBFL ------------------------> M**N****I**** 000 00:00:15.00 10 42) TestCFRW ------------------------> M*VN*X**I**** not configured n/a 43) TestLtlFpoeMemoryConsistency ----> ***N****I**** 000 00:00:30.00 1 44) TestRwEngineOverSubscription ----> ***N****I**** 000 00:00:01.00 10 45) TestErrorCounterMonitor ---------> ***N****I**** 000 00:00:30.00 10 46) TestVslBridgeLink ---------------> M**D*X**I**** not configured n/a 47) TestVslLocalLoopback ------------> M*PD*X**I**** not configured n/a 48) TestVslStatus -------------------> M*PD*X**I**** not configured n/a 49) TestEARLInternalTables ----------> ***N****I**** 000 00:05:00.00 1 50) TestNVRAMBatteryMonitor ---------> ***N**F*I**** 000 01:00:00.00 72 51) TestMediaLoopback ---------------> **PD*X**I**** not configured n/a 52) TestMicroburst ------------------> **PN****I**** 000 00:00:05.00 10 53) TestFEXFabricLinkStatus ---------> **PN****I**** 000 00:00:03.00 3
This example shows how to display the online diagnostic results for module 6:
Router# show diagnostic result switch 1 module 5 Current bootup diagnostic level: complete Switch 1 Module 5: Supervisor Engine 6T 10GE w/ CTS (Active) SerialNo : SAL1927JELC Overall Diagnostic Result for Switch 1 Module 5 : PASS Diagnostic level at card bootup: complete Test results: (. = Pass, F = Fail, U = Untested) 1) TestTransceiverIntegrity: Port 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 ---------------------------------------------------------------- U U U U . . . U . . U U U U U U U U U U Port 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 ---------------------------------------------------------------- . . . . . U U . . . U U U U U U U U U U Port 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 ---------------------------------------------------------------- . . . . . U U . U U U U U U U U U U U U 4) TestVSActiveToStandbyLoopback ---> U Port 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 ---------------------------------------------------------------- . . . . . U U . . . U U U U U U U U U U Port 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 ---------------------------------------------------------------- . . . . . U U . . . U U U U U U U U U U 7) TestScratchRegister -------------> U 8) TestNewIndexLearn ---------------> . 9) TestDontConditionalLearn --------> . 10) TestBpduTrap --------------------> . 11) TestMatchCapture ----------------> . 12) TestProtocolMatchChannel --------> U 13) TestPortSecurity ----------------> . 14) TestIPv4FibShortcut -------------> . 15) TestL3Capture2 ------------------> . 16) TestIPv6FibShortcut -------------> . 17) TestMPLSFibShortcut -------------> . 18) TestNATFibShortcut --------------> . 19) TestAclPermit -------------------> . 20) TestAclDeny ---------------------> . 21) TestAclRedirectRBAcl ------------> . 22) TestQosDQUP ---------------------> . 23) TestL3VlanMet -------------------> . 24) TestIngressEgressSpan -----------> . 25) TestNetflowShortcut -------------> . 26) TestInbandEdit ------------------> . 27) TestFabricVlanLoopback ----------> . 28) TestTrafficStress ---------------> U 29) TestL3TcamMonitoring ------------> U 30) TestFibTcam ---------------------> U 31) TestAclQosTcam ------------------> U 32) TestEarlMemOnBootup -------------> . 33) TestAsicMemory ------------------> U 34) TestEobcStressPing --------------> U 35) TestFirmwareDiagStatus ----------> . 36) TestAsicSync --------------------> U 37) TestUnusedPortLoopback: Port 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 ---------------------------------------------------------------- U U U U U U U U U U U U U U U U U U U U 38) TestNonDisruptiveLoopback: Port 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 ---------------------------------------------------------------- U U U U U U U U U U U U U U U U U U U U 39) TestFabricFlowControlStatus -----> U 40) TestPortTxMonitoring: Port 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 ---------------------------------------------------------------- U U U U U U U U U U U U U U U U U U U U 41) TestOBFL ------------------------> . 43) TestLtlFpoeMemoryConsistency ----> U 44) TestRwEngineOverSubscription ----> U 45) TestErrorCounterMonitor ---------> U 46) TestVslBridgeLink ---------------> . 47) TestVslLocalLoopback: Port 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 ---------------------------------------------------------------- . . . . . . . . . . U U U U U U U U U U Port 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 ---------------------------------------------------------------- U U U U U . . U U U U U U U U U U U U U 49) TestEARLInternalTables ----------> U 50) TestNVRAMBatteryMonitor ---------> U Port 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 ---------------------------------------------------------------- U U U U U U U U U U U U U U U U U U U U Port 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 ---------------------------------------------------------------- U U U U U U U U U U U U U U U U U U U U 53) TestFEXFabricLinkStatus: Port 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 ---------------------------------------------------------------- U U U U U U U U U U U U U U U U U U U U
This example shows how to display the detailed online diagnostic results for module 6:
Router# show diagnostic result switch 1 module 5 detail Current bootup diagnostic level: complete Switch 1 Module 5: Supervisor Engine 6T 10GE w/ CTS (Active) SerialNo : SAL1927JELC Overall Diagnostic Result for Switch 1 Module 5 : PASS Diagnostic level at card bootup: complete Test results: (. = Pass, F = Fail, U = Untested) ___________________________________________________________________________ 1) TestTransceiverIntegrity: Port 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 ---------------------------------------------------------------- U U U U . . . U . . U U U U U U U U U U Error code ------------------> 0 (DIAG_SUCCESS) Total run count -------------> 5 Last test testing type ------> OnDemand Last test execution time ----> Apr 07 2016 10:39:09 First test failure time -----> n/a Last test failure time ------> n/a Last test pass time ---------> Apr 07 2016 10:39:09 Total failure count ---------> 0 Consecutive failure count ---> 0 ___________________________________________________________________________ Port 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 ---------------------------------------------------------------- . . . . . U U . . . U U U U U U U U U U Error code ------------------> 0 (DIAG_SUCCESS) Total run count -------------> 1 Last test testing type ------> Bootup Last test execution time ----> Apr 07 2016 10:38:42 First test failure time -----> n/a Last test failure time ------> n/a Last test pass time ---------> Apr 07 2016 10:38:42 Total failure count ---------> 0 Consecutive failure count ---> 0 ___________________________________________________________________________ Port 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 ---------------------------------------------------------------- . . . . . U U . U U U U U U U U U U U U Error code ------------------> 0 (DIAG_SUCCESS) Total run count -------------> 1 Last test testing type ------> Bootup Last test execution time ----> Apr 07 2016 10:38:47 First test failure time -----> n/a Last test failure time ------> n/a Last test pass time ---------> Apr 07 2016 10:38:47 Total failure count ---------> 0 Consecutive failure count ---> 0 ___________________________________________________________________________ 4) TestVSActiveToStandbyLoopback ---> U Error code ------------------> 3 (DIAG_SKIPPED) Total run count -------------> 0 Last test testing type ------> n/a Last test execution time ----> n/a First test failure time -----> n/a Last test failure time ------> n/a Last test pass time ---------> n/a Total failure count ---------> 0 Consecutive failure count ---> 0 ___________________________________________________________________________ Port 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 ---------------------------------------------------------------- . . . . . U U . . . U U U U U U U U U U Error code ------------------> 0 (DIAG_SUCCESS) Total run count -------------> 1 Last test testing type ------> Bootup Last test execution time ----> Apr 07 2016 10:38:49 First test failure time -----> n/a Last test failure time ------> n/a Last test pass time ---------> Apr 07 2016 10:38:49 Total failure count ---------> 0 Consecutive failure count ---> 0 ___________________________________________________________________________ Port 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 ---------------------------------------------------------------- . . . . . U U . . . U U U U U U U U U U Error code ------------------> 0 (DIAG_SUCCESS) Total run count -------------> 1 Last test testing type ------> Bootup Last test execution time ----> Apr 07 2016 10:38:52 First test failure time -----> n/a Last test failure time ------> n/a Last test pass time ---------> Apr 07 2016 10:38:52 Total failure count ---------> 0 Consecutive failure count ---> 0 ___________________________________________________________________________ 7) TestScratchRegister -------------> U Error code ------------------> 3 (DIAG_SKIPPED) Total run count -------------> 0 Last test testing type ------> n/a Last test execution time ----> n/a First test failure time -----> n/a Last test failure time ------> n/a Last test pass time ---------> n/a Total failure count ---------> 0 Consecutive failure count ---> 0 ___________________________________________________________________________ 8) TestNewIndexLearn ---------------> . Error code ------------------> 0 (DIAG_SUCCESS) Total run count -------------> 1 Last test testing type ------> Bootup Last test execution time ----> Apr 07 2016 10:38:56 First test failure time -----> n/a Last test failure time ------> n/a Last test pass time ---------> Apr 07 2016 10:38:56 Total failure count ---------> 0 Consecutive failure count ---> 0 ___________________________________________________________________________ 9) TestDontConditionalLearn --------> . Error code ------------------> 0 (DIAG_SUCCESS) Total run count -------------> 1 Last test testing type ------> Bootup Last test execution time ----> Apr 07 2016 10:38:56 First test failure time -----> n/a Last test failure time ------> n/a Last test pass time ---------> Apr 07 2016 10:38:56 Total failure count ---------> 0 Consecutive failure count ---> 0 ___________________________________________________________________________ 10) TestBpduTrap --------------------> . Error code ------------------> 0 (DIAG_SUCCESS) Total run count -------------> 1 Last test testing type ------> Bootup Last test execution time ----> Apr 07 2016 10:38:56 First test failure time -----> n/a Last test failure time ------> n/a Last test pass time ---------> Apr 07 2016 10:38:56 Total failure count ---------> 0 Consecutive failure count ---> 0 ___________________________________________________________________________ 11) TestMatchCapture ----------------> . Error code ------------------> 0 (DIAG_SUCCESS) Total run count -------------> 1 Last test testing type ------> Bootup Last test execution time ----> Apr 07 2016 10:38:56 First test failure time -----> n/a Last test failure time ------> n/a Last test pass time ---------> Apr 07 2016 10:38:56 Total failure count ---------> 0 Consecutive failure count ---> 0 ___________________________________________________________________________ 12) TestProtocolMatchChannel --------> U Error code ------------------> 358 (DIAG_SKIPPED_PORT_LOOPBACK_NOT_ALLOWED) Total run count -------------> 0 Last test testing type ------> n/a Last test execution time ----> n/a First test failure time -----> n/a Last test failure time ------> n/a Last test pass time ---------> n/a Total failure count ---------> 0 Consecutive failure count ---> 0 ___________________________________________________________________________ 13) TestPortSecurity ----------------> . Error code ------------------> 0 (DIAG_SUCCESS) Total run count -------------> 1 Last test testing type ------> Bootup Last test execution time ----> Apr 07 2016 10:38:57 First test failure time -----> n/a Last test failure time ------> n/a Last test pass time ---------> Apr 07 2016 10:38:57 Total failure count ---------> 0 Consecutive failure count ---> 0 ___________________________________________________________________________ 14) TestIPv4FibShortcut -------------> . Error code ------------------> 0 (DIAG_SUCCESS) Total run count -------------> 1 Last test testing type ------> Bootup Last test execution time ----> Apr 07 2016 10:38:57 First test failure time -----> n/a Last test failure time ------> n/a Last test pass time ---------> Apr 07 2016 10:38:57 Total failure count ---------> 0 Consecutive failure count ---> 0 ___________________________________________________________________________ 15) TestL3Capture2 ------------------> . Error code ------------------> 0 (DIAG_SUCCESS) Total run count -------------> 1 Last test testing type ------> Bootup Last test execution time ----> Apr 07 2016 10:38:57 First test failure time -----> n/a Last test failure time ------> n/a Last test pass time ---------> Apr 07 2016 10:38:57 Total failure count ---------> 0 Consecutive failure count ---> 0 ___________________________________________________________________________ 16) TestIPv6FibShortcut -------------> . Error code ------------------> 0 (DIAG_SUCCESS) Total run count -------------> 1 Last test testing type ------> Bootup Last test execution time ----> Apr 07 2016 10:38:57 First test failure time -----> n/a Last test failure time ------> n/a Last test pass time ---------> Apr 07 2016 10:38:57 Total failure count ---------> 0 Consecutive failure count ---> 0 ___________________________________________________________________________ 17) TestMPLSFibShortcut -------------> . Error code ------------------> 0 (DIAG_SUCCESS) Total run count -------------> 1 Last test testing type ------> Bootup Last test execution time ----> Apr 07 2016 10:38:57 First test failure time -----> n/a Last test failure time ------> n/a Last test pass time ---------> Apr 07 2016 10:38:57 Total failure count ---------> 0 Consecutive failure count ---> 0 ___________________________________________________________________________ 18) TestNATFibShortcut --------------> . Error code ------------------> 0 (DIAG_SUCCESS) Total run count -------------> 1 Last test testing type ------> Bootup Last test execution time ----> Apr 07 2016 10:38:57 First test failure time -----> n/a Last test failure time ------> n/a Last test pass time ---------> Apr 07 2016 10:38:57 Total failure count ---------> 0 Consecutive failure count ---> 0 ___________________________________________________________________________ 19) TestAclPermit -------------------> . Error code ------------------> 0 (DIAG_SUCCESS) Total run count -------------> 1 Last test testing type ------> Bootup Last test execution time ----> Apr 07 2016 10:38:57 First test failure time -----> n/a Last test failure time ------> n/a Last test pass time ---------> Apr 07 2016 10:38:57 Total failure count ---------> 0 Consecutive failure count ---> 0 ___________________________________________________________________________ 20) TestAclDeny ---------------------> . Error code ------------------> 0 (DIAG_SUCCESS) Total run count -------------> 1 Last test testing type ------> Bootup Last test execution time ----> Apr 07 2016 10:38:57 First test failure time -----> n/a Last test failure time ------> n/a Last test pass time ---------> Apr 07 2016 10:38:57 Total failure count ---------> 0 Consecutive failure count ---> 0 ___________________________________________________________________________ 21) TestAclRedirectRBAcl ------------> . Error code ------------------> 0 (DIAG_SUCCESS) Total run count -------------> 1 Last test testing type ------> Bootup Last test execution time ----> Apr 07 2016 10:38:57 First test failure time -----> n/a Last test failure time ------> n/a Last test pass time ---------> Apr 07 2016 10:38:57 Total failure count ---------> 0 Consecutive failure count ---> 0 ___________________________________________________________________________ 22) TestQosDQUP ---------------------> . Error code ------------------> 0 (DIAG_SUCCESS) Total run count -------------> 1 Last test testing type ------> Bootup Last test execution time ----> Apr 07 2016 10:38:57 First test failure time -----> n/a Last test failure time ------> n/a Last test pass time ---------> Apr 07 2016 10:38:57 Total failure count ---------> 0 Consecutive failure count ---> 0 ___________________________________________________________________________ 23) TestL3VlanMet -------------------> . Error code ------------------> 0 (DIAG_SUCCESS) Total run count -------------> 1 Last test testing type ------> Bootup Last test execution time ----> Apr 07 2016 10:38:57 First test failure time -----> n/a Last test failure time ------> n/a Last test pass time ---------> Apr 07 2016 10:38:57 Total failure count ---------> 0 Consecutive failure count ---> 0 ___________________________________________________________________________ 24) TestIngressEgressSpan -----------> . Error code ------------------> 0 (DIAG_SUCCESS) Total run count -------------> 1 Last test testing type ------> Bootup Last test execution time ----> Apr 07 2016 10:38:58 First test failure time -----> n/a Last test failure time ------> n/a Last test pass time ---------> Apr 07 2016 10:38:58 Total failure count ---------> 0 Consecutive failure count ---> 0 ___________________________________________________________________________ 25) TestNetflowShortcut -------------> . Error code ------------------> 0 (DIAG_SUCCESS) Total run count -------------> 1 Last test testing type ------> Bootup Last test execution time ----> Apr 07 2016 10:38:59 First test failure time -----> n/a Last test failure time ------> n/a Last test pass time ---------> Apr 07 2016 10:38:59 Total failure count ---------> 0 Consecutive failure count ---> 0 ___________________________________________________________________________ 26) TestInbandEdit ------------------> . Error code ------------------> 0 (DIAG_SUCCESS) Total run count -------------> 1 Last test testing type ------> Bootup Last test execution time ----> Apr 07 2016 10:38:59 First test failure time -----> n/a Last test failure time ------> n/a Last test pass time ---------> Apr 07 2016 10:38:59 Total failure count ---------> 0 Consecutive failure count ---> 0 ___________________________________________________________________________ 27) TestFabricVlanLoopback ----------> . Error code ------------------> 0 (DIAG_SUCCESS) Total run count -------------> 1 Last test testing type ------> Bootup Last test execution time ----> Apr 07 2016 10:38:59 First test failure time -----> n/a Last test failure time ------> n/a Last test pass time ---------> Apr 07 2016 10:38:59 Total failure count ---------> 0 Consecutive failure count ---> 0 ___________________________________________________________________________ 28) TestTrafficStress ---------------> U Error code ------------------> 3 (DIAG_SKIPPED) Total run count -------------> 0 Last test testing type ------> n/a Last test execution time ----> n/a First test failure time -----> n/a Last test failure time ------> n/a Last test pass time ---------> n/a Total failure count ---------> 0 Consecutive failure count ---> 0 ___________________________________________________________________________ 29) TestL3TcamMonitoring ------------> U Error code ------------------> 3 (DIAG_SKIPPED) Total run count -------------> 0 Last test testing type ------> n/a Last test execution time ----> n/a First test failure time -----> n/a Last test failure time ------> n/a Last test pass time ---------> n/a Total failure count ---------> 0 Consecutive failure count ---> 0 ___________________________________________________________________________ 30) TestFibTcam ---------------------> U Error code ------------------> 3 (DIAG_SKIPPED) Total run count -------------> 0 Last test testing type ------> n/a Last test execution time ----> n/a First test failure time -----> n/a Last test failure time ------> n/a Last test pass time ---------> n/a Total failure count ---------> 0 Consecutive failure count ---> 0 ___________________________________________________________________________ 31) TestAclQosTcam ------------------> U Error code ------------------> 3 (DIAG_SKIPPED) Total run count -------------> 0 Last test testing type ------> n/a Last test execution time ----> n/a First test failure time -----> n/a Last test failure time ------> n/a Last test pass time ---------> n/a Total failure count ---------> 0 Consecutive failure count ---> 0 ___________________________________________________________________________ 32) TestEarlMemOnBootup -------------> . Error code ------------------> 0 (DIAG_SUCCESS) Total run count -------------> 1 Last test testing type ------> Bootup Last test execution time ----> Apr 07 2016 10:38:59 First test failure time -----> n/a Last test failure time ------> n/a Last test pass time ---------> Apr 07 2016 10:38:59 Total failure count ---------> 0 Consecutive failure count ---> 0 ___________________________________________________________________________ 33) TestAsicMemory ------------------> U Error code ------------------> 3 (DIAG_SKIPPED) Total run count -------------> 0 Last test testing type ------> n/a Last test execution time ----> n/a First test failure time -----> n/a Last test failure time ------> n/a Last test pass time ---------> n/a Total failure count ---------> 0 Consecutive failure count ---> 0 ___________________________________________________________________________ 34) TestEobcStressPing --------------> U Error code ------------------> 3 (DIAG_SKIPPED) Total run count -------------> 0 Last test testing type ------> n/a Last test execution time ----> n/a First test failure time -----> n/a Last test failure time ------> n/a Last test pass time ---------> n/a Total failure count ---------> 0 Consecutive failure count ---> 0 ___________________________________________________________________________ 35) TestFirmwareDiagStatus ----------> . Error code ------------------> 0 (DIAG_SUCCESS) Total run count -------------> 1 Last test testing type ------> Bootup Last test execution time ----> Apr 07 2016 10:38:59 First test failure time -----> n/a Last test failure time ------> n/a Last test pass time ---------> Apr 07 2016 10:38:59 Total failure count ---------> 0 Consecutive failure count ---> 0 ___________________________________________________________________________ 36) TestAsicSync --------------------> U Error code ------------------> 3 (DIAG_SKIPPED) Total run count -------------> 0 Last test testing type ------> n/a Last test execution time ----> n/a First test failure time -----> n/a Last test failure time ------> n/a Last test pass time ---------> n/a Total failure count ---------> 0 Consecutive failure count ---> 0 ___________________________________________________________________________ 37) TestUnusedPortLoopback: Port 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 ---------------------------------------------------------------- U U U U U U U U U U U U U U U U U U U U Error code ------------------> 3 (DIAG_SKIPPED) Total run count -------------> 0 Last test testing type ------> n/a Last test execution time ----> n/a First test failure time -----> n/a Last test failure time ------> n/a Last test pass time ---------> n/a Total failure count ---------> 0 Consecutive failure count ---> 0 ___________________________________________________________________________ 38) TestNonDisruptiveLoopback: Port 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 ---------------------------------------------------------------- U U U U U U U U U U U U U U U U U U U U Error code ------------------> 3 (DIAG_SKIPPED) Total run count -------------> 0 Last test testing type ------> n/a Last test execution time ----> n/a First test failure time -----> n/a Last test failure time ------> n/a Last test pass time ---------> n/a Total failure count ---------> 0 Consecutive failure count ---> 0 ___________________________________________________________________________ 39) TestFabricFlowControlStatus -----> U Error code ------------------> 3 (DIAG_SKIPPED) Total run count -------------> 0 Last test testing type ------> n/a Last test execution time ----> n/a First test failure time -----> n/a Last test failure time ------> n/a Last test pass time ---------> n/a Total failure count ---------> 0 Consecutive failure count ---> 0 ___________________________________________________________________________ 40) TestPortTxMonitoring: Port 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 ---------------------------------------------------------------- U U U U U U U U U U U U U U U U U U U U Error code ------------------> 3 (DIAG_SKIPPED) Total run count -------------> 0 Last test testing type ------> n/a Last test execution time ----> n/a First test failure time -----> n/a Last test failure time ------> n/a Last test pass time ---------> n/a Total failure count ---------> 0 Consecutive failure count ---> 0 ___________________________________________________________________________ 41) TestOBFL ------------------------> . Error code ------------------> 0 (DIAG_SUCCESS) Total run count -------------> 1 Last test testing type ------> Bootup Last test execution time ----> Apr 07 2016 10:38:59 First test failure time -----> n/a Last test failure time ------> n/a Last test pass time ---------> Apr 07 2016 10:38:59 Total failure count ---------> 0 Consecutive failure count ---> 0 ___________________________________________________________________________ Error code ------------------> 0 (DIAG_SUCCESS) Total run count -------------> 1 Last test testing type ------> Bootup Last test execution time ----> Apr 07 2016 10:38:59 First test failure time -----> n/a Last test failure time ------> n/a Last test pass time ---------> Apr 07 2016 10:38:59 Total failure count ---------> 0 Consecutive failure count ---> 0 ___________________________________________________________________________ 43) TestLtlFpoeMemoryConsistency ----> U Error code ------------------> 3 (DIAG_SKIPPED) Total run count -------------> 0 Last test testing type ------> n/a Last test execution time ----> n/a First test failure time -----> n/a Last test failure time ------> n/a Last test pass time ---------> n/a Total failure count ---------> 0 Consecutive failure count ---> 0 ___________________________________________________________________________ 44) TestRwEngineOverSubscription ----> U Error code ------------------> 3 (DIAG_SKIPPED) Total run count -------------> 0 Last test testing type ------> n/a Last test execution time ----> n/a First test failure time -----> n/a Last test failure time ------> n/a Last test pass time ---------> n/a Total failure count ---------> 0 Consecutive failure count ---> 0 ___________________________________________________________________________ 45) TestErrorCounterMonitor ---------> U Error code ------------------> 3 (DIAG_SKIPPED) Total run count -------------> 0 Last test testing type ------> n/a Last test execution time ----> n/a First test failure time -----> n/a Last test failure time ------> n/a Last test pass time ---------> n/a Total failure count ---------> 0 Consecutive failure count ---> 0 Error Records ---------------> n/a ___________________________________________________________________________ 46) TestVslBridgeLink ---------------> . Error code ------------------> 0 (DIAG_SUCCESS) Total run count -------------> 1 Last test testing type ------> Bootup Last test execution time ----> Apr 07 2016 10:38:59 First test failure time -----> n/a Last test failure time ------> n/a Last test pass time ---------> Apr 07 2016 10:38:59 Total failure count ---------> 0 Consecutive failure count ---> 0 ___________________________________________________________________________ 47) TestVslLocalLoopback: Port 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 ---------------------------------------------------------------- . . . . . . . . . . U U U U U U U U U U Error code ------------------> 0 (DIAG_SUCCESS) Total run count -------------> 1 Last test testing type ------> Bootup Last test execution time ----> Apr 07 2016 10:39:00 First test failure time -----> n/a Last test failure time ------> n/a Last test pass time ---------> Apr 07 2016 10:39:00 Total failure count ---------> 0 Consecutive failure count ---> 0 ___________________________________________________________________________ Port 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 ---------------------------------------------------------------- U U U U U . . U U U U U U U U U U U U U Error code ------------------> 0 (DIAG_SUCCESS) Total run count -------------> 2 Last test testing type ------> Health Monitoring Last test execution time ----> Apr 07 2016 12:06:26 First test failure time -----> n/a Last test failure time ------> n/a Last test pass time ---------> Apr 07 2016 12:06:26 Total failure count ---------> 0 Consecutive failure count ---> 0 ___________________________________________________________________________ 49) TestEARLInternalTables ----------> U Error code ------------------> 3 (DIAG_SKIPPED) Total run count -------------> 0 Last test testing type ------> n/a Last test execution time ----> n/a First test failure time -----> n/a Last test failure time ------> n/a Last test pass time ---------> n/a Total failure count ---------> 0 Consecutive failure count ---> 0 Total CC run count ----------> 0 Table size ------------------> 0 Total fail count ------------> 0 Total correction count ------> 0 Last completion time --------> Apr 07 2016 10:33:49 Last result -----------------> UNKNOWN Last fail count -------------> 0 Last correction count -------> 0 Last entries checked --------> 0 Consistency checker ---------> OFF Total CC run count ----------> 0 Table size ------------------> 0 Total fail count ------------> 0 Total correction count ------> 0 Last completion time --------> Apr 07 2016 10:33:49 Last result -----------------> UNKNOWN Last fail count -------------> 0 Last correction count -------> 0 Last entries checked --------> 0 Consistency checker ---------> OFF Total CC run count ----------> 0 Table size ------------------> 0 Total fail count ------------> 0 Total correction count ------> 0 Last completion time --------> Apr 07 2016 10:33:49 Last result -----------------> UNKNOWN Last fail count -------------> 0 Last correction count -------> 0 Last entries checked --------> 0 Consistency checker ---------> OFF Total CC run count ----------> 0 Table size ------------------> 0 Total fail count ------------> 0 Total correction count ------> 0 Last completion time --------> Apr 07 2016 10:33:49 Last result -----------------> UNKNOWN Last fail count -------------> 0 Last correction count -------> 0 Last entries checked --------> 0 Consistency checker ---------> OFF ___________________________________________________________________________ 50) TestNVRAMBatteryMonitor ---------> U Error code ------------------> 3 (DIAG_SKIPPED) Total run count -------------> 0 Last test testing type ------> n/a Last test execution time ----> n/a First test failure time -----> n/a Last test failure time ------> n/a Last test pass time ---------> n/a Total failure count ---------> 0 Consecutive failure count ---> 0 ___________________________________________________________________________ Port 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 ---------------------------------------------------------------- U U U U U U U U U U U U U U U U U U U U Error code ------------------> 3 (DIAG_SKIPPED) Total run count -------------> 0 Last test testing type ------> n/a Last test execution time ----> n/a First test failure time -----> n/a Last test failure time ------> n/a Last test pass time ---------> n/a Total failure count ---------> 0 Consecutive failure count ---> 0 ___________________________________________________________________________ Port 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 ---------------------------------------------------------------- U U U U U U U U U U U U U U U U U U U U Error code ------------------> 3 (DIAG_SKIPPED) Total run count -------------> 0 Last test testing type ------> n/a Last test execution time ----> n/a First test failure time -----> n/a Last test failure time ------> n/a Last test pass time ---------> n/a Total failure count ---------> 0 Consecutive failure count ---> 0 Consecutive microbursts count ---> 0 Last microburst event time ------> n/a Last microburst ports -----------> n/a Ingress Drop Count ----------> n/a Egress Drop Count -----------> n/a Ingress Drop Count ----------> n/a Egress Drop Count -----------> n/a Ingress Drop Count ----------> n/a Egress Drop Count -----------> n/a Ingress Drop Count ----------> n/a Egress Drop Count -----------> n/a Ingress Drop Count ----------> n/a Egress Drop Count -----------> n/a Ingress Drop Count ----------> n/a Egress Drop Count -----------> n/a Ingress Drop Count ----------> n/a Egress Drop Count -----------> n/a Ingress Drop Count ----------> n/a Egress Drop Count -----------> n/a Ingress Drop Count ----------> n/a Egress Drop Count -----------> n/a Ingress Drop Count ----------> n/a Egress Drop Count -----------> n/a Ingress Drop Count ----------> n/a Egress Drop Count -----------> n/a Ingress Drop Count ----------> n/a Egress Drop Count -----------> n/a Ingress Drop Count ----------> n/a Egress Drop Count -----------> n/a Ingress Drop Count ----------> n/a Egress Drop Count -----------> n/a Ingress Drop Count ----------> n/a Egress Drop Count -----------> n/a Ingress Drop Count ----------> n/a Egress Drop Count -----------> n/a Ingress Drop Count ----------> n/a Egress Drop Count -----------> n/a Ingress Drop Count ----------> n/a Egress Drop Count -----------> n/a Ingress Drop Count ----------> n/a Egress Drop Count -----------> n/a Ingress Drop Count ----------> n/a Egress Drop Count -----------> n/a ___________________________________________________________________________ 53) TestFEXFabricLinkStatus: Port 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 ---------------------------------------------------------------- U U U U U U U U U U U U U U U U U U U U Error code ------------------> 3 (DIAG_SKIPPED) Total run count -------------> 0 Last test testing type ------> n/a Last test execution time ----> n/a First test failure time -----> n/a Last test failure time ------> n/a Last test pass time ---------> n/a Total failure count ---------> 0 Consecutive failure count ---> 0 ___________________________________________________________________________
This example shows how to display the output for the health checks performed:
Router# show diagnostic health Non-zero port counters for 6/4 - Non-zero port counters for 6/5 -
How to Perform Memory Tests
Most online diagnostic tests do not need any special setup or configuration. However, the memory tests, which include the TestFibTcamSSRAM and TestLinecardMemory tests, have some required tasks and some recommended tasks that you should complete before running them.
Before you run any of the online diagnostic memory tests, perform the following tasks:
– Isolate network traffic by disabling all connected ports.
– Do not send test packets during a memory test.
– Reset the system before returning the system to normal operating mode.
-
Turn off all background health-monitoring tests using the
no diagnostic monitor module
number
test all
command.
How to Perform a Diagnostic Sanity Check
You can run the diagnostic sanity check in order to see potential problem areas in your network. The sanity check runs a set of predetermined checks on the configuration with a possible combination of certain system states to compile a list of warning conditions. The checks are designed to look for anything that seems out of place and are intended to serve as an aid for maintaining the system sanity.
To run the diagnostic sanity check, perform this task:
|
|
|
show diagnostic sanity
|
Runs a set of tests on the configuration and certain system states.
|
This example displays samples of the messages that could be displayed with the
show diagnostic sanity
command:
Router# show diagnostic sanity Pinging default gateway 10.6.141.1 .... Type escape sequence to abort. Sending 5, 100-byte ICMP Echos to 10.6.141.1, timeout is 2 seconds: Success rate is 0 percent (0/5) IGMP snooping disabled please enable it for optimum config. IGMP snooping disabled but RGMP enabled on the following interfaces, please enable IGMP for proper config : Vlan1, Vlan2, GigabitEthernet1/1 Multicast routing is enabled globally but not enabled on the following GigabitEthernet1/1, GigabitEthernet1/2 A programming algorithm mismatch was found on the device bootflash: Formatting the device is recommended. The bootflash: does not have enough free space to accomodate the crashinfo file. Please check your confreg value : 0x0. Please check your confreg value on standby: 0x0. The boot string is empty. Please enter a valid boot string . Could not verify boot image "disk0:" specified in the boot string on the Invalid boot image "bootflash:asdasd" specified in the boot string on the Please check your boot string on the slave. UDLD has been disabled globally - port-level UDLD sanity checks are The following ports have UDLD disabled. Please enable UDLD for optimum The following ports have an unknown UDLD link state. Please enable UDLD on both sides of the link: The following ports have portfast enabled: The following ports have trunk mode set to on: The following trunks have mode set to auto: The following ports with mode set to desirable are not trunking: The following trunk ports have negotiated to half-duplex: The following ports are configured for channel mode on: Gi1/1, Gi1/2, Gi1/3, Gi1/4 The following ports, not channeling are configured for channel mode The following vlan(s) have a spanning tree root of 32768: The following vlan(s) have max age on the spanning tree root different from The following vlan(s) have forward delay on the spanning tree root different The following vlan(s) have hello time on the spanning tree root different The following vlan(s) have max age on the bridge different from the The following vlan(s) have fwd delay on the bridge different from the The following vlan(s) have hello time on the bridge different from the The following vlan(s) have a different port priority than the default on the port gigabitEthernet1/1 The following ports have recieve flow control disabled: The following inline power ports have power-deny/faulty status: The following ports have negotiated to half-duplex: The following vlans have a duplex mismatch: The following interafaces have a native vlan mismatch: interface (native vlan - neighbor vlan) The value for Community-Access on read-only operations for SNMP is the same as default. Please verify that this is the best value from a security point The value for Community-Access on write-only operations for SNMP is the same as default. Please verify that this is the best value from a security point The value for Community-Access on read-write operations for SNMP is the same as default. Please verify that this is the best value from a security point
Tip For additional information about Cisco Catalyst 6500 Series Switches (including configuration examples and troubleshooting information), see the documents listed on this page:
http://www.cisco.com/en/US/products/hw/switches/ps708/tsd_products_support_series_home.html
Participate in the Technical Documentation Ideas forum
Feedback