iSCSI 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 iSCSI 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 iSCSI 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
- 3.0
- Testing Days Needed
- 2 days
- Last Modified
- 2015-11-20
- Abstract
- To verify that the DUT adheres to RFC 7143 regarding the negotiation of key=value pairs during Login Phase.
- Notes
- Previous versions of this test suite include: v0.1, v1.0, v1.1, v1.2, v2.1, v2.2
- Status
- Fully Documented (Partially Implemented)
- Revision
- 3.0
- Testing Days Needed
- 5 days
- Last Modified
- 2015-11-20
- Abstract
- To verify that parameters from the Login Phase are correctly used during the Full Feature Phase according to the rules defined in RFC 7143.
- Notes
- Previous versions of this test suite include: v0.1, v1.0, v1.1, v1.2, v2.0, v2.1
- Status
- Fully Documented (Active)
- Revision
- 3.1
- Testing Days Needed
- 5 days
- Last Modified
- 2016-05-17
- Abstract
- To verify that iSCSI targets implementing security using CHAP properly adhere to the rules defined in RFC 3720. This version of the test suite includes changes due to the iSCSI Corrections and Clarifications Document.
- Notes
- Previous versions of this test suite include: v0.1, v1.0, v1.1, v2.0
- Status
- Fully Documented (Partially Implemented)
- Revision
- 2.1
- Testing Days Needed
- 5 days
- Last Modified
- 2010-01-13
- Abstract
- Examines how iSCSI targets respond to different error scenarios and that targets adhere to the rules defined in the iSCSI Standard RFC 3720 and the iSCSI Corrections and Clarifications RFC 5048.
- Notes
- Previous versions of this test suite include: v0.1, v0.2, v2.0
- Status
- Fully Documented (Partially Implemented)
- Revision
- 3.0
- Testing Days Needed
- 2 days
- Last Modified
- 2015-11-20
- Abstract
- To verify that the DUT adheres to RFC 7143 defined rules regarding the negotiation of key=value pairs during Login Phase.
- Notes
- Previous versions of this test suite include: v0.1, v1.0, v1.1, v1.2, v2.0
- Status
- Fully Documented (Partially Implemented)
- Revision
- 3.1
- Testing Days Needed
- 5 days
- Last Modified
- 2015-12-03
- Abstract
- To verify that parameters from the Login Phase are correctly used during the Full Feature Phase according to the rules defined in iSCSI Standard RFC 7143.
- Notes
- Previous versions of this test suite include: v0.1, v1.0, v1.1, v1.2, v1.3, v1.4, v2.0, v2.1, v3.0
- Status
- Fully Documented (Active)
- Revision
- 3.1
- Testing Days Needed
- 2 days
- Last Modified
- 2016-05-17
- Abstract
- To verify that iSCSI initiators implementing security using CHAP properly adhere to the rules defined in the iSCSI Standard RFC 3720 and the iSCSI Corrections and Clarifications RFC 5048.
- Notes
- Previous versions of this test suite include: v0.1, v0.2, v2.0
- Status
- Draft (Partially Implemented)
- Revision
- 1
- Testing Days Needed
- 5 Days
- Last Modified
- 2008-12-11
- Abstract
- If you wish to have specific items tested which are not part of our normal test suites, or if you wish to have only certain tests run contained within some of our test suites then feel free to select this option. If this option is chosen please let us know what device and what tests you would like and we will try to work with you to let you know what we can accomodate during your testing time slot.
Key
| Fully Documented |
| Draft |