FAS Systems

System-Level Diagnostics Guide

NetApp, Inc. Telephone: +1 (408) 822-6000 Part number: 215-05496_A0 ur001

495 East Java Drive Fax: +1 (408) 822-4501 November 2013
Sunnyvale, CA 94089 Support telephone: +1 (888) 463-8277
U.S. Web: www.netapp.com
Feedback: doccomments@netapp.com
 Table of Contents | 3

Contents
Introduction to systemlevel diagnostics .................................................... 4
Requirements for running system-level diagnostics ................................................... 5
How to use online command-line help ........................................................................ 6
Running system installation diagnostics ..................................................... 8
Running system panic diagnostics ............................................................ 12
Running slow system response diagnostics .............................................. 15
Running hardware installation diagnostics ............................................. 19
Running device failure diagnostics ........................................................... 23
Copyright information ............................................................................... 27
Trademark information ............................................................................. 28
How to send your comments ...................................................................... 29
Index ............................................................................................................. 30
4 | System-Level Diagnostics Guide

Introduction to systemlevel diagnostics

System-level diagnostics provides a command-line 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.
System-level diagnostics is available for supported storage systems only. Entering system-level
diagnostics at the command-line interface of unsupported storage systems generates an error
message.
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
System response time becomes sluggish
To run system-level diagnostics, you must already be running Data ONTAP because you need to
reach the Maintenance mode boot option in Data ONTAP. There are several approaches to get to
this option, but this is the recommended approach taken in the procedures documented in this guide.
Some hardware components in your system may require a specific approach, and this would be
documented in the applicable field replaceable unit flyer. This guide does not provide detailed
definitions of specific commands, subcommands, tests, or conditions. The na_sldiag(1) man page
describes the various commands and subcommands available for running system-level diagnostics.
Once the command is entered, the tests run in the background and the passed or failed outcome of the
tests is logged in the internal memory-based log, which has a fixed size. Some tests are utilities and
will simply state completed rather than passed or failed. After you run the appropriate tests, the
procedures documented in this guide help you generate status report. Once the test results show a
successful completion of system-level diagnostics, it is a recommended best practice to clear the log.
In the event of test failures, the status reports will help technical support make appropriate
recommendations. The failure could be resolved by re-installing a field-replaceable unit, by ensuring
cables are connected, or by enabling specific tests recommended by technical support and then re-
running those tests. If the failure cannot be resolved, then there is a hardware failure and the affected
hardware must be replaced.
There are no error messages that require further definitions or explanations.
 Introduction to systemlevel diagnostics | 5

Requirements for running system-level diagnostics

Depending on the system-level diagnostic tests you are running, you need to be aware of time and
system hardware requirements.
Each documented task has slight differences; use the recommended procedure for the task.
The following requirements must be met when running system-level diagnostics; otherwise, parts of
the tests fail and error messages appear in the status report:

General requirements
Each system being tested must be on a separate network.
The network interface test assigns unique static IP addresses, beginning with 172.25.150.23, to all
available network interfaces on a storage system. This results in network interface ports on
different storage controllers being assigned the same IP address. If all the systems being tested are
on the same network, then duplicate ip address warning messages appear on the connected
consoles. These warning messages do not affect the test results.

System memory requirements

You need to set aside time when running memory tests; the larger the memory capacity of your
storage system, the longer it takes.

NIC requirements
All adjacent network interface ports on the system must be connected for best performance using
a standard Ethernet cable.
Examples of adjacent ports are e0a and e0b or e2c and e2d.
Attention: e0M and e0P ports cannot be connected together due to an internal switch
connection. In systems with e0M and e0P ports, the most efficient pairings are e0M with e0a
and e0P with e0b.
If there are a number of network interface ports on the system, you may need to run the NIC
system-level diagnostic test several times, limiting each run to no more than two pairs each time.

SAS requirements
When running the SAS system-level diagnostic tests, adjacent SAS ports must be connected for
best performance; storage shelves must be disconnected from the ports.
Note: Connections between adjacent SAS ports is no longer a requirement for systems running
Data ONTAP 8.2; however, only the internal loopback test will be run for systems with
unconnected SAS ports.
6 | System-Level Diagnostics Guide

