From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: 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 BD57821C9127B for ; Tue, 29 Aug 2017 01:28:29 -0700 (PDT) Received: from fmsmga001.fm.intel.com ([10.253.24.23]) by orsmga102.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 29 Aug 2017 01:31:09 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.41,444,1498546800"; d="scan'208";a="1189257831" Received: from fmsmsx106.amr.corp.intel.com ([10.18.124.204]) by fmsmga001.fm.intel.com with ESMTP; 29 Aug 2017 01:31:09 -0700 Received: from fmsmsx117.amr.corp.intel.com (10.18.116.17) by FMSMSX106.amr.corp.intel.com (10.18.124.204) with Microsoft SMTP Server (TLS) id 14.3.319.2; Tue, 29 Aug 2017 01:31:09 -0700 Received: from shsmsx101.ccr.corp.intel.com (10.239.4.153) by fmsmsx117.amr.corp.intel.com (10.18.116.17) with Microsoft SMTP Server (TLS) id 14.3.319.2; Tue, 29 Aug 2017 01:31:08 -0700 Received: from shsmsx103.ccr.corp.intel.com ([169.254.4.219]) by SHSMSX101.ccr.corp.intel.com ([169.254.1.168]) with mapi id 14.03.0319.002; Tue, 29 Aug 2017 16:31:07 +0800 From: "Ye, Ting" To: Santhapur Naveen , "edk2-devel@lists.01.org" Thread-Topic: iSCSI behavior Thread-Index: AdMgjxJAHbHF3NtfTBel/V2bJu1OFgAEKfmw Date: Tue, 29 Aug 2017 08:31:06 +0000 Message-ID: References: <625A2455CC232F40B0F38F05ACED6D97FA8E45EA@VENUS1.in.megatrends.com> In-Reply-To: <625A2455CC232F40B0F38F05ACED6D97FA8E45EA@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: iSCSI behavior 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, 29 Aug 2017 08:28:30 -0000 Content-Language: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi Naveen, For 1), if you configure two attempts with iSCSI Mode "Enabled", you will r= eceive an warning that you have configured two attempts using same NIC.=20 If you configure two attempts with iSCSI Mode "Enabled for MPIO", it is val= id, and if the first attempt failed, the second attempt will be tried. For 2), Enabled for MPIO means you have enabled multi path I/O in iSCSI for= supporting failover. For 3 and 4), iSCSI does not allow configuring one new IPv6 address using i= SCSI menu so Attempt #1 does not show initiator address. Instead, iSCSI driver will let IPv6 driver to perform source address select= ion according to the configured iSCSI target IP address. You need assign IP= v6 source address using ifconfig6 or autoconfiguration before using iSCSI o= n IPv6 stack. Thanks, Ting Ye -----Original Message----- From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org] On Behalf Of Sant= hapur Naveen Sent: Tuesday, August 29, 2017 2:46 PM To: edk2-devel@lists.01.org Subject: [edk2] iSCSI behavior Hello all, I've some questions regarding iSCSI. Please help me out. 1. If I have added two attempts and are enabled for the same MAC, if = the first attempt fails to connect, will the second attempt be tried? 2. If answer to the above is YES, then what's the difference between = ISCSI Modes 'Enabled' and 'Enable for MPIO'? 3. In our observation, we've found that the behavior is not same when= two attempts are added for IPv4 and IPv6. 4. Are there any standard set of test procedures for ISCSI behavior? The following is the conflict Case 1: Attempt#1------Enabled for MPIO------IPv6-----DHCP Attempt#2------Enabled f= or MPIO------IPv6-----DHCP Actual behavior: Attempt#2 doesn't show any initiator IPv6 address. Case 2: Attempt 1------Enabled for MPIO------IPv4-----DHCP Attempt 2------Enabled f= or MPIO------IPv4-----DHCP Actual behavior: Attempt#2 shows Initiator IPv4 address. Please provide your suggestions. Thank you Naveen _______________________________________________ edk2-devel mailing list edk2-devel@lists.01.org https://lists.01.org/mailman/listinfo/edk2-devel