HP StorageWorks 2012sa Modular Smart Array user (488320-004, March 2013)
Table Of Contents
- Contents
- About This Guide
- 1
- System Components
- 2
- Installing and Cabling Enclosures
- 3
- Connecting Hosts
- 4
- Configuring a System for the First Time
- 5
- Troubleshooting
- Fault Isolation Methodology
- Correcting Enclosure IDs
- Using System LEDs to Diagnose Problems
- Is the front panel Fault ID amber?
- Is the controller back panel OK LED off?
- Is the controller back panel Fault/Service Required LED amber?
- Are both drive module LEDs, Online/Activity, and Fault/UID LEDs off?
- Is the drive module Fault/UID LED blinking amber?
- Is a connected port’s Host Link Status LED off?
- Is a connected port’s Expansion Port status LED off?
- Is a connected port’s Ethernet link status LED off?
- Is the power-and-cooling module AC Power Good LED off?
- Is the power-and-cooling module DC Voltage/Fan Fault/Service Required LED amber?
- Is the drive enclosure back panel OK LED off?
- Is the drive enclosure Fault/Service Required LED amber?
- Isolating a Host-Side Connection Fault
- Isolating a Controller Module Expansion Port Connection Fault
- Resolving Voltage and Temperature Warnings
- A
- Environmental Requirements and Specifications
- B
- Regulatory Compliance and Safety
- Index
54 HP 2012sa Modular Smart Array user guide • January 2013
When a fault occurs, the Fault ID status LED on an enclosure’s right ear (see
Figure 1-1) illuminates. Check the LEDs on the back of the enclosure to narrow the
fault to a FRU, connection, or both. The LEDs also help you identify the location of
a FRU reporting a fault.
Use SMU to verify any faults found while viewing the LEDs. SMU is also a good
tool to use in determining where the fault is occurring if the LEDs cannot be viewed
due to the location of the system. SMU provides you with a visual representation of
the system and where the fault is occurring. It can also provide more detailed
information about FRUs, data, and faults.
Review the Event Logs
The event logs record all system events. It is very important to review the logs, not
only to identify the fault, but also to search for events that might have caused the
fault to occur. For example, a host could lose connectivity to a virtual disk if a user
changes channel settings without taking the storage resources assigned to it into
consideration. In addition, the type of fault can help you isolate the problem to
hardware or software.
Isolate the Fault
Occasionally it might become necessary to isolate a fault. This is particularly true
with data paths due to the number of components the data path consists of. For
example, if a host-side data error occurs, it could be caused by any of the
components in the data path: controller module, cable, or data host.