IBM ServeRAID, Справочник пользователя

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

F
fault tolerance. The ability of a computer system to
operate correctly even though one or more of its
component parts are malfunctioning.
firmware. Proprietary code that is usually delivered as
microcode as part of an operating system. Firmware is
more efficient than software loaded from an alterable
medium and more adaptable to change than pure
hardware circuitry. An example of firmware is the Basic
Input/Output System (BIOS) in read-only memory
(ROM) on a PC motherboard.
H
hot add. To add and configure a new ServeRAID
controller while the server is operational.
hot-spare drive. A physical drive that is defined for
automatic use when a similar drive fails.
hot-pluggable. Pertaining to a system in which
components can be added while the system is running.
hot-swappable. Pertaining to a component that can
be removed or replaced while the system is running.
hot-swap rebuild. An operation that is started by the
ServeRAID controller when it detects that a physical
drive that is part of an array and in the defunct state
has been removed and replaced on a SCSI cable or
backplane.
I
integrated RAID controller. An integrated SCSI
controller with RAID capabilities, such as the LSI 1020
and LSI 1030. These integrated RAID controllers are
standard features on some IBM xSeries servers; they
can be used to create a RAID level-1 logical drive from
two physical drives. A third physical drive can be used
as a hot-spare drive.
initialize logical drive. In the ServeRAID utilities, to
erase the first 1024 sectors on a drive, preventing
access to any data previously stored on the drive.
initiator identifiers. The SCSI initiator IDs assigned to
a cluster or failover pair.
IPSSEND command-line program. An advanced
command-line program that can be used to manage
your ServeRAID controllers. It can be used to configure
your controller, isolate and debug problems, recover
from errors, and to copy controller configurations from
one server to another.
L
logical drive. A grouping of physical drives that the
operating system recognizes as a single drive.
logical-drive migration. To add or remove physical
drives from an existing array, to change RAID levels,
change logical-drive size, or effect an increase in free
space.
M
merge-group number. In a clustering configuration,
the numbers that identify each logical drive. Non-shared
logical drives are assigned merge-group numbers of
either 206 or 207; shared logical drives need unique
merge-group numbers, so that they can be identified
even if they move to the other server.
merge-group state. In a clustering environment,
whether or not a logical drive is shared.
migrating. The state of a logical drive undergoing a
logical-drive migration.
mirror role. The role assigned to the two physical
drives that an integrated RAID controller uses to create
a RAID level-1 logical drive. When the logical drive is
created, data is copied from the primary physical drive
to the secondary physical drive. Any data on the
secondary drive is destroyed.
N
Notification Manager. A tool used to notify remote
systems of events, problems, and configuration changes
occurring on a local system.
O
offline. A logical-drive state in which the logical drive
is inaccessible.
okay. A logical-drive state in which the logical drive is
functional.
online. A physical-drive state in which the physical
drive is functioning properly and is part of an array.
P
partner name. In a cluster or failover pair, one of the
two controller names entered during configuration.
parity. The data stored on a RAID level-5, level-5E, or
level-50 logical drive that can be used, in conjunction
with the data on the remaining drives, to recreate a
failed physical drive’s data.
200
IBM ServeRAID: User’s Reference, Version 5.10