Table of Contents
Advertisement
When performing fault isolation and troubleshooting steps, select the option or options that best suit your site environment.
Use of any one of the following options is not mutually exclusive to the use of another option. The order for the options is
based on frequency of use.
To identify 5U enclosure fault conditions:
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, moving from most severe 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 command line interface (CLI). If you discover a problem, review the CLI for any recommended actions.
4. Visually inspect front panel fault LEDs, then locate component fault LEDs, based on LED-identified general location. If a
hardware issue prevents access to the CLI, it is the only option available.
Table 6 5U enclosure non-fault conditions
Symptom
Operator's panel area LEDs, no fault conditions
System power, system ID, and host connectivity LEDs
with no module, logical, or drawer fault LEDs
Drawer panel LEDs, no fault conditions
Drawer power and sideplane OK LED
Drawer data activity bar
Drive module LEDs, no fault conditions
Amber flashing LED: 1 second on, 1 second off
Controller or expansion module LEDs, no fault conditions
LEDs other than:
-IOM amber fault LEDs
-SAS port amber fault LEDs
FCM LEDs, no fault conditions
FCM OK amber LED flashing
PSU LEDs, no fault conditions
PSU OK amber LED flashing
Isolate hardware and connectivity faults
You may occasionally have to isolate a fault related to the enclosure hardware or related to data connections associated with
the 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 on the host side, such as a faulty host bus adapter (HBA) or switch. It could be on the
enclosure side, such as a faulty input/output module (IOM), cable, or connector. It also could be a failure involving more than
one of these components.
Gather common installation hardware fault information and isolate the fault using the identified procedure.
66 Chapter 8 Hardware installation and configuration issues
Cause
System functioning properly
System functioning properly
Drive unit identification (UID) bit is set
System likely functioning properly
FCM is in standby mode
PSU is in standby mode
Recommended Action
No action required.
No action required.
No action required.
Often, no action required. See
SAS 12Gb/s expansion input/output
module LEDs" on page
55.
No action required.
No action required.
"Interpret
Advertisement
Table of Contents
