From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga14.intel.com (mga14.intel.com [192.55.52.115]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ml01.01.org (Postfix) with ESMTPS id 1FC0581F28 for ; Tue, 28 Feb 2017 00:52:46 -0800 (PST) Received: from orsmga001.jf.intel.com ([10.7.209.18]) by fmsmga103.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 28 Feb 2017 00:52:44 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.35,218,1484035200"; d="scan'208";a="1103097362" Received: from fmsmsx105.amr.corp.intel.com ([10.18.124.203]) by orsmga001.jf.intel.com with ESMTP; 28 Feb 2017 00:52:44 -0800 Received: from fmsmsx113.amr.corp.intel.com (10.18.116.7) by FMSMSX105.amr.corp.intel.com (10.18.124.203) with Microsoft SMTP Server (TLS) id 14.3.248.2; Tue, 28 Feb 2017 00:52:44 -0800 Received: from shsmsx152.ccr.corp.intel.com (10.239.6.52) by FMSMSX113.amr.corp.intel.com (10.18.116.7) with Microsoft SMTP Server (TLS) id 14.3.248.2; Tue, 28 Feb 2017 00:52:43 -0800 Received: from shsmsx103.ccr.corp.intel.com ([169.254.4.20]) by SHSMSX152.ccr.corp.intel.com ([169.254.6.132]) with mapi id 14.03.0248.002; Tue, 28 Feb 2017 16:52:42 +0800 From: "Ye, Ting" To: Santhapur Naveen , "edk2-devel@lists.01.org" Thread-Topic: ISCSI says "Session Doesn't Exist" Thread-Index: AdKOo1PNr5oKc1KtQkGfr5/iCtjCdwCKemiwABmDlokAGveAcA== Date: Tue, 28 Feb 2017 08:52:41 +0000 Message-ID: References: <625A2455CC232F40B0F38F05ACED6D978C4E1F3B@VENUS1.in.megatrends.com>, <625A2455CC232F40B0F38F05ACED6D978C4E2EFB@VENUS1.in.megatrends.com> In-Reply-To: <625A2455CC232F40B0F38F05ACED6D978C4E2EFB@VENUS1.in.megatrends.com> Accept-Language: zh-CN, en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.239.127.40] MIME-Version: 1.0 Subject: Re: ISCSI says "Session Doesn't Exist" X-BeenThere: edk2-devel@lists.01.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: EDK II Development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Feb 2017 08:52:46 -0000 Content-Language: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi Naveen, Thanks for your info. We are able to reproduce the issue using Windows Serv= er 2012 now. So far we are still not sure whether it is a particular issue = in Windows iSCSI target or UEFI iSCSI initiator. Will update to you once we have further information later.=20 For your info: A link describes the know issues in Windows Server 2012 iSCS= I target, https://technet.microsoft.com/en-us/library/jj863561(v=3Dws.11).a= spx. It has a related issue but not the same one we met now.=20 Standard Login Key Negotiation RFC 3720, section 10.13.3, specifies the following: For a new session, the target MUST generate a non-zero TSIH and ONLY return= it in the Login Final-Response. The behavior exhibited by ISCSI Target Server: When the iSCSI initiator performed a standard login and negotiated the logi= n parameters, the iSCSI Target Server was observed to set the TSIH field in= the first Login Response PDU. Thanks, Ting -----Original Message----- From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org] On Behalf Of Sant= hapur Naveen Sent: Tuesday, February 28, 2017 4:04 AM To: Ye, Ting ; edk2-devel@lists.01.org Subject: Re: [edk2] ISCSI says "Session Doesn't Exist" Hello Ting, I've configured iSCSI target in Windows Server 2012. And the procedure is s= imilar as in https://blogs.technet.microsoft.com/filecab/2012/05/21/introdu= ction-of-iscsi-target-in-windows-server-2012/ Please let me know if I had to make any changes to my iSCSI server. Thank you, Naveen ________________________________________ From: Ye, Ting [ting.ye@intel.com] Sent: Monday, February 27, 2017 1:23 PM To: Santhapur Naveen; edk2-devel@lists.01.org Subject: RE: ISCSI says "Session Doesn't Exist" Hi Naveen, According to the table you shared (defined in RFC 3720), it seems when TSIH= is ZERO, the target should not fail the login with "session does not exist= ". +------------------------------------------------------------------+ |new | zero | any | instantiate a new session | +------------------------------------------------------------------+ |existing | zero | any | do session reinstatement | | | | | (see section 5.3.5) | +------------------------------------------------------------------+ I checked the latest code in NetworkPkg/IScsiDxe, the Tsih is always set to= ZERO in IScsiSessionInit. The immediate reset will also trigger driver bin= ding start so IScsiSessionInit will be executed. It seems to me your iSCSI target does not comply with the rules defined in = RFC documentation. If possible, would you please tell us which iSCSI target= are you using? Thanks, Ting -----Original Message----- From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org] On Behalf Of Sant= hapur Naveen Sent: Friday, February 24, 2017 9:59 PM To: edk2-devel@lists.01.org Subject: [edk2] ISCSI says "Session Doesn't Exist" Hello all, I've a question about IScsi and any suggestions would be helpful [Issue Summary] If I add an ISCSI attempt and on the next reboot, a connection will be esta= blished in between the initiator and the target. Till now, it is fine. Now = if I do an immediate reset with in 20 seconds, on the next boot, the initia= tor is trying to establish a session, but the target rejects saying "Sessio= n does not exist". If I reset after 20 seconds or so, the connection would = have been established with the same login details. To dive deeper, I've checked the RFC documentation on this and found the fo= llowing information. But when I checked the wireshark capture, I found my T= SIH is ZERO even for the immediate session. If I want to make my immediate = session also into a successful one, what should I be doing? I'm aware that = there's a function available IScsiSessionAbort(). Would it help me or provi= de your suggestions to get me going. +------------------------------------------------------------------+ |ISID | TSIH | CID | Target action | +------------------------------------------------------------------+ |new | non-zero | any | fail the login | | | | | ("session does not exist") | +------------------------------------------------------------------+ |new | zero | any | instantiate a new session | +------------------------------------------------------------------+ |existing | zero | any | do session reinstatement | | | | | (see section 5.3.5) | +------------------------------------------------------------------+ |existing | non-zero | new | add a new connection to | | | existing | | the session | +------------------------------------------------------------------+ |existing | non-zero |existing| do connection reinstatement| | | existing | | (see section 5.3.4) | +------------------------------------------------------------------+ |existing | non-zero | any | fail the login | | | new | | ("session does not exist") | +------------------------------------------------------------------+ Thanks, Naveen _______________________________________________ edk2-devel mailing list edk2-devel@lists.01.org https://lists.01.org/mailman/listinfo/edk2-devel _______________________________________________ edk2-devel mailing list edk2-devel@lists.01.org https://lists.01.org/mailman/listinfo/edk2-devel