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.
On 03/10/2010 02:14 AM, aclhkaclhk aclhkaclhk wrote:
1. ping -I bond0 192.168.123.174
yes, ok
Could you run iscsid manually in debugging mode and send me all the log
output.
Instead of doing service iscsi start just do
// this starts iscsi with debugging going to the console
iscsid -d 8
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
the bonding is 802.3ab. the bonding is functioning ok because i have
created a xen bridge over the bonding. the domu using the xen bridge
can connect to outside and vice versa
bond0 - xenbr1 - domu - outside hosts
pls advise
On Mar 9, 6:19 pm, aclhkaclhk aclhkaclhk aclhkac...@gmail.com wrote:
i do not want to use multipath as i have setup a HA iscsi target.
192.168.123.174 is the cluster ip
On Mar 9, 6:25 pm, aclhkaclhk aclhkaclhk aclhkac...@gmail.com wrote:
the bonding is 802.3ab. the bonding is functioning ok because i have
created a xen bridge over the bonding. the domu using the
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
i created a domu (using bond0) in iscsi-initiator linux. it could
connect to iscsi-target.
On Mar 9, 6:29 pm, aclhkaclhk aclhkaclhk aclhkac...@gmail.com wrote:
i do not want to use multipath as i have setup a HA iscsi target.
192.168.123.174 is the cluster ip
On Mar 9, 6:25 pm, aclhkaclhk
Agreed, I would probably continue to do it on the dom0 for now and pass-through
the block devs. If this solution were used it would give me the flexibility to
initiate in the guest if I would decide to do so. I believe there would
definitely be cpu and network overhead. Given the cpu's
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
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
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 --
11 matches
Mail list logo
