public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Ye, Ting" <ting.ye@intel.com>
To: Santhapur Naveen <naveens@amiindia.co.in>,
	"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Subject: Re: iSCSI behavior
Date: Tue, 29 Aug 2017 08:31:06 +0000	[thread overview]
Message-ID: <BC0C045B0E2A584CA4575E779FA2C12A1A94613A@SHSMSX103.ccr.corp.intel.com> (raw)
In-Reply-To: <625A2455CC232F40B0F38F05ACED6D97FA8E45EA@VENUS1.in.megatrends.com>

Hi Naveen,

For 1), if you configure two attempts with iSCSI Mode "Enabled", you will receive an warning that you have configured two attempts using same NIC. 
If you configure two attempts with iSCSI Mode "Enabled for MPIO", it is valid, 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 iSCSI menu so Attempt #1 does not show initiator address.
Instead, iSCSI driver will let IPv6 driver to perform source address selection according to the configured iSCSI target IP address. You need assign IPv6 source address using ifconfig6 or autoconfiguration before using iSCSI on IPv6 stack.

Thanks,
Ting Ye


-----Original Message-----
From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org] On Behalf Of Santhapur 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 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
_______________________________________________
edk2-devel mailing list
edk2-devel@lists.01.org
https://lists.01.org/mailman/listinfo/edk2-devel


  reply	other threads:[~2017-08-29  8:28 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-29  6:46 iSCSI behavior Santhapur Naveen
2017-08-29  8:31 ` Ye, Ting [this message]
2017-08-29 12:22   ` Santhapur Naveen
2017-08-30  7:59     ` Ye, Ting
2017-08-30  8:46       ` Santhapur Naveen
2017-08-30  8:56         ` Ye, Ting
2017-08-30  8:58           ` Santhapur Naveen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-list from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=BC0C045B0E2A584CA4575E779FA2C12A1A94613A@SHSMSX103.ccr.corp.intel.com \
    --to=devel@edk2.groups.io \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox