Table of Contents
Advertisement
If the system-level diagnostics tests...
After you finish
If the failures persist after repeating the steps, you need to replace the hardware.
Running hardware installation diagnostics
You run diagnostics after adding or replacing hardware components in your storage system to verify that the
component has no problems and that the installation is successful.
Step 1.
At the storage system prompt, switch to the LOADER prompt:
Step 2.
Enter the following command at the LOADER prompt:
Note: You must run this command from the LOADER prompt for system-level diagnostics to
function properly. The
system-level diagnostics.
Step 3.
Run the default tests on the particular device you added or replaced by entering the following
command:
sldiag device run [-dev devtype|mb|slotslotnum] [-name device]
• -dev devtype specifies the type of device to be tested.
– ata is an Advanced Technology Attachment device.
– bootmedia is the system booting device.
– cna is a Converged Network Adapter not connected to a network or storage device.
– env is motherboard environmentals.
– fcache is the Flash Cache adapter, also known as the Performance Acceleration Module 2.
– fcal is a Fibre Channel-Arbitrated Loop device not connected to a storage device or Fibre
Channel network.
– fcvi is the Fiber Channel Virtual Interface not connected to a Fibre Channel network.
– interconnect or nvram-ib is the high-availability interface.
– mem is system memory.
– nic is a Network Interface Card not connected to a network.
– nvram is nonvolatile RAM.
– nvmem is a hybrid of NVRAM and system memory.
– sas is a Serial Attached SCSI device not connected to a disk shelf.
ThinkSystem DM3000x and DM5000x Hardware Installation and Maintenance Guide
108
command starts special drivers designed specifically for
boot_diags
Then...
specified device or named device by
disabling all others first.
2. Verify that the tests were modified by
entering the following command:
option show
3. Repeat Steps 3 through 5 of Running slow
system response diagnostics.
4. After you identify and resolve the problem,
reset the tests to their default states by
repeating substeps 1 and 2.
5. Repeat Steps 1 through 5 of Running slow
system response diagnostics.
halt
boot_diags
sldiag
Advertisement
Table of Contents
