From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received-SPF: None (no SPF record) identity=mailfrom; client-ip=203.199.198.232; helo=imsva.in.megatrends.com; envelope-from=karunakarp@amiindia.co.in; receiver=edk2-devel@lists.01.org Received: from IMSVA.IN.MEGATRENDS.COM (Webmail.amiindia.co.in [203.199.198.232]) (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 47F6B21E781F8 for ; Mon, 9 Oct 2017 07:48:35 -0700 (PDT) Received: from IMSVA.IN.MEGATRENDS.COM (IMSVA.IN.MEGATRENDS.COM [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 0DE838205E; Mon, 9 Oct 2017 20:24:49 +0530 (IST) Received: from IMSVA.IN.MEGATRENDS.COM (IMSVA.IN.MEGATRENDS.COM [127.0.0.1]) by IMSVA (Postfix) with ESMTP id EB3C88205B; Mon, 9 Oct 2017 20:24:48 +0530 (IST) Received: from webmail.amiindia.co.in (venus2.in.megatrends.com [10.0.0.7]) by IMSVA.IN.MEGATRENDS.COM (Postfix) with ESMTPS; Mon, 9 Oct 2017 20:24:48 +0530 (IST) Received: from VENUS1.in.megatrends.com ([fe80::951:7975:6ecf:eae5]) by Venus2.in.megatrends.com ([fe80::2002:4a07:4f17:c09b%14]) with mapi id 14.03.0248.002; Mon, 9 Oct 2017 20:21:57 +0530 From: Karunakar P To: "'edk2-devel@lists.01.org'" CC: "Wu, Jiaxin" , "Ye, Ting" , "'Fu, Siyuan'" Thread-Topic: Re: Different ISCSI behavior when 2 attempts are added Thread-Index: AdNBDiU9yAVXAfg8R/eVu/qacNsJ1Q== Date: Mon, 9 Oct 2017 14:51:57 +0000 Message-ID: Accept-Language: en-GB, en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.0.84.128] MIME-Version: 1.0 X-TM-AS-GCONF: 00 X-TM-AS-Product-Ver: IMSVA-9.1.0.1600-8.1.0.1062-23382.000 X-TM-AS-Result: No--15.246-5.0-31-10 X-imss-scan-details: No--15.246-5.0-31-10 X-TMASE-Version: IMSVA-9.1.0.1600-8.1.1062-23382.000 X-TMASE-Result: 10--15.246200-10.000000 X-TMASE-MatchedRID: WMT2WRIkHPNxWR+9hcFWA8NrWpY804TGKx5ICGp/WtFzeKCaw73ZgSqJ GNKrfaCBAEITvPJt4dTFs2ib8f85661rxCs44isjbc297PAGtWbo/OjYPAGsigzvg1/q1MH2f/b TCoZRptI22uoEm245fkFWCvm86w840sXpjQvtH9Abrq24GKfh0Oq/uWzz2rh3+TdKNkxxkWSoBV 9sc+TYx+I+Ja+Fp+EYrBBSnn/GVMan+dP7GcjVHbqQyAveNtg6Mx981lgKTcP7n73d09vr9zdb7 25U3Cx8S+eT5OICrfYiiDah36Jf597M71Z6QWc4SDkh6bW+bccvcKmqjEcY3uO53bHtM9W3Fj/F nq7VF8xSEHEvdGPYmvcml4T4Z1GdgiIO7Sf/7rGL6bUMM+bbIpv8tNLRPUrWyj+mMsG+WjYGk2p TPAu+98m2lthOPKPTEWfo4vokWoiXBXaJoB9JZxRFJJyf5BJeyJ1gFgOMhOkvM/mydp5vVHkguu QorcgMJVLxM6IfZWSNJjC43bhy132S5jUeBQNTbBHjbqiPgOV+3BndfXUhXQ== X-TMASE-SNAP-Result: 1.821001.0001-0-1-12:0,22:0,33:0,34:0,39:0-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: Mon, 09 Oct 2017 14:48:35 -0000 Content-Language: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable 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