Teledyne SAS User Manual

Protocol Solutions Group

3385 Scott Blvd., Santa Clara, CA 95054
Tel: [phone]
Fax: [phone]

SAS Verification Test Descriptions

June 2010

Table of Contents
SAS Link and Transport Layer Test Suite 2
SAS 2.0 Speed Negotiation 137
NACA Test 186

SERIAL ATTACHED SCSI

(SAS) CONSORTIUM

SAS Test Suite for CATC Test Script Project

Version 0.13

Technical Document

Last Updated: 12 July 2005 7/12/05

Serial Attached SCSI Consortium 121 Technology Drive, Suite 2
InterOperability Laboratory Durham, NH 03824
Research Computing Center Phone: [phone]
University of New Hampshire Fax: [phone]
http://www.iol.unh.edu/consortiums/sas

The University of New Hampshire

InterOperability Laboratory

TABLE OF CONTENTS

TABLE OF CONTENTS........................................................................................2

MODIFICATION RECORD ..................................................................................6

ACKNOWLEDGMENTS .......................................................................................7

INTRODUCTION....................................................................................................8

TARGETS: LINK LAYER....................................................................................10

TEST 7.1.1 - LINK RESET – REPEAT PHY SEQUENCE IF NO IDENTIFY RECIEVED .......................................... 11

TEST 7.1.2 - LINK RESET – IGNORE ADDITIONAL IDENTIFY RECIEVED....................................................... 12

TEST 7.1.3 - LINK RESET – HARD_RESET RECIEVED .......................................................................... 13

TEST 7.2.1 - CONNECTIONS – OPEN_ACCEPT ................................................................................... 14

TEST 7.2.2 - CONNECTIONS – 2 SOAF RECEIVED ................................................................................. 15

TEST 7.2.4 - CONNECTIONS - OPEN_REJECT CONNECTION RAT E NOT SUPPORTED.................................... 16

TEST 7.2.5 - CONNECTIONS - OPEN_REJECT PROTOCOL NOT SUPPORTED ............................................... 17

TEST 7.2.6 - CONNECTIONS - OPEN_REJECT WRONG DESTINATION....................................................... 18

TEST 7.2.7 - CONNECTIONS - OPEN_REJECT RETRY........................................................................... 19

TEST 7.3.1 - SSP_FRAMES - INTERLOCKED FRAME ............................................................................... 20

TEST 7.3.2 - SSP_FRAMES - NO ACK FOR INTERLOCKED FRAME ............................................................ 21

TEST 7.3.3 - SSP_FRAMES – MULTIPLE ACKS ..................................................................................... 22

TEST 7.3.4 - SSP FRAMES - RRDY.................................................................................................... 23

TEST 7.4.1 - CLOSING SSP CONNECTIONS – DONE (NORMAL)............................................................. 24

TEST 7.4.2 - CLOSING SSP CONNECTIONS – DONE (ACK/NAK TIMEOUT) ............................................ 25

TEST 7.4.3 - CLOSING SSP CONNECTIONS – DONE (CREDIT TIMEOUT) ............................................... 26

TEST 7.4.4 - CLOSING SSP CONNECTIONS – CLOSE (NORMAL) ........................................................... 27

TEST 7.4.5 - CLOSING SSP CONNECTIONS – BREAK SOURCED BY TESTING STATI ON .................................. 28

TEST 7.4.6 - CLOSING SSP CONNECTIONS – BREAK SOURCED BY DUT................................................... 29

TEST 7.5.1.1 - CONNECTIONS THROUGH EXPANDERS – OPEN SSP TARGET ............................................... 30

TEST 7.5.5.1 - BREAK – OPENTIMEOUT TIMER SSP TARGET ................................................................. 31

TARGETS: TRANSPORT LAYER .....................................................................33

TEST 9.1.1 - SSP FRAMES STRUCTURE – HASHED ADDRESS ................................................................... 34

TEST 9.1.2 - SSP FRAMES STRUCTURE – INFORMATION UNIT.................................................................. 35

TEST 9.1.3 - SSP FRAMES STRUCTURE – NUMBER OF FILL BYTES ..................................................... 36

TEST 9.2.1 - SSP COMMAND IU – TAG.............................................................................................. 37

TEST 9.2.2 - SSP COMMAND IU – TARGET PORT TRANSFER TAG ..................................................... 38

TEST 9.3.3 - SSP DATA IU – NUMBER OF FILL BYTES NON-ZERO...................................................... 39

TEST 9.3.4 - SSP DATA IU – NUMBER OF FILL BYTES ZERO.............................................................. 40

TEST 9.3.5 - SSP DATA IU – DATA OFFSET ...................................................................................... 41

TEST 9.4.1 - SSP XFER_RDY IU – REQUESTED OFFSET ................................................................. 42

TEST 9.4.2 - SSP XFER_RDY IU – REQUESTED OFFSET LARGE TRANSFER......................................... 43

TEST 9.4.3 - SSP XFER_RDY IU – MAXIMUM BURST SIZE ............................................................. 44

TEST 9.4.4 - SSP XFER_RDY IU – WRITE DATA LENGTH ................................................................ 45

Serial Attached SCSI Consortium Group 2 SAS Link and Transport Layer Test Suite v0.13

