Chapter 7
Troubleshooting
47
7
Troubleshooting
These procedures are intended to be used only during initial configuration, for the purpose of verifying that hardware
setup is successful. They are not intended to be used as troubleshooting procedures for configured systems using
production data and I/O.
USB CLI port connection
MSA 1060/2060/2062 controllers feature a CLI port employing a mini-USB Type B form factor. If you encounter
problems communicating with the port after cabling your computer to the USB device, you may need to either download
a device driver (Windows), or set appropriate parameters via an operating system command (Linux). See
the controller CLI port" on page
for more information. You may need to unplug and reconnect the CLI cable if the
terminal emulator application cannot access the COM port.
Fault isolation methodology
MSA 1060/2060/2062 controllers provide many ways to isolate faults. This section presents the basic methodology used
to locate faults within a storage system, and to identify the associated Field Replaceable Units (FRUs) affected.
As noted in
, use the SMU to configure and provision the system upon completing the
hardware installation. As part of this process, configure and enable event and/or alert notification so the system will
notify you when a problem occurs that is at or above the configured severity (as described in the Storage Management
Guide). With notifications configured and enabled, you can follow the recommended actions in the notification message
to resolve the problem, as further discussed in the options presented below.
Basic steps
The basic fault isolation steps are listed below and described in
"Performing basic steps" on the next page
l
Gather fault information, including using system LEDs.
l
Determine where in the system the fault is occurring.
l
Review event logs.
l
If required, isolate the fault to a data path component or configuration.
Cabling systems to enable use of the licensed Remote Snap feature—to replicate volumes—is another important fault
isolation consideration pertaining to initial system installation. See
"Isolating Remote Snap replication faults" on
for more information about troubleshooting during initial setup.
Options available for performing basic steps
When performing fault isolation and troubleshooting steps, select the option or options that best suit your site
environment. Use of any option (four options are described below) is not mutually exclusive to the use of another option.
You can use the SMU to check the health icons/values for the system and its components to ensure that everything is
okay, or to drill down to a problem component. If you discover a problem, both the SMU and the CLI provide
recommended action text online. Options for performing basic steps are listed according to frequency of use:
l
Monitor event or alert notification.
l
Use the SMU.
l
Use the CLI.
l
View the enclosure LEDs.
Monitor notifications
With notifications configured and enabled, you can view alerts or event logs to monitor the health of the system and its
components. Alerts inform the user of conditions requiring action to maintain availability and prevent potential loss of
data. Timely alert notification compels user acknowledgment via the SMU, leading to resolution. In contrast, events are