This document discusses how to use the GOLD diagnostics online testing feature to identify possible hardware issues and capture the test output for Technical Support engineer review.
Online diagnostics are categorized as bootup, on-demand, schedule, or health monitoring diagnostics. Bootup diagnostics run during bootup, module Online Insertion and Removal (OIR), or switchover to a backup supervisor engine. On-demand diagnostics run from the Command Line Interface (CLI). Schedule diagnostics run at user-designated intervals or specified times when the switch is connected to a live network. Health-monitoring runs in the background.
This scenario displays examples using on-demand diagnostics to troubleshoot possible hardware failures and captures the test results for Technical Support review if a service request is required.
When a switch component exhibits symptoms of possible hardware failure, additional diagnostics tests should be performed to confirm the issue is hardware related and rule out other causes of the symptoms.
Some tests disrupt network activity, so it is important to verify that the test you run does not affect your current network traffic.
Runtime diagnostic checks can be run on demand or scheduled to run at a specific time. They can run continually in the background. When a module or supervisor exhibits failure symptoms or an error message is received, the test can usually be performed on demand.
Issuing a diagnostic start command triggers on-demand diagnostics tests statically. Specify how many times a test runs and whether to continue running the test upon failure detection. On-demand diagnostics is useful primarily as a troubleshooting tool to verify hardware functions when an administrator suspects a hardware fault.
On-demand diagnostics does not cause the faulty hardware to reset or power down the Cisco Catalyst 6500 series. Syslog messages warn about the faulty hardware, and the administrator needs to check the diagnostics results to see if the tests pass or fail, and then take appropriate action. As an example, this command triggers two on-demand module memory tests (test number 12) on a module in slot 2. If the first memory test fails, no further testing is performed, as shown:
Router#diagnostic ondemand iterations 2 Router#diagnostic ondemand action-on-failure stop Router#diagnostic start module 2 test ? Router#diagnostic start module 2 test 12
To display the test suite and the monitoring interval and test attributes for the module, issue the show diagnostic content command. This example shows how to display the test suite and the monitoring interval and test attributes:
Router# show diagnostic content module 1
Diagnostic Tests List for Module 1:
Diagnostics test suite attributes:
M/C/* - Minimal level test / Complete level test / Not applicable
B/* - Bypass bootup test / Not applicable
P/* - Per port test / Not applicable
D/N - Disruptive test / Non-disruptive test
S/* - Only applicable to standby unit / Not applicable
X/* - Not a health monitoring test / Not applicable
F/* - Fixed monitoring interval test / Not applicable
E/* - Always enabled monitoring test / Not applicable
A/I - Monitoring is active / Monitoring is inactive
Scheduled diagnostics tests run at either one specific time or periodically. This is useful when scheduling disruptive tests during maintenance windows. When failures are detected, appropriate syslog messages are displayed. Diagnostics results can be accessed by issuing the show diagnostic result command on the switch. Scheduled diagnostics does not cause the faulty hardware to reset or power down the Cisco Catalyst 6500 series. This CLI schedules a loopback test (test number 1) on a module situated in module 2 every Monday at 3 a.m., as shown:
Router(config)#diagnostic schedule module 2 test 1 weekly MON 03:00
Once testing is complete, capture the test results. If opening a Technical Support case, include the test results as a case attachment.