Table of Contents
Advertisement
Running device failure diagnostics
Running diagnostics can help you determine why access to a specific device becomes intermittent or why
the device becomes unavailable in your storage system.
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 diagnostics on the device causing problems by entering the following command:
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.
– serviceproc is the Service Processor.
– storage is an ATA, FC-AL, or SAS interface that has an attached disk shelf.
– toe is a TCP Offload Engine, a type of NIC.
• mb specifies that all the motherboard devices are to be tested.
• slot slotnum specifies that a device in a specific slot number is to be tested.
• -name device specifies a given device class and type.
Step 4.
View the status of the test by entering the following command:
Your storage system provides the following output while the tests are still running:
There are still test(s) being processed.
After all the tests are complete, the following response appears by default:
*> <SLDIAG:_ALL_TESTS_COMPLETED>
Step 5.
Identify any hardware problems by entering the following command:
devtype|mb|slotslotnum] [-name device] -long -state failed
Example
The following example shows how the full status of failures resulting from testing the FC-AL
adapter are displayed:
command starts special drivers designed specifically for
boot_diags
halt
boot_diags
sldiag device status
sldiag device status [-dev
.
Chapter 6
System level diagnostics
sldiag device
111
Advertisement
Table of Contents
