Isolate Hardware And Connectivity Faults; Table 3 Non-Fault Conditions - Seagate Exos CORVAULT Hardware Installation And Maintenance Manual

1. Monitor event and alert notifications through your host system interface.
a. Event notifications: The system event logs record all system events and identifies the event type and its severity.
b. Alert notifications: An alert reports a system fault, registers the type and severity, then tracks its resolution.
2. Alerts fall into three categories, listed in order of severity. Resolve them, starting with most severe and moving to
least severe.
a. Critical alerts: Such alerts require immediate resolution, since they may cause a controller module to shut down or
place data at risk.
b. Warnings: Such alerts require immediate attention so you can evaluate the problem and correct it.
c. Informational alerts: Such alerts neither require immediate attention nor immediate action.
3. Use the Storage Management Console (SMC). You can use the SMC to monitor the health icons or values for the
system and its components, to make sure that everything is functioning properly, or to locate a problem component.
4. Use the command line interface (CLI). If you discover a problem, review both the SMC and the CLI for any
recommended actions.
5. Visually inspect the front panel fault LEDs, then locate the component fault LEDs, based on general location
identified through the front panel. If a hardware issue prevents access to the SMC or CLI, this is the only option
available.

Table 3 Non-fault conditions

Symptom
Front panel LEDs, no fault conditions
System power, system ID, and host connectivity
LEDs with no fault condition LEDs
Disk drive module LEDs, no fault conditions
Amber flashing LED: 1 second on, 1 second off
Amber flashing LED: 3 seconds on, 1 off
l
Green LED flickers
l
PSU LEDs, no fault conditions
Green LED on
Controller module LEDs, no fault conditions
LEDs other than Hardware fault LED

Isolate hardware and connectivity faults

You may occasionally have to isolate a fault related to the storage enclosure hardware or related to data connections
associated with the storage enclosure. This is particularly true with data paths because of the number of components
involved along the data path and the complexity of the interactions. For example, if a host-side data error occurs, it
could be caused by any of the involved hardware components: it could be a faulty host bus adapter (HBA) or a faulty
58 Chapter 6 Hardware installation and configuration issues
Cause
System functioning properly
Disk drive module
reconstruction
Disk drive module
identification
AC power is present, PSU
functioning normally
System likely functioning
properly
Recommended Action
No action required.
No action required.
CAUTION Do not remove a disk drive module
during reconstruction, since that would terminate the
current operation and result in data loss.
No action required.
No action required.
Often, no action required. Refer to
module LEDs" on page 50
or
faults" on the facing page
.
"Interpret controller
"Isolate system application