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=omkark@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 A37062110D531 for ; Tue, 5 Jun 2018 02:01:22 -0700 (PDT) Received: from IMSVA.IN.MEGATRENDS.COM (IMSVA.IN.MEGATRENDS.COM [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 5605C8205A; Tue, 5 Jun 2018 14:35:28 +0530 (IST) Received: from IMSVA.IN.MEGATRENDS.COM (IMSVA.IN.MEGATRENDS.COM [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 42C0382059; Tue, 5 Jun 2018 14:35:27 +0530 (IST) Received: from webmail.amiindia.co.in (venus2.in.megatrends.com [10.0.0.7]) by IMSVA.IN.MEGATRENDS.COM (Postfix) with ESMTPS; Tue, 5 Jun 2018 14:35:27 +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; Tue, 5 Jun 2018 14:31:17 +0530 From: Omkar K To: "'Ye, Ting'" , "edk2-devel@lists.01.org" CC: "Madhan B. Santharam" , Sivaraman Nainar Thread-Topic: reg: ISCSI Aborted attempt entry in IBFT Table Thread-Index: AdP42UDlkFChXFAfQSSCa5fOzOTx6QDB0jOQADK8eZA= Date: Tue, 5 Jun 2018 09:01:15 +0000 Message-ID: <0A1D4EFB13BE094CAC182DD1FADDCFE601C5D56AC2@VENUS1.in.megatrends.com> References: In-Reply-To: Accept-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.0.3.48] MIME-Version: 1.0 X-TM-AS-GCONF: 00 X-TM-AS-Product-Ver: IMSVA-9.1.0.1817-8.2.0.1013-23888.005 X-TM-AS-Result: No--9.728-5.0-31-10 X-imss-scan-details: No--9.728-5.0-31-10 X-TMASE-Version: IMSVA-9.1.0.1817-8.2.1013-23888.005 X-TMASE-Result: 10--9.727900-10.000000 X-TMASE-MatchedRID: 6otD/cJAac3HPqim4ABQktxajlW+zwxC5Y0kb0hqaty7qpOHKudqc+9S C4vr4MBRArt7567b9d1O4fijP2drFdTO9w9KisCUEe5D10MltLaeimGtNywjti62hjZS0WoY152 a4j27JxiTINn4OCXr/IES1fL6yUUFrBQfAFELoV9N3UUbIf4esn5Lmbb/xUuayQjMdhdwNq9D9+ lIO/D78nAi2u6GZ8+S1eeaKehxgUKzOchXTgjX0R3EEAbn+GRbAr4+IpK/6afLVJ6SOHUYb5xMD ZMu70jxiELjQGwKd1dneSfbMEEeu10zC58S7cYptT4jIeGRd/V1k+gP1XamtJsoi2XrUn/J8c3c Q4o3WzMXeuQCqIxleXnN0DN7HnFmcpuV2wiOvzLqplwtpJuVQeqi5waiRimNIUU6X3a5wMVfS3F 5XCELSZRMZUCEHkRt X-TMASE-SNAP-Result: 1.821001.0001-0-1-12:0,22:0,33:0,34:0-0 Subject: Re: reg: ISCSI Aborted attempt entry in IBFT Table X-BeenThere: edk2-devel@lists.01.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: EDK II Development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Jun 2018 09:01:23 -0000 Content-Language: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hello Ting, 1. We did not enable MPIO. 2. in IScsiStart(), at this point // // Select the first login session. Abort others. // if (Private->Session =3D=3D NULL) { Private->Session =3D Session; BootSelected =3D AttemptConfigData->AttemptConfigIndex; // // Don't validate other attempt in multipath mode if one is success. // if (mPrivate->EnableMpio) { break; } } else { IScsiSessionAbort (Session); FreePool (Session); } other than one attempt per Nic, other sessions are aborted. Still, all the = attempts are published in IBFT. We can observe the issue when different targets are configured on one NIC w= here all the attempts are published in IBFT. But, the issue disappeared when the aborted attempts are not published in I= BFT. Thanks, Omkar -----Original Message----- From: Ye, Ting [mailto:ting.ye@intel.com]=20 Sent: Monday, June 04, 2018 2:26 PM To: Sivaraman Nainar; edk2-devel@lists.01.org Cc: Omkar K; Madhan B. Santharam Subject: RE: reg: ISCSI Aborted attempt entry in IBFT Table Hi Siva, Per design, the iSCSI multipath I/O will publish all configured attempts to= IBFT, no matter the connection is success or fail currently. Did you enable the MPIO when you configure the attempts?=20 I am not clear what do you mean "aborted attempt". Thanks, Ting -----Original Message----- From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org] On Behalf Of Siva= raman Nainar Sent: Thursday, May 31, 2018 8:18 PM To: edk2-devel@lists.01.org Cc: Omkar K ; Madhan B. Santharam Subject: [edk2] reg: ISCSI Aborted attempt entry in IBFT Table Hello all: Here is the issue which requires clarification. Issue Synopsis: When there are more than one iSCSI target configured and Ibft table publish= ed with the connected and aborted attempt details, all the targets are not = seen in ESXi and SLES OS. But in Windows it can see the targets connected. Use case: Target 1: IP : 192.xx.xx.31 Target 2 : IP : 192.xx.xx.1 NIC 1 configured with attempts Target 1 & Target 2 NIC 2 configured with at= tempts Target 1 Connection Login Ibft Block Device in UEFI Shell SLES / Esx OS Windows NIC1 Target1 Success Published Mounted Target Seen NIC1 Target2 Success Published Mounted Target Seen NIC1 Target1 NIC1 Target2 NIC2 Target1 Individual Login success Published for all attempts (3) NIC1 Target 1 NIC2 Target 1 None Seen NIC1 Target 1 NIC2 Target 1 When the attempts which are login success but Aborted by ISCSI Driver are p= resent in ibft table SLES and ESX not able to see the targets during Instal= lation. If the ISCSI Driver not adding the ibft entry for the aborted attempts then= the targets are seen in Esx and SLES. So it requires clarification that If the driver need to SKIP adding the abo= rted attempt entry to ibft or its OS responsibility to handle the invalid e= ntries in ibft. -Siva _______________________________________________ edk2-devel mailing list edk2-devel@lists.01.org https://lists.01.org/mailman/listinfo/edk2-devel