From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received-SPF: Pass (sender SPF authorized) identity=mailfrom; client-ip=134.134.136.24; helo=mga09.intel.com; envelope-from=ting.ye@intel.com; receiver=edk2-devel@lists.01.org Received: from mga09.intel.com (mga09.intel.com [134.134.136.24]) (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 5A36721106FBB for ; Wed, 6 Jun 2018 01:34:30 -0700 (PDT) X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from orsmga001.jf.intel.com ([10.7.209.18]) by orsmga102.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 06 Jun 2018 01:34:30 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.49,482,1520924400"; d="scan'208";a="62208509" Received: from fmsmsx103.amr.corp.intel.com ([10.18.124.201]) by orsmga001.jf.intel.com with ESMTP; 06 Jun 2018 01:34:30 -0700 Received: from fmsmsx126.amr.corp.intel.com (10.18.125.43) by FMSMSX103.amr.corp.intel.com (10.18.124.201) with Microsoft SMTP Server (TLS) id 14.3.319.2; Wed, 6 Jun 2018 01:34:29 -0700 Received: from shsmsx104.ccr.corp.intel.com (10.239.4.70) by FMSMSX126.amr.corp.intel.com (10.18.125.43) with Microsoft SMTP Server (TLS) id 14.3.319.2; Wed, 6 Jun 2018 01:34:29 -0700 Received: from shsmsx103.ccr.corp.intel.com ([169.254.4.51]) by SHSMSX104.ccr.corp.intel.com ([169.254.5.87]) with mapi id 14.03.0319.002; Wed, 6 Jun 2018 16:34:27 +0800 From: "Ye, Ting" To: Omkar K , "edk2-devel@lists.01.org" CC: "Madhan B. Santharam" Thread-Topic: reg: ISCSI Aborted attempt entry in IBFT Table Thread-Index: AdP42UDlkFChXFAfQSSCa5fOzOTx6QDB0jOQADK8eZAAMUWyIA== Date: Wed, 6 Jun 2018 08:34:27 +0000 Message-ID: References: <0A1D4EFB13BE094CAC182DD1FADDCFE601C5D56AC2@VENUS1.in.megatrends.com> In-Reply-To: <0A1D4EFB13BE094CAC182DD1FADDCFE601C5D56AC2@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: 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: Wed, 06 Jun 2018 08:34:31 -0000 Content-Language: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi Omkar, If not MPIO, current iSCSI driver will try the configured attempts and only= publish the successful entries in iBFT. The failed attempts will be remove= d. In your case, it looks the ESXi and SLES OS treat the multiple entries on o= ne NIC (different targets) are illegal.=20 Thanks, Ting -----Original Message----- From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org] On Behalf Of Omka= r K Sent: Tuesday, June 5, 2018 5:01 PM To: Ye, Ting ; edk2-devel@lists.01.org Cc: Madhan B. Santharam Subject: Re: [edk2] reg: ISCSI Aborted attempt entry in IBFT Table 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 _______________________________________________ edk2-devel mailing list edk2-devel@lists.01.org https://lists.01.org/mailman/listinfo/edk2-devel