FC-AL requirements
When running the FC-AL system-level diagnostic tests, you must have loopback hoods on FC-
AL interfaces on the motherboard or expansion adapters for best performance; all other cables for
storage or Fibre Channel networks must be disconnected from the ports.
Note: While the use of loopback hoods on FC-AL interfaces are no longer requirements for
systems running Data ONTAP 8.2, the scope of the test coverage on the interface is also
reduced.

Interconnect requirements
Both platform controller modules in a dual controller system must be in Maintenance mode for
the interconnect system-level diagnostic test to run.
Attention: You will receive a warning message if you attempt to run the interconnect system-
level diagnostic test with other system-level diagnostic tests.

How to use online command-line help

You can get command-line syntax help from the command line by entering the name of the
command followed by help or the question mark (?).
The fonts or symbols used in syntax help are as follows:

keyword Specifies the name of a command or an option that must be entered as

shown.
< > (less than, greater Specify that you must replace the variable identified inside the symbols
than symbols) with a value.
| (pipe) Indicates that you must choose one of the elements on either side of the
pipe.
[ ] (brackets) Indicate that the element inside the brackets is optional.
{ } (braces) Indicate that the element inside the braces is required.

You can also type the question mark at the command line for a list of all the commands that are
available at the current level of administration (administrative or advanced).
The following example shows the result of entering the environment help command at the
storage system command line. The command output displays the syntax help for the environment
commands.

toaster> environment help

Usage: environment status |
[status] [shelf [<adapter>]] |
[status] [shelf_log] |
[status] [shelf_stats] |
 Introduction to systemlevel diagnostics | 7

[status] [shelf_power_status] |
[status] [chassis [all | list-sensors | Fan | Power | Temp | Power
Supply | RTC Battery | NVRAM4-temperature-7 | NVRAM4-battery-7]]
8 | System-Level Diagnostics Guide

Running system installation diagnostics

You run diagnostics after an initial system installation to identify the version of system-level
diagnostics and the supported devices on your storage system, and to verify that the installation is
successful and that all hardware is functioning properly.

Before you begin

Your storage system must already be running Data ONTAP.

Steps

1. At the storage system prompt, enter the following command to get to the LOADER prompt:
halt
2. On the node with the replaced component, enter the following command at the LOADER prompt:
boot_diags

Note: You must enter this command from the LOADER prompt for system-level diagnostics to
function properly. The boot_diags command starts special drivers designed specifically for
system-level diagnostics.

Important: During the boot_diags process, you might see the following prompts:

A prompt warning of a system ID mismatch and asking to override the system ID.
A prompt warning that when entering Maintenance mode in an HA configuration you must
ensure that the partner remains down.
You can safely respond y to these prompts.

The Maintenance mode prompt (*>) appears.

3. View the version of system-level diagnostics present on your storage system by entering the
following command:
sldiag version show
The version is displayed in the format System Level DiagnosticsX.nn.nn. The X is an
alpha reference and nn.nn are major and minor numeric references, respectively.
4. Identify the device types in your new system installation so that you know which components to
verify by entering the following command:
sldiag device types
Your storage system displays some or all of the following devices:
ata is an Advanced Technology Attachment device.
bootmedia is the system booting device.
 Running system installation diagnostics | 9

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.

5. Run all the default selected diagnostic tests on your storage system by entering the following
command:
sldiag device run

6. View the status of the test by entering the following command:

sldiag device status

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>

7. Verify that there are no hardware problems on your new storage system by entering the following
command:
sldiag device status -long -state failed

The example shows that the tests were run without the appropriate hardware:
10 | System-Level Diagnostics Guide

If the system- Then...

level diagnostics
tests...
Were completed There are no hardware problems and your storage system returns to the prompt.
without any
a. Clear the status logs by entering the following command:
failures
sldiag device clearstatus
b. Verify that the log is cleared by entering the following command:
sldiag device status
The following default response is displayed:

SLDIAG: No log messages are present.

c. Exit Maintenance mode by entering the following command:

halt
d. Enter the following command at the firmware prompt to reboot the storage system:
boot
You have completed system-level diagnostics.

Resulted in some Determine the cause of the problem.

