Physical Address
304 North Cardinal St.
Dorchester Center, MA 02124
Understanding CAN/CSA ISO/IEC 14776-326-16: SCSI Primary Commands for Modern Storage Systems
A comprehensive guide to the scope, technical requirements, and compliance considerations of the SPC-6 standard adopted by Canada
The CAN/CSA ISO/IEC 14776-326-16 standard, also known as SCSI Primary Commands (SPC-6), is the Canadian adoption of the international ISO/IEC 14776-326:2016 specification. This standard defines the fundamental command set for SCSI (Small Computer System Interface) storage devices, providing a consistent protocol for communication between hosts and peripherals such as hard disk drives, solid state drives, tape drives, and storage arrays. This article explores the scope, technical requirements, and compliance aspects of this critical standard.
1. Scope of CAN/CSA ISO/IEC 14776-326-16
The standard applies to all SCSI devices that implement the primary command set, regardless of the underlying transport layer (e.g., SAS, Fibre Channel, iSCSI, or SCSI over PCIe). SPC-6 establishes mandatory and optional commands that every SCSI target must support, including:
- Device identification and configuration via the
INQUIRYcommand - Data transfer commands:
READ(multiple variants),WRITE - Mode and log sense/select operations
- Command queuing and task management functions
- Error reporting through sense data and status codes
Tip: Developers implementing SPC-6 should pay special attention to the
INQUIRY response format. The standard mandates precise keyword compliance for Vital Product Data (VPD) pages such as the Device Identification page (page 83h). Malformed page data can cause interoperability failures even if all other commands work correctly. This standard replaces earlier editions (SPC-5 and prior) and adds new command descriptors and functionality that better support modern storage features, including zoned block devices, persistent reservations with enhanced capabilities, and extended sense data reporting.
2. Technical Requirements
2.1 Command Descriptor Blocks (CDBs)
Every SCSI command is encoded in a Command Descriptor Block (CDB) whose size and format depend on the operation. SPC-6 defines CDBs for all primary commands and extends the supported CDB sizes up to 260 bytes (variable-length CDBs). Table 1 summarises the key command categories with their mandatory status.
| Command Name | Opcode (Group) | Mandatory Status | Key Function |
|---|---|---|---|
| INQUIRY | 12h | Required | Return device identification and VPD data |
| READ (10) | 28h | Required | Read logical blocks from the medium |
| WRITE (10) | 2Ah | Required | Write logical blocks to the medium |
| MODE SENSE (10) | 5Ah | Required | Read device configuration parameters |
| REQUEST SENSE | 03h | Required | Retrieve sensed error information |
| TEST UNIT READY | 00h | Required | Check device readiness without data transfer |
| REPORT LUNS | A0h | Required (for multi-LUN targets) | List available logical units |
2.2 Sense Data and Error Handling
SPC-6 introduces a unified sense data format (fixed and descriptor) that provides up to 60 bytes of detailed error information, including field replaceable unit (FRU) codes and command-specific information. The standard adds 16 new sense key codes and over 200 additional additional sense code (ASC/ASCQ) pairs to cover scenarios such as:
- Logical block provisioning status (thin provisioning)
- Data protection violations (protection information)
- Timeout or unit attention cascades
Warning: While SPC-6 deprecates several older commands (e.g., MODE SELECT (6) variant), existing applications may still rely on them. Adopters should plan a transition strategy to avoid interoperability issues with legacy initiators that do not yet support the expanded error descriptors.
The standard also mandates support for the Extended COPY (XCOPY) command used in advanced offload operations. Implementations must correctly handle token management and segment descriptor formatting to ensure compatibility with SAN-based copy offload mechanisms.
3. Implementation Highlights
3.1 New and Enhanced Features in SPC-6
Compared to SPC-5, CAN/CSA ISO/IEC 14776-326-16 introduces the following improvements:
- Zoned Block Device (ZBD) support: New commands to manage zone state machines, report zones, and reset write pointers.
- Variable Length CDB improvements: Higher addressing and additional operation codes for future-proofing.
- Security protocol commands: Integration with TCG storage security standards (encrypted drives).
- Streamlined task management: Enhanced abort and reset functions that work over any SCSI transport.
Success: By adopting SPC-6, storage OEMs can support host-driven zoned namespaces and advanced error recovery without custom vendor-specific commands. This significantly improves interoperability across data centre ecosystems.
3.2 Conformance Profiles
The standard defines conformance profiles that allow products to claim compliance to subsets of the command set (e.g., “Basic Disk Profile” or “Enterprise Array Profile”). Each profile lists the mandatory and conditionally required commands. Developers should choose the profile that matches their product’s target use case to simplify certification.
4. Compliance and Certification
In Canada, compliance to CAN/CSA ISO/IEC 14776-326-16 is typically validated through the CSA certification process. Manufacturers and developers must:
- Implement the mandatory commands listed in the standard’s conformance matrix.
- Submit test results from an accredited test laboratory (e.g., UNH-IOL, or SCSI Trade Association test suites).
- Provide a conformance statement (ICS) detailing which optional commands and VPD pages are supported.
Critical: Non-conformance in
INQUIRY or MODE SENSE response formats is the most common cause of interoperability rejection during certification. During testing, carefully compare every byte of the response against the standard’s tables. Even a single reserved bit set to 1 can break host drivers. Beyond certification, the standard encourages manufacturers to participate in plugfests organised by the SCSI Trade Association to verify end-to-end interoperability with multiple host bus adapters and operating systems.
4.1 Certification Bodies
Recognised testing organizations for CAN/CSA ISO/IEC 14776-326-16 include CSA Group (Canada), Underwriters Laboratories (UL), and Intertek. All tests are based on the CSA version of the standard, which is identical in technical content to the ISO/IEC edition but includes national deviations if applicable.
Frequently Asked Questions
Q: Is CAN/CSA ISO/IEC 14776-326-16 identical to the international ISO/IEC 14776-326:2016?
A: Yes. The Canadian adoption is technically identical to the international standard. CSA may include a national foreword or annexes, but the technical requirements and command specifications are unchanged. Products certified to the ISO/IEC version are thus compliant with the Canadian edition as well.
A: Yes. The Canadian adoption is technically identical to the international standard. CSA may include a national foreword or annexes, but the technical requirements and command specifications are unchanged. Products certified to the ISO/IEC version are thus compliant with the Canadian edition as well.
Q: What is the main difference between SPC-6 (this standard) and earlier SPC-5?
A: SPC-6 adds support for zoned block devices (ZBD), introduces extended sense data descriptors, improves security protocol command integration, and deprecates several older CDB variants. Mandatory commands remain largely the same, so migration is manageable.
A: SPC-6 adds support for zoned block devices (ZBD), introduces extended sense data descriptors, improves security protocol command integration, and deprecates several older CDB variants. Mandatory commands remain largely the same, so migration is manageable.
Q: Do I need to support all optional commands to claim compliance?
A: No. Compliance is based on the chosen conformance profile. A device only needs to implement the mandatory commands for its profile. Optional commands can be omitted, but their omission must be clearly documented in the Implementation Conformance Statement (ICS).
A: No. Compliance is based on the chosen conformance profile. A device only needs to implement the mandatory commands for its profile. Optional commands can be omitted, but their omission must be clearly documented in the Implementation Conformance Statement (ICS).
Q: How can I test my implementation for free?
A: The SCSI Trade Association provides a reference test suite at no cost for members. Additionally, the open-source sg3_utils package can perform basic SPC-6 compliance checks. For official certification, involve an accredited laboratory.
A: The SCSI Trade Association provides a reference test suite at no cost for members. Additionally, the open-source sg3_utils package can perform basic SPC-6 compliance checks. For official certification, involve an accredited laboratory.