beautypg.com

Troubleshooting, Cli port connection, Fault isolation methodology – HP P2000 G3 MSA Array Systems User Manual

Page 51: 7 troubleshooting, Gather fault information, Determine where the fault is occurring, Review the event logs, Isolate the fault, 7troubleshooting

background image

HP P2000 G3 FC MSA System User Guide

51

7

Troubleshooting

CLI port connection

P2000 G3 MSA System controllers feature a new 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

Connecting to the controller CLI port

for more information.

Fault isolation methodology

P2000 G3 MSA System controllers provide 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 disk 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.
The Log Collector utility allows customers to gather log information for use during support calls. See the

P2000 G3 Software Support/Documentation CD that ships with your product for details.

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.

This manual is related to the following products: