U NIVERSITY of N EW H AMPSHIRE I NTER O PERABILITY L AB iSCSI Plugfest (Oct 28 - Nov 3) UNH InterOperability Laboratory Yamini Shastry Graduate Research Assistant InterOperability Laboratory University of New Hampshire

iSCSI Plugfest (Oct 28 - Nov 3) UNH InterOperability Laboratory 15 Companies Attended, Testing was against Draft 8 Products:None Target only Initiator only BothTotal Number of companies: Totals: 10 Initiators, 13 Targets

iSCSI Plugfest (Oct 28 - Nov 3) UNH InterOperability Laboratory Login Conformance Test Package - Test Suite - Scripts - Testor Interop test procedure Reference implementation - For both Initiator & Target Protocol Analyzer Overview of testing

iSCSI Plugfest (Oct 28 - Nov 3) UNH InterOperability Laboratory INITIATOR Test Results for Login Conformance Test type:% Pass Reserved Bits test 0 List Negotiation 25 Full Feature Phase Command in Login Phase 50 Status Class Check 50

iSCSI Plugfest (Oct 28 - Nov 3) UNH InterOperability Laboratory TARGET Test Results for Login Conformance Test type:% Pass Reserved Bits test 10 Target Name 20 Full Feature Phase Command in Login Phase 70 Send Targets 30

iSCSI Plugfest (Oct 28 - Nov 3) UNH InterOperability Laboratory Issues Discovered Issue 1: I-bit not set on first login of the session. How should Target react? Changes Made: – “Class 2 - Initiator error (not format error)” - Bit 6 of byte 1, in login request pdu changed from I to 1.

iSCSI Plugfest (Oct 28 - Nov 3) UNH InterOperability Laboratory Issues Discovered Issue 2: Is not offering a key an implicit offering of default value? Changes Made: – Reworded to say no. - An explanation added about originator and responder.

iSCSI Plugfest (Oct 28 - Nov 3) UNH InterOperability Laboratory Issues Discovered Issue 3: When is the Target Name required. When is it optional? Changes Made: After discussion on list, consensus - Target name MUST be sent on first Login of every connection. - Target Name changed from LO to IO. - Rewording in many clauses in Draft 9

iSCSI Plugfest (Oct 28 - Nov 3) UNH InterOperability Laboratory Issues Discovered Issue 4: Is a receiver required to check the reserved fields? Changes Made: After discussion on list, consensus - Section 3 – “Any compliant receiver must ignore any bit not specified and all reserved fields.”

iSCSI Plugfest (Oct 28 - Nov 3) UNH InterOperability Laboratory Issues Discovered Issue 5: Can an Initiator send commands out of CmdSN order on any single connection? Changes Made: After much discussion on list, consensus – Reworded to say no.

iSCSI Plugfest (Oct 28 - Nov 3) UNH InterOperability Laboratory Summary Few implementations supported digests. Few implementations dealt with multiple connections in a single session. Few implementations dealt with discovery session. Few allowed command windows greater than 1.

iSCSI Plugfest (Oct 28 - Nov 3) UNH InterOperability Laboratory Summary (continued) Few allowed unsolicited and/or immediate data. Only one implementation had security code. No one dealt with Markers. No one dealt with Error recovery. Most parameter negotiation was for default values; - Little deviation was accepted.

iSCSI Plugfest (Oct 28 - Nov 3) UNH InterOperability Laboratory Summary (continued) Areas Not Tested: - Security - Digests - Error Recovery - Multiple Connections per Session - Naming and Discovery More Testing needs to be Done in: - Parameter Negotiation - Discovery Sessions

iSCSI Plugfest (Oct 28 - Nov 3) UNH InterOperability Laboratory Proposed items for the next iSCSI Plugfest 1.Error recovery 2.Full Feature conformance 3.More extensive parameter negotiation in Login Phase 4.More parameter combinations 5.Multiple connections in a single session 6.Larger command windows 7.More testing in Discovery session 8.Digests 9.Security

iSCSI Plugfest (Oct 28 - Nov 3) UNH InterOperability Laboratory Next iSCSI Plugfest information: When:February 11-15, 2002 Where:InterOperability Laboratory University of New Hampshire Durham, New Hampshire Contact:Stephen Schaeffer