The University of New Hampshire

InterOperability Laboratory

TEST 9.5.1 - SSP RESPONSE IU – NO DATA PRESENT ..................................................................... 46

TEST 9.5.2 - SSP RESPONSE IU – SENSE DATA PRESENT ............................................................... 47

TEST 9.5.4 - SSP RESPONSE IU – SENSE/RESPONSE DATA NOT PRESENT ...................................... 48

TEST 9.5.5 - SSP RESPONSE IU –RESPONSE DATA PRESENT............................................................. 49

TEST 9.6.1 - SSP ERROR HANDLING – INVALID LENGTH ................................................................... 50

TEST 9.6.2 - SSP ERROR HANDLING – INVALID LUN ....................................................................... 51

TEST 9.6.3 - SSP ERROR HANDLING – NO ACK/NAK RECEIVED ....................................................... 52

TEST 9.6.5 - SSP ERROR HANDLING – UNKNOWN TAG .................................................................... 53

TARGETS: APPLICATION LAYER ..................................................................54

TEST 10.1.1 - SCSI CDB – TEST UNIT READY..................................................................................... 55

TEST 10.1.2 - SCSI CDB – INQUIRY ............................................................................................... 56

TEST 10.1.3 - SCSI CDB – START STOP .......................................................................................... 57

TEST 10.1.4 - SCSI CDB – MODE SENSE ........................................................................................ 58

TEST 10.1.5 - SCSI CDB – MODE SELECT ...................................................................................... 59

TEST 10.1.6 - SCSI CDB – READ CAPACITY ................................................................................... 60

TEST 10.1.7 - SCSI CDB – WRITE(10) ............................................................................................. 61

TEST 10.1.8 - SCSI CDB – READ(10) .............................................................................................. 62

TEST 10.1.9 - SCSI CDB – LOG SENSE ........................................................................................... 63

INITIATORS: LINK LAYER...............................................................................64

TEST 7.1.1 - LINK RESET – REPEAT PHY SEQUENCE IF NO IDENTIFY RECIEVED .......................................... 65

TEST 7.1.2 - LINK RESET – IGNORE ADDITIONAL IDENTIFY RECIEVED....................................................... 66

TEST 7.1.3 - LINK RESET – HARD_RESET RECEIVED .......................................................................... 67

TEST 7.1.4 - LINK RESET – SMP INITIATOR TO PERFORM DISCOVER ......................................................... 68

TEST 7.1.5 - LINK RESET – EDGE EXPANDER TRANSMITS OPEN_REJECT ................................................ 69

TEST 7.2.1 - CONNECTIONS – OPEN_ACCEPT ................................................................................... 70

TEST 7.2.2 - CONNECTIONS – 2 SOAF RECEIVED................................................................................. 71

TEST 7.2.4 - CONNECTIONS - OPEN_REJECT CONNECTION RAT E NOT SUPPORTED.................................... 72

TEST 7.2.5 - CONNECTIONS - OPEN_REJECT PROTOCOL NOT SUPPORTED ............................................... 73

TEST 7.2.6 - CONNECTIONS - OPEN_REJECT WRONG DESTINATION....................................................... 74

TEST 7.2.7 - CONNECTIONS - OPEN_REJECT RETRY........................................................................... 75

TEST 7.3.3 - SSP_FRAMES – MULTIPLE ACKS ..................................................................................... 76

TEST 7.3.4 - SSP FRAMES - RRDY.................................................................................................... 77

TEST 7.4.1 - CLOSING SSP CONNECTIONS – DONE (NORMAL)............................................................. 78

TEST 7.4.2 - CLOSING SSP CONNECTIONS – DONE (ACK/NAK TIMEOUT) ............................................ 79

TEST 7.4.3 - CLOSING SSP CONNECTIONS – DONE (CREDIT TIMEOUT) ............................................... 80

TEST 7.4.4 - CLOSING SSP CONNECTIONS – CLOSE (NORMAL) ........................................................... 81

TEST 7.4.5 - CLOSING SSP CONNECTIONS – BREAK SOURCED BY TESTING STATI ON .................................. 82

TEST 7.4.6 - CLOSING SSP CONNECTIONS – BREAK SOURCED BY DUT................................................... 83

TEST 7.5.1.2 - CONNECTIONS THROUGH EXPANDERS – OPEN SSP INITIATOR............................................. 84

TEST 7.5.1.4 - CONNECTIONS THROUGH EXPANDERS – OPEN SMP INITIATOR ........................................... 85

TEST 7.5.5.2 - BREAK – OPENTIMEOUT TIMER SSP INITIATOR .............................................................. 86

TEST 7.5.5.2 - BREAK – OPENTIMEOUT TIMER SSP INITIATOR .............................................................. 86

Serial Attached SCSI Consortium Group 3 SAS Link and Transport Layer Test Suite v0.13

The University of New Hampshire

InterOperability Laboratory

TEST 7.5.5.4 - BREAK – OPENTIMEOUT TIMER SMP INITIATOR ............................................................. 87

TEST 7.5.5.4 - BREAK – OPENTIMEOUT TIMER SMP INITIATOR ............................................................. 87

INITIATORS: TRANSPORT LAYER ................................................................88

