Physical Address
304 North Cardinal St.
Dorchester Center, MA 02124
Understanding ISO/IEC 14776-351:2007 – The SCSI-3 Architecture Model (SAM-3)
A comprehensive guide to the architectural framework for SCSI devices and protocols
Scope and Purpose
The Small Computer System Interface (SCSI) family of standards has been instrumental in shaping modern storage architectures. Among them, ISO/IEC 14776-351:2007 (also adopted as CAN/CSA-ISO/IEC 14776-351:07) defines the SCSI-3 Architecture Model (SAM-3). This standard establishes a comprehensive framework for the interaction of SCSI devices, covering command sets, task management, service delivery subsystems, and transport protocol bindings.
SAM-3 is the foundation upon which all SCSI command standards (e.g., SPC-3, SBC-3) and transport protocols (e.g., FCP, SAS) are built. It ensures interoperability by prescribing clear roles for initiators (requesters of I/O operations) and targets (responders that execute commands). The model also introduces the concept of a device server and a task manager within each target, decoupling command execution from the specifics of the physical interconnect.
Tip: Use the layered architecture of SAM-3 to design modular SCSI implementations. Changes in transport technology do not require rework of the core command handling logic.
Technical Requirements and Architecture
Layered Model
SAM-3 organizes SCSI communication into distinct functional layers:
| Layer | Function | Examples |
|---|---|---|
| Application Layer | Defines command sets, data formats, and status reporting. | SCSI Primary Commands (SPC), SCSI Block Commands (SBC) |
| Transport Layer | Provides reliable delivery of commands, data, and status across the interconnect. | Fibre Channel Protocol (FCP), Serial Attached SCSI (SAS) |
| Interconnect Layer | Specifies electrical, signaling, and physical connection characteristics. | Parallel SCSI, SAS cables, Fibre Channel optics |
Command and Task Management
Each command issued by an initiator becomes a task within the target. SAM-3 defines task attributes (simple, ordered, head-of-queue, and automatic contingent allegiance) that govern the order of execution. The task manager is responsible for handling task sets and performing management functions such as reset, abort, and clear operations. The model also specifies the behavior of an initiator and target across multiple concurrent I/O processes, ensuring consistency in error recovery.
Device Server and Task Router
A target contains one or more device servers, each responsible for processing tasks assigned to a given logical unit. The task router routes incoming commands to the appropriate device server. SAM-3 mandates that all device servers adhere to the same command set architecture, although individual logical units may support different command sets (e.g., disk vs. tape).
Warning: Non‑compliance with the task ordering and contingent allegiance rules can lead to data corruption and unpredictable behavior. Always follow the prescribed attribute precedence.
Implementation and Compliance
Implementation Highlights
When building a SCSI device, developers should leverage SAM-3’s building block approach. For example, the layered separation allows a designer to implement a new transport protocol (e.g., NVMe over Fabrics SCSI translation) without altering the command server code. The standard also provides conformance clauses for both initiators and targets, covering mandatory, optional, and conditional requirements. Key mandatory aspects include support for certain task management functions and proper handling of the auto-contingent allegiance (ACA) condition.
Success: Products that achieve full conformance to SAM-3 demonstrate high interoperability across diverse SCSI implementations, reducing validation cycles and market friction.
Compliance Notes
Compliance with ISO/IEC 14776-351:2007 is typically assessed through a combination of protocol analysis and functional testing. The standard references several normative documents, including ISO/IEC 14776-311 (SAM-2) for legacy context and ISO/IEC 14776-312 (SAM-4) for later revisions. Certification programs often require a device to pass an integrated test suite covering command interlocking, task attribute sequencing, and error recovery scenarios.
Manufacturers should pay special attention to the SCSI Primary Commands (SPC-3) conformance as it builds directly upon SAM-3. Additionally, when adopting the standard in a specific region, local adoptions (e.g., the Canadian CSA version) may include minor deviations or additional guidance.
Caution: Implementing proprietary task manager extensions can result in a device that fails interoperability testing. Always refer to the latest ISO/IEC 14776 series updates for backward compatibility.
Frequently Asked Questions
Q: What is the primary purpose of SAM-3?
A: SAM-3 defines the generic architecture for SCSI devices, ensuring consistent command handling and task management across various transport protocols and device types.
A: SAM-3 defines the generic architecture for SCSI devices, ensuring consistent command handling and task management across various transport protocols and device types.
Q: Is ISO/IEC 14776-351:2007 still current?
A: No, it has been superseded by SAM-4 (ISO/IEC 14776-312) and the later SAM-5 (ISO/IEC 14776-313). However, many legacy devices still reference SAM-3, and understanding it is essential for backward compatibility.
A: No, it has been superseded by SAM-4 (ISO/IEC 14776-312) and the later SAM-5 (ISO/IEC 14776-313). However, many legacy devices still reference SAM-3, and understanding it is essential for backward compatibility.
Q: How does SAM-3 relate to Fibre Channel or SAS standards?
A: SAM-3 provides the model for command set interaction. Fibre Channel Protocol (FCP) and Serial Attached SCSI (SAS) implement the transport layer that maps SCSI commands to the respective interconnect.
A: SAM-3 provides the model for command set interaction. Fibre Channel Protocol (FCP) and Serial Attached SCSI (SAS) implement the transport layer that maps SCSI commands to the respective interconnect.
Q: What are the consequences of non‑compliance with SAM-3?
A: Non‑compliant devices may experience interoperability failures, inability to participate in mixed-vendor configurations, and potential data integrity issues during error recovery.
A: Non‑compliant devices may experience interoperability failures, inability to participate in mixed-vendor configurations, and potential data integrity issues during error recovery.
© 2026 Standards Publication. This article is provided for informational purposes and does not replace the official standard text.