HP 2000SA G2-Modular-Smart-Array - Manual (Page 51)

HP 2000sa G2 Modular Smart Array User Guide 51
8 Troubleshooting
Fault isolation methodology
The 2000sa G2 Modular Smart Array storage system provides many ways to isolate faults within the
system. This section presents the basic methodology used to locate faults and the associated FRUs (Field
Replaceable Units).
The basic fault isolation steps are:
• Gather fault information, including using system LEDs
• Determine where in the system the fault is occurring
• Review event logs
• If required, isolate the fault to a data path component or configuration
Gather fault information
When a fault occurs, it is important to gather as much information as possible. Doing so will help you
determine the correct action needed to remedy the fault.
Begin by reviewing the reported fault. Is the fault related to an internal data path or an external data path?
Is the fault related to a hardware component such as a drive module, controller module, or power supply?
By isolating the fault to one of the components within the storage system, you will be able to determine the
necessary action more rapidly.
Determine where the fault is occurring
Once you have an understanding of the reported fault, review the enclosure LEDs. The enclosure LEDs are
designed to alert users of any system faults, and might be what alerted the user to a fault in the first place.
When a fault occurs, the Fault ID status LED on an enclosure’s right ear (see
Front panel components on
page 17) 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 comprising the data path. 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.
If the enclosure does not initialize
It may take up to two minutes for the enclosures to initialize. If the enclosure does not initialize:
• Perform a rescan.
• Power cycle the system.
• Make sure the power cord is properly connected, and check the power source that it is connected to.
• Check the event log for errors.