public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: Sivaraman Nainar <sivaramann@amiindia.co.in>
To: "edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Cc: "Madhan B. Santharam" <madhans@ami.com>, Omkar K <omkark@amiindia.co.in>
Subject: reg: ISCSI Aborted attempt entry in IBFT Table
Date: Thu, 31 May 2018 12:18:02 +0000	[thread overview]
Message-ID: <B4DE137BDB63634BAC03BD9DE765F1970216726988@VENUS1.in.megatrends.com> (raw)

Hello all:
Here is the issue which requires clarification.
Issue Synopsis:
When there are more than one iSCSI target configured and Ibft table published with the connected and aborted attempt details, all the targets are not seen in ESXi and SLES OS. But in Windows it can see the targets connected.
Use case:
Target 1: IP : 192.xx.xx.31             Target 2 : IP : 192.xx.xx.1
NIC 1 configured with attempts Target 1 & Target 2
NIC 2 configured with attempts Target 1
Connection

Login

Ibft

Block Device in UEFI Shell

SLES / Esx OS

Windows

NIC1 Target1

Success

Published

Mounted

Target Seen



NIC1 Target2

Success

Published

Mounted

Target Seen



NIC1 Target1
NIC1 Target2
NIC2 Target1

Individual Login success

Published for all attempts (3)

NIC1 Target 1 NIC2 Target 1

None Seen

NIC1 Target 1 NIC2 Target 1


When the attempts which are login success but Aborted by ISCSI Driver are present in ibft table SLES and ESX not able to see the targets during Installation.
If the ISCSI Driver not adding the ibft entry for the aborted attempts then the targets are seen in Esx and SLES.
So it requires clarification that If the driver need to SKIP adding the aborted attempt entry to ibft or its OS responsibility to handle the invalid entries in ibft.
-Siva


             reply	other threads:[~2018-05-31 12:18 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-31 12:18 Sivaraman Nainar [this message]
2018-06-04  8:56 ` reg: ISCSI Aborted attempt entry in IBFT Table Ye, Ting
2018-06-05  9:01   ` Omkar K
2018-06-06  8:34     ` Ye, Ting
2018-06-06  9:00       ` Sivaraman Nainar
2018-06-07  0:40         ` Ye, Ting

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=B4DE137BDB63634BAC03BD9DE765F1970216726988@VENUS1.in.megatrends.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