test failures
a. Exit Maintenance mode by entering the following command:
halt
b. Perform a clean shutdown and disconnect the power supplies.
c. Verify that you have observed all the considerations identified for running system-
level diagnostics, that cables are securely connected, and that hardware
components are properly installed in the storage system.
d. Reconnect the power supplies and power on the storage system.
e. Repeat Steps 1 through 7 of Running system installation diagnostics.

Example
The following example shows how the full status of failures that occurred is displayed:

*> sldiag device status -long -state failed

TEST START ------------------------------------------

DEVTYPE: nvram_ib
NAME: external loopback test
START DATE: Sat Jan 3 23:10:55 GMT 2009

STATUS: Completed
 Running system installation diagnostics | 11

ib3a: could not set loopback mode, test failed

END DATE: Sat Jan 3 23:11:04 GMT 2009

LOOP: 1/1
TEST END --------------------------------------------

TEST START ------------------------------------------

DEVTYPE: fcal
NAME: Fcal Loopback Test
START DATE: Sat Jan 3 23:10:56 GMT 2009

STATUS: Completed
Starting test on Fcal Adapter: 0b
Started gathering adapter info.
Adapter get adapter info OK
Adapter fc_data_link_rate: 1Gib
Adapter name: QLogic 2532
Adapter firmware rev: 4.5.2
Adapter hardware rev: 2

Started adapter get WWN string test.

Adapter get WWN string OK wwn_str: 5:00a:098300:035309

Started adapter interrupt test

Adapter interrupt test OK

Started adapter reset test.

Adapter reset OK

Started Adapter Get Connection State Test.

Connection State: 5
Loop on FC Adapter 0b is OPEN

Started adapter Retry LIP test

Adapter Retry LIP OK

ERROR: failed to init adaptor port for IOCTL call

ioctl_status.class_type = 0x1

ioctl_status.subclass = 0x3

ioctl_status.info = 0x0
Started INTERNAL LOOPBACK:
INTERNAL LOOPBACK OK
Error Count: 2 Run Time: 70 secs
>>>>> ERROR, please ensure the port has a shelf or plug.
END DATE: Sat Jan 3 23:12:07 GMT 2009

LOOP: 1/1
TEST END --------------------------------------------
12 | System-Level Diagnostics Guide

Running system panic diagnostics

Running diagnostics after your storage system suffers a system panic can help you to identify the
possible cause of the panic.

Steps

1. At the storage system prompt, enter the following command to get to the LOADER prompt:
halt

2. On the node with the replaced component, enter the following command at the LOADER prompt:
boot_diags

Note: You must enter this command from the LOADER prompt for system-level diagnostics to
function properly. The boot_diags command starts special drivers designed specifically for
system-level diagnostics.

Important: During the boot_diags process, you might see the following prompts:

A prompt warning of a system ID mismatch and asking to override the system ID.
A prompt warning that when entering Maintenance mode in an HA configuration you must
ensure that the partner remains down.
You can safely respond y to these prompts.

The Maintenance mode prompt (*>) appears.

3. Run diagnostics on all the devices by entering the following command:
sldiag device run

4. View the status of the test by entering the following command:

sldiag device status
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, you receive the following default response:

*> <SLDIAG:_ALL_TESTS_COMPLETED>

5. Identify the cause of the system panic by entering the following command:
sldiag device status -long -state failed
The example shows that the tests were run without the appropriate hardware:
 Running system panic diagnostics | 13

If the system- Then...

level diagnostics
tests...
Were completed There are no hardware problems and your storage system returns to the prompt.
without any
a. Clear the status logs by entering the following command:
failures
sldiag device clearstatus
b. Verify that the log is cleared by entering the following command:
sldiag device status
The following default response is displayed:

SLDIAG: No log messages are present.

c. Exit Maintenance mode by entering the following command:

halt
d. Enter the following command at the firmware prompt to reboot the storage system:
boot
You have completed system-level diagnostics.

Resulted in some Determine the cause of the problem.

test failures
a. Exit Maintenance mode by entering the following command:
halt
b. Perform a clean shutdown and disconnect the power supplies.
c. Verify that you have observed all the considerations identified for running system-
level diagnostics, that cables are securely connected, and that hardware
components are properly installed in the storage system.
d. Reconnect the power supplies and power on the storage system.
e. Repeat Steps 1 through 5 of Running system panic diagnostics.

