From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received-SPF: Pass (sender SPF authorized) identity=mailfrom; client-ip=192.55.52.88; helo=mga01.intel.com; envelope-from=ting.ye@intel.com; receiver=edk2-devel@lists.01.org Received: from mga01.intel.com (mga01.intel.com [192.55.52.88]) (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 0262B21F3C187 for ; Mon, 9 Oct 2017 20:05:19 -0700 (PDT) Received: from fmsmga003.fm.intel.com ([10.253.24.29]) by fmsmga101.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 09 Oct 2017 20:08:47 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.42,502,1500966000"; d="scan'208,217";a="908384970" Received: from fmsmsx103.amr.corp.intel.com ([10.18.124.201]) by FMSMGA003.fm.intel.com with ESMTP; 09 Oct 2017 20:08:47 -0700 Received: from fmsmsx102.amr.corp.intel.com (10.18.124.200) by FMSMSX103.amr.corp.intel.com (10.18.124.201) with Microsoft SMTP Server (TLS) id 14.3.319.2; Mon, 9 Oct 2017 20:08:47 -0700 Received: from shsmsx151.ccr.corp.intel.com (10.239.6.50) by FMSMSX102.amr.corp.intel.com (10.18.124.200) with Microsoft SMTP Server (TLS) id 14.3.319.2; Mon, 9 Oct 2017 20:08:46 -0700 Received: from shsmsx103.ccr.corp.intel.com ([169.254.4.213]) by SHSMSX151.ccr.corp.intel.com ([169.254.3.98]) with mapi id 14.03.0319.002; Tue, 10 Oct 2017 11:08:44 +0800 From: "Ye, Ting" To: "Wu, Jiaxin" , Karunakar P , "'edk2-devel@lists.01.org'" CC: "Fu, Siyuan" Thread-Topic: Different ISCSI behavior when 2 attempts are added Thread-Index: AdNBDiU9yAVXAfg8R/eVu/qacNsJ1QAZN0GAAABuhOA= Date: Tue, 10 Oct 2017 03:08:44 +0000 Message-ID: References: <895558F6EA4E3B41AC93A00D163B72741633C7A8@SHSMSX103.ccr.corp.intel.com> In-Reply-To: <895558F6EA4E3B41AC93A00D163B72741633C7A8@SHSMSX103.ccr.corp.intel.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 X-Content-Filtered-By: Mailman/MimeDel 2.1.22 Subject: Re: Different ISCSI behavior when 2 attempts are added X-BeenThere: edk2-devel@lists.01.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: EDK II Development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Oct 2017 03:05:20 -0000 Content-Language: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Yes, I agree that it is the implementation's choice. If you need Attempt 1 = in Case 2&4, try to update "Enabled" to "Enabled for MPIO". Thanks, Ting Ye From: Wu, Jiaxin Sent: Tuesday, October 10, 2017 11:01 AM To: Karunakar P ; 'edk2-devel@lists.01.org' Cc: Ye, Ting ; Fu, Siyuan Subject: RE: Different ISCSI behavior when 2 attempts are added Hi Karunakar, I think it's not the bug according the current iSCSI implementation that t= he first login session will be selected while others are aborted directly. = Here, IP4 is the first login session. I didn't find any state that the first attempt should be connected. Ting an= d Siyuan, If anything wrong, please correct me. Thanks, Jiaxin From: Karunakar P [mailto:karunakarp@amiindia.co.in] Sent: Monday, October 9, 2017 10:52 PM To: 'edk2-devel@lists.01.org' > Cc: Wu, Jiaxin >; Ye, Ting = >; Fu, Siyuan > Subject: Re: Different ISCSI behavior when 2 attempts are added Hello All, Found the below behavior when I try for ISCSI connection with 2 Valid attem= pts. Case 1: Attempt 1---Enabled(ISCSI Mode)---IP4----Enabled(Initiator DHCP)---Disabled= (Target DHCP)--->Valid Attempt Attempt 2---Enabled(ISCSI Mode)---IP6----Enabled(Initiator DHCP)---Disabled= (Target DHCP)--->Valid Attempt EDK2 RESULT:- Attempt1(IP4) connected and shown in shell ,Attempt2 tried bu= t session does not exist Case 2: Attempt 1---Enabled(ISCSI Mode)---IP6----Enabled(Initiator DHCP)---Disabled= (Target DHCP)--->Valid Attempt Attempt 2---Enabled(ISCSI Mode)---IP4----Enabled(Initiator DHCP)---Disabled= (Target DHCP)--->Valid Attempt EDK2 RESULT:- Attempt2(IP4) connected and shown in shell ,Attempt1 tried bu= t session does not exist Case 3: Attempt 1---Enabled(ISCSI Mode)---Autoconfigure --->Valid Attempt Attempt 2---Enabled(ISCSI Mode)---IP6----Enabled(Initiator DHCP)---Disabled= (Target DHCP)--->Valid Attempt EDK2 RESULT:- Attempt1(IP4) connected and shown in shell ,Attempt2 tried bu= t session does not exist Case 4: Attempt 1---Enabled(ISCSI Mode)---IP6--->Valid Attempt Attempt 2---Enabled(ISCSI Mode)---Autoconfigure ----Enabled(Initiator DHCP)= ---Disabled(Target DHCP)--->Valid Attempt EDK2 RESULT:- Attempt2(IP4) connected and shown in shell ,Attempt1 tried bu= t session does not exist 1. Case1 & Case3 looks fine as 1st valid attempt connected 2. But Case2 & Case4 looks bit different, 1St attempt was valid but c= onnection success with 2nd attempt 3. As we found that IScsiIp4 Driver Binding Start is getting call fir= st and processing the IP4 attempt first even though it is 2nd attempt Could you please comment on this whether this is a bug or Not? Thanks, Karunakar