TEST 9.1.1 - SSP FRAMES STRUCTURE – HASHED ADDRESS ................................................................... 89

TEST 9.1.2 - SSP FRAMES STRUCTURE – INFORMATION UNIT.................................................................. 90

TEST 9.1.3 - SSP FRAMES STRUCTURE – NUMBER OF FILL BYTES ..................................................... 91

TEST 9.2.1 - SSP COMMAND IU – TAG.............................................................................................. 92

TEST 9.2.2 - SSP COMMAND IU – TARGET PORT TRANSFER TAG ..................................................... 93

TEST 9.3.1 - SSP DATA IU – TPT TAG FIRST BURST DATA ..................................................................... 94

TEST 9.3.2 - SSP DATA IU – TPT TAG NON-DATA ............................................................................... 95

TEST 9.5.3 - SSP RESPONSE IU – DATAPRES RESERVED................................................................ 96

TEST 9.6.4 - SSP ERROR HANDLING – EXTRA RESPONSE FRAME RECEIVED ....................................... 97

EXPANDERS: LINK LAYER ..............................................................................98

TEST 7.1.1 - LINK RESET – REPEAT PHY SEQUENCE IF NO IDENTIFY RECEIVED .......................................... 99

TEST 7.1.2 - LINK RESET – IGNORE ADDITIONAL IDENTIFY RECIEVED..................................................... 100

TEST 7.1.3 - LINK RESET – HARD_RESET RECEIVED ........................................................................ 101

TEST 7.2.1 - CONNECTIONS – OPEN_ACCEPT ................................................................................. 102

TEST 7.2.2 - CONNECTIONS – 2 SOAF RECEIVED............................................................................... 103

TEST 7.2.3 - CONNECTIONS - OPEN_REJECT NO DESTINATION ........................................................... 104

TEST 7.2.8 - CONNECTIONS - OPEN_REJECT BAD DESTINATION ......................................................... 105

TEST 7.5.1.3 - CONNECTIONS THROUGH EXPANDERS – OPEN STP TARGET ............................................. 106

TEST 7.5.2.1 - CONNECTIONS THROUGH EXPANDERS – OPEN REJECT (STP RESOURCES BUSY)............ 107

TEST 7.5.3.1 - CONNECTIONS THROUGH EXPANDERS – SATA_HOLD..................................................... 108

TEST 7.5.4.1 - CONNECTIONS THROUGH EXPANDERS – SATA_RIP......................................................... 109

TEST 7.5.5.3 - BREAK – OPENTIMEOUT TIMER STP TARGET ............................................................... 110

TEST 7.5.5.5 - BREAK – CONNECTION REQUEST NOT TRANSMITTED ......................................................111

TEST 7.5.5.6 - BREAK – CONNECTION REQUEST TRANSMITTED ........................................................... 112

TEST 7.5.6.1 - AIP –TRANSMITTED.................................................................................................. 113

TEST 7.5.6.2 - AIP –OPEN RECEIVED HIGHER PRIORITY ..................................................................... 114

TEST 7.5.6.3 - AIP –OPEN RECEIVED LOWER PRIORITY ...................................................................... 115

TEST 7.5.7.1 - AWT TIMER –ARBITRATION WAIT TIME ................................................................. 116

TEST 7.5.7.2 - AWT TIMER – RESET TO ZERO .................................................................................... 117

TEST 7.5.7.3 - AWT TIMER – ARBITRATION FAIRNESS ......................................................................... 118

TEST 7.5.8.1 - OPEN_REJECT – PAT H WAY BLOCKED......................................................................... 119

TEST 7.5.9.1 - SMP_REQUEST – PROPER RESPONSE FORMAT ............................................................. 120

TEST 7.5.9.2 - SMP_REQUEST – CLOSE ....................................................................................... 121

TEST 7.5.9.3 - SMP_REQUEST – PROPER REQUEST FORMAT .............................................................. 122

EXPANDERS: APPLICATION LAYER.......................................................... 123

TEST 10.2.1 - STP OPERATIONS – IDENTIFY DEVICE................................................................... 124

TEST 10.2.2 - STP OPERATIONS – SET FEATURES........................................................................ 125

TEST 10.2.3 - STP OPERATIONS – IDLE ....................................................................................... 126

TEST 10.2.4 - STP OPERATIONS – SET MULTIPLE MODE ............................................................. 127

Serial Attached SCSI Consortium Group 4 SAS Link and Transport Layer Test Suite v0.13

The University of New Hampshire

InterOperability Laboratory

TEST 10.2.5 - STP OPERATIONS – WRITE SECTORS ..................................................................... 128

TEST 10.2.6 - STP OPERATIONS – READ SECTORS....................................................................... 129

TEST 10.2.7 - STP OPERATIONS – WRITE MULTIPLE ................................................................... 130

TEST 10.2.8 - STP OPERATIONS – READ MULTIPLE ..................................................................... 131

TEST 10.2.9 - STP OPERATIONS – WRITE DMA............................................................................ 132

TEST 10.2.10 - STP OPERATIONS – READ DMA............................................................................ 133

APPENDICES ..................................................................................................... 135

Serial Attached SCSI Consortium Group 5 SAS Link and Transport Layer Test Suite v0.13

The University of New Hampshire

InterOperability Laboratory

MODIFICATION RECORD

[1]September 7, 2004 (Version 0.1) DRAFT RELEASE

David Woolf: Initial draft release

[2]January 27, 2005 (Version 0.7) DRAFT RELEASE

David Woolf: updates to test procedures after initial CATC Review

[3]February 28, 2005 (Version 0.8) DRAFT RELEASE

David Woolf: updates to test procedures after further CATC Review

[4]March 3, 2005 (Version 0.9) DRAFT RELEASE

David Woolf: updates to test procedures after further CATC Review

[5]April 14, 2005 (Version 0.12) DRAFT RELEASE

David Woolf: added STP Operations tests

[6]July 11, 2005 (Version 0.13) DRAFT RELEASE

David Woolf: minor edits

Serial Attached SCSI Consortium 6 SAS Link and Transport Layer Test Suite v0.13

The University of New Hampshire

InterOperability Laboratory

ACKNOWLEDGMENTS

The University of New Hampshire would like to acknowledge the efforts of the following individuals
in the development of this test suite.

Kurtis Kofler UNH InterOperability Laboratory (UNH-IOL)
David Woolf UNH InterOperability Laboratory (UNH-IOL)
Michael Micheletti LeCroy Protocol Solutions Group

Serial Attached SCSI Consortium 7 SAS Link and Transport Layer Test Suite v0.13

The University of New Hampshire

InterOperability Laboratory

INTRODUCTION

The University of New Hampshire’s InterOperability Laboratory (IOL) is an institution
designed to improve the interoperability of standards based products by providing an
environment where a product can be tested against other implementations of a standard. This
particular suite of tests has been developed in junction with CATC to help implementers evaluate
the functionality of their Serial Attached SCSI (SAS) products. Specifically this Test Suite is
directed at verifying the Link, Transport, and Application layer of SAS Targets, Initiators, and
Expanders.

These tests are designed to determine if a SAS product conforms to specifications defined
in ISO/IEC 14776-150, Serial Attached SCSI (SAS) standard T10/1562-D, Revision 5
(hereafter referred to as the “SAS Standard”). Successful completion of all tests contained in this
suite does not guarantee that the tested device will successfully operate with other SAS products.
However, when combined with satisfactory operation in the IOL’s interoperability test bed, these
tests provide a reasonable level of confidence that the Device Under Test (DUT) will function
properly in many SAS environments.

The tests contained in this document are organized in order to simplify the identification
of information related to a test, and to facilitate in the actual testing process. Tests are separated
into groups, primarily in order to reduce setup time in the lab environment, however the different
groups typically also tend to focus on specific aspects of device functionality. A three-number,
dot-notated naming system is used to catalog the tests, where the first number always indicates
the specific clause of the reference standard on which the test suite is based. The second and
third numbers indicate the test’s group number and test number within that group, respectively.
This format allows for the addition of future tests in the appropriate groups without requiring the
renumbering of the subsequent tests.

The test definitions themselves are intended to provide a high-level description of the
motivation, resources, procedures, and methodologies specific to each test. Formally, each test
description contains the following sections:

Purpose

The purpose is a brief statement outlining what the test attempts to achieve. The test is
written at the functional level.

References

This section specifies all reference material external to the test suite, including the
specific subclauses references for the test in question, and any other references that might be
helpful in understanding the test methodology and/or test results. External sources are always
referenced by a bracketed number (e.g., [1]) when mentioned in the test description. Any other

Serial Attached SCSI Consortium 8 SAS Link and Transport Layer Test Suite v0.13

The University of New Hampshire

InterOperability Laboratory

references in the test description that are not indicated in this manner refer to elements within the
test suite document itself (e.g., “Appendix 5.A”, or “Table 5.1.1-1”)

Resource Requirements

The requirements section specifies the test hardware and/or software needed to perform
the test. This is generally expressed in terms of minimum requirements, however in some cases
specific equipment manufacturer/model information may be provided.

Revision History

This specifies the date of the last modification to this test.

Test Setup

The setup section describes the initial configuration of the test environment. Small
changes in the configuration should not be included here, and are generally covered in the test
procedure section (next).

Procedure

The procedure section of the test description contains the systematic instructions for
carrying out the test. It provides a cookbook approach to testing, and may be interspersed with
observable results.

Observable Results

This section lists the specific observables that can be examined by the tester in order to
verify that the DUT is operating properly. When multiple values for an observable are possible,
this section provides a short discussion on how to interpret them. The determination of a pass or
fail outcome for a particular test is generally based on the successful (or unsuccessful) detection
of a specific observable.

Serial Attached SCSI Consortium 9 SAS Link and Transport Layer Test Suite v0.13

The University of New Hampshire

InterOperability Laboratory

TARGETS: LINK LAYER

Overview:

This group of tests verifies the Link Layer specifications of the SAS physical layer

defined in Clause 7 of the SAS Standard.

Serial Attached SCSI Consortium 10 SAS Link and Transport Layer Test Suite v0.13

The University of New Hampshire

InterOperability Laboratory

Test 7.1.1 - Link Reset – Repeat PHY Sequence if no Identify Recieved

Purpose: To determine that the DUT will repeat the Phy reset sequence if an Identify frame is not received within 1

msec of completing a Phy reset sequence.

References: 7.9.1 SAS Standard

Resource Requirements: SAS Protocol Analyzer and Generator

Revision History: September 7, 2004

Test Setup: The DUT and the Testing Station are physically connected.

Test Procedure:

• The Testing Station should transmit COMINT to start a Phy Reset sequence with the DUT.

• The Testing Station should complete a Phy Reset sequence with the DUT.

• Once the Phy reset sequence between the DUT and the Testing Station are complete, the Testing

Station should transmit valid SAS primitives or SAS Idle. The Testing Station should not transmit an
Identify Address Frame.

Observable Results:

• Verify that 1 msec after the DUT completed a Phy Reset Sequence with the DUT, the DUT initiated
another Phy reset sequence by transmitting COMINIT.

Serial Attached SCSI Consortium 11 SAS Link and Transport Layer Test Suite v0.13

The University of New Hampshire

InterOperability Laboratory

Test 7.1.2 - Link Reset – Ignore Additional Identify Recieved

Purpose: To determine that the DUT will ignore an Identify frame received after a valid Identify has already been

received.

References: 7.9.1 SAS Standard

Resource Requirements: SAS Protocol Analyzer and Generator

Revision History: September 7, 2004

Test Setup: The DUT and the Testing Station are physically connected.

Test Procedure:

• The Testing Station should transmit COMINT to start a Phy Reset sequence with the DUT.

• The Testing Station should complete a Phy Reset sequence with the DUT.

• Once the Phy reset sequence between the DUT and the Testing Station are complete, the Testing

Station should transmit valid SAS primitives or SAS Idle. The Testing Station should transmit 2 valid
Identify Address Frames each with a different SAS address.

Observable Results:

• Verify that the DUT ignores the second received Identify Address Frame and does not transmit
COMINIT.

• Verify that the DUT does not attempt to open a connection to the address in the second Identify
Address frame.

Serial Attached SCSI Consortium 12 SAS Link and Transport Layer Test Suite v0.13

The University of New Hampshire

InterOperability Laboratory

Test 7.1.3 - Link Reset – HARD_RESET Recieved

Purpose: To determine that the DUT properly handles a received HARD_RESET.

References: 7.2.5.8, 7.9.1 SAS Standard

Resource Requirements: SAS Protocol Analyzer and Generator

Revision History: September 7, 2004

Test Setup: The DUT and the Testing Station are physically connected.

Test Procedure:

• The Testing Station should transmit COMINT to start a Phy Reset sequence with the DUT.

• The Testing Station should complete a Phy Reset sequence with the DUT.

• Once the Phy reset sequence between the DUT and the Testing Station are complete, the Testing

Station should transmit 6 consecutive HARD_RESET primitives. This must occur before the Identify
sequence is complete.

Observable Results:

• Verify that the DUT transmits COMINIT upon receiving the HARD_RESET primitives from the
Testing Station.

Serial Attached SCSI Consortium 13 SAS Link and Transport Layer Test Suite v0.13

The University of New Hampshire

InterOperability Laboratory

Test 7.2.1 - Connections – OPEN_ACCEPT

Purpose: To determine that the DUT properly transmits RRDY after receiving OPEN_ACCEPT.

References: 7.12.2.2 SAS Standard

Resource Requirements: SAS Protocol Analyzer and Generator

Revision History: September 7, 2004

Test Setup: The DUT and the Testing Station are physically connected.

Test Procedure (Targets):

• The Testing Station should start and complete a Phy Reset sequence followed by an Identify sequence
with the DUT. Since the DUT is a target the Testing Station should transmit an Identify Address frame
indicating that it is an initiator.

• The Testing Station should transmit an Open Address frame to the DUT. Wait for the DUT to transmit
OPEN_ACCEPT and RRDY.

Observable Results:

• Verify that the DUT transmitted RRDY no more than 1 ms after transmitted OPEN_ACCEPT.

Serial Attached SCSI Consortium 14 SAS Link and Transport Layer Test Suite v0.13

The University of New Hampshire

InterOperability Laboratory

Test 7.2.2 - Connections – 2 SOAF Received

Purpose: To determine that the DUT properly handles received 2 SOAF primitives.

References: 7.2.5.11 SAS Standard

Resource Requirements: SAS Protocol Analyzer and Generator

Revision History: September 7, 2004

Test Setup: The DUT and the Testing Station are physically connected.

Test Procedure (Targets):

• The Testing Station should start and complete a Phy Reset sequence followed by an Identify sequence
with the DUT. Since the DUT is a target the Testing Station should transmit an Identify Address frame
indicating that it is an initiator.

• The Testing Station should transmit the following to the DUT

o SOAF primitive
o the first 4 dwords of an OpenAddress frame
o complete Open Address frame starting with SOAF and using the SAS address of the DUT.

• Wait for the DUT to transmit OPEN_ACCEPT and RRDY.

Observable Results:

• Verify that the DUT responded to the received, complete Open Address frame with OPEN_ACCEPT.

Serial Attached SCSI Consortium 15 SAS Link and Transport Layer Test Suite v0.13

The University of New Hampshire

InterOperability Laboratory

Test 7.2.4 - Connections - OPEN_REJECT Connection Rate Not Supported

Purpose: To determine that the DUT handles errors in OpenAddress frames properly.

