Download presentation
Presentation is loading. Please wait.
Published byAubrey Reed Modified over 9 years ago
1
U NIVERSITY of N EW H AMPSHIRE I NTER O PERABILITY L AB iSCSI Plugfest (Feb 11- Feb15) UNH InterOperability Laboratory Yamini Shastry Graduate Research Assistant InterOperability Laboratory University of New Hampshire yshastry@iol.unh.edu www.iol.unh.edu
2
iSCSI Plugfest (Feb 11- 15) UNH InterOperability Laboratory Implementations at the Plugfest Draft 8Draft 9Total Initiators5813 Targets71421 TOTALS122234
3
iSCSI Plugfest (Feb 11- 15) UNH InterOperability Laboratory 19 Companies Attended D8 OnlyD9 Only Both D8 & D9 Total Tools Only0033 Initiator Only0101 Target Only1618 Both Initiator &Target 0257 TOTALS19919
4
iSCSI Plugfest (Feb 11- 15) UNH InterOperability Laboratory Summary of three Plugfests PlugfestDateDraft Tested Companies Attended 1Jul 20010 & 628 2Oct 2001815 3Feb 20028 & 919 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%
5
iSCSI Plugfest (Feb 11- 15) UNH InterOperability Laboratory 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
6
iSCSI Plugfest (Feb 11- 15) UNH InterOperability Laboratory 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.
7
iSCSI Plugfest (Feb 11- 15) UNH InterOperability Laboratory 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 it in iSCSI Standard.”
8
iSCSI Plugfest (Feb 11- 15) UNH InterOperability Laboratory Features Summary Many 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
9
iSCSI Plugfest (Feb 11- 15) UNH InterOperability Laboratory 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
10
iSCSI Plugfest (Feb 11- 15) UNH InterOperability Laboratory Features Summary (continued) No one: - dealt with Markers - dealt with bidirectional operations - dealt with Error recovery above level 0
11
iSCSI Plugfest (Feb 11- 15) UNH InterOperability Laboratory 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
12
iSCSI Plugfest (Feb 11- 15) UNH InterOperability Laboratory 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
13
iSCSI Plugfest (Feb 11- 15) UNH InterOperability Laboratory Next iSCSI Plugfest When:June 3-7 Where:InterOperability Laboratory University of New Hampshire Durham, New Hampshire Contact:Stephen Schaeffer stephens@iol.unh.edu 603-862-5082
Similar presentations
© 2025 SlidePlayer.com. Inc.
All rights reserved.