Mike suggest you to enable debug in tcp and see what happened in another
email.
Ming
On Wed, 2006-02-15 at 10:26 +0800, Jin, Steve wrote:
> Yes, I have tried SCP command to transfer a big file between to hosts when
> enabling bonding driver. Using SAR command, I can see traffic normally load
> balance. Transfer is successful.
> BTW, Linux-iSCSI has no such issues when enabling bonding driver. For its
> lack of support to kernel 2.6.14, I have to choose open-iscsi.
> Does anyone try that before? I wait waiting for the reply:)
>
> -----Original Message-----
> From: open-iscsi@xxxxxxxxxxxxxxxx [mailto:open-iscsi@xxxxxxxxxxxxxxxx] On
> Behalf Of Ming Zhang
> Sent: 2006年2月15日 1:07
> To: open-iscsi@xxxxxxxxxxxxxxxx
> Cc: iet-dev
> Subject: Re: urgent help for open-iscsi-1.0-485.tar.gz with e1000 bonding
> driver
>
>
> after u do bonding, could u run ftp or nc to make sure u network
> bidirectional traffic is good before running iscsi?
>
> also u can turn on openiscsi debug and see if more message there?
>
> ming
>
> On Tue, 2006-02-14 at 01:41 -0800, steve.jin@xxxxxxxxx wrote:
> > Hi,All
> > Here is the urgent request from IPTV performance. We introduce
> > iscsi storage model into IPTV streaming testing. Open-iSCSI is the
> > initiator we selected. Target side is Enterprise target(ietd). We want
> > to use mulitple NICs for high throughput.
> > If only one NIC is used(each one NIC at both target side and
> > initiator side), iscsi conneciton has no problem. Performance is really
> > good.
> > Then we do NIC bonding:
> > a. Target side: 2 NIC are bonding into one virtual NIC. Round Robin
> > is used.
> > b. Initator side: 2 NIC are bonding into one virutal NIC Round
> > robin is used.
> > c. Start target and initator.
> > Problem appears: operaton "iscsiadm -m node -r ****** -l" fails.
> > Could anyone provide help? Help is highly appreviated!
> > Here is the log:
> >
> > /////////////////////////////////////////////////////////////////////////////////////////////////////////////////////
> >
> > ip_tables: (C) 2000-2002 Netfilter core team
> > bonding: Warning: failed to get speed and duplex from eth4, assumed to
> > be 100Mb/sec and Full.
> >
> > bonding: bond0: enslaving eth4 as an active interface with an up link.
> >
> > e1000: eth4: e1000_watchdog_task: NIC Link is Up 1000 Mbps Full Duplex
> >
> > e1000: eth5: e1000_watchdog_task: NIC Link is Up 1000 Mbps Full Duplex
> >
> > bonding: bond0: enslaving eth5 as an active interface with an up link.
> >
> > scsi2 : iSCSI Initiator over TCP/IP, v.0.3
> >
> > connection2:0: iscsi: detected conn error (1011)
> >
> > Vendor: LINUX Model: ISCSI Rev: 0
> >
> > Type: Direct-Access ANSI SCSI revision: 03
> >
> > connection2:0: iscsi: detected conn error (1011)
> >
> > connection2:0: iscsi: detected conn error (1011)
> >
> > SCSI device sda: 9783296 512-byte hdwr sectors (5009 MB)
> >
> > SCSI device sda: drive cache: write back
> >
> > SCSI device sda: 9783296 512-byte hdwr sectors (5009 MB)
> >
> > SCSI device sda: drive cache: write back
> >
> > sda: <6> connection2:0: iscsi: detected conn error (1011)
> >
> > [root@m02 iscsi]# mount /dev/sda /mnt
> >
> > iscsi: registered transport (tcp)
> >
> > ------------> dead
> > ///////////////////////////////////////////////////////////////////////////////////
> >
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid3432&bid#0486&dat1642
|