References: 7.2.5.11, 7.8.3 Table 74 SAS Standard

Resource Requirements: SAS Protocol Analyzer and Generator

Revision History: September 13, 2004

Test Setup: The DUT and the Testing Station are physically connected.

Test Procedure (Targets):

• The Testing Station should start and complete a Phy Reset sequence followed by an Identify sequence
with the DUT. Since the DUT is a target the Testing Station should transmit an Identify Address frame
indicating that it is an initiator.

• The Testing Station should transmit an OpenAddress frame to the DUT with an invalid connection
rate.

• Wait for the DUT to transmit OPEN_REJECT (Connection rate not supported).

Observable Results: Verify that the DUT responded to the received, complete Open Address frame with
OPEN_REJECT (Connection rate not supported).

Serial Attached SCSI Consortium 16 SAS Link and Transport Layer Test Suite v0.13

The University of New Hampshire

InterOperability Laboratory

Test 7.2.5 - Connections - OPEN_REJECT Protocol Not Supported

Purpose: To determine that the DUT handles errors in OpenAddress frames properly.

References: 7.2.5.11 SAS Standard

Resource Requirements: SAS Protocol Analyzer and Generator

Revision History: September 13, 2004

Test Setup: The DUT and the Testing Station are physically connected.

Test Procedure (Targets):

• The Testing Station should start and complete a Phy Reset sequence followed by an Identify sequence
with the DUT. Since the DUT is a target the Testing Station should transmit an Identify Address frame
indicating that it is an initiator.

• The Testing Station should transmit an OpenAddress frame to the DUT with an invalid initiator or
target role.

• Wait for the DUT to transmit OPEN_REJECT (Protocol not supported).

Observable Results: Verify that the DUT responded to the received, complete Open Address frame with
OPEN_REJECT (Protocol not supported).

Serial Attached SCSI Consortium 17 SAS Link and Transport Layer Test Suite v0.13

The University of New Hampshire

InterOperability Laboratory

Test 7.2.6 - Connections - OPEN_REJECT Wrong Destination

Purpose: To determine that the DUT handles errors in OpenAddress frames properly.

References: 7.2.5.11 SAS Standard

Resource Requirements: SAS Protocol Analyzer and Generator

Revision History: September 13, 2004

Test Setup: The DUT and the Testing Station are physically connected.

Test Procedure (Targets):

• The Testing Station should start and complete a Phy Reset sequence followed by an Identify sequence
with the DUT. Since the DUT is a target the Testing Station should transmit an Identify Address frame
indicating that it is an initiator.

• The Testing Station should transmit an OpenAddress frame to the DUT with an incorrect destination
SAS Address.

• Wait for the DUT to transmit OPEN_REJECT (Wrong Destination).

Observable Results: Verify that the DUT responded to the received, complete Open Address frame with
OPEN_REJECT (Wrong Destination).

Serial Attached SCSI Consortium 18 SAS Link and Transport Layer Test Suite v0.13

The University of New Hampshire

InterOperability Laboratory

Test 7.2.7 - Connections - OPEN_REJECT Retry

Purpose: To determine that the DUT handles extra connection requests properly.

References: 7.2.5.11 SAS Standard

Resource Requirements: SAS Protocol Analyzer and Generator

Revision History: September 13, 2004

Test Setup: The DUT and the Testing Station are physically connected.

Test Procedure (Targets):

• The Testing Station should start and complete a Phy Reset sequence followed by an Identify sequence
with the DUT. Since the DUT is a target the Testing Station should transmit an Identify Address frame
indicating that it is an initiator.

• The Testing Station should continuously transmit OpenAddress frames to the DUT with a correct
destination SAS Address.

• Wait for the DUT to transmit OPEN_REJECT (Retry).

Observable Results: Verify that the DUT responded to the received, complete Open Address frame with
OPEN_REJECT (Retry). This item may not be testable for some devices.

Serial Attached SCSI Consortium 19 SAS Link and Transport Layer Test Suite v0.13

The University of New Hampshire

InterOperability Laboratory

Test 7.3.1 - SSP_Frames - Interlocked Frame

Purpose: To determine that the DUT handles interlocked frames properly.

References: 7.16.3, 7.16.5 SAS Standard

Resource Requirements: SAS Protocol Analyzer and Generator

Revision History: September 13, 2004

Test Setup: The DUT and the Testing Station are physically connected. This test is only applicable to targets.

Test Procedure (Targets):

• The Testing Station should start and complete a Phy Reset sequence followed by an Identify sequence
with the DUT. Since the DUT is a target the Testing Station should transmit an Identify Address frame
indicating that it is an initiator.

• The Testing Station should open a SSP connection to the DUT and transmit a SCSI_INQUIRY
command.

• Wait for the DUT to transmit ACK followed by SCSI Response.

Observable Results: Verify that upon receiving the INQUIRY command, the DUT transmitted ACK before
transmitting any other frame to the Testing Station.

Serial Attached SCSI Consortium 20 SAS Link and Transport Layer Test Suite v0.13

The University of New Hampshire

InterOperability Laboratory

Test 7.3.2 - SSP_Frames - No ACK for Interlocked Frame

Purpose: To determine that the DUT responds properly when no ACK or NAK is received after transmitting an

