150 likes | 325 Views
iSCSI Plugfest (Oct 28 - Nov 3) UNH InterOperability Laboratory. Yamini Shastry Graduate Research Assistant InterOperability Laboratory University of New Hampshire yshastry@iol.unh.edu www.iol.unh.edu. 15 Companies Attended, Testing was against Draft 8. Overview of testing.
E N D
iSCSI Plugfest (Oct 28 - Nov 3) UNH InterOperability Laboratory Yamini Shastry Graduate Research AssistantInterOperability LaboratoryUniversity of New Hampshire yshastry@iol.unh.eduwww.iol.unh.edu
Overview of testing • Login Conformance Test Package - Test Suite - Scripts - Testor • Interop test procedure • Reference implementation • - For both Initiator & Target • Protocol Analyzer
Issues Discovered • Issue 1: • I-bit not set on first login of the session. How should Target react? • Changes Made: • - 3.13.5 – “Class 2 - Initiator error (not format error)”- Bit 6 of byte 1, in login request pdu changed from I to 1.
Issues Discovered • Issue 2: • Is not offering a key an implicit offering of default value? • Changes Made: • - 2.2.4 – Reworded to say no.- An explanation added about originator and responder.
Issues Discovered • Issue 3: • When is the Target Name required. When is it optional? • Changes Made: • After discussion on ips@ece.cmu.edu list, consensus was: • - 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
Issues Discovered • Issue 4: • Is a receiver required to check the reserved fields? • Changes Made: • After discussion on ips@ece.cmu.edu list, consensus was: • - Section 3 – “Any compliant receiver must ignore any bit not specified and all reserved fields.”
Issues Discovered • Issue 5: • Can an Initiator send commands out of CmdSN order on any single connection? • Changes Made: • After much discussion on ips@ece.cmu.edu list, consensus was: • - 2.2.2.1 – Reworded to say no.
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.
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.
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
Proposed items for the next iSCSI Plugfest • Error recovery • Full Feature conformance • More extensive parameter negotiation in Login Phase • More parameter combinations • Multiple connections in a single session • Larger command windows • More testing in Discovery session • Digests • Security
Next iSCSI Plugfest information: When: February 11-15, 2002 Where: InterOperability Laboratory University of New Hampshire Durham, New Hampshire Contact: Stephen Schaeffer stephens@iol.unh.edu 603-862-5082