EasyManua.ls Logo

Dot Hill Systems 4524 - Troubleshooting; USB CLI Port Connection; Fault Isolation Methodology; Basic Steps

Default Icon
145 pages
Print Icon
To Next Page IconTo Next Page
To Next Page IconTo Next Page
To Previous Page IconTo Previous Page
To Previous Page IconTo Previous Page
Loading...
AssuredSAN 4004 Series Setup Guide 81
5Troubleshooting
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.
NOTE: For further troubleshooting help, after initial setup and when user data is present, contact Dot Hill
support as specified at https://crc.dothill.com
.
USB CLI port connection
AssuredSAN 4004 Series 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 Appendix D for more information.
Fault isolation methodology
AssuredSAN 4004 Series storage systems provide many ways to isolate faults. This section presents the
basic methodology used to locate faults within a storage system, and to identify the pertinent FRUs (Field
Replaceable Units) affected.
As noted in Basic operation on page 80, use the SMC or RAIDar to configure and provision the system
upon completing the hardware installation. As part of this process, configure and enable event notification
so the system will notify you when a problem occurs that is at or above the configured severity (see “Using
the Configuration Wizard > Configuring event notification” within the Storage Management Guide). With
event notification 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:
Gather fault information, including using system LEDs
(see Gather fault information on page 82)
Determine where in the system the fault is occurring
(see Determine where the fault is occurring on page 82)
Review event logs
(see Review the event logs on page 83)
If required, isolate the fault to a data path component or configuration
(see Isolate the fault on page 83)
Cabling systems to enable use of the licensed AssuredRemote feature—to replicate volumes—is another
important fault isolation consideration pertaining to initial system installation. See Isolating replication
faults on page 92 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 SMC or RAIDar 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, either the SMC or RAIDar, and the CLI provide recommended-action text online. Options for
performing basic steps are listed according to frequency of use:
Use the SMC or RAIDar

Table of Contents

Related product manuals