From: "Ye, Ting" <ting.ye@intel.com>
To: Sivaraman Nainar <sivaramann@amiindia.co.in>,
"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Cc: Omkar K <omkark@amiindia.co.in>, "Madhan B. Santharam" <madhans@ami.com>
Subject: Re: reg: ISCSI Aborted attempt entry in IBFT Table
Date: Mon, 4 Jun 2018 08:56:06 +0000 [thread overview]
Message-ID: <BC0C045B0E2A584CA4575E779FA2C12A1AA9E7B9@SHSMSX103.ccr.corp.intel.com> (raw)
In-Reply-To: <B4DE137BDB63634BAC03BD9DE765F1970216726988@VENUS1.in.megatrends.com>
Hi Siva,
Per design, the iSCSI multipath I/O will publish all configured attempts to IBFT, no matter the connection is success or fail currently.
Did you enable the MPIO when you configure the attempts?
I am not clear what do you mean "aborted attempt".
Thanks,
Ting
-----Original Message-----
From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org] On Behalf Of Sivaraman Nainar
Sent: Thursday, May 31, 2018 8:18 PM
To: edk2-devel@lists.01.org
Cc: Omkar K <omkark@amiindia.co.in>; Madhan B. Santharam <madhans@ami.com>
Subject: [edk2] reg: ISCSI Aborted attempt entry in IBFT Table
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
_______________________________________________
edk2-devel mailing list
edk2-devel@lists.01.org
https://lists.01.org/mailman/listinfo/edk2-devel
next prev parent reply other threads:[~2018-06-04 8:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-31 12:18 reg: ISCSI Aborted attempt entry in IBFT Table Sivaraman Nainar
2018-06-04 8:56 ` Ye, Ting [this message]
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=BC0C045B0E2A584CA4575E779FA2C12A1AA9E7B9@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