1. ping -I bond0 192.168.123.174 yes, ok 2. a week ago, I have setup the iscsi-initiator linux without eth0. only bond0 (mode4, eth1 and eth2) was assigned IP addr. eth0 was unassigned and without connection to switch. Login to iscsi target was ok via bond0. There was no need to create iface0.
the reason to use eth0 is that if there is any problem with bonding configuration, I could still connect to the host via eth0. Furthermore, i want to separate dom0 (eth0) traffic from domU (bond0). # route Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 192.168.122.0 * 255.255.255.0 U 0 0 0 virbr0 192.168.123.0 * 255.255.255.0 U 0 0 0 eth0 192.168.123.0 * 255.255.255.0 U 0 0 0 bond0 169.254.0.0 * 255.255.0.0 U 0 0 0 bond0 default 192.168.123.1 0.0.0.0 UG 0 0 0 eth0 On Mar 10, 3:34 am, Mike Christie <[email protected]> wrote: > On 03/09/2010 04: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 > > I am not sure if I have ever tried bonding with ifaces. > > Can you do > > ping -I bond0 192.168.123.174 > > ? If that does not work then the iscsi iface bonding will not either (we > use the same syscalls to bind to the interface). > > Is it possible to just set up the routing table so the iscsi traffic > goes through the bonded interface to the target? -- You received this message because you are subscribed to the Google Groups "open-iscsi" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/open-iscsi?hl=en.