interlocked frame.

References: 7.16.3, 7.16.5 SAS Standard

Resource Requirements: SAS Protocol Analyzer and Generator

Revision History: January 25, 2005

Test Setup: The DUT and the Testing Station are physically connected. This test is only applicable to targets.

Test Procedure (Targets):

• The Testing Station should start and complete a Phy Reset sequence followed by an Identify sequence
with the DUT. Since the DUT is a target the Testing Station should transmit an Identify Address frame
indicating that it is an initiator.

• The Testing Station should open a SSP connection to the DUT and transmit a SCSI_INQUIRY
command.

• Wait for the DUT to transmit ACK followed by SCSI Response.

• The Testing Station should not transmit ACK or NAK to the SCSI Response frame.

• The Testing Station should transmit a second SCSI_INQUIRY command with a different TAG than

the first SCSI INQUIRY command.

Observable Results: Verify that the DUT aborts the first INQUIRY command with DONE(ACK/NAK TIMEOUT)
after the ACK/NAK timeout of 1 msec.

Serial Attached SCSI Consortium 21 SAS Link and Transport Layer Test Suite v0.13

The University of New Hampshire

InterOperability Laboratory

Test 7.3.3 - SSP_Frames – Multiple ACKs

Purpose: To determine that the DUT properly transmits ACK within 1 msec of receiving a frame requiring an ACK

response.

References: 7.16.3, 7.16.5 SAS Standard

Resource Requirements: SAS Protocol Analyzer, SAS Initiator, SAS Target, Software capable of generating SCSI

traffic from the SAS Initiator. In order to minimize physical layer problems, the Initiator, Target, and Analyzer
should be connected with near-ideal channels.

Revision History: September 13, 2004

Test Setup: The SAS Initiator and Target are connected through the SAS Analyzer.

Test Procedure:

• Using the generation software, cause the SAS Initiator to begin a series of 1000 64 kB READ
operations on the SAS Target. Capture this on the SAS Analyzer.

Observable Results: If the DUT is an initiator, search the Analyzer capture of the target transmissions for the
DONE (ACK/NAK TIMEOUT) primitive. If the DUT is a target, search the Analyzer capture of the initiator
transmissions for the DONE (ACK/NAK TIMEOUT) primitive. If any of these primitives are found, it indicates that
the DUT did not transmit ACK within the 1 msec necessary after receiving frame requiring ACK or NAK.

Serial Attached SCSI Consortium 22 SAS Link and Transport Layer Test Suite v0.13

The University of New Hampshire

InterOperability Laboratory

Test 7.3.4 - SSP Frames - RRDY

Purpose: To determine that the DUT properly grants credit to transit frames using RRDY.

References: 7.16.4 SAS Standard

Resource Requirements: SAS Protocol Analyzer and Generator

Revision History: September 13, 2004

Test Setup: The DUT and the Testing Station are physically connected.

Test Procedure (Targets):

• The Testing Station should start and complete a Phy Reset sequence followed by an Identify sequence
with the DUT. Since the DUT is a target the Testing Station should transmit an Identify Address frame
indicating that it is an initiator.

• The Testing Station should open an SSP connection to the DUT.

• Wait for the DUT to transmit OPEN_ACCEPT and RRDY.

Observable Results: Verify that the DUT transmitted RRDY when an SSP connection was opened.

Serial Attached SCSI Consortium 23 SAS Link and Transport Layer Test Suite v0.13

The University of New Hampshire

InterOperability Laboratory

Test 7.4.1 - Closing SSP Connections – DONE (NORMAL)

Purpose: To determine that the DUT properly responds when DONE is received.

References: 7.16.6 SAS Standard

Resource Requirements: SAS Protocol Analyzer and Generator

Revision History: September 13, 2004

Test Setup: The DUT and the Testing Station are physically connected.

Test Procedure (Targets):

• The Testing Station should start and complete a Phy Reset sequence followed by an Identify sequence
with the DUT. Since the DUT is a target the Testing Station should transmit an Identify Address frame
indicating that it is an initiator.

• The Testing Station should open an SSP connection to the Testing Station.

• Wait for the DUT to transmit OPEN_ACCEPT and RRDY.

• The Testing Station should transmit DONE (NORMAL).

Observable Results: Verify that the DUT transmitted DONE (NORMAL) within 1 msec of receiving DONE
(NORMAL) from the Testing Station.

Serial Attached SCSI Consortium 24 SAS Link and Transport Layer Test Suite v0.13

The University of New Hampshire

InterOperability Laboratory

Test 7.4.2 - Closing SSP Connections – DONE (ACK/NAK TIMEOUT)

Purpose: To determine that the DUT properly responds when ACK or NAK has not been received for a transmitted

frame.

References: 7.16.6 SAS Standard

Resource Requirements: SAS Protocol Analyzer and Generator

Revision History: September 13, 2004

Test Setup: The DUT and the Testing Station are physically connected.

Test Procedure (Targets):

• The Testing Station should start and complete a Phy Reset sequence followed by an Identify sequence
with the DUT. Since the DUT is a target the Testing Station should transmit an Identify Address frame
indicating that it is an initiator.

• The Testing Station should open an SSP connection to the Testing Station.

