[Pkg-iscsi-maintainers] Bug#699240: open-iscsi: Broadcom Offload Engine is unusable because of missing iscsiuio daemon

Wed Feb 13 16:44:35 UTC 2013

Rafal,

I've added back the bug email address. Please use the "Reply All"
button. :-)

On Wednesday 13 February 2013 08:32 PM, Rafał Ramocki wrote:
> Hi,
>
>
> 2013/2/13 Ritesh Raj Sarraf <rrs at researchut.com
> <mailto:rrs at researchut.com>>
>
>     Yes. Offload is dependent on the hardware, something that I don't have
>     access to. With you assistance, we can improve the state in Debian.
>
>
> I count on it too :) Now all of hardware of this type that I have
> access to is used in production environment. It is quite easy to
> migrate services somewhere else from time to time. But for now only
> tests without upgrading system to any other than stable are possible.
> (upgrading and downgrading iscsi-tools is okej for me)

That's fine. We still can use your current running systems to get some idea.

> > While 'iscsid -d8 -f'  shows:
>
>     >
>     > iscsid: Received iferror -19: No such device.
>     > iscsid: cannot make a connection to 10.2.90.69:3260
>     <http://10.2.90.69:3260> (-19,2)
>
>     Any clues on what interface was it configured here?
>
>
>
> Unfortunately I do not know what interface name iscsid is using to
> communicate. I suppose it might be  bnx2i.00:10:18:e6:c3:55 and it is
> failing because it is not available in system as regular interface (it
> is not listed by ifconfig).

iSCSI works over TCP/IP. Unless specified otherwise, it will use your
Operating System's Default Route Interface for the network you are
trying to discover to. What does your routing table look like?

Also, the README shipped with the open-iscsi package talks about Offload
configuration in section 5.1.2. To quote it...

    5.1.2 Setting up a iface for a iSCSI offload card
    =================================================

    This section describes how to setup ifaces for use with Chelsio,
    Broadcom and
    QLogic cards.

    By default, iscsiadm will create a iface for each Broadcom, QLogic
    and Chelsio
    port. The iface name will be of the form:

    $transport/driver_name.$MAC_ADDRESS

    Running:

    # iscsiadm -m iface
    default tcp,<empty>,<empty>,<empty>,<empty>
    iser iser,<empty>,<empty>,<empty>,<empty>
    cxgb3i.00:07:43:05:97:07
    cxgb3i,00:07:43:05:97:07,<empty>,<empty>,<empty>
    qla4xxx.00:0e:1e:04:8b:2e
    qla4xxx,00:0e:1e:04:8b:2e,<empty>,<empty>,<empty>

    Will report iface configurations that are setup in /etc/iscsi/ifaces.
    The format is:

    iface_name
    transport_name,hwaddress,ipaddress,net_ifacename,initiatorname

    iface_name:             name of iface
    transport_name:         name of driver
    hwaddress:              MAC address
    ipaddress:              IP address to use for this port
    net_iface_name:         Net_ifacename will be <empty> because change
    between
    reboots. It is used for software iSCSI's vlan or alias binding.

Now, you could relate it to what you have, and see if your settings are
complete. But please do share your routing table too.

>  
> > But no information about connecting to target. I use following
> configuration:
>
>     >
>     > # iscsiadm -m node -T iqn.1992-04.com.emc:cx.ckm00122000265.a7
>     > # BEGIN RECORD 2.0-873
>     > node.name <http://node.name> =
>     iqn.1992-04.com.emc:cx.ckm00122000265.a7
>     > node.tpgt = -1
>     > node.startup = automatic
>     > node.leading_login = No
>     > iface.hwaddress = 00:10:18:e6:c3:55
>     > iface.ipaddress = 10.2.90.68
>     > iface.iscsi_ifacename = bnx2i.00:10:18:e6:c3:55
>     > iface.net_ifacename = <empty>
>     Is this supposed to remain empty?
>
>
> It might be filled net_interface OR hwaddress. You can't have them
> both. But as I see now when I was preparing configuration for bug
> reporting purposes I did a mistake. hwaddress should be
> 00:10:18:e6:c3:54. I a few days on testing in on many cases and left
> this kind of bug in bug report... such a shame :/

No big deal. We all do that. :-)

>  
>
>
>     Is iscsiuio part of the upstream open-iscsi source repository ? And
>     then, like you've said, we'll have to assess the licensing/copyright
>     details.
>
>     Best to start would be to check it in Fedora too. Fedora claims to be
>     GPL. So if those patches are shipped there, then we can spend some
>     time
>     to study its possibility of getting included in Debian.
>
>
> Fedora do have the this package. There is iscsiuio daemon in it.
>  
> http://pkgs.fedoraproject.org/cgit/iscsi-initiator-utils.git/tree/sources
>
> Level up tehre are also patches. I believe that minimum required to
> work have numbers 57-59 and 71-77
>
> regards 

That looks like a separate package. I will see if I can get some time
this or the next week to explore it. Maybe I might package it, but like
I said, without access to hardware, I will not be doing a good job in
maintaining its quality.

-- 
Ritesh Raj Sarraf
RESEARCHUT - http://www.researchut.com
"Necessity is the mother of invention."

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/pkg-iscsi-maintainers/attachments/20130213/55fa1b9d/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 899 bytes
Desc: OpenPGP digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-iscsi-maintainers/attachments/20130213/55fa1b9d/attachment-0001.pgp>