Example
The following example displays the full status of the failures that occurred:

*> sldiag device status -long -state failed

TEST START ------------------------------------------

DEVTYPE: nvram_ib
NAME: external loopback test
START DATE: Sat Jan 3 23:10:55 GMT 2009

STATUS: Completed
14 | System-Level Diagnostics Guide

ib3a: could not set loopback mode, test failed

END DATE: Sat Jan 3 23:11:04 GMT 2009

LOOP: 1/1
TEST END --------------------------------------------

TEST START ------------------------------------------

DEVTYPE: fcal
NAME: Fcal Loopback Test
START DATE: Sat Jan 3 23:10:56 GMT 2009

STATUS: Completed
Starting test on Fcal Adapter: 0b
Started gathering adapter info.
Adapter get adapter info OK
Adapter fc_data_link_rate: 1Gib
Adapter name: QLogic 2532
Adapter firmware rev: 4.5.2
Adapter hardware rev: 2

Started adapter get WWN string test.

Adapter get WWN string OK wwn_str: 5:00a:098300:035309

Started adapter interrupt test

Adapter interrupt test OK

Started adapter reset test.

Adapter reset OK

Started Adapter Get Connection State Test.

Connection State: 5
Loop on FC Adapter 0b is OPEN

Started adapter Retry LIP test

Adapter Retry LIP OK

ERROR: failed to init adaptor port for IOCTL call

ioctl_status.class_type = 0x1

ioctl_status.subclass = 0x3

ioctl_status.info = 0x0
Started INTERNAL LOOPBACK:
INTERNAL LOOPBACK OK
Error Count: 2 Run Time: 70 secs
>>>>> ERROR, please ensure the port has a shelf or plug.
END DATE: Sat Jan 3 23:12:07 GMT 2009

LOOP: 1/1
TEST END --------------------------------------------

After you finish

If the failures persist after repeating the steps, you need to replace the hardware.
 15

Running slow system response diagnostics

Running diagnostics can help you identify the causes of slow system response times.

Steps

1. At the storage system prompt, enter the following command to get to the LOADER prompt:
halt

2. On the node with the replaced component, enter the following command at the LOADER prompt:
boot_diags

Note: You must enter this command from the LOADER prompt for system-level diagnostics to
function properly. The boot_diags command starts special drivers designed specifically for
system-level diagnostics.

Important: During the boot_diags process, you might see the following prompts:

A prompt warning of a system ID mismatch and asking to override the system ID.
A prompt warning that when entering Maintenance mode in an HA configuration you must
ensure that the partner remains down.
You can safely respond y to these prompts.

The Maintenance mode prompt (*>) appears.

3. Run diagnostics on all the devices by entering the following command:
sldiag device run

4. View the status of the test by entering the following command:

sldiag device status

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>

5. Identify the cause of the system sluggishness by entering the following command:
sldiag device status -long -state failed

The example shows that the tests were run without the appropriate hardware:
16 | System-Level Diagnostics Guide

If the system- Then...

level diagnostics
tests...
Were completed There are no hardware problems and your storage system returns to the prompt.
without any
a. Clear the status logs by entering the following command:
failures
sldiag device clearstatus
b. Verify that the log is cleared by entering the following command:
sldiag device status
The following default response is displayed:

SLDIAG: No log messages are present.

c. Exit Maintenance mode by entering the following command:

halt
d. Enter the following command at the firmware prompt to reboot the storage system:
boot
You have completed system-level diagnostics.

Resulted in some Determine the cause of the problem.

test failures
a. Exit Maintenance mode by entering the following command:
halt
b. Perform a clean shutdown and disconnect the power supplies.
c. Verify that you observed all the requirements for running system-level diagnostics,
that cables are securely connected, and that hardware components are properly
installed in the storage system.
d. Reconnect the power supplies and power on the storage system.
e. Repeat Steps 1 through 5 of Running slow system response diagnostics.
 Running slow system response diagnostics | 17

If the system- Then...

