Multipath ?
Hi. I'm new to this iSCSI things. But the SAN I'm testing agains has 3 1GB interfaces.. all put together as one "portal ip-adress". I have 4 1GB interfaces in my main host. What is the preferred way of making I/O at above 100MB/s in a setup like this? Bonding the NIC's under linux or does the iSCSI-initiator need to get some details? Jesper -- Jesper Krogh --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "open-iscsi" group. To post to this group, send email to open-iscsi@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/open-iscsi -~--~~~~--~~--~--~---
Re: Cannot login to iscsi target on VMware SuSE10
Sorry for reply you late. I was in a vacation these days. :) I've tested the newest version of open-iscsi( open-iscsi-2.0-865.15) on my VMware machine. It works well. That's great. Thank you for your great help. Best wishes, Kevin On 2月6日, 上午1时10分, Mike Christie <[EMAIL PROTECTED]> wrote: > KevinKW wrote: > > Thanks for the reply. > > NP > > > > > On 2月2日, 上午2时48分, Mike Christie <[EMAIL PROTECTED]> wrote: > >> Did you notice that when you run > >> # iscsiadm -m node -r 68a68a -l > > >> and iscsiadm hangs, does iscsid die? It looks like the kernel detects a > >> error, tries to tell userspace about it, but iscsid has died. Because > >> iscsid is no longer up, iscsiadm will not be notified that the session > >> was logged into, and will just sit around waiting for an answer. > > >>> connection2:0: iscsi: detected conn error (1006) > > After I ran the command iscsiadm, I thought the corresponding iscsid > > didn't die, it seems sleep there. Even when I killed the iscsiadm, it > > will still be there. > > Umm ok, could you retry this with the current tools from > open-iscsi.org:http://www.open-iscsi.org/bits/open-iscsi-2.0-865.15.tar.gz > Use the kernel modules and tools from that tarball and that instead of doing > > iscsiadm -m node -r 123-l > There is no "-r" argument and you now pass the target and/or portal: > > iscsiadm -m node -T my_target -p ip:port -l > or > iscsiadm -m node -T my_target -l > > If open-iscsi-2.0-865.15 does not work then get some debuging output. > > Build the modules with debuugging > make DEBUG_TCP=1 DEBUG_SCSI=1 > make DEBUG_TCP=1 DEBUG_SCSI=1 install > > Load modules > modprobe -r iscsi_tcp > modprobe iscsi_tcp > > Run iscsid with debuugging > iscsid -d 8 -f & > > then run iscsiadm with debugging: > > iscsiadm -m node ... -l -d 8 > > And send all the output. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "open-iscsi" group. To post to this group, send email to open-iscsi@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/open-iscsi -~--~~~~--~~--~--~---
iscsiadm: No records found!
Hello all, i have run iscsiadm -m discovery -t sendtargets -p 10.129.1.71 after this when i restart open-iscsi, its showing that no records found /etc/init.d/open-iscsi restart * Disconnecting iSCSI targets [ OK ] * Stopping iSCSI initiator service [ OK ] * Starting iSCSI initiator service iscsid [ OK ] * Setting up iSCSI targets iscsiadm: No records found! [ OK ] Can anybody tell what could be the problem? --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "open-iscsi" group. To post to this group, send email to open-iscsi@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/open-iscsi -~--~~~~--~~--~--~---
RE: iscsiadm: No records found!
You provided almost no information about the iSCSI target, the version of open-iSCSI, Distro or Kernel rev. When you run the discovery command does it find any targets? One suggestion. Add :3260 to the end of the discovery command. Don -Original Message- From: open-iscsi@googlegroups.com [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Thursday, February 14, 2008 8:05 AM To: open-iscsi Subject: iscsiadm: No records found! Hello all, i have run iscsiadm -m discovery -t sendtargets -p 10.129.1.71 after this when i restart open-iscsi, its showing that no records found /etc/init.d/open-iscsi restart * Disconnecting iSCSI targets [ OK ] * Stopping iSCSI initiator service [ OK ] * Starting iSCSI initiator service iscsid [ OK ] * Setting up iSCSI targets iscsiadm: No records found! [ OK ] Can anybody tell what could be the problem? --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "open-iscsi" group. To post to this group, send email to open-iscsi@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/open-iscsi -~--~~~~--~~--~--~---
Re: iscsiadm: No records found!
On Feb 14, 8:22 pm, "Don Williams" <[EMAIL PROTECTED]> wrote: > You provided almost no information about the iSCSI target, the version of > open-iSCSI, Distro or Kernel rev. > kernel :- 2.6.22-14-generic OS:- Ubuntu Gutsy open-iscsi version:- 2.0.865-1 > When you run the discovery command does it find any targets? > When i run discovery command there is no output. > One suggestion. Add :3260 to the end of the discovery command. I tried this. No result > Don > Apart from this i ll show you the iscsid.conf node.startup = automatic node.session.auth.authmethod = CHAP node.session.auth.username = xx node.session.auth.password = xxx discovery.sendtargets.auth.authmethod = CHAP discovery.sendtargets.auth.username = discovery.sendtargets.auth.password = xxx node.session.timeo.replacement_timeout = 120 node.conn[0].timeo.login_timeout = 15 node.conn[0].timeo.logout_timeout = 15 node.conn[0].timeo.noop_out_interval = 10 node.conn[0].timeo.noop_out_timeout = 15 node.session.iscsi.InitialR2T = No node.session.iscsi.ImmediateData = Yes node.session.iscsi.FirstBurstLength = 262144 node.session.iscsi.MaxBurstLength = 16776192 node.conn[0].iscsi.MaxRecvDataSegmentLength = 131072 discovery.sendtargets.iscsi.MaxRecvDataSegmentLength = 32768 When i run iscsid -f -d 8 The following was the output [EMAIL PROTECTED]:/etc/iscsi# iscsid -f -d 8 iscsid: transport class version 2.0-724. iscsid version 2.0-865 iscsid: in ctldev_open iscsid: created NETLINK_ISCSI socket... iscsid: InitiatorName==iqn.1993-08.org.debian:01:7b3b391c825 iscsid: an InitiatorAlias= is required, but was not found in /etc/ iscsi/initiatorname.iscsi iscsid: InitiatorName=iqn.1993-08.org.debian:01:7b3b391c825 iscsid: InitiatorAlias=venus iscsid: iscsid_exit iscsid: in ctldev_close iscsid: reaped pid 6626, reap_count now 0 iscsid: poll result 1 iscsid: poll result 1 iscsid: poll result 1 The last three lines of above output was the result of running the iscsiadm command for discovery. > -Original Message- > From: open-iscsi@googlegroups.com [mailto:[EMAIL PROTECTED] On > > Behalf Of [EMAIL PROTECTED] > Sent: Thursday, February 14, 2008 8:05 AM > To: open-iscsi > Subject: iscsiadm: No records found! > > Hello all, > > i have run > iscsiadm -m discovery -t sendtargets -p 10.129.1.71 > > after this when i restart open-iscsi, its showing that no records > found > /etc/init.d/open-iscsi restart > > * Disconnecting iSCSI > targets > [ OK ] > * Stopping iSCSI initiator > service > [ OK ] > * Starting iSCSI initiator service > iscsid > [ OK ] > * Setting up iSCSI > targets > iscsiadm: No records found! > > [ OK ] > > Can anybody tell what could be the problem? --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "open-iscsi" group. To post to this group, send email to open-iscsi@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/open-iscsi -~--~~~~--~~--~--~---
RE: iscsiadm: No records found!
What iSCSI target are you using? Are you using a packaged version of the open-iSCSI initiator or did you build it from the code on the open-iSCSI website? You should also create an /etc/iscsi/initiatorname.iscsi Don -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Thursday, February 14, 2008 11:32 AM To: open-iscsi Cc: [EMAIL PROTECTED] Subject: Re: iscsiadm: No records found! On Feb 14, 8:22 pm, "Don Williams" <[EMAIL PROTECTED]> wrote: > You provided almost no information about the iSCSI target, the version of > open-iSCSI, Distro or Kernel rev. > kernel :- 2.6.22-14-generic OS:- Ubuntu Gutsy open-iscsi version:- 2.0.865-1 > When you run the discovery command does it find any targets? > When i run discovery command there is no output. > One suggestion. Add :3260 to the end of the discovery command. I tried this. No result > Don > Apart from this i ll show you the iscsid.conf node.startup = automatic node.session.auth.authmethod = CHAP node.session.auth.username = xx node.session.auth.password = xxx discovery.sendtargets.auth.authmethod = CHAP discovery.sendtargets.auth.username = discovery.sendtargets.auth.password = xxx node.session.timeo.replacement_timeout = 120 node.conn[0].timeo.login_timeout = 15 node.conn[0].timeo.logout_timeout = 15 node.conn[0].timeo.noop_out_interval = 10 node.conn[0].timeo.noop_out_timeout = 15 node.session.iscsi.InitialR2T = No node.session.iscsi.ImmediateData = Yes node.session.iscsi.FirstBurstLength = 262144 node.session.iscsi.MaxBurstLength = 16776192 node.conn[0].iscsi.MaxRecvDataSegmentLength = 131072 discovery.sendtargets.iscsi.MaxRecvDataSegmentLength = 32768 When i run iscsid -f -d 8 The following was the output [EMAIL PROTECTED]:/etc/iscsi# iscsid -f -d 8 iscsid: transport class version 2.0-724. iscsid version 2.0-865 iscsid: in ctldev_open iscsid: created NETLINK_ISCSI socket... iscsid: InitiatorName==iqn.1993-08.org.debian:01:7b3b391c825 iscsid: an InitiatorAlias= is required, but was not found in /etc/ iscsi/initiatorname.iscsi iscsid: InitiatorName=iqn.1993-08.org.debian:01:7b3b391c825 iscsid: InitiatorAlias=venus iscsid: iscsid_exit iscsid: in ctldev_close iscsid: reaped pid 6626, reap_count now 0 iscsid: poll result 1 iscsid: poll result 1 iscsid: poll result 1 The last three lines of above output was the result of running the iscsiadm command for discovery. > -Original Message- > From: open-iscsi@googlegroups.com [mailto:[EMAIL PROTECTED] On > > Behalf Of [EMAIL PROTECTED] > Sent: Thursday, February 14, 2008 8:05 AM > To: open-iscsi > Subject: iscsiadm: No records found! > > Hello all, > > i have run > iscsiadm -m discovery -t sendtargets -p 10.129.1.71 > > after this when i restart open-iscsi, its showing that no records > found > /etc/init.d/open-iscsi restart > > * Disconnecting iSCSI > targets > [ OK ] > * Stopping iSCSI initiator > service > [ OK ] > * Starting iSCSI initiator service > iscsid > [ OK ] > * Setting up iSCSI > targets > iscsiadm: No records found! > > [ OK ] > > Can anybody tell what could be the problem? --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "open-iscsi" group. To post to this group, send email to open-iscsi@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/open-iscsi -~--~~~~--~~--~--~---
Re: iscsiadm: No records found!
On Thu, Feb 14, 2008 at 10:28 PM, Don Williams <[EMAIL PROTECTED]> wrote: > What iSCSI target are you using? > The target machine is the following:- http://www.raidstore.com/RaidProductDetail.asp?ItemID=551 Its a NAS Box. The web-interface provides an interface to select which authentication to use and etc When i do nmap -p3260 on this machine PORT STATE SERVICE 3260/tcp open unknown its shows that 3260 port is open... > Are you using a packaged version of the open-iSCSI initiator or did you iam using the packaged version of open-iscsi > > build it from the code on the open-iSCSI website? > > You should also create an /etc/iscsi/initiatorname.iscsi Its already there. > > > Don > > > -Original Message- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > Sent: Thursday, February 14, 2008 11:32 AM > To: open-iscsi > Cc: [EMAIL PROTECTED] > Subject: Re: iscsiadm: No records found! > > > > On Feb 14, 8:22 pm, "Don Williams" <[EMAIL PROTECTED]> wrote: > > You provided almost no information about the iSCSI target, the version > of > > open-iSCSI, Distro or Kernel rev. > > > kernel :- 2.6.22-14-generic > OS:- Ubuntu Gutsy > open-iscsi version:- 2.0.865-1 > > When you run the discovery command does it find any targets? > > > When i run discovery command there is no output. > > > One suggestion. Add :3260 to the end of the discovery command. > > I tried this. No result > > Don > > > Apart from this i ll show you the iscsid.conf > > node.startup = automatic > node.session.auth.authmethod = CHAP > node.session.auth.username = xx > node.session.auth.password = xxx > discovery.sendtargets.auth.authmethod = CHAP > discovery.sendtargets.auth.username = > discovery.sendtargets.auth.password = xxx > node.session.timeo.replacement_timeout = 120 > node.conn[0].timeo.login_timeout = 15 > node.conn[0].timeo.logout_timeout = 15 > node.conn[0].timeo.noop_out_interval = 10 > node.conn[0].timeo.noop_out_timeout = 15 > > node.session.iscsi.InitialR2T = No > node.session.iscsi.ImmediateData = Yes > node.session.iscsi.FirstBurstLength = 262144 > node.session.iscsi.MaxBurstLength = 16776192 > node.conn[0].iscsi.MaxRecvDataSegmentLength = 131072 > discovery.sendtargets.iscsi.MaxRecvDataSegmentLength = 32768 > > When i run iscsid -f -d 8 > The following was the output > [EMAIL PROTECTED]:/etc/iscsi# iscsid -f -d 8 > iscsid: transport class version 2.0-724. iscsid version 2.0-865 > iscsid: in ctldev_open > iscsid: created NETLINK_ISCSI socket... > iscsid: InitiatorName==iqn.1993-08.org.debian:01:7b3b391c825 > iscsid: an InitiatorAlias= is required, but was not found in /etc/ > iscsi/initiatorname.iscsi > iscsid: InitiatorName=iqn.1993-08.org.debian:01:7b3b391c825 > iscsid: InitiatorAlias=venus > iscsid: iscsid_exit > iscsid: in ctldev_close > iscsid: reaped pid 6626, reap_count now 0 > iscsid: poll result 1 > iscsid: poll result 1 > iscsid: poll result 1 > > The last three lines of above output was the result of running the > iscsiadm command for discovery. > > > > > -Original Message- > > From: open-iscsi@googlegroups.com [mailto:[EMAIL PROTECTED] > On > > > > Behalf Of [EMAIL PROTECTED] > > Sent: Thursday, February 14, 2008 8:05 AM > > To: open-iscsi > > Subject: iscsiadm: No records found! > > > > Hello all, > > > > i have run > > iscsiadm -m discovery -t sendtargets -p 10.129.1.71 > > > > after this when i restart open-iscsi, its showing that no records > > found > > /etc/init.d/open-iscsi restart > > > > * Disconnecting iSCSI > > targets > > [ OK ] > > * Stopping iSCSI initiator > > service > > [ OK ] > > * Starting iSCSI initiator service > > iscsid > > [ OK ] > > * Setting up iSCSI > > targets > > iscsiadm: No records found! > > > > [ OK ] > > > > Can anybody tell what could be the problem? > > --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "open-iscsi" group. To post to this group, send email to open-iscsi@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/open-iscsi -~--~~~~--~~--~--~---
Re: can not bind NETLINK_ISCSI socket
David Lee Lambert wrote: > I'm trying to get open-iscsi to run on a Gentoo system. I've set some > other systems up, but on this one the /etc/init.d/open-iscsi script > hangs. When I try to start the daemon manually with debugging > options, here's what I get: > > > > # iscsid -f -d 99 > iscsid: transport class version 2.0-865. iscsid version 2.0-865 > iscsid: in ctldev_open > iscsid: can not bind NETLINK_ISCSI socket > iscsid: iscsid_exit > iscsid: in ctldev_close > *** glibc detected *** double free or corruption (out): 0x08078118 *** > Aborted > > > > Any pointers on where to look for the problem? > It looks like a couple bugs :( First one is that iscsid will not start with the can not bind error. We normally see this when iscsid has been run, but not fully cleaned up. For example with older versions you have to do "killall -9 iscsid" to kill all the processes. The second problem is the double free. I have not seen that one before. Are you using the tools from gentoo or upstream? If you could try the newest tools if you are not already http://www.open-iscsi.org/bits/open-iscsi-2.0-865.15.tar.gz and retry the start up it would be helpful. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "open-iscsi" group. To post to this group, send email to open-iscsi@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/open-iscsi -~--~~~~--~~--~--~---
Re: Multipath ?
Jesper Krogh wrote: > > Hi. > > I'm new to this iSCSI things. But the SAN I'm testing agains has 3 1GB > interfaces.. all put together as one "portal ip-adress". > > I have 4 1GB interfaces in my main host. What is the preferred way of > making I/O at above 100MB/s in a setup like this? Bonding the NIC's under > linux or does the iSCSI-initiator need to get some details? > You can also do a block level approach. If you use the current tools on open-iscsi.org, then you can setup the initiator so we create a session through each nic on the main host that connects to the one portal ip-address on the target (see the iface info in the iscsi README). Then you can use dm-multipath to round-robin over all those sessions. I have not done any benchmarking of dm-multipath + iscsi iface vs bonding. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "open-iscsi" group. To post to this group, send email to open-iscsi@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/open-iscsi -~--~~~~--~~--~--~---
Re: iscsiadm: No records found!
[EMAIL PROTECTED] wrote: > Apart from this i ll show you the iscsid.conf > > node.startup = automatic > node.session.auth.authmethod = CHAP > node.session.auth.username = xx > node.session.auth.password = xxx > discovery.sendtargets.auth.authmethod = CHAP > discovery.sendtargets.auth.username = > discovery.sendtargets.auth.password = xxx Maybe we should start with a really simple setup. If you remove all the CHAP settings from the target and initiator, does it work? If you then do one way chap does it work? --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "open-iscsi" group. To post to this group, send email to open-iscsi@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/open-iscsi -~--~~~~--~~--~--~---
Re: iscsiadm: No records found!
On Feb 14, 10:23 pm, Mike Christie <[EMAIL PROTECTED]> wrote: > [EMAIL PROTECTED] wrote: > > Apart from this i ll show you the iscsid.conf > > > node.startup = automatic > > node.session.auth.authmethod = CHAP > > node.session.auth.username = xx > > node.session.auth.password = xxx > > discovery.sendtargets.auth.authmethod = CHAP > > discovery.sendtargets.auth.username = > > discovery.sendtargets.auth.password = xxx > > Maybe we should start with a really simple setup. If you remove all the > CHAP settings from the target and initiator, does it work? If you then I have removed all the CHAP setting from both the initiator as well as target. Still the same problem. > do one way chap does it work? --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "open-iscsi" group. To post to this group, send email to open-iscsi@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/open-iscsi -~--~~~~--~~--~--~---
Re: Multipath ?
Jesper Krogh wrote: > Mike Christie wrote: > >> Jesper Krogh wrote: >> >>> Hi. >>> >>> I'm new to this iSCSI things. But the SAN I'm testing agains has 3 1GB >>> interfaces.. all put together as one "portal ip-adress". >>> >>> I have 4 1GB interfaces in my main host. What is the preferred way of >>> making I/O at above 100MB/s in a setup like this? Bonding the NIC's under >>> linux or does the iSCSI-initiator need to get some details? >>> >>> >> You can also do a block level approach. If you use the current tools on >> open-iscsi.org, then you can setup the initiator so we create a session >> through each nic on the main host that connects to the one portal >> ip-address on the target (see the iface info in the iscsi README). Then >> you can use dm-multipath to round-robin over all those sessions. >> >> I have not done any benchmarking of dm-multipath + iscsi iface vs bonding. >> > > Sounds interesting. Thanks a lot for the information. > > I'm doing a bit of both nic bonding and dm-multipath, and I don't seem to get 2GB out of the dm-multipath setup, but it is certainly over 1G. I'd say I usually see somewhere around 1.3-1.4GB, but as always the blocksizes and other variables play a huge role. For us the dm-multipath was the right choice so that we are able to use two switches and split the fabric into two networks for resiliency. This could also be a bit of speed impact for me, so you might see more speed than I do. If you bond the NIC's it seems to work fine too and iscsi does not need to know of that. Sorry I dont' have any good benchmarks across just a bonded nic setup. One interesting thing we found, though, was that with dm-multipath and iscsi we would get lots of path failures when the iscsi target (iet target in our case) ran with blockio and write-through caching. I'm guessing that the dm-multipath "readsector0" and "tur" tools that check the paths have a limited timeout that can be exceeded when you don't allow cache to help out. The real danger here is that in certain situations dm-multipath would fail out all possible paths, making the initiator very unhappy. I don't think this is the fault of dm-multipath, and I didn't look very far into tuning it's timeout value. When we switched to fileio and write-back caching we no longer had path failures - so the fix was easy, but not necessarily intuitive. I'd be really curious to hear if anyone else sees this problem, with iet or with a different iscsi target. (That's not meant to hijack this thread - but if it's germane I'm curious as to other multipath results) -Ty! -- -===- Ty! Boyack NREL Unix Network Manager [EMAIL PROTECTED] (970) 491-1186 -===- --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "open-iscsi" group. To post to this group, send email to open-iscsi@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/open-iscsi -~--~~~~--~~--~--~---
Re: Multipath ?
Mike Christie wrote: > Jesper Krogh wrote: >> Hi. >> >> I'm new to this iSCSI things. But the SAN I'm testing agains has 3 1GB >> interfaces.. all put together as one "portal ip-adress". >> >> I have 4 1GB interfaces in my main host. What is the preferred way of >> making I/O at above 100MB/s in a setup like this? Bonding the NIC's under >> linux or does the iSCSI-initiator need to get some details? >> > > You can also do a block level approach. If you use the current tools on > open-iscsi.org, then you can setup the initiator so we create a session > through each nic on the main host that connects to the one portal > ip-address on the target (see the iface info in the iscsi README). Then > you can use dm-multipath to round-robin over all those sessions. > > I have not done any benchmarking of dm-multipath + iscsi iface vs bonding. Sounds interesting. Thanks a lot for the information. -- Jesper --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "open-iscsi" group. To post to this group, send email to open-iscsi@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/open-iscsi -~--~~~~--~~--~--~---
