From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: 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 8754621E2BE2C for ; Mon, 28 Aug 2017 23:43:35 -0700 (PDT) Received: from IMSVA.IN.MEGATRENDS.COM (IMSVA.IN.MEGATRENDS.COM [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 6AEAA8205A for ; Tue, 29 Aug 2017 12:18:47 +0530 (IST) Received: from IMSVA.IN.MEGATRENDS.COM (IMSVA.IN.MEGATRENDS.COM [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 54B9C82058 for ; Tue, 29 Aug 2017 12:18:47 +0530 (IST) Received: from webmail.amiindia.co.in (venus2.in.megatrends.com [10.0.0.7]) by IMSVA.IN.MEGATRENDS.COM (Postfix) with ESMTPS for ; Tue, 29 Aug 2017 12:18:47 +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, 29 Aug 2017 12:16:12 +0530 From: Santhapur Naveen To: "edk2-devel@lists.01.org" Thread-Topic: iSCSI behavior Thread-Index: AdMgjxJAHbHF3NtfTBel/V2bJu1OFg== Date: Tue, 29 Aug 2017 06:46:11 +0000 Message-ID: <625A2455CC232F40B0F38F05ACED6D97FA8E45EA@VENUS1.in.megatrends.com> Accept-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.0.84.77] MIME-Version: 1.0 X-TM-AS-GCONF: 00 X-TM-AS-Product-Ver: IMSVA-9.1.0.1600-8.1.0.1062-23288.005 X-TM-AS-Result: No--18.505-5.0-31-10 X-imss-scan-details: No--18.505-5.0-31-10 X-TMASE-Version: IMSVA-9.1.0.1600-8.1.1062-23288.005 X-TMASE-Result: 10--18.505400-10.000000 X-TMASE-MatchedRID: 4PPjBTu2Ztx48YB5KfXbgoGLeiqu1yTKC3HuWcgyQCbKY//WmIj/oW8S phis2z8914gnLq0QZ8eKTvaW2OiqPWuhOfSMRxl/QpxiLlDD9FVAq6/y5AEOOlj/amLs8rQSLiy 64RCveAYnxccK4EM0cCZu90svPKGa1QQDT0/WZj+ZroPNdqiG88DyPNek9e/adDwP5ItpCOwcSR F9JP5Ozi4jb1n1eNA354mbosKUuYfCKxdd3mKUa4oLoibgjVEX+Gz435tISEHimKcLRvsB1fBYR o06eVj38vzD3/0Zl0qFbYEMj70WzDScgMqgJnG/e5NWR5iixe25pw2tsxj4tLXvDHySC+eUTxE5 RpfriHSQhHmNCS57VOXbZzu8Xg2bfbBn31Ku2wzLtNJZxvPj1jGaUEu3RNHWgnL+Z5JyhjWFAf5 iylR8Wnb4Bm7FqQnLXHn0K2CbIexZxuGjBHE908DORqgKKiYqcmsHQK7cMOeyy072phvASaPFjJ EFr+ol4E9s12Gvf50UBfgS1SLQ+CAHAopEd76v8kaqcbtOR3FRwh/5jn23cni1W5o239p5qg6nb FE3Z2kv/KGs+0Dl8Q== X-TMASE-SNAP-Result: 1.821001.0001-0-1-12:0,22:0,33:0,34:0,39:0-0 X-Content-Filtered-By: Mailman/MimeDel 2.1.22 Subject: 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 06:43:36 -0000 Content-Language: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable 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 for 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 for MPIO------IPv4-----DHCP Actual behavior: Attempt#2 shows Initiator IPv4 address. Please provide your suggestions. Thank you Naveen