Physical Address
304 North Cardinal St.
Dorchester Center, MA 02124
Understanding CAN/CSA-ISO/IEC 14776-411: The SCSI Primary Commands – 2 Standard (SPC-2)
A Framework for Universal Storage Device Interoperability and Compliance
CAN/CSA-ISO/IEC 14776-411, also recognized globally as ISO/IEC 14776-411, defines the SCSI Primary Commands – 2 (SPC-2) standard. Adopted by the Canadian Standards Association (CSA), this standard remains a historical cornerstone for storage device manufacturers, system integrators, and compliance testing labs. It specifies the command set that is common to all SCSI logical units, providing the fundamental protocol rules that govern the behavior of device servers and application clients across multiple transport protocols.
Scope and Application of CAN/CSA-ISO/IEC 14776-411
The SPC-2 standard defines the primary command set for SCSI devices, forming the essential command layer above the SCSI Architecture Model (SAM-2, ISO/IEC 14776-412). It provides a universal protocol layer that is independent of the specific device type (disk, tape, media changer) and the physical transport (Parallel SCSI, Fibre Channel, SAS).
Adoption Note: CAN/CSA-ISO/IEC 14776-411-02 is the identical adoption of the international standard ISO/IEC 14776-411:1999. Its adoption under the CSA framework ensures that devices tested against this specification meet a recognized benchmark for interoperability in the Canadian and global markets.
The scope of this standard includes:
- Definition of common Command Descriptor Blocks (CDBs) used by all SCSI logical units.
- Specification of the behavior for device servers across all SCSI transports.
- Standardization of task management functions and data transfer protocols.
- Mandatory and optional primary commands required for compliance (e.g., INQUIRY, REPORT LUNS, TEST UNIT READY, REQUEST SENSE).
Core Technical Requirements and Command Architecture
SPC-2 establishes a rigorous command architecture that defines how application clients interact with device servers. The standard is structured around Command Descriptor Blocks (CDBs), which dictate the exact operation to be performed. The primary commands are categorized into mandatory and vendor-specific sets.
Primary Command Set
Any device claiming compliance with CAN/CSA-ISO/IEC 14776-411 must implement the mandatory primary commands. These commands form the minimum set required for basic discovery, configuration, and status reporting.
| Command | Opcode | Category | Description |
|---|---|---|---|
| INQUIRY | 12h | Mandatory | Requests detailed device parameters and VPD pages (e.g., Device Identification) |
| REPORT LUNS | A0h | Mandatory | Enumerates the logical units available on the target device |
| TEST UNIT READY | 00h | Mandatory | Polls the device to check if it is ready for data transfers |
| REQUEST SENSE | 03h | Mandatory | Retrieves the latest sense data describing a check condition |
| SEND DIAGNOSTIC | 1Dh | Mandatory | Initiates self-tests or diagnostic functions on the logical unit |
The INQUIRY command is arguably the most critical within SPC-2. It formalized the return of VPD (Vital Product Data) pages, such as the Device Identification page (page 83h), which was extensively standardized in SPC-2 to support robust persistent binding and storage area network management.
Implementation Caution: SPC-2 (14776-411) introduced stricter requirements for the INQUIRY data format compared to earlier SCSI-2 standards. Developers transitioning from legacy SCSI-2 to the SCSI-3 architecture must verify their Peripheral Device Type and Peripheral Qualifier field formatting against the SPC-2 logic block model.
Data Structures and Mode Pages
SPC-2 formalized the Mode Parameter Header, Mode Parameter Block Descriptor, and Mode Pages. Parameters such as the Disconnect-Reconnect mode page and the Control mode page were rigorously defined, providing a standardized method for SCSI initiators to control device settings, error recovery, and timeouts. The standard also introduced a formalized structure for Log Sense pages, enabling predictive failure analysis (PFA) in enterprise drives.
Implementation Highlights for Storage Systems
When implementing a SCSI device that claims compliance with ISO/IEC 14776-411, engineers must pay close attention to specific architectural layers:
- Device Server Model: The standard mandates a layered architecture where the device server manages contingencies, unit attention conditions, and error recovery. The peripheral device layer must interpret commands, manage state transitions, and report status accurately using the standard sense data format.
- Task Management: SPC-2 defines how tasks are managed across multiple transports. It specifies how to handle abort task, reset logical unit, and target reset functions, ensuring consistent behavior regardless of the physical transport layer.
- Transport Independence: Unlike later standards that leaned heavily on specific transports, SPC-2 was designed to be a purely logical command set. It was mapped effectively to FCP (Fibre Channel), SPI (Parallel SCSI), and early iSCSI implementations, making it a true bridge standard for the early 2000s.
Interoperability Benefit: Using the standardized INQUIRY VPD page 83h (Device Identification) from SPC-2 allows operating systems and storage arrays to uniquely identify a logical unit regardless of the physical connection path. This is foundational for preventing data corruption during multipath failover and persistent binding.
Compliance Notes and Conformance Testing
Compliance with CAN/CSA-ISO/IEC 14776-411 is typically verified through rigorous conformance testing, often performed by the SCSI Trade Association (STA) or independent labs like the University of New Hampshire InterOperability Laboratory (UNH-IOL). Key compliance aspects include:
- Mandatory vs. Optional: A strict distinction must be maintained between mandatory and optional commands. A device that fails to implement a mandatory command, such as REPORT LUNS or INQUIRY, cannot claim compliance with this standard.
- Concurrent Use: The standard specifies rules for handling multiple concurrent commands, including tagged command queuing, which is vital for maintaining performance and operational integrity in SSDs and HDDs.
- CSA Adoption: While CSA adoption (CAN/CSA-ISO/IEC 14776-411) does not typically add technical modifications to the ISO text, it provides a legal and technical anchor for regulatory approvals and procurement specifications in Canada. The technical content is identical to ISO/IEC 14776-411:1999.
Obsolescence Notice: SPC-2 (ISO/IEC 14776-411) has been superseded by later revisions of the SCSI Primary Commands standard (SPC-3, SPC-4, SPC-5). While the core concepts remain valid for understanding storage protocols, designers of new commercial systems should refer to the latest version of the standard (ISO/IEC 14776-414 or later) to ensure modern protocol requirements, such as extended CDBs and enhanced security, are met.
Frequently Asked Questions
Q: What is the primary technical difference between SPC-2 (ISO/IEC 14776-411) and the older SCSI-2 common command set?
A: SPC-2 is part of the SCSI-3 Architecture family. The critical difference is the strict adherence to a layered protocol model (SAM-2) that separates the primary commands from the transport protocol. SPC-2 also introduced standardized VPD pages (like page 83h for WWNs) and formalized the REPORT LUNS command, which were absent in the legacy SCSI-2 specification.
A: SPC-2 is part of the SCSI-3 Architecture family. The critical difference is the strict adherence to a layered protocol model (SAM-2) that separates the primary commands from the transport protocol. SPC-2 also introduced standardized VPD pages (like page 83h for WWNs) and formalized the REPORT LUNS command, which were absent in the legacy SCSI-2 specification.
Q: Does the CAN/CSA-ISO/IEC 14776-411 adoption contain any Canadian-specific modifications?
A: No, the Canadian adoption is intended to be an exact, identical adoption of the international standard ISO/IEC 14776-411:1999. The suffix in the CSA designation indicates the year of adoption. This allows Canadian procurers and manufacturers to reference a nationally recognized standard without requiring the original international specification document.
A: No, the Canadian adoption is intended to be an exact, identical adoption of the international standard ISO/IEC 14776-411:1999. The suffix in the CSA designation indicates the year of adoption. This allows Canadian procurers and manufacturers to reference a nationally recognized standard without requiring the original international specification document.
Q: Why is the INQUIRY command critical for demonstrating compliance with this standard?
A: The INQUIRY command is the primary discovery tool in SCSI. SPC-2 specifies exactly how a device must respond, including standard VPD pages. A compliant device must provide accurate data in the INQUIRY response to allow the host system to load the correct device driver and configure the LUN correctly. A failure in the INQUIRY response breaks the entire storage software stack.
A: The INQUIRY command is the primary discovery tool in SCSI. SPC-2 specifies exactly how a device must respond, including standard VPD pages. A compliant device must provide accurate data in the INQUIRY response to allow the host system to load the correct device driver and configure the LUN correctly. A failure in the INQUIRY response breaks the entire storage software stack.
— Article published in 2026. For current product development, please reference the active SCSI Primary Commands standard (e.g., ISO/IEC 14776-414).