Hi Federico,

I've upgrade to 3.4 and bindded the network to the iscsi connection on "iSCSI Multipathing" tab, but for what i see it added two new connections to my targets 192.168.12.1 and 192.168.12.4 (the ones i choosed) but they are still using tcp (sofware iscsi ) instead of bnx2i

iscsiadm -m session
tcp: [1] 192.168.11.1:3260,1 iqn.1986-03.com.hp:storage.msa2324i.1226151a60
tcp: [2] 192.168.12.2:3260,3 iqn.1986-03.com.hp:storage.msa2324i.1226151a60
tcp: [3] 192.168.12.4:3260,4 iqn.1986-03.com.hp:storage.msa2324i.1226151a60
tcp: [4] 192.168.11.3:3260,2 iqn.1986-03.com.hp:storage.msa2324i.1226151a60
tcp: [5] 192.168.12.2:3260,3 iqn.1986-03.com.hp:storage.msa2324i.1226151a60
tcp: [6] 192.168.12.4:3260,4 iqn.1986-03.com.hp:storage.msa2324i.1226151a60

I see that when i bindded the network in iscsi multipathing it creates my interface eth3 in /var/lib/iscsi/ifaces but with transport_name=tcp :

cat /var/lib/iscsi/ifaces/eth3
# BEGIN RECORD 6.2.0-873.10.el6
iface.iscsi_ifacename = eth3
iface.transport_name = tcp
iface.vlan_id = 0
iface.vlan_priority = 0
iface.iface_num = 0
iface.mtu = 0
iface.port = 0
# END RECORD

Is there anyway to tell ovirt to use bnx2i instead of tcp?

Best regards,
Ricardo Esteves.

On 14-05-2014 23:48, Federico Simoncelli wrote:
----- Original Message -----

From: "Federico Simoncelli" <fsimonce@redhat.com>
To: "Ricardo Esteves" <ricardo.m.esteves@gmail.com>
Cc: users@ovirt.org
Sent: Wednesday, May 14, 2014 3:47:58 PM
Subject: Re: [ovirt-users] oVirt 3.2 - iSCSI offload (broadcom - bnx2i)

----- Original Message -----

From: "Ricardo Esteves" <ricardo.m.esteves@gmail.com>
To: "Federico Simoncelli" <fsimonce@redhat.com>
Cc: users@ovirt.org
Sent: Wednesday, May 14, 2014 1:45:53 AM
Subject: RE: [ovirt-users] oVirt 3.2 - iSCSI offload (broadcom - bnx2i)

In attachment follows the defaults and the modified versions of the nodes
files.

If selecting the relevant host in "Hosts" you see the bnx2i interface in the
"Network Interfaces" subtab, then you can try to:

Sorry I just noticed that you mentioned in the subject that you're using
oVirt 3.2. What I suggested is available only since oVirt 3.4.