public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Subramanian, Sriram (EG Servers Platform SW)" <sriram-s@hpe.com>
To: Ye Ting <ting.ye@intel.com>, Fu Siyuan <siyuan.fu@intel.com>,
	Wu Jiaxin <jiaxin.wu@intel.com>
Cc: "Zimmer, Vincent" <vincent.zimmer@intel.com>,
	"Li, Ruth" <ruth.li@intel.com>,
	"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Subject: Re: Question on iBFT for iSCSI
Date: Thu, 25 Aug 2016 09:44:36 +0000	[thread overview]
Message-ID: <DF4PR84MB0041272800C4E86B0528277A80ED0@DF4PR84MB0041.NAMPRD84.PROD.OUTLOOK.COM> (raw)

Any feedback anyone? Is it reasonable to make the change to publish the configured/DHCP provided target IP address rather than the redirected IP to iBFT?

Thanks,
Sriram.

-----Original Message-----
From: Subramanian, Sriram (EG Servers Platform SW) 
Sent: Tuesday, August 23, 2016 7:01 PM
To: 'Ye Ting' <ting.ye@intel.com>; 'Fu Siyuan' <siyuan.fu@intel.com>; 'Wu Jiaxin' <jiaxin.wu@intel.com>
Cc: 'Zimmer, Vincent' <vincent.zimmer@intel.com>; Li, Ruth <ruth.li@intel.com>; edk2-devel@lists.01.org
Subject: Question on iBFT for iSCSI

All,

The IScsiDxe implementation in EDK2 publishes the iBFT with the target IP address to which it connected to, and not the configured IP. These IPs will be the same if there is no iSCSI redirection. However, if the configured target redirects the initiator to another target (as part of iSCSI Login response), the Session data is updated to the new target IP.

To my knowledge, there doesn't look to be any standard/specification governing this, so I believe this is open to debate. 

The reason for this question is that the configured IP address may be that of a server that's doing the redirect to achieve load balancing or high availability in the cluster.

Now if we set the Target IP address in the iBFT to the final IP to which we connected, we lose the redirection capability in case the target at the final IP goes down, and the OS wants to re-establish the connection. 

If we published the original configured IP, then the OS will attempt to reconnect to the configured IP in the iBFT, and will get redirected to another target which is up.

So do you think it makes sense to publish the original configured static IP (or the original IP provided via DHCP) instead of the redirected IP? What are your thoughts on this?

Thanks,
Sriram.


             reply	other threads:[~2016-08-25  9:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-25  9:44 Subramanian, Sriram (EG Servers Platform SW) [this message]
  -- strict thread matches above, loose matches on Subject: below --
2016-08-23 13:30 Question on iBFT for iSCSI Subramanian, Sriram (EG Servers Platform SW)

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=DF4PR84MB0041272800C4E86B0528277A80ED0@DF4PR84MB0041.NAMPRD84.PROD.OUTLOOK.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