IBM 86655RY - Netfinity 7600 - 8665, Руководство по техническому обслуживанию аппаратной части

Страница: 216 / 294

206
Hardware Maintenance Manual: Netfinity 7600 – Type 8665 Models 1RY, 2RY
• Analyzes data from periodic internal measurements
• Recommends replacement when specific thresholds are exceeded
The data from periodic internal measurements is collected when data sectors are
accessed.
Data scrubbing performs the following operations:
• Forces all data sectors to be read
• Provides more data to improve the accuracy of PFA
The thresholds have been determined by examining the history logs of drives
that have failed in actual customer operation. When PFA detects a threshold
exceeded failure, the system administrator can be notified through Netfinity
Director. The design goal of PFA is to provide a minimum of 24 hours warning
before a drive experiences “catastrophic” failure.
2. A cable breaking, a component burning out, a solder connection failing, are all
examples of “on/off” unpredictable catastrophic failures. As assembly and
component processes have improved, these types of defects have been reduced
but not eliminated. PFA cannot always provide warning for on/off unpredictable
failures.
Device Event Table:
This table contains counters indicating the number of times
unexpected events were reported through the storage subsystem. These events may
be caused by several sources, including:
ServeRAID controller, Cables (external and internal), Connectors, Hot-Swap
Backplane(s), Hot-Swap Drive Trays, Target Devices (Disk Drives, CD-ROMs, etc.),
and SCSI Terminators.
The Device Event Table can be displayed using the IPSSEND program or the .
Using the IPSSEND program
Note: In the following command, replace
<controller>
with the ServeRAID
controller number.
At a command prompt, type the following:
ipssend getevent <controller> device
Frequently asked questions regarding the Device Event Table: In the
Device Event Table, what are hard events?: The hard event count entry in the device
event table is a count of events detected by the SCSI I/O processor since the Device
Event Table was last cleared. These events are usually not caused by the target device.
The controller processor can detect many types of events. Usually these events are
related to SCSI cabling, back planes or internal problems in the ServeRAID controller.
Hard events are usually not related to the hard drives or other SCSI devices that are
on the bus.
How should hard events be handled?: If you find a hard event entered into the Event log,
first check to see if there is a discernible pattern to the events in the device error table.
For example a large number of events on a particular drive or channel may indicate a
problem with the cabling or back plane for that particular drive, channel, etc. Always
check for cables being properly seated, bent pins, pushed pins, damaged cables and
proper termination. Before replacing the ServeRAID controller, replace the SCSI
cables followed by the back plane. If you have exhausted all other possibilities, then
replace the ServeRAID controller. Remember that the ServeRAID card is the least
likely item in the subsystem to cause hard events and the most expensive to replace.
In the Device Event Table what is the meaning of soft events?: The soft event entry in the
device error table is a count of the SCSI check conditions (other than unit attention)