KEY: 7145F633
===
On Feb 21, 2011, at 5:29 PM, Mike Christie wrote:
On 02/20/2011 06:56 AM, Hoot, Joseph wrote:
Mike,
We had noticed another item that needed updating in the man page (or in the
code itself). Here are the scenarios:
1) `iscsiadm -m node -u
Mike,
We had noticed another item that needed updating in the man page (or in the
code itself). Here are the scenarios:
1) `iscsiadm -m node -u -T iqn_here` = unlogin from that iqn.
2) `iscsiadm -m node -U` = unlogin from ALL iqn's
3) `iscsiadm -m node -u iqn_here` = --- notice we
Mike,
You said that this is not dynamic. Do you know if there are plans to make it
dynamic? I'm not sure if this is part of the RFC or not. I am thinking that
it could be done using async-logout maybe?
Thanks,
Joe
On Feb 10, 2011, at 2:15 PM, Hoot, Joseph wrote:
Hi all,
I'm looking
Hi all,
I'm looking to globally adjust my session timeouts dynamically, if possible. I
have found that if I adjust /etc/iscsi/iscsid.conf and change the following two
values and then run `iscsiadm -m discovery -t st -p portal_ip_here`, it will
use whatever is in iscsid.conf and update the
you can do it per NODE via `iscsiadm -m node -T iqn_here -o delete`
or, if you'd like to remove everything (sometimes I do this if I need to adjust
an iscsid tunable for timeo or something), you can shutdown iscsi via
`/etc/initi.d/iscsi stop` and then `rm -rf /var/lib/iscsi/send_targets/*; rm
/09/2010 01:49 PM, Hoot, Joseph wrote:
I had a similar issue, just not using bonding. The gist of my problem was
that, when connecting a physical network card to a bridge, iscsiadm will not
login through that bridge (at least in my experience). I could discover
just fine, but wasn't ever
We've run into some issues in the past with iSCSI disconnects. As an FYI, one
thing that has helped is is to put dm-multipath in the middle and add another
iface. This allows one path to fail and you still get access to the device. I
know it doesn't necessarily answer your question, but may
We turn our TOE off via ethtool because we've had questionable issues and that
was a first stab at troubleshooting. We have both EQL 5000 and 6000 series.
I'm not sure if it was definitely the problem or not, but we just default to
turning it off in rc.local.
On Feb 22, 2010, at 10:16 PM,
. I'll pull that up shortly.
On Nov 17, 2009, at 10:06 PM, Mike Christie wrote:
Mike Christie wrote:
Hoot, Joseph wrote:
more INLINE below...
On Nov 17, 2009, at 7:27 PM, Mike Christie wrote:
Pasi Kärkkäinen wrote:
On Mon, Nov 16, 2009 at 09:39:00PM -0500, Hoot, Joseph wrote:
On Nov 16
more INLINE below...
On Nov 17, 2009, at 7:27 PM, Mike Christie wrote:
Pasi Kärkkäinen wrote:
On Mon, Nov 16, 2009 at 09:39:00PM -0500, Hoot, Joseph wrote:
On Nov 16, 2009, at 8:19 PM, Hoot, Joseph wrote:
thanks. That helps. So I know that with the EqualLogic targets, there is
a Group
Hi all,
I'm trying to understand what I'm seeing in my /var/log/messages. Here's what
I have:
Nov 13 10:49:47 oim6102506 kernel: connection5:0: ping timeout of 10 secs
expired, last rx 191838122, last ping 191839372, now 191841872
Nov 13 10:49:47 oim6102506 kernel: connection5:0: detected
is more for curiosity sake:
2) Are there plans in the future to have more than one connection per session?
and I guess in addition to that, would that mean multiple connections to a
single volume over the same nic?
On Nov 16, 2009, at 7:18 PM, Mike Christie wrote:
Hoot, Joseph wrote:
Hi
On Nov 16, 2009, at 8:19 PM, Hoot, Joseph wrote:
thanks. That helps. So I know that with the EqualLogic targets, there is a
Group IP which, I believe, responds with an iscsi login_redirect.
1) Could the Login authentication failed message be the response because of
a login redirect
-r
2.6.18-128.2.1.4.9.el5xen
[r...@ovm1 ~]# rpm -qa | grep iscsi
iscsi-initiator-utils-6.2.0.871-0.7.el5
[r...@ovm1 ~]#
On Nov 10, 2009, at 2:30 PM, Mike Christie wrote:
Hoot, Joseph wrote:
[r...@storage ~]# uname -r
2.6.18-164.el5
[r...@storage ~]# rpm -qa | grep iscsi
iscsi-initiator
[r...@storage ~]# uname -r
2.6.18-164.el5
[r...@storage ~]# rpm -qa | grep iscsi
iscsi-initiator-utils-6.2.0.868-0.18.el5_3.1
[r...@storage ~]#
On Nov 10, 2009, at 12:17 PM, Mike Christie wrote:
Hoot, Joseph wrote:
I've had about 3 threads of dt (kicking off a bit randomly) on (3) separate
What version of OiS are you using? I had lots of weirdness and the
same types of disconnects to our Dell EqualLogic when we were
(actually still are in production) using 868 code. I'm now using open-
iscsi-871 code plus a sendwait patch and haven' had the issue. I've
now been slamming
, Mike Christie wrote:
Hoot, Joseph wrote:
What version of OiS are you using? I had lots of weirdness and the
same types of disconnects to our Dell EqualLogic when we were
(actually still are in production) using 868 code. I'm now using
open-
iscsi-871 code plus a sendwait patch and haven
a one off
patch. I can get more details if you'd like.
But so far so good for now
On Nov 9, 2009, at 6:18 PM, Mike Christie wrote:
Hoot, Joseph wrote:
it was for OiS 871 code prior to RHEL 5.4 release (not sure if the
release include it or not). I'm not sure who came up with it. I
LV's without any problem.
Cheers,
Stephan
-Original Message-
From: open-iscsi@googlegroups.com [mailto:open-
is...@googlegroups.com]
On Behalf Of Hoot, Joseph
Sent: Sunday, October 04, 2009 8:56 PM
To: open-iscsi@googlegroups.com
Subject: Re: iscsi through linux software bridge
Has anyone been successful in setting up a linux software bridge and
loging into an iscsi target?
I've setup the following:
Linux Target:
==
eth2 - 192.168.30.1
eth3 - 192.168.30.2
Linux Client:
==
eth2 - BRIDGE=iscsi0
iscsi0 - TYPE=Bridge
iscsi0:1 - 192.168.30.3
eth3 -
I dont' think I sent this properly to the list. This is my second
attempt :)
Has anyone been successful in setting up a linux software bridge and
loging into an iscsi target?
I've setup the following:
Linux Target:
==
eth2 - 192.168.30.1
eth3 - 192.168.30.2
Linux Client:
iface + routing
On 07/13/2009 09:20 AM, Hoot, Joseph wrote:
Mike,
Just as an FYI (in case you were most curious about this issue) I've
narrowed this issue down to something with CHAP. On my EqualLogic, if
I
disable CHAP, I can't reproduce this issue.
So I did the following. I after
: open-iscsi@googlegroups.com [mailto:open-is...@googlegroups.com]
On Behalf Of Mike Christie
Sent: Saturday, July 11, 2009 7:42 PM
To: open-iscsi@googlegroups.com
Subject: Re: iscsiadm -m iface + routing
On 07/10/2009 01:06 PM, Hoot, Joseph wrote:
Mike,
I have some more details on this. It seems
2008 Mike Christie mchris...@redhat.com - 6.2.0.868-0.7
- 444379 Increase login retries for boot.
* Tue Mar 25 2008 Mike Christie mchris...@redhat.com - 6.2.0.868-0.6
- 438092 Print netdev.
-Original Message-
From: Hoot, Joseph
Sent: Thursday, July 09, 2009 11:43 AM
To: 'open-iscsi
Hi all,
I'm currently attempting to implement a Dell EqualLogic iSCSI solution
connected through m1000e switches to Dell m610 blades with (2) iSCSI
dedicated nics in each blade running Oracle VM Server v2.1.5 (which, I
believe, is based off of RHEL5.1).
[r...@oim6102501 log]# rpm -qa | grep
25 matches
Mail list logo
