Not via the iscsiadm -m fw command, that mode is currently only used to fetch
ibft/discovery information from fw and proceed to login if requested.
-Anish
> -Original Message-
> From: open-iscsi@googlegroups.com [mailto:open-iscsi@googlegroups.com]
> On Behalf Of Frank Fegert
> Sent: Wed
t; If you can think up a more generic mechanism to add it to libiscsi without
> being overly intrusive that seems reasonable to me. At the moment I don't
> have any better suggestions.
>
> Thanks,
> John
[Anish Bhatt]
Sounds reasonable. Could be accomplished by passing the
Replying for visibility as open-lldp bounced the original message.
On Monday, July 6, 2015 at 5:40:24 PM UTC-7, Anish Bhatt wrote:
>
> I was trying to use the *sk_cgrp_prioidx* value to find correct dcb
> priority for iscsi (using *cgdcbxd* + *cgrulesengd* as recommended by
>
I was trying to use the sk_cgrp_prioidx value to find correct dcb priority for
iscsi (using cgdcbxd + cgrulesengd as recommended by
http://open-lldp.org/dcb_overview). The sk_cgrp_prioidx index into netprio_map
hangs off of struck sock, and the particular iscsi offload driver I'm working
with (
> From: open-iscsi@googlegroups.com [open-iscsi@googlegroups.com]
> on behalf of Anish Bhatt [an...@chelsio.com]
> Sent: Friday, October 24, 2014 12:33 PM
> To: open-iscsi@googlegroups.com
> Cc: Karen Xie; Aviram Bar Haim
> Subject: [RFC] Adding hardware transport support to
I believe it's uname -r on every single linux distro, not just Debian. Probably
just an oversight.
From the uname man page :
-a, --allprint all information,
-r, --kernel-release print the kernel release
-Anish
From: open-iscsi@goo
Pretty sure this is all scripted, and no one is being addressed individually :
https://github.com/gregkh/kernel-history/blob/master/email/mass_mailer
-Anish
From: open-iscsi@googlegroups.com [open-iscsi@googlegroups.com] on behalf of
Ulrich Windl [ulrich.
To: open-iscsi@googlegroups.com
> Cc: Karen Xie
> Subject: Re: boot support for offload transports
>
> On 11/20/2014 06:46 PM, Anish Bhatt wrote:
> > Hello,
> >
> > I was trying to figure out the current state of all the code
> > tagged with “#ifdef OFFLOAD_BOOT_SU
Hello,
I was trying to figure out the current state of all the code tagged
with "#ifdef OFFLOAD_BOOT_SUPPORTED". The recent ibft patches don't seem to
touch any of this at all, and I was wondering what the roadmap for this is ? A
couple of distros seem to enable this, but the default co
Did you by any chance take note of what cards do what? Mostly interested
in bnx2i, cxgb*i, intel, and the ibm boxes with the initiator on them.
[Anish Bhatt] I’d be happy with any cxgb*I support you need. I happened to be
looking at all the stuff under #ifdef OFFLOAD_BOOT_SUPPORTED fairly
I'm currently working on adding open-iscsi hardware transport support to
openstack. The iscsiadm component resides in nova.
As far as I know, iscsiadm has no way to automatically figuring out what
transport to use based simply on on a remote portal/iqn/ip without some sort of
manual discovery.
is not authentication failure and has nothing
> to do with authentication failure. (Indeed, it isn't even the case that
> authentication has been done at all when the 0101 response is generated;
> the RFC clearly states that it may be issued prior to completion of
> authentication.
My bad, I misread the error message to be from here :
if (login_rsp->status_detail == ISCSI_LOGIN_STATUS_AUTH_FAILED) {
log_error("Login failed to authenticate "
"with target %s", session->target_name);
0101 implies you're getting a status class of 0x1 & status detail of 0x1
#define ISCSI_STATUS_CLS_REDIRECT 0x01
#define ISCSI_LOGIN_STATUS_AUTH_FAILED0x01
You are getting redirect as well as auth failed, hence.
-Anish
From: open-iscsi@googlegroup
csi_tcp
>
> But if you were only going to use tcp, then you do not need -I/ifaces at all.
>
> On Jul 25, 2014, at 2:15 PM, Anish Bhatt wrote:
>
> > My motivation was that the minimum required to get tcp via -I is creating
> an iface file that only has " iface.transport
Yes
> -Original Message-
> From: Michael Christie [mailto:micha...@cs.wisc.edu]
> Sent: Friday, July 25, 2014 2:10 PM
> To: open-iscsi@googlegroups.com
> Cc: Karen Xie; Anish Bhatt
> Subject: Re: [PATCH v2] iscsiadm : make iface.ipaddress optional in iface
> config
v2: cxgb4i changed to NOT_REQ as set ipaddress is not supported
Signed-off-by: Anish Bhatt
---
usr/initiator_common.c | 15 ---
usr/transport.c| 8
usr/transport.h| 6 ++
3 files changed, 22 insertions(+), 7 deletions(-)
diff --git a/usr
I'll modify the patch to set cxgb4i to NOT_REQ for cxgb4i, will change it back
to OPT when we add support.
-Anish
> -Original Message-
> From: Karen Xie
> Sent: Friday, July 25, 2014 12:19 PM
> To: Mike Christie; Anish Bhatt
> Cc: open-iscsi@googlegroups.com
&
:micha...@cs.wisc.edu]
> Sent: Friday, July 25, 2014 10:48 AM
> To: open-iscsi@googlegroups.com
> Cc: Anish Bhatt
> Subject: Re: [PATCH trivial] iscsiadm : support using -I tcp or -I iscsi_tcp
>
> On 07/25/2014 12:26 PM, Mike Christie wrote:
> > On 07/24/2014 10:24 PM, Anish
This came up as a scripting issue, iscsiadm currently does not support
specifying tcp as a "default" iface when nothing else is available.
Behaves exactly as if no -I option was used.
Signed-off-by: Anish Bhatt
---
usr/iscsiadm.c | 4
1 file changed, 4 insertions(+)
diff -
Anish
From: Mike Christie [micha...@cs.wisc.edu]
Sent: Thursday, July 24, 2014 9:21 AM
To: open-iscsi@googlegroups.com
Cc: Anish Bhatt; Karen Xie; Anish Bhatt
Subject: Re: [PATCH] iscsiadm : make iface.ipaddress optional in iface configs
for transports that don
I had actually sent this patch out quite some time ago, but it never got
applied or followed up on.
-Anish
--
You received this message because you are subscribed to the Google Groups
"open-iscsi" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to open-is
From: Anish Bhatt
Signed-off-by: Anish Bhatt
---
usr/initiator_common.c | 15 ---
usr/transport.c| 8
usr/transport.h| 6 ++
3 files changed, 22 insertions(+), 7 deletions(-)
diff --git a/usr/initiator_common.c b/usr/initiator_common.c
index 50f8d41
If you're running iscsi-target then discovery will return a portal for every
single IP configured on the machine. Are you running both on the same machine ?
-Anish
From: open-iscsi@googlegroups.com [open-iscsi@googlegroups.com] on behalf of
fel...@usto.re [fel...@
://stgt.sourceforge.net/
-Anish Bhatt
From: open-iscsi@googlegroups.com [open-iscsi@googlegroups.com] on behalf of
fel...@usto.re [fel...@usto.re]
Sent: Wednesday, June 11, 2014 10:10 AM
To: open-iscsi@googlegroups.com
Subject: Does open-iscsi implement target and initiator?
Hi,
I am
m all.
> -Original Message-
> From: Mike Christie [mailto:micha...@cs.wisc.edu]
> Sent: Monday, June 11, 2012 4:17 PM
> To: open-iscsi@googlegroups.com
> Cc: Anish Bhatt
> Subject: Re: [PATCH] iscsid: Add support for net_prio cgroups
>
> On 06/11/2012 06:08 PM, Anish Bhatt wrote:
m all.
> -Original Message-
> From: Mike Christie [mailto:micha...@cs.wisc.edu]
> Sent: Monday, June 11, 2012 3:40 PM
> To: open-iscsi@googlegroups.com
> Cc: Anish Bhatt
> Subject: Re: [PATCH] iscsid: Add support for net_prio cgroups
>
> On 06/08/2012 11:10 PM, Anish Bhatt wro
Mike,
Has there been any progress in figuring out how DCB would co-exist
with net prio cgroups since you removed DCB support ?
-Anish
On Monday, February 27, 2012 2:15:51 PM UTC-8, Rustad, Mark D wrote:
>
> Mike,
>
> On Feb 27, 2012, at 1:24 PM, Mike Christie wrote:
>
> > When it is chang
Both Bugzilla and Redmine have good git integration, that should be
helpful.
-Anish
One socket to bind them all.
> -Original Message-
> From: open-iscsi@googlegroups.com [mailto:open-iscsi@googlegroups.com]
> On Behalf Of Mike Christie
> Sent: Wednesday, November 09, 2011 12:14 PM
> To:
cs.wisc.edu]
> Sent: Tuesday, October 25, 2011 4:38 PM
> To: open-iscsi@googlegroups.com
> Cc: Anish Bhatt
> Subject: Re: [PATCH] make if.ipaddress optional in iface configuration
> files for offload iscsi
>
> On 10/25/2011 06:20 PM, Anish Bhatt wrote:
> >
> > Update pat
> -Original Message-
> From: Mike Christie [mailto:micha...@cs.wisc.edu]
> Sent: Tuesday, October 25, 2011 3:45 PM
> To: open-iscsi@googlegroups.com
> Cc: Anish Bhatt
> Subject: Re: [PATCH] make if.ipaddress optional in iface configuration
> files for offload iscsi
>
patch lets the transport template specify that this field
is optional. After patch, transport can pull ip address from the system,
but this can still be overridden by specifying iface.ipaddress , thus
dropping the hard requirement.
-Anish Bhatt
One socket to bind them all.
--
You
m all.
> -Original Message-
> From: open-iscsi@googlegroups.com [mailto:open-iscsi@googlegroups.com]
> On Behalf Of Rustad, Mark D
> Sent: Friday, October 07, 2011 2:35 PM
> To: open-iscsi@googlegroups.com; Anish Bhatt
> Cc: shyam_i...@dell.com
> Subject: Re: Add initial DCB support
Or,
The DCB patches are in the open-iscsi git tree which currently
resides at http://github.com/mikechristie/open-iscsi
There doesn't seem to be any documentation on this as of now, but from
what I understand it was decided that none of this should be set via
iscsiadm, suggesting the use
Bringing up an old discussion for clarification here. If I understand
correctly iscsi tlvs will be exchanged with protocol id set to
3260(0xCBC) at all times, and this will get mapped to the correct iscsi
traffic flow at the endpoint irrespective of actual running port number.
Is that correct ?
-An
Assuming all your LUNs are under the same target, you can check what
LUNs are being served by `iscsiadm -m session -P 3` after you log in.
Maybe 4 is not the correct LUN number (the first LUN being LUN 0) ?
-Anish
One socket to bind them all.
> -Original Message-
> From: open-iscsi@googl
Anton,
Your externally compiled open-iscsi modules are conflicting with
the inbox modules (*iscsi2) shipped with RHEL/CentOS 5. A quick hack to
get around this would be to remove all modules matching *iscsi* from the
/lib/modules//kernel/drivers/scsi, followed by a make
install on open-iscsi.
[mailto:be...@broadcom.com]
> Sent: Wednesday, November 03, 2010 1:05 PM
> To: Mike Christie
> Cc: open-iscsi@googlegroups.com; Anish Bhatt; Eddie Wai
> Subject: Re: case sensitivity of hardware addresses & vlan configs
>
> Hi Anish,
>
> For the current the Broadcom solution usi
> -Original Message-
> From: Mike Christie [mailto:micha...@cs.wisc.edu]
> Sent: Wednesday, November 03, 2010 12:36 PM
> To: open-iscsi@googlegroups.com
> Cc: Anish Bhatt; Benjamin Li
> Subject: Re: case sensitivity of hardware addresses & vlan configs
>
>
MAC addresses specified in iface files are currently case sensitive.
This can be an issue on vlan interfaces, as isciadm -m iface does not
create config files for vlan interfaces and they need to be written
manually. Attached patch will convert uppercase MAC addresses to lower
case after reading t
40 matches
Mail list logo