From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga03.intel.com (mga03.intel.com [134.134.136.65]) (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 EAFA021E95DFF for ; Wed, 30 Aug 2017 01:54:15 -0700 (PDT) Received: from orsmga005.jf.intel.com ([10.7.209.41]) by orsmga103.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 30 Aug 2017 01:56:57 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.41,448,1498546800"; d="scan'208";a="143608270" Received: from fmsmsx104.amr.corp.intel.com ([10.18.124.202]) by orsmga005.jf.intel.com with ESMTP; 30 Aug 2017 01:56:57 -0700 Received: from FMSMSX109.amr.corp.intel.com (10.18.116.9) by fmsmsx104.amr.corp.intel.com (10.18.124.202) with Microsoft SMTP Server (TLS) id 14.3.319.2; Wed, 30 Aug 2017 01:56:56 -0700 Received: from shsmsx152.ccr.corp.intel.com (10.239.6.52) by fmsmsx109.amr.corp.intel.com (10.18.116.9) with Microsoft SMTP Server (TLS) id 14.3.319.2; Wed, 30 Aug 2017 01:56:56 -0700 Received: from shsmsx103.ccr.corp.intel.com ([169.254.4.219]) by SHSMSX152.ccr.corp.intel.com ([169.254.6.93]) with mapi id 14.03.0319.002; Wed, 30 Aug 2017 16:56:54 +0800 From: "Ye, Ting" To: Santhapur Naveen , "edk2-devel@lists.01.org" Thread-Topic: iSCSI behavior Thread-Index: AdMgjxJAHbHF3NtfTBel/V2bJu1OFgAEKfmwAAenbmAAKX3xcAABz+hQAACQ3KA= Date: Wed, 30 Aug 2017 08:56:54 +0000 Message-ID: References: <625A2455CC232F40B0F38F05ACED6D97FA8E45EA@VENUS1.in.megatrends.com> <625A2455CC232F40B0F38F05ACED6D97FA8E4766@VENUS1.in.megatrends.com> <625A2455CC232F40B0F38F05ACED6D97FA8E4AEC@VENUS1.in.megatrends.com> In-Reply-To: <625A2455CC232F40B0F38F05ACED6D97FA8E4AEC@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: Wed, 30 Aug 2017 08:54:16 -0000 Content-Language: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable There is no such document available. It is an implementation choice only. Thanks, Ting -----Original Message----- From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org] On Behalf Of Sant= hapur Naveen Sent: Wednesday, August 30, 2017 4:47 PM To: Ye, Ting ; edk2-devel@lists.01.org Subject: Re: [edk2] iSCSI behavior Hi Ting, Thank you for your confirmation. I would like to know if there are any specification document(s) available s= o that I can refer them on need. Thank you Naveen -----Original Message----- From: Ye, Ting [mailto:ting.ye@intel.com]=20 Sent: Wednesday, August 30, 2017 1:30 PM To: Santhapur Naveen; edk2-devel@lists.01.org Subject: RE: iSCSI behavior Hi Naveen, For 1) Yes. 2) Yes, it is valid in current implementation. Yes, IPv6 source address should be configured separately. It could be throu= gh manual or auto configuration. Thanks, Ting Ye -----Original Message----- From: Santhapur Naveen [mailto:naveens@amiindia.co.in]=20 Sent: Tuesday, August 29, 2017 8:22 PM To: Ye, Ting ; edk2-devel@lists.01.org Subject: RE: iSCSI behavior Hi Ting, Thanks for your reply. I got your point but my question(s) are 1) I agree that if I add two attempts for the same NIC, there will be a war= ning popup. But my question is whether the second attempt also be tried for= connection if first attempt fails to connect? 2) Is it valid to add two attempts where both are 'Enable for MPIO' for the= same NIC? I'm not clear about IPv6, you mean to say we need to configure an IPv6 addr= ess apart from adding the Attempt? Thank you Naveen -----Original Message----- From: Ye, Ting [mailto:ting.ye@intel.com]=20 Sent: Tuesday, August 29, 2017 2:01 PM To: Santhapur Naveen; edk2-devel@lists.01.org Subject: RE: iSCSI behavior 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 _______________________________________________ edk2-devel mailing list edk2-devel@lists.01.org https://lists.01.org/mailman/listinfo/edk2-devel