level diagnostics
tests...
Resulted in the Technical support might recommend modifying the default settings on some of the tests
same test failures to help identify the problem.
a. Modify the selection state of a specific device or type of device on your storage
system by entering the following command:
sldiag device modify [-dev devtype|mb|slotslotnum] [-
name device] [-selection enable|disable|default|only]
-selection enable|disable|default|only allows you to enable,
disable, accept the default selection of a specified device type or named device, or
only enable the specified device or named device by disabling all others first.
b. Verify that the tests were modified by entering the following command:
sldiag option show
c. Repeat Steps 3 through 5 of Running slow system response diagnostics.
d. After you identify and resolve the problem, reset the tests to their default states
by repeating substeps 1 and 2.
e. Repeat Steps 1 through 5 of Running slow system response diagnostics.

Example
The following example pulls up the full status of failures that occurred:

*> sldiag device status -long -state failed

TEST START ------------------------------------------

DEVTYPE: nvram_ib
NAME: external loopback test
START DATE: Sat Jan 3 23:10:55 GMT 2009

STATUS: Completed
ib3a: could not set loopback mode, test failed
END DATE: Sat Jan 3 23:11:04 GMT 2009

LOOP: 1/1
TEST END --------------------------------------------

TEST START ------------------------------------------

DEVTYPE: fcal
NAME: Fcal Loopback Test
START DATE: Sat Jan 3 23:10:56 GMT 2009

STATUS: Completed
Starting test on Fcal Adapter: 0b
Started gathering adapter info.
Adapter get adapter info OK
18 | System-Level Diagnostics Guide

Adapter fc_data_link_rate: 1Gib

Adapter name: QLogic 2532
Adapter firmware rev: 4.5.2
Adapter hardware rev: 2

Started adapter get WWN string test.

Adapter get WWN string OK wwn_str: 5:00a:098300:035309

Started adapter interrupt test

Adapter interrupt test OK

Started adapter reset test.

Adapter reset OK

Started Adapter Get Connection State Test.

Connection State: 5
Loop on FC Adapter 0b is OPEN

Started adapter Retry LIP test

Adapter Retry LIP OK

ERROR: failed to init adaptor port for IOCTL call

ioctl_status.class_type = 0x1

ioctl_status.subclass = 0x3

ioctl_status.info = 0x0
Started INTERNAL LOOPBACK:
INTERNAL LOOPBACK OK
Error Count: 2 Run Time: 70 secs
>>>>> ERROR, please ensure the port has a shelf or plug.
END DATE: Sat Jan 3 23:12:07 GMT 2009

LOOP: 1/1
TEST END --------------------------------------------

After you finish

If the failures persist after repeating the steps, you need to replace the hardware.
 19

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.

Steps

1. As the node boots, interrupt the boot process by pressing Ctrl-C.

2. If the boot process was interrupted too late and the Boot Menu appeared, perform the following
steps:
a) Select the Maintenance mode option from the displayed menu.
b) After the system boots to Maintenance mode, enter the following command at the prompt:
halt

After you issue the command, wait until the system stops at the LOADER prompt.
Important: During the boot process, you might see the following prompts:

A prompt warning of a system ID mismatch and asking to override the system ID.
A prompt warning that when entering Maintenance mode in a HA configuration you
must ensure that the healthy node remains down.
You can safely respond y to these prompts.

3. On the node with the replaced component, enter the following command at the LOADER prompt:
boot_diags

Note: You must enter this command from the LOADER prompt for system-level diagnostics to
function properly. The boot_diags command starts special drivers designed specifically for
system-level diagnostics.

Important: During the boot_diags process, you might see the following prompts:

A prompt warning of a system ID mismatch and asking to override the system ID.
A prompt warning that when entering Maintenance mode in an HA configuration you must
ensure that the partner remains down.
You can safely respond y to these prompts.

The Maintenance mode prompt (*>) appears.

4. 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]
20 | System-Level Diagnostics Guide

-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.
slotslotnum specifies that a device in a specific slot number is to be tested.
-namedevice specifies a given device class and type.

5. View the status of the test by entering the following command:

sldiag device status

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>

6. Verify that no hardware problems resulted from the addition or replacement of hardware
components on your storage system by entering the following command:
sldiag device status [-dev devtype|mb|slotslotnum] [-name device] -long
-state failed

The example shows that the tests were run without the appropriate hardware:
 Running hardware installation diagnostics | 21

If the system- Then...

level diagnostics
tests...
Were completed There are no hardware problems and your storage system returns to the prompt.
without any
a. Clear the status logs by entering the following command:
failures
sldiag device clearstatus [-dev devtype|mb|slotslotnum]
b. Verify that the log is cleared by entering the following command:
sldiag device status [-dev devtype|mb|slotslotnum]
The following default response is displayed:

SLDIAG: No log messages are present.

c. Exit Maintenance mode by entering the following command:

halt
d. Enter the following command at the firmware prompt to reboot the storage system:
boot
You have completed system-level diagnostics.

Resulted in some Determine the cause of the problem.

test failures
a. Exit Maintenance mode by entering the following command:
halt
b. Perform a clean shutdown and disconnect the power supplies.
c. Verify that you have observed all the considerations identified for running system-
level diagnostics, that cables are securely connected, and that hardware
components are properly installed in the storage system.
d. Reconnect the power supplies and power on the storage system.
e. Repeat Steps 1 through 6 of Running hardware installation diagnostics.

Example
The following example pulls up the full status of failures resulting from testing a newly installed
FC-AL adapter:

*> sldiag device status -dev fcal -long -state failed

TEST START ------------------------------------------

DEVTYPE: fcal
NAME: Fcal Loopback Test
START DATE: Sat Jan 3 23:10:56 GMT 2009
22 | System-Level Diagnostics Guide

STATUS: Completed
Starting test on Fcal Adapter: 0b
Started gathering adapter info.
Adapter get adapter info OK
Adapter fc_data_link_rate: 1Gib
Adapter name: QLogic 2532
Adapter firmware rev: 4.5.2
Adapter hardware rev: 2

Started adapter get WWN string test.

Adapter get WWN string OK wwn_str: 5:00a:098300:035309

Started adapter interrupt test

Adapter interrupt test OK

Started adapter reset test.

Adapter reset OK

Started Adapter Get Connection State Test.

Connection State: 5
Loop on FC Adapter 0b is OPEN

Started adapter Retry LIP test

Adapter Retry LIP OK

ERROR: failed to init adaptor port for IOCTL call

ioctl_status.class_type = 0x1

ioctl_status.subclass = 0x3

ioctl_status.info = 0x0
Started INTERNAL LOOPBACK:
INTERNAL LOOPBACK OK
Error Count: 2 Run Time: 70 secs
>>>>> ERROR, please ensure the port has a shelf or plug.
END DATE: Sat Jan 3 23:12:07 GMT 2009

LOOP: 1/1
TEST END --------------------------------------------

After you finish

If the failures persist after repeating the steps, you need to replace the hardware.
 23

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.

Steps

1. At the storage system prompt, enter the following command to get to the LOADER prompt:
halt
2. On the node with the replaced component, enter the following command at the LOADER prompt:
boot_diags

Note: You must enter this command from the LOADER prompt for system-level diagnostics to
function properly. The boot_diags command starts special drivers designed specifically for
system-level diagnostics.

Important: During the boot_diags process, you might see the following prompts:

A prompt warning of a system ID mismatch and asking to override the system ID.
A prompt warning that when entering Maintenance mode in an HA configuration you must
ensure that the partner remains down.
You can safely respond y to these prompts.

The Maintenance mode prompt (*>) appears.

3. Run diagnostics on the device causing problems 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.
24 | System-Level Diagnostics Guide

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.
slotslotnum specifies that a device in a specific slot number is to be tested.
-namedevice specifies a given device class and type.

4. View the status of the test by entering the following command: sldiag device status
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>

5. Identify any hardware problems by entering the following command: sldiag device status
[-dev devtype|mb|slotslotnum] [-name device] -long -state failed

The example shows that the tests were run without the appropriate hardware:

If the system- Then...

level diagnostics
tests...
Resulted in some Determine the cause of the problem.
test failures
a. Exit Maintenance mode by entering the following command: halt
b. Perform a clean shutdown and disconnect the power supplies.
c. Verify that you have observed all the considerations identified for running system-
level diagnostics, that cables are securely connected, and that hardware components
are properly installed in the storage system.
d. Reconnect the power supplies and power on the storage system.
e. Repeat Steps 1 through 5 of Running device failure diagnostics.
 Running device failure diagnostics | 25

If the system- Then...

