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.93; helo=mga11.intel.com; envelope-from=ting.ye@intel.com; receiver=edk2-devel@lists.01.org Received: from mga11.intel.com (mga11.intel.com [192.55.52.93]) (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 078342110C824 for ; Mon, 4 Jun 2018 01:56:08 -0700 (PDT) X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from fmsmga008.fm.intel.com ([10.253.24.58]) by fmsmga102.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 04 Jun 2018 01:56:08 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.49,476,1520924400"; d="scan'208";a="45074116" Received: from fmsmsx105.amr.corp.intel.com ([10.18.124.203]) by fmsmga008.fm.intel.com with ESMTP; 04 Jun 2018 01:56:08 -0700 Received: from fmsmsx115.amr.corp.intel.com (10.18.116.19) by FMSMSX105.amr.corp.intel.com (10.18.124.203) with Microsoft SMTP Server (TLS) id 14.3.319.2; Mon, 4 Jun 2018 01:56:08 -0700 Received: from shsmsx151.ccr.corp.intel.com (10.239.6.50) by fmsmsx115.amr.corp.intel.com (10.18.116.19) with Microsoft SMTP Server (TLS) id 14.3.319.2; Mon, 4 Jun 2018 01:56:08 -0700 Received: from shsmsx103.ccr.corp.intel.com ([169.254.4.51]) by SHSMSX151.ccr.corp.intel.com ([169.254.3.116]) with mapi id 14.03.0319.002; Mon, 4 Jun 2018 16:56:07 +0800 From: "Ye, Ting" To: Sivaraman Nainar , "edk2-devel@lists.01.org" CC: Omkar K , "Madhan B. Santharam" Thread-Topic: reg: ISCSI Aborted attempt entry in IBFT Table Thread-Index: AdP42UDlkFChXFAfQSSCa5fOzOTx6QDB0jOQ Date: Mon, 4 Jun 2018 08:56:06 +0000 Message-ID: References: In-Reply-To: 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: Mon, 04 Jun 2018 08:56:09 -0000 Content-Language: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable 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