Seagate Ultra 160, Руководство по эксплуатации продукта

Страница: 17 / 186

Parallel SCSI Interface Product Manual, Rev. A 3
1.1.2 Applicable standards
The following ANSI standards should be referenced for more details about SCSI system standards of opera-
tion:
• SCSI Architecture Model - 4 (SAM-4), T10/1683-D
• SCSI Enclosure Services - 2 (SES-2), T10/1559-D
• SCSI Block Commands - 3 (SBC-3), T10/1215-D
• SCSI Primary Commands - 4 (SPC-4), T10/1731-D
• SCSI Enhanced Parallel Interface (EPI), T10/1143-DT
• SCSI Parallel Interface (SPI-5), T10/1525D
• SCSI Medium Changer Commands - 3 (SMC-3), T10/1730-D
• SCSI Controller Command Set - 2 (SCC-2), T10/1225D
• SCSI Stream Command - 3 (SSC-3), T10/1611-D
1.2 General interface description
This Parallel SCSI Interface Manual describes the Seagate Technology LLC. subset of the SCSI (Small Com-
puter Systems Interface) as implemented on the Seagate-built drives. The interface is compatible with the
SCSI Interface Specifications listed in Section 1.1.2. The drives covered by this manual are classified as “Intel-
ligent” peripherals.
The Seagate SCSI interface described herein consists of a 9 or 18 bit bidirectional data bus (includes bits for
parity checking and enabling CRC protection), plus 9 control signals. The SCSI interface supports multiple ini-
tiators, disconnect/reconnect, self-configuring host software, automatic features that relieve the host from the
necessity of knowing the physical architecture of the target (logical block addressing is used), and some other
miscellaneous features.
The SCSI physical interface uses either single-ended drivers and receivers or low voltage differential drivers
and receivers and uses asynchronous or synchronous communication protocols. The bus interface transfer
rate for asynchronous or synchronous is given in individual drive’s Product Manual. The bus protocol supports
multiple initiators, disconnect/reconnect, additional messages plus 6-byte, 10-byte, 12-byte, 16-byte and vari-
able length Command Descriptor Blocks.
Unless specified otherwise in the individual drive’s Product Manual, the drive is always a SCSI target port, and
never a SCSI initiator port. For certain commands, which may or may not be supported by a particular drive
model, the drive must act as a SCSI initiator port, but does not otherwise do so. For purposes of this specifica-
tion, “drive” may be substituted for the word “target” wherever “target” appears.
In the event of a conflict between this document and ANSI SCSI documents, the requirements of the ANSI doc-
uments shall apply.
Note. In this revision, some new terminology is introduced as taken from the ANSI specifications. In many
instances, the broader scope terms such as “initiator” and “target” are not used, but rather the more
specific terms “Application Client” and “Device Server” appear. In Figure 2, it can be seen that several
“application clients” from a single initiator may have one or more tasks in queue with several “device
servers” in a single target. A drive could be a SCSI target port or it could be one of the device servers
as part of some larger entity. When reading the description, one needs to be able to put the drive of
interest in the proper context in terms of what is shown in Figure 2. For a proper understanding of the
operation of the SCSI protocol, the terms in the SCSI architectural model as described in ANSI specifi-
cation T10/1683-D (SAM-4) should be well understood before reading operation descriptions in any
SCSI document. Although a Glossary of terms is provided herein, the definitions may not be adequate
for some. The SAM-4 specification gives a more detailed understanding of some of the new SCSI ter-
minology