Introduction to system‑level diagnostics
DG5000 System-level diagnostics provides a menu-driven interface for tests that search for and determine hardware problems on supported storage systems. You use system-level diagnostics to confirm that a specific component is operating properly or to help identify faulty components. DG5000 system-level diagnostics is specifically designed for DG5000 storage systems only.
You run system-level diagnostics after one of the following common troubleshooting situations:
- Initial system installation
- Addition or replacement of hardware components
- System panic caused by an unidentified hardware failure
- Access to a specific device becomes intermittent or the device becomes unavailable
To access system-level diagnostics for the storage system, you must directly connect to the serial console port of the storage system or access the serial console remotely via the Baseband Management Controller (BMC) of the storage system. Then, take over or halt the storage system to reach the LOADER prompt. Once at the LOADER prompt, enter the boot_diags command to start system-level diagnostics.
Scan system — Scan the system to obtain an accurate H/W inventory of the system for subsequent testing
Test system — Test specific components or the entire system for proper operation.
Show VPD information — Display vital product data (VPD) for components in the system.
Show FW revision — Display the firmware revisioninformation for components in the system.
Show MAC address — Display the unique MAC addresses allocated to components in the system.
Show logs — Display a recorded log of previousscan and test results.
Reboot (BMC power cycle) controller to LOADER — Exit system-level diagnostics and return to the LOADER prompt.
Scan system — Scan the system to obtain an accurate H/W inventory of the system for subsequent testing
Once a menu command is chosen, all output is displayed on the console session. Terminal session logging can be used to conveniently capture test results and other displayed information. In addition, system scans, system tests and memory tests are persistently logged on the boot media. The last ten results for each scan or test command are available for review.
If test results complete successfully, you can exit system-level diagnostics and reboot the system for normal operation. In the event of test failures, the test results will help technical support make appropriate recommendations. The failure could be resolved by reinstalling the FRU. If the failure cannot be resolved, then there is a likely hardware failure and the affected hardware must be replaced.