SAS Test Plans

The test plans on this page may be downloaded and used for internal purposes only. The test plans may not be commercialized in any way without express permission of the UNH-IOL.

The SAS testing service currently offers the following test plans. These documents are constantly being updated to improve readability and to reflect the current specifications. Please contact us if you would like more information or have questions about the SAS testing service.

When testing based on the following test plans is performed, all reports generated will be digitally signed using an Adobe digital certificate. Upon reception of the report, the recipient can verify its authenticity using our document validation instructions.

IOL

Conformance

Status
Fully Documented (Partially Implemented)
Revision
0.5
Testing Days Needed
1 Week
Last Modified
2011-06-28
Abstract
This Test Suite measures the power drawn by a device in each Phy Power Condition, verifies that the device conforms to the Power Management Protocol defined in the SAS Spec, and verifies the Power Management state machine specified in the SAS 2.1 standard.
Status
Fully Documented (Partially Implemented)
Revision
v1.4
Testing Days Needed
1 week*
Last Modified
2014-10-09
Abstract
This Test Suite defines transmitter physical layer conformance testing for SAS 3.0 devices.This Test Suite requires the DUT to support various test patterns and modes. For a summary of these requirements, please refer to Appendix 5.B of the Test Suite.
Notes
*This test suite will require 1 week per port per rate.
Status
Fully Documented (Active)
Revision
1.0
Testing Days Needed
1 Week
Last Modified
2014-10-01
Abstract
This group of tests verifies the RX electrical signaling requirements for SAS signals, as defined in Clause 5 of the SAS-3 Standard.
Status
Fully Documented (Active)
Revision
1.4
Testing Days Needed
1 Week
Last Modified
2015-09-21
Abstract
This test suite covers many of the various changes and adjustments to SAS Speed Negotiation introduced with SAS 3.0.
Status
Fully Documented (Active)
Revision
3.04
Testing Days Needed
1 Week
Last Modified
2011-09-06
Abstract
This test suite verifies Out-Of-Band specifications for SAS devices as defined in Clause 5 of the SAS standard and SAS SPL. This test suite was previously known as Clause 6 Phy Layer Test Suite: OOB.
Status
Fully Documented (Active)
Revision
3.1
Testing Days Needed
1 Week
Last Modified
2011-09-06
Abstract
This test suite verifies the sync specifications for SAS devices as defined in Clause 5 of the SAS SPL. This test suite was previously known as Clause 6 Phy Layer Test Suite: Sync.
Status
Fully Documented (Active)
Revision
1.4
Testing Days Needed
3 days
Last Modified
2016-02-01
Abstract
This test suite verifies link layer specifications for SAS devices as defined in Clause 6 of the SAS SPL. This test suite was previously known as Clause 7 Link Layer Test Suite.
Status
Fully Documented (Active)
Revision
1.14
Testing Days Needed
3 days
Last Modified
2011-09-06
Abstract
This test suite verifies Transport layer specifications for SAS devices as defined in Clause 8 of the SAS SPL. This test suite was previously known as Clause 9 Transport Layer Test Suite.
Status
Fully Documented (Partially Implemented)
Revision
0.4
Testing Days Needed
1 Week
Last Modified
2011-09-06
Abstract
This test suite verifies Target Error Handling specifications for SAS devices as defined in Clause 8 of the SAS SPL.This test suite was previously known as Clause 9 Target Error Handling Test Suite
Status
Fully Documented (Active)
Revision
1.02
Testing Days Needed
3 days
Last Modified
2012-04-02
Abstract
This test suite verifies application layer specifications for SAS devices as defined in Clause 10 of the SAS standard.

Interoperability

Status
Fully Documented (Active)
Revision
1.01
Testing Days Needed
1 Week
Last Modified
2005-08-15
Abstract
This test suite defines procedures for verifying point to point links between SAS devices. In addition it defines a procedure for building and testing a Large SAS System.
Notes
Is necessary for devices involved in this test to support error counters accessible either by a local management application or by SCSI command queries. These error counters must track CRC errors detected and NAK primitives received.

Key

Fully Documented
Draft