How to force `iscsiadm` to create only one session on login?
Hello all! I'm using `open-iscsi` version `2.0.873` on OpenSUSE 13.2, and I am trying to connect to a Linux LIO-based target with the following command: iscsiadm --mode node --portal IP:3260,1 --login And for some reason it creates two sessions: Logging in to [iface: default, target: iqn.2018-04.XXX, portal: IP,3260] (multiple) Logging in to [iface: default, target: iqn.2018-04.XXX, portal: IP,3260] (multiple) Login to [iface: default, target: iqn.2018-04.XXX, portal: IP,3260] successful. Login to [iface: default, target: iqn.2018-04.XXX, portal: IP,3260] successful. I have not touched the standard configuration file `/etc/iscsid.conf`. I do have multiple VLAN's defined on my initiator network interface (i.e. `eth0.1`, `eth0.2`, etc.), but only one of them is configured (thus `eth0` is `LOWER_UP` and `eth0.2` is `LOWER_UP,UP`.) On the target there are multiple network interfaces but only one is configured and up (without VLAN's). I do have installed `multipath-tools` on the initiator, and the `dm_mpath` module (and related) are loaded -- but this is the standard behaviour of OpenSUSE. Therefore my question is: * why does it insist on initiating multiple sessions? * how can I convince `iscsiadm` to create only one session? Thanks, Ciprian. -- 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-iscsi+unsubscr...@googlegroups.com. To post to this group, send email to open-iscsi@googlegroups.com. Visit this group at https://groups.google.com/group/open-iscsi. For more options, visit https://groups.google.com/d/optout.
Re: Connection faillure RHEL 5.5 bnx2i
Michael Wolf wrote: Is bnx2i driver able to connect with multiple paths on RHEL 5.5? Out of a sick curiosity: does it make any difference if you're connected only to the iSCSI via only one interface? -- 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: Confirm that bnx2i iSCSI offload works for RHEL 5.5 on DELL EqualLogic
Michael Wolf wrote: Only four of them are connected to the SAN. How to figure out which hw- adress belongs to which interface? Perhaps BIOS / iface's ROM util should give you some hint(s). -- 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: iscsiadm and bonding
On 03/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 able to login. I am no longer attempting (at least for the moment because of time) to get it working this way, but I would love to change our environment in the future if a scenario such as this would work, because it gives me the flexibility to pass a virtual network card through to the guest and allow the guest to initiate its own iSCSI traffic instead of me doing it all at the dom0 level and then passing those block devices through. Out of curiosity, why would you do that? Why let the guest bear the iSCSI load instead of the host OS offering block devices? Eventually the host OS could use hardware acceleration (assuming that works)? Anybody care to give and argument because from what I've seen iSCSI load gets distributed to various CPUs in funny ways. Assuming KVM and no hardware iSCSI, have the host do iSCSI and the guests with Realtek emu cards, the iSCSI CPU load gets distributed. Have the guest do the iSCSI, again with Realtek emu one can see only the CPUs allocated to that guest being used; and heavy usage. But then switch to vrtio for network and the iSCSI load is once again spread through multiple CPUs no matter who's doing the iSCSI. At least for 1 guest... so which poison to chose? -- 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: Can anybody confirm that bnx2i on 5709 cards works with Equallogic 6xxx?
Nope! But the fact is I didn't have time to fiddle with it. Last time when I tried I brought the blade server down badly with the kernel shouting at me... It never worked for me, right now all my installs use tcp transport which is heavy on the CPU. ByteEnable wrote: Did you ever get this to work per your satisfaction? On Jan 20, 12:46 pm, Ciprian Vizitiu (GBIF) cvizi...@gbif.org wrote: Hi, Can anybody here please confirm whether iSCSI offload via bnx2i, on RHEL 5.4, with 5709 Broadcoms towards EQLs 6000 series works or not? Despite countless attempts (and latest EQL OS update) I still can't match them (but then the software transport works perfectly). :-| -- 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: Can anybody confirm that bnx2i on 5709 cards works with Equallogic 6xxx?
Mike Christie wrote: On 02/22/2010 04:08 PM, ByteEnable wrote: Did you ever get this to work per your satisfaction? Are you guys only having trouble with bnx2i and Equallogic targets? At least in my case it's the only target that I have. :-) Also Brocade switch between me and the Eql (if that matters in any way). -- 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.
Can anybody confirm that bnx2i on 5709 cards works with Equallogic 6xxx?
Hi, Can anybody here please confirm whether iSCSI offload via bnx2i, on RHEL 5.4, with 5709 Broadcoms towards EQLs 6000 series works or not? Despite countless attempts (and latest EQL OS update) I still can't match them (but then the software transport works perfectly). :-| -- 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.
Bonding interfaces
Hi everybody, Just wondering if anybody's got any experience with the bonding driver (and LACP on the switch) used as an iSCSI path? OK? Don't do it!? Yes, but...? -- 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: Bonding interfaces
OK, my mistake then; I should have written LACP on the switch stack. I mean if I have a multi blade switch (which came with the enclosure) and the server room is so small that I can actually hook the SAN with multiple wires to the said switch stack... why not? I'm asking because I haven't seen this option mentioned, everybody seems to standardise on multipath, wondered why... What's the catch? :-o Morten Johansen wrote: Hi I would say Yes, but... :-) I imagine it would give you High Avaliability against your switch, and possibly double the throughput. But using separate NICs, separate switches and DM-Multipath would give you the same thing, only all the way through to the SAN. Den 3 Dec, 2009 kl. 12:04 skrev Ciprian Marius Vizitiu (GBIF): Hi everybody, Just wondering if anybody's got any experience with the bonding driver (and LACP on the switch) used as an iSCSI path? OK? Don't do it!? Yes, but...? -- 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. -- Ciprian Vizitiu Webmaster / System Administrator GBIF Secretariat Universitetsparken DK-2100 Copenhagen Ø Denmark Tel. +45 35 32 14 78 gsm +45 28 75 14 78 Fax. +45 35 32 14 80 e-mail: cvizi...@gbif.org web: www.gbif.org -- 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.
iferror codes list
Hi everybody, Is there a list with all the iferror codes and their meaning? I'm trying to use bnx2i on RHEL 5.4 in order to do iSOE on a Dell M610 and a EQL PS6000XV and from time to time I get iferror -1. --~--~-~--~~~---~--~~ 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 open-iscsi+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/open-iscsi -~--~~~~--~~--~--~---
RE: iferror codes list
The iferror values are just normal old errnos. -1 is #define EPERM1 /* Operation not permitted */ You should get the iferror translated to a string in /var/log/messages. [...] Ignore this last part about the log message. The printf and iferror use is broken. Well I was about to suggest that; the only relevant error messages that I see are: iscsid: Received iferror -1 iscsid: cannot make a connection to 192.168.1.10:3260 (-1,11) Which to me is not very informative. :-| OK, here's the problem: I'm trying to hook a RHEL 5.4 x86_64 running on M610 to an EQL6000XV. I'm way past network problems if only because I can easily use the tcp transport and it works. Heck, apart for the lack of jumbo support I can't really complain about the tcp transport. Yet, out of a sick curiosity about system performance I'm stubbornly insisting into making use of the bnx2i driver to offload some iSCSI into the 57009S; yes, I DO have the hardware key. After some agonizing attempts I've reached the point where I can detect the targets but any attempts to actually start the session will result (depending apparently on the planets position) in either two of the targets connecting or none of the targets connected. A simple service iscsi restart will sometimes result in success and sometimes in failure. It's puzzling and maddening in the same time... Don't even know where to start, I was really hoping the iferror values would mean something. Any help would be really appreciated! o:-) --~--~-~--~~~---~--~~ 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 open-iscsi+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/open-iscsi -~--~~~~--~~--~--~---
