On Tue, Mar 09, 2010 at 07:49:00AM -0500, 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.  
> 

This sounds like a configuration problem to me. 

Did you remove the IP addresses from eth0/eth1, and make sure only bond0 has 
the IP? 
Was the routing table correct? 

As long as the kernel routing table is correct open-iscsi shouldn't care what
interface you're using.

(Unless you bind the open-iscsi iface to some physical interface).


-- Pasi


> 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.
> 
> I've attached a network diagram that explains my situation.  The goal is to 
> give the administrator flexibility to have fiber or iSCSI storage at the xen 
> dom0 as well as being able to pass-through that storage to the guest and 
> allow the guest to initiate iSCSI sessions.  This gives the guest the 
> flexibility to be able to run snapshot-type commands and things using the 
> EqualLogic HIT kits.
> 
> -- 
> 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.
> 

Content-Description: ATT00001.txt
> 
> Thanks,
> Joe
> 
> ===========================
> Joseph R. Hoot
> Lead System Programmer/Analyst
> joe.h...@itec.suny.edu
> GPG KEY:   7145F633
> ===========================
> 
> On Mar 9, 2010, at 5:19 AM, aclhkaclhk aclhkaclhk wrote:
> 
> > thanks, i could discover using bond0 but could not login.
> > 
> > iscsi-target (openfiler): eth0 (192.168.123.174)
> > iscsi-initiator: eth0 (192.168.123.176), bond0-mode4 (192.168.123.178)
> > 
> > /var/lib/iscsi/ifaces/iface0
> > # BEGIN RECORD 2.0-871
> > iface.iscsi_ifacename = iface0
> > iface.net_ifacename = bond0
> > iface.transport_name = tcp
> > # END RECORD
> > 
> > [r...@pc176 ifaces]# iscsiadm -m discovery -t st -p 192.168.123.174
> > --
> > interface iface0
> > 192.168.123.174:3260,1 192.168.123.174-vg0drbd-iscsi0
> > [r...@pc176 ifaces]#  iscsiadm --mode node --targetname
> > 192.168.123.174-vg0drbd-iscsi0 --portal 192.168.123.174:3260 --login
> > --
> > interface iface0
> > Logging in to [iface: iface0, target: 192.168.123.174-vg0drbd-iscsi0,
> > portal: 192.168.123.174,3260]
> > iscsiadm: Could not login to [iface: iface0, target: 192.168.123.174-
> > vg0drbd-iscsi0, portal: 192.168.123.174,3260]:
> > iscsiadm: initiator reported error (8 - connection timed out)
> > 
> > i could use eth0 to discover and login
> > 
> > ping 192.168.123.174 from iscsi-initiator is ok
> > ping 192.168.123.178 from iscsi-target is ok
> > 
> > 192.168.123.178 is authorised in iscsi-target to login
> > 
> > 
> > On Mar 8, 6:30 pm, Pasi K?rkk?inen <pa...@iki.fi> wrote:
> >> On Mon, Mar 08, 2010 at 02:08:43AM -0800, aclhkaclhk aclhkaclhk wrote:
> >>> my server has eth0 (onboard), eth1 and eth2 (intel lan card). eth1 and
> >>> eth2 are bonded as bond0
> >> 
> >>> i want to login iscsi target using bond0 instead of eth0.
> >> 
> >>> iscsiadm --mode node --targetname 192.168.123.1-vg0drbd-iscsi0 --
> >>> portal 192.168.123.1:3260 --login --interface bond0
> >>> iscsiadm: Could not read iface info for bond0.
> >> 
> >>> with interface, eth0 is used.
> >> 
> >>> the bonding was setup correctly. it could be used by xen.
> >> 
> >> You need to create the open-iscsi 'iface0' first, and bind it to 'bond0'.
> >> Then you can login using 'iface0' interface.
> >> 
> >> Like this (on the fly):
> >> 
> >> # iscsiadm -m iface -I iface0 -o new
> >> New interface iface0 added
> >> 
> >> # iscsiadm -m iface -I iface0 --op=update -n iface.net_ifacename -v bond0
> >> iface0 updated.
> >> 
> >> You can set up this permanently in /var/lib/iscsi/ifaces/ directory,
> >> by creating a file called 'iface0' with this content:
> >> 
> >> iface.iscsi_ifacename = iface0
> >> iface.transport_name = tcp
> >> iface.net_ifacename = bond0
> >> 
> >> Hopefully that helps.
> >> 
> >> -- Pasi
> > 
> > -- 
> > 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.
> > 
> 


-- 
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.

Reply via email to