level diagnostics
tests...
Resulted in the Technical support might recommend modifying the default settings on some of the tests
same test failures to help identify the problem.
a. Modify the selection state of a specific device or type of device on your storage
system by entering the following command: sldiag device modify [-dev
devtype|mb|slotslotnum] [-name device] [-selection
enable|disable|default|only]
-selection enable|disable|default|only allows you to enable,
disable, accept the default selection of a specified device type or named device, or
only enable the specified device or named device by disabling all others first.
b. Verify that the tests were modified by entering the following command: sldiag
option show
c. Repeat Steps 3 through 5 of Running device failure diagnostics.
d. After you identify and resolve the problem, reset the tests to their default states
by repeating substeps 1 and 2.
e. Repeat Steps 1 through 5 of Running device failure diagnostics.

Were completed There are no hardware problems and your storage system returns to the prompt.
without any
a. Clear the status logs by entering the following command: sldiag device
failures
clearstatus [-dev devtype|mb|slotslotnum]
b. Verify that the log is cleared by entering the following command: sldiag
device status [-dev devtype|mb|slotslotnum]
The following default response is displayed:

SLDIAG: No log messages are present.

c. Exit Maintenance mode by entering the following command: halt

d. Enter the following command at the firmware prompt to reboot the storage system:
boot
You have completed system-level diagnostics.

Example
The following example shows how the full status of failures resulting from testing the FC-AL
adapter are displayed:

*> sldiag device status fcal -long -state failed

TEST START ------------------------------------------

26 | System-Level Diagnostics Guide

DEVTYPE: fcal
NAME: Fcal Loopback Test
START DATE: Sat Jan 3 23:10:56 GMT 2009

STATUS: Completed
Starting test on Fcal Adapter: 0b
Started gathering adapter info.
Adapter get adapter info OK
Adapter fc_data_link_rate: 1Gib
Adapter name: QLogic 2532
Adapter firmware rev: 4.5.2
Adapter hardware rev: 2

Started adapter get WWN string test.

Adapter get WWN string OK wwn_str: 5:00a:098300:035309

Started adapter interrupt test

Adapter interrupt test OK

Started adapter reset test.

Adapter reset OK

Started Adapter Get Connection State Test.

Connection State: 5
Loop on FC Adapter 0b is OPEN

Started adapter Retry LIP test

Adapter Retry LIP OK

ERROR: failed to init adaptor port for IOCTL call

ioctl_status.class_type = 0x1

ioctl_status.subclass = 0x3

ioctl_status.info = 0x0
Started INTERNAL LOOPBACK:
INTERNAL LOOPBACK OK
Error Count: 2 Run Time: 70 secs
>>>>> ERROR, please ensure the port has a shelf or plug.
END DATE: Sat Jan 3 23:12:07 GMT 2009

LOOP: 1/1
TEST END --------------------------------------------

After you finish

If the failures persist after repeating the steps, you need to replace the hardware.
 27

Copyright information
Copyright 19942013 NetApp, Inc. All rights reserved. Printed in the U.S.
No part of this document covered by copyright may be reproduced in any form or by any means
graphic, electronic, or mechanical, including photocopying, recording, taping, or storage in an
electronic retrieval systemwithout prior written permission of the copyright owner.
Software derived from copyrighted NetApp material is subject to the following license and
disclaimer:
THIS SOFTWARE IS PROVIDED BY NETAPP "AS IS" AND WITHOUT ANY EXPRESS OR
IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE,
WHICH ARE HEREBY DISCLAIMED. IN NO EVENT SHALL NETAPP BE LIABLE FOR ANY
DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE
GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER
IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR
OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF
ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
NetApp reserves the right to change any products described herein at any time, and without notice.
NetApp assumes no responsibility or liability arising from the use of products described herein,
except as expressly agreed to in writing by NetApp. The use or purchase of this product does not
convey a license under any patent rights, trademark rights, or any other intellectual property rights of
NetApp.
The product described in this manual may be protected by one or more U.S. patents, foreign patents,
or pending applications.
RESTRICTED RIGHTS LEGEND: Use, duplication, or disclosure by the government is subject to
restrictions as set forth in subparagraph (c)(1)(ii) of the Rights in Technical Data and Computer
Software clause at DFARS 252.277-7103 (October 1988) and FAR 52-227-19 (June 1987).
28 | System-Level Diagnostics Guide

Trademark information
NetApp, the NetApp logo, Network Appliance, the Network Appliance logo, Akorri,
ApplianceWatch, ASUP, AutoSupport, BalancePoint, BalancePoint Predictor, Bycast, Campaign
Express, ComplianceClock, Cryptainer, CryptoShred, CyberSnap, Data Center Fitness, Data
ONTAP, DataFabric, DataFort, Decru, Decru DataFort, DenseStak, Engenio, Engenio logo, E-Stack,
ExpressPod, FAServer, FastStak, FilerView, Flash Accel, Flash Cache, Flash Pool, FlashRay,
FlexCache, FlexClone, FlexPod, FlexScale, FlexShare, FlexSuite, FlexVol, FPolicy, GetSuccessful,
gFiler, Go further, faster, Imagine Virtually Anything, Lifetime Key Management, LockVault, Mars,
Manage ONTAP, MetroCluster, MultiStore, NearStore, NetCache, NOW (NetApp on the Web),
Onaro, OnCommand, ONTAPI, OpenKey, PerformanceStak, RAID-DP, ReplicatorX, SANscreen,
SANshare, SANtricity, SecureAdmin, SecureShare, Select, Service Builder, Shadow Tape,
Simplicity, Simulate ONTAP, SnapCopy, Snap Creator, SnapDirector, SnapDrive, SnapFilter,
SnapIntegrator, SnapLock, SnapManager, SnapMigrator, SnapMirror, SnapMover, SnapProtect,
SnapRestore, Snapshot, SnapSuite, SnapValidator, SnapVault, StorageGRID, StoreVault, the
StoreVault logo, SyncMirror, Tech OnTap, The evolution of storage, Topio, VelocityStak, vFiler,
VFM, Virtual File Manager, VPolicy, WAFL, Web Filer, and XBB are trademarks or registered
trademarks of NetApp, Inc. in the United States, other countries, or both.
IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of International Business
Machines Corporation in the United States, other countries, or both. A complete and current list of
other IBM trademarks is available on the web at www.ibm.com/legal/copytrade.shtml.
Apple is a registered trademark and QuickTime is a trademark of Apple, Inc. in the United States
and/or other countries. Microsoft is a registered trademark and Windows Media is a trademark of
Microsoft Corporation in the United States and/or other countries. RealAudio, RealNetworks,
RealPlayer, RealSystem, RealText, and RealVideo are registered trademarks and RealMedia,
RealProxy, and SureStream are trademarks of RealNetworks, Inc. in the United States and/or other
countries.
All other brands or products are trademarks or registered trademarks of their respective holders and
should be treated as such.
NetApp, Inc. is a licensee of the CompactFlash and CF Logo trademarks.
NetApp, Inc. NetCache is certified RealSystem compatible.
 29

How to send your comments

You can help us to improve the quality of our documentation by sending us your feedback.
Your feedback is important in helping us to provide the most accurate and high-quality information.
If you have suggestions for improving this document, send us your comments by email to
doccomments@netapp.com. To help us direct your comments to the correct division, include in the
subject line the product name, version, and operating system.
You can also contact us in the following ways:
NetApp, Inc., 495 East Java Drive, Sunnyvale, CA 94089 U.S.
Telephone: +1 (408) 822-6000
Fax: +1 (408) 822-4501
Support telephone: +1 (888) 463-8277
 30 | System-Level Diagnostics Guide

Index
C after device failures 23
after hardware installations 19
considerations after slow system responses 15
for running system-level diagnostics 5 after system installations 8
after system panics 12
system-level considerations for 5
D
device failures S
running diagnostics after 23
diagnostics slow system response
running after device failure 23 running diagnostics for 15
running after hardware installation 19 system-level diagnostics
running after slow system response 15 considerations for running 5
running after system installation 8 systems
running after system panic 12 running diagnostics after installation failures 8
running diagnostics after panics 12
running diagnostics for slow response 15
F
failures T
running diagnostics after device 23
troubleshooting
considerations for running system-level diagnostics
H 5
hardware installations device failures 23
running diagnostics after 19 hardware installations 19
slow system response 15
system installation 8
O system panics 12
online command-line help 6

R
running diagnostics