Chapter 3: Subsystem Connection
documentation by the hard drive manufacturers for performance
data.
When c
․
abling, follow all the Fibre channel specifications. Pay
․
se the drives with the same capacity not
only in the same logical drive but also in the whole configuration.
․
ation is supported, e.g., 150GB SAS
․
st drive that it is expected to replace. If the capacity
it is
a diameter of less than 76mm
(3 inches).
․
Route the cables away from places where it can be damaged by
other devices, e.g., fan exhaust.
․
Do not overtighten or bend the cables.
3.2
ort Infortrend’s EonPath multi-pathing
tomatically
lected for data distribution.
attention to signal quality and avoid electronic noise from
adjacent interfaces, e.g., do not lay power cords on optical
cables.
RAID arrays adopt the “least-common-denominator” approach.
The maximum capacity of each drive used in the array is the
maximum capacity of the smallest drive. Therefore, it is
suggested that you u
Mixing drives of different sizes and speeds can cause some
operation problems.
Tiered storage configur
drives in your RAID enclosure and 750GB SATA drives in
JBODs. However, you should not include SAS and SATA drives
in a single logical drive.
A spare drive should have a minimum capacity that is equivalent
to the large
of the spare is less than the capacity of the drive it is expected to
replace, the controller will not proceed with the failed drive
rebuilding.
When the configuration consists of multiple enclosures,
suggested that you use the new firmware function, “
Enclosure
Spare,
” instead of the “
Global Spare
,” to avoid a spare drive
participating in the rebuilding of drives in another enclosure.
․
When rack-mounting the subsystem, leave enough slack in the
cables so that they do not bend to
Sample
Topologies
The S12F subsystems supp
software. This software is necessary for controlling and optimizing the
access to logical drives via redundant host channel paths. With TPGS
support in the EonPath software, an optimal route is au
se
3-5