• Wait for the DUT to transmit OPEN_ACCEPT and RRDY. The Testing Station should transmit a

SCSI INQUIRY command to the DUT, then close the connection.

• Wait for the DUT to open an SSP Connection to the Testing Station. Allow the DUT to transmit a
SCSI Response. The Testing Station should not transmit ACK or NAK.

Observable Results: Verify that the DUT transmitted DONE (ACK/NAK TIMEOUT) within 1 msec of
transmitting the Command or Response frame.

Serial Attached SCSI Consortium 25 SAS Link and Transport Layer Test Suite v0.13

The University of New Hampshire

InterOperability Laboratory

Test 7.4.3 - Closing SSP Connections – DONE (CREDIT TIMEOUT)

Purpose: To determine that the DUT properly responds when RRDY has not been received for an impending

transaction.

References: 7.16.6 SAS Standard

Resource Requirements: SAS Protocol Analyzer and Generator

Revision History: September 13, 2004

Test Setup: The DUT and the Testing Station are physically connected.

Test Procedure (Targets):

• The Testing Station should start and complete a Phy Reset sequence followed by an Identify sequence
with the DUT. Since the DUT is a target the Testing Station should transmit an Identify Address frame
indicating that it is an initiator.

• The Testing Station should open an SSP connection to the DUT.

• Wait for the DUT to transmit OPEN_ACCEPT and RRDY. The Testing Station should transmit a

SCSI INQUIRY command to the DUT, then close the connection.

• Wait for the DUT to open an SSP connection to the Testing Station. The Testing Station should not
transmit RRDY to grant credit for the DUT to transmit a SCSI Response to the Testing Station.

Observable Results: Verify that the DUT transmitted DONE (CREDIT TIMEOUT) within 1 msec of opening the
SSP connection.

Serial Attached SCSI Consortium 26 SAS Link and Transport Layer Test Suite v0.13

The University of New Hampshire

InterOperability Laboratory

Test 7.4.4 - Closing SSP Connections – CLOSE (NORMAL)

Purpose: To determine that the DUT properly responds when CLOSE (NORMAL) is received.

References: 7.12.7, 7.16.6 SAS Standard

Resource Requirements: SAS Protocol Analyzer and Generator

Revision History: September 13, 2004

Test Setup: The DUT and the Testing Station are physically connected.

Test Procedure (Targets):

• The Testing Station should start and complete a Phy Reset sequence followed by an Identify sequence
with the DUT. Since the DUT is a target the Testing Station should transmit an Identify Address frame
indicating that it is an initiator.

• The Testing Station should open an SSP connection to the DUT. Wait for the DUT to transmit
OPEN_ACCEPT. The Testing Station should transmit a CLOSE (NORMAL) primitive to the DUT.

Observable Results: Verify that the DUT transmitted CLOSE (NORMAL) within 1 msec of receiving CLOSE
(NORMAL) from the Testing Station.

Serial Attached SCSI Consortium 27 SAS Link and Transport Layer Test Suite v0.13

The University of New Hampshire

InterOperability Laboratory

Test 7.4.5 - Closing SSP Connections – BREAK Sourced by Testing Station

Purpose: To determine that the DUT properly responds when BREAK is received.

References: 7.12.6 SAS Standard

Resource Requirements: SAS Protocol Analyzer and Generator

Revision History: September 13, 2004

Test Setup: The DUT and the Testing Station are physically connected.

Test Procedure (Targets):

• The Testing Station should start and complete a Phy Reset sequence followed by an Identify sequence
with the DUT. Since the DUT is a target the Testing Station should transmit an Identify Address frame
indicating that it is an initiator.

• The Testing Station should transmit an OpenAddress frame to the DUT, followed by BREAK.

Observable Results: Verify that the DUT transmitted BREAK within 1 msec of receiving BREAK from the
Testing Station.

Serial Attached SCSI Consortium 28 SAS Link and Transport Layer Test Suite v0.13

The University of New Hampshire

InterOperability Laboratory

Test 7.4.6 - Closing SSP Connections – BREAK Sourced by DUT

Purpose: To determine that the DUT properly sources BREAK when required.

References: 7.12.7 SAS Standard

Resource Requirements: SAS Protocol Analyzer and Generator

Revision History: September 13, 2004

Test Setup: The DUT and the Testing Station are physically connected.

Test Procedure (Targets):

• The Testing Station should start and complete a Phy Reset sequence followed by an Identify sequence
with the DUT. Since the DUT is a target the Testing Station should transmit an Identify Address frame
indicating that it is an initiator.

• The Testing Station should open an SSP connection to the DUT.

• Wait for the DUT to transmit OPEN_ACCEPT and RRDY. The Testing Station should transmit a

SCSI INQUIRY command to the DUT, then close the connection.

• Wait for the DUT to open an SSP connection to the Testing Station. Allow the DUT to transmit a SCSI
Response to the Testing Station.

• When the DUT transmits CLOSE (NORMAL) to close the connection, the Testing Station should not
transmit CLOSE (NORMAL) in response.

Observable Results: Verify that the DUT transmitted BREAK within 1 msec of transmitting CLOSE (NORMAL)
to the Testing Station.

Serial Attached SCSI Consortium 29 SAS Link and Transport Layer Test Suite v0.13