from:"david elsen"

RE: [ANNOUNCE] open-iscsi-2.0-872-rc2

2010-07-07 Thread david elsen

does it have any kernel dependency? Will it work on rhel 5.3 inbox kernel
(2.6.18.128)?

Date: Wed, 7 Jul 2010 14:37:18 -0500
From: micha...@cs.wisc.edu
To: open-iscsi@googlegroups.com
Subject: [ANNOUNCE] open-iscsi-2.0-872-rc2

There is a new release candidate release, open-iscsi-2.0-872-rc2 here:

http://kernel.org/pub/linux/kernel/people/mnc/open-iscsi/releases/open-iscsi-2.0-872-rc2.tar.gz

(still having troubles with open-iscsi.org so it is on kernel.org).

Major changes:

- be2iscsi support.

- discovery mode is depreciated. The discovery db commands are now fixed
to support the update command (-o update -n name -v value), but it
conflicted with the old default behavior, so this releases adds a
discovery2 command. With this you need to pass in the --discovery/-D
command to instruct iscsiadm to do discovery. If you do not, then it
will do a discovery db operation, so it behaves similar to node mode and
the --login command.

To do discovery do:

# iscsiadm -m discovery2 -t st -p IP:port -D

This will create a discovery record for IP:port if not created. If there
is an existing record, then iscsiadm will use the settings in there.

If you just wanted to create a discovery record do:

# iscsiadm -m discovery2 -t st -p IP:port -o new

And if you wanted to update a record setting run:

# iscsiadm -m discovery2 -t st -p IP:port -o update -n name -v setting

To see settings do:

# iscsiadm -m discovery2 -t st -p IP:port [optional to see CHAP
passwords also use--show]

To see how portals were found:

# iscsaidm -m discovery2 -P 1

- The iSNS discovery node is now fully supported and the command has
been marked as stable (or actually the experimental tag was removed).
The discovery command for this has changed.

To discover a target with isns do:

iscsiadm -m discovery2 -t isns -p IP:port

(the iscsid.conf setting is not supported).

You can also set things up so iscsid just does iSNS queries and logs in
and out of targets based on those queries and iSNS SCNs. With this
Discovery Daemon mode there is not need to run the iscsiadm isns
discovery command above. iscsid will do it for you.

To set this up do:

- Create a iSNS record by passing iscsiadm the -o new argument in
discovery2 mode.
# iscsiadm -m discovery2 -t isns -p 20.15.0.7:3205 -o new
New discovery record for [20.15.0.7,3205] added.

- Set the use_discoveryd setting for the record.
# iscsiadm -m discovery2 -t isns -p 20.15.0.7:3205 -o update -n
discovery.isns.use_discoveryd -v Yes

- [OPTIONAL] Set the polling interval if using Microsoft or
linux-isns/SLES or RHEL 5 iSNS servers:

# iscsiadm -m discovery2 -t st -p 20.15.0.7:3205 -o update -n
discovery.isns.discoveryd_poll_inval -v 30

To have the new settings take effect restart iscsid by restarting the
iscsi service.

See section 7.4 of the README for more info and details.

- There is also a SendTargets Discovery Daemon mode. It works like
linux-iscsi's default mode. Again, for this, you do not have to run
iscsiadm's sendtargets discovery command. iscsid will do it for you. To
set this up do:

- Create a SendTargets record by passing iscsiadm the -o new argument in
discovery2 mode.
# iscsiadm -m discovery2 -t st -p 20.15.0.7:3260 -o new
New discovery record for [20.15.0.7,3260] added.

- Set the use_discoveryd setting for the record.
# iscsiadm -m discovery2 -t st -p 20.15.0.7:3260 -o update -n
discovery.sendtargets.use_discoveryd -v Yes

- Set the polling interval.
# iscsiadm -m discovery2 -t st -p 20.15.0.7:3260 -o update -n
discovery.sendtargets.discoveryd_poll_inval -v 30

To have the new settings take effect restart iscsid by restarting the
iscsi service.

See section 7.4 of the README for more info and details.

- 2.6.33 - 2.6.35 kernel support added.

--
You received this message because you are subscribed to the Google Groups
open-iscsi group.
To post to this group, send email to open-is...@googlegroups.com.
To unsubscribe from this group, send email to
open-iscsi+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/open-iscsi?hl=en.

_
The New Busy is not the old busy. Search, chat and e-mail from your inbox.
http://www.windowslive.com/campaign/thenewbusy?ocid=PID28326::T:WLMTAGL:ON:WL:en-US:WM_HMP:042010_3

RE: removing auto login from Initiator

2010-05-20 Thread david elsen

For Logout:

Yes, I was doing logout and then deleting the entry.

For Login:

I do discovery to get the iSCSI name and record.

Then update it to manual and doing the login with iSCSI name.

I will update /etc/iscsi/iscsid.conf to it easier.

thanks,

david

Date: Mon, 17 May 2010 19:41:47 -0500
From: micha...@cs.wisc.edu
To: open-iscsi@googlegroups.com
CC: elsen_da...@hotmail.com
Subject: Re: removing auto login from Initiator

On 05/17/2010 05:55 PM, david elsen wrote:

Mike,

Thanks. Your suggestion worked.

But I have to do following:

1. Discovery login to get the name.

2. Update the record for manual

3. Normal login.

to do the login

For deleting, I have to do:

1. Logout

2. Delete.

I am not sure what you are saying.

Are you deleting and updating the record to manual? If so
you do not have to set the record for manual and delete it. You can just
do one or the other. For deletion then you do not need to logout, if you
just delete the records you do not want, then do the login.

You could also just set them all as manual by default by setting the
node.startup = manual in /etc/iscsi/iscsid.conf. Then just manually
login to the ones you want or set the ones you want to node.startup =
automatic by running iscsiadm.

_
Hotmail has tools for the New Busy. Search, chat and e-mail from your inbox.
http://www.windowslive.com/campaign/thenewbusy?ocid=PID28326::T:WLMTAGL:ON:WL:en-US:WM_HMP:042010_1

RE: removing auto login from Initiator

2010-05-17 Thread david elsen

Mike,

Thanks. Your suggestion worked.

But I have to do following:

1. Discovery login to get the name.

2. Update the record for manual

3. Normal login.

to do the login

For deleting, I have to do:

1. Logout

2. Delete.

I am not sure if I can have any simpler approach.

Thanks,

David

Date: Fri, 14 May 2010 22:56:07 -0500
From: micha...@cs.wisc.edu
To: open-iscsi@googlegroups.com
CC: elsen_da...@hotmail.com
Subject: Re: removing auto login from Initiator

On 05/14/2010 07:47 PM, david elsen wrote:

Once I have done login to the target using iscsiadm - from the initiator,
after next reboot Initiator connects to the target without running the
command.

How can I stop that? I have multiple targets on my set-up and want to
connect them one-by-one.

Either

1. delete the record

iscsiadm -m node -T target -p ip -o delete

2. mark node.startup as manual for the record

iscsiadm -m node -T target -p ip -o update -n node.startup -v manual
iscsiadm -m node -T target -p ip -o update -n node.conn[0].startup -v
manual

_
The New Busy is not the too busy. Combine all your e-mail accounts with Hotmail.
http://www.windowslive.com/campaign/thenewbusy?tile=multiaccountocid=PID28326::T:WLMTAGL:ON:WL:en-US:WM_HMP:042010_4

removing auto login from Initiator

2010-05-14 Thread david elsen



Once I have done login to the target using iscsiadm - from the initiator, 
after next reboot Initiator connects to the target without running the command.

 

How can I stop that? I have multiple targets on my set-up and want to connect 
them one-by-one.

 

Can someone help me with with this please?

 

thanks,

david

 
  
_
The New Busy is not the too busy. Combine all your e-mail accounts with Hotmail.
http://www.windowslive.com/campaign/thenewbusy?tile=multiaccountocid=PID28326::T:WLMTAGL:ON:WL:en-US:WM_HMP:042010_4

-- 
You received this message because you are subscribed to the Google Groups 
open-iscsi group.
To post to this group, send email to open-is...@googlegroups.com.
To unsubscribe from this group, send email to 
open-iscsi+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/open-iscsi?hl=en.

RE: compilation error with open-iscsi-2.0-871.tar.gz on RHEL 5.3

2010-05-12 Thread david elsen

thanks. yes it worked. In README, it is written to do make install directly
otherwise I might have missed it.

Date: Tue, 11 May 2010 21:32:24 -0500
From: micha...@cs.wisc.edu
To: open-iscsi@googlegroups.com
CC: elsen_da...@hotmail.com
Subject: Re: compilation error with open-iscsi-2.0-871.tar.gz on RHEL 5.3

On 05/11/2010 05:40 PM, david elsen wrote:

Can someone tell me what I am missing on my system if I am getting
following compilation error? I am using RHEL 5.3 default kernel.

[r...@pegasus open-iscsi-2.0-871]# make install

It should work if you do a make then make install.

_
The New Busy think 9 to 5 is a cute idea. Combine multiple calendars with
Hotmail.
http://www.windowslive.com/campaign/thenewbusy?tile=multicalendarocid=PID28326::T:WLMTAGL:ON:WL:en-US:WM_HMP:042010_5

compilation error with open-iscsi-2.0-871.tar.gz on RHEL 5.3

2010-05-11 Thread david elsen


Can someone tell me what I am missing on my system if I am getting following 
compilation error? I am using RHEL 5.3 default kernel.


[r...@pegasus open-iscsi-2.0-871]# make install
make -C kernel install_kernel
make[1]: Entering directory `/root/open-iscsi-2.0-871/kernel'
echo Patching source code for linux-2.6.14-23 ...
Patching source code for linux-2.6.14-23 ...
if [ -e cur_patched ]; then \
make -C . clean; \
fi
patch -p1  2.6.14-23_compat.patch
patching file iscsi_tcp.c
Hunk #1 succeeded at 460 (offset 4 lines).
Hunk #3 succeeded at 838 (offset 4 lines).
Hunk #5 succeeded at 859 (offset 4 lines).
patching file iscsi_tcp.h
patching file libiscsi.c
Hunk #2 succeeded at 86 (offset 23 lines).
Hunk #4 succeeded at 328 (offset 23 lines).
Hunk #6 succeeded at 401 (offset 23 lines).
Hunk #8 succeeded at 729 (offset 23 lines).
Hunk #10 succeeded at 796 (offset 23 lines).
Hunk #11 succeeded at 1504 (offset 6 lines).
patching file libiscsi.h
patching file libiscsi_tcp.c
Hunk #5 succeeded at 697 with fuzz 2 (offset 1 line).
patching file libiscsi_tcp.h
patching file open_iscsi_compat.h
patching file scsi_transport_iscsi.c
patching file scsi_transport_iscsi.h
cp 2.6.14-23_compat.patch has_14to23_patch
ln -s has_14to23_patch cur_patched
make -C /lib/modules/2.6.18-128.el5PAE/build M=`pwd` KBUILD_OUTPUT=  V=0 modules
make[2]: Entering directory `/usr/src/kernels/2.6.18-128.el5-PAE-i686'
  CC [M]  /root/open-iscsi-2.0-871/kernel/scsi_transport_iscsi.o
/root/open-iscsi-2.0-871/kernel/scsi_transport_iscsi.c: In function 
‘__iscsi_unblock_session’:
/root/open-iscsi-2.0-871/kernel/scsi_transport_iscsi.c:535: warning: unused 
variable ‘ihost’
/root/open-iscsi-2.0-871/kernel/scsi_transport_iscsi.c: In function 
‘__iscsi_block_session’:
/root/open-iscsi-2.0-871/kernel/scsi_transport_iscsi.c:579: warning: passing 
argument 2 of ‘queue_delayed_work’ from incompatible pointer type
/root/open-iscsi-2.0-871/kernel/scsi_transport_iscsi.c: At top level:
/root/open-iscsi-2.0-871/kernel/scsi_transport_iscsi.c:1266: warning: 
‘iscsi_if_ep_connect’ defined but not used
  CC [M]  /root/open-iscsi-2.0-871/kernel/libiscsi.o
/root/open-iscsi-2.0-871/kernel/libiscsi.c: In function ‘iscsi_target_alloc’:
/root/open-iscsi-2.0-871/kernel/libiscsi.c:1547: warning: unused variable 
‘session’
  CC [M]  /root/open-iscsi-2.0-871/kernel/libiscsi_tcp.o
/root/open-iscsi-2.0-871/kernel/libiscsi_tcp.c: In function 
‘iscsi_tcp_dgst_header’:
/root/open-iscsi-2.0-871/kernel/libiscsi_tcp.c:305: warning: passing argument 2 
of ‘sg_init_one’ discards qualifiers from pointer target type
  CC [M]  /root/open-iscsi-2.0-871/kernel/iscsi_tcp.o
  Building modules, stage 2.
  MODPOST
  CC  /root/open-iscsi-2.0-871/kernel/iscsi_tcp.mod.o
  LD [M]  /root/open-iscsi-2.0-871/kernel/iscsi_tcp.ko
  CC  /root/open-iscsi-2.0-871/kernel/libiscsi.mod.o
  LD [M]  /root/open-iscsi-2.0-871/kernel/libiscsi.ko
  CC  /root/open-iscsi-2.0-871/kernel/libiscsi_tcp.mod.o
  LD [M]  /root/open-iscsi-2.0-871/kernel/libiscsi_tcp.ko
  CC  /root/open-iscsi-2.0-871/kernel/scsi_transport_iscsi.mod.o
  LD [M]  /root/open-iscsi-2.0-871/kernel/scsi_transport_iscsi.ko
make[2]: Leaving directory `/usr/src/kernels/2.6.18-128.el5-PAE-i686'
make -C /lib/modules/2.6.18-128.el5PAE/build M=`pwd` KBUILD_OUTPUT=  V=0 
modules_install INSTALL_MOD_DIR=kernel/drivers/scsi INSTALL_MOD_PATH=
make[2]: Entering directory `/usr/src/kernels/2.6.18-128.el5-PAE-i686'
  INSTALL /root/open-iscsi-2.0-871/kernel/iscsi_tcp.ko
  INSTALL /root/open-iscsi-2.0-871/kernel/libiscsi.ko
  INSTALL /root/open-iscsi-2.0-871/kernel/libiscsi_tcp.ko
  INSTALL /root/open-iscsi-2.0-871/kernel/scsi_transport_iscsi.ko
  DEPMOD  2.6.18-128.el5PAE
make[2]: Leaving directory `/usr/src/kernels/2.6.18-128.el5-PAE-i686'
make[1]: Leaving directory `/root/open-iscsi-2.0-871/kernel'
cc usr/iscsid.c   -o usr/iscsid
In file included from usr/iscsid.c:34:
usr/mgmt_ipc.h:23:22: error: iscsi_if.h: No such file or directory
In file included from usr/mgmt_ipc.h:24,
 from usr/iscsid.c:34:
usr/config.h:27:18: error: list.h: No such file or directory
In file included from usr/mgmt_ipc.h:24,
 from usr/iscsid.c:34:
usr/config.h:189: error: field ‘list’ has incomplete type
usr/config.h:205: error: ‘TARGET_NAME_MAXLEN’ undeclared here (not in a 
function)
usr/config.h:210: error: field ‘list’ has incomplete type
In file included from usr/iscsid.c:34:
usr/mgmt_ipc.h:119: error: field ‘ev’ has incomplete type
usr/mgmt_ipc.h:120: error: field ‘stats’ has incomplete type
usr/mgmt_ipc.h:121: error: invalid application of ‘sizeof’ to incomplete type 
‘struct iscsi_stats_custom’ 
usr/mgmt_ipc.h:122: error: ‘ISCSI_STATS_CUSTOM_MAX’ undeclared here (not in a 
function)
usr/mgmt_ipc.h:125: error: ‘VALUE_MAXLEN’ undeclared here (not in a function)
In file included from usr/iscsid.c:36:
usr/iscsi_ipc.h:79: warning: ‘enum iscsi_param’ declared inside parameter list
usr/iscsi_ipc.h:79: warning:

RE: information on the config option -- node.session.iscsi.FastAbort = No

2010-04-29 Thread david elsen

Mike,

How can I get the 5.4 and 5.5 kernel fixes and latest iscs-initiator-utils for
RHEL 5.3 Kernel?

I would like to change the ISID from initiator while it is trying to connect to
target. I would like to establish multiple iSCSI session between my Initiator
and target. I do not see any option for this in the Linux initiator on my
system.

I am using RHEL 5.3 with 2.6.18-128.el5 kernel.

Thanks,

David

Date: Wed, 28 Apr 2010 12:48:44 -0500
From: micha...@cs.wisc.edu
To: open-iscsi@googlegroups.com
CC: mforou...@gmail.com
Subject: Re: information on the config option -- node.session.iscsi.FastAbort
= No

On 04/28/2010 12:43 PM, Mike Christie wrote:
On 04/28/2010 10:40 AM, maguar887 wrote:
We are currently running open iscsi version 2.0-871 on RHEL 5.3
(2.6.18-92.1.6.0.2.el5) against a Dell Equallogic iScsi SAN group
(firmware 4.3.5)

You need to upgrade your kernel. It had a bug with eql targets in the
async logout path. It is fixed in 5.4 and 5.5 kernels.

Upgrade your iscsi-initiator-utils too.

_
The New Busy is not the old busy. Search, chat and e-mail from your inbox.
http://www.windowslive.com/campaign/thenewbusy?ocid=PID28326::T:WLMTAGL:ON:WL:en-US:WM_HMP:042010_3

RE: information on the config option -- node.session.iscsi.FastAbort = No

2010-04-29 Thread david elsen

Mike,

You cannot control the ISID. The iscsi layer does thos for you. You can
control the initiator name, but if you just wanted to create multiple
sessions with different ISIDs and let the iscsi layer do it for you then
the tools in 5.3 should work. Do you see info in the
/usr/share/docs/iscsi-initiator-tools-$version/README about ifaces.

Thanks, I will go through the README file and see if I can get it done.

Thanks,

David

Date: Thu, 29 Apr 2010 13:50:37 -0500
From: micha...@cs.wisc.edu
To: elsen_da...@hotmail.com
CC: open-iscsi@googlegroups.com; mforou...@gmail.com
Subject: Re: information on the config option -- node.session.iscsi.FastAbort
= No

On 04/29/2010 12:48 PM, david elsen wrote:

Mike,

How can I get the 5.4 and 5.5 kernel fixes and latest iscs-initiator-utils
for RHEL 5.3 Kernel?

I am not sure. Do you normally use Red Hat's rhn service for this?

I would like to change the ISID from initiator while it is trying to
connect to target. I would like to establish multiple iSCSI session between
my Initiator and target. I do not see any option for this in the Linux
initiator on my system.

I am using RHEL 5.3 with 2.6.18-128.el5 kernel.

Thanks,

David

You need to upgrade your kernel. It had a bug with eql targets in the
async logout path. It is fixed in 5.4 and 5.5 kernels.

Upgrade your iscsi-initiator-utils too.

_
The New Busy is not the old busy. Search, chat and e-mail from your inbox.
http://www.windowslive.com/campaign/thenewbusy?ocid=PID28326::T:WLMTAGL:ON:WL:en-US:WM_HMP:042010_3

_
Hotmail is redefining busy with tools for the New Busy. Get more from your
inbox.
http://www.windowslive.com/campaign/thenewbusy?ocid=PID28326::T:WLMTAGL:ON:WL:en-US:WM_HMP:042010_2

RE: [ANNOUNCE] open-iscsi-2.0-872-rc2

RE: removing auto login from Initiator

RE: removing auto login from Initiator

removing auto login from Initiator

RE: compilation error with open-iscsi-2.0-871.tar.gz on RHEL 5.3

compilation error with open-iscsi-2.0-871.tar.gz on RHEL 5.3

RE: information on the config option -- node.session.iscsi.FastAbort = No

RE: information on the config option -- node.session.iscsi.FastAbort = No

8 matches

Site Navigation

Mail list logo

Footer information