u niversity of n ew h ampshire i nter o perability l ab iscsi plugfest (feb 11- feb15) unh...

UNIVERSITY of NEW HAMPSHIRE

INTEROPERABILITY LAB

iSCSI Plugfest (Feb 11- Feb15) UNH InterOperability Laboratory

Yamini Shastry

Graduate Research AssistantInterOperability Laboratory

University of New Hampshire

[email protected]

iSCSI Plugfest (Feb 11- 15) UNH InterOperability Laboratory

Implementations at the Plugfest

Draft 8 Draft 9 Total

Initiators 5 8 13

Targets 7 14 21

TOTALS 12 22 34


19 Companies Attended

D8 Only D9 OnlyBoth

D8 & D9Total

Tools Only 0 0 3 3

Initiator Only 0 1 0 1

Target Only 1 6 1 8

Both Initiator &Target

0 2 5 7

TOTALS 1 9 9 19


Summary of three Plugfests

Plugfest Date Draft TestedCompanies Attended

1 Jul 2001 0 & 6 28

2 Oct 2001 8 15

3 Feb 2002 8 & 9 19

• 36 Different companies participated overall- Out of which 17 are members, i.e., almost 50% • 10 companies attended all 3 plugfests - Out of which 9 are members, i.e., 90%


Login Conformance Test Package (D8 & D9)- Test Suite- Scripts- Testor

Interop test procedure

Reference implementation- Initiator (D8 & D9)- Target (D8 & D9)

Protocol Analyzer (D8)

Overview of testing


Issues Discovered

Issue 1:

Should the value of the Desired Data Transfer Length in an R2T be limited to MaxBurstSize?

- Discussion on the CMU mailing list.

- Clarified that MaxBurstSize does indeed limit the amount of data an R2T can request.


Issues Discovered

Issue 2:

What should be done when SCSI-1 and SCSI-2 systems try to use iSCSI (which is based on SCSI-3).

- Discussion on the CMU mailing list.

- Conclusion:

“Will not say anything about itin iSCSI Standard.”


Features SummaryMany implementations:

- supported discovery sessions- supported parameter renegotiation during FFP

Few implementations:- supported digests- dealt with multiple connections in a single session- allowed unsolicited and/or immediate data- supported portal groups- supported Target and Initiator alias- supported multiple outstanding R2Ts


Features Summary (continued)

Only 2 implementations:

- had security code- supported persistent reservations- supported out of order PDUs

within a sequence

Only 1 implementation:

- supported out of order R2Ts - supported additional header segments


Features Summary (continued)

No one:

- dealt with Markers- dealt with bidirectional operations- dealt with Error recovery above level 0


Summary Areas Not Tested:

- Security - Error Recovery above level 0 - Digests - Multiple device interop

- Markers - Naming and Discovery - Portal Groups - Additional Header Segment

- Out of order PDUs and R2Ts

More Testing needs to be done in:- MultiConnections in a Session- Discovery Sessions

- Multiple Outstanding R2Ts - Parameter renegotiation during FFP


Proposed items for the next iSCSI Plugfest

- Error recovery above level 0- Full Feature conformance- Digests- More testing in Discovery session- Security- Multiple Connections in single session- Performance measurement test suite- Testing of changes caused by drafts 10 and 11


Next iSCSI Plugfest

When: June 3-7

Where: InterOperability LaboratoryUniversity of New HampshireDurham, New Hampshire

Contact: Stephen [email protected]

u niversity of n ew h ampshire i nter o perability l ab iscsi plugfest (feb 11- feb15) unh...

Documents