AF:
NF:0
PS:10
SRH:1
SFN:
DSR:
MID:
CFG:
PT:0
S:andy.sharp@lsi.com
RQ:
SSV:mhbs.lsil.com
NSV:
SSH:
R:<Dave.Limato@lsi.com>,<Richard.Hardiman@lsi.com>,<Svati.Chandra@lsi.com>,<larry.scheer@lsi.com>,<Ram.Upendran@lsi.com>
MAID:2
X-Sylpheed-Privacy-System:
X-Sylpheed-Sign:0
SCF:#mh/Mailbox/sent
RMID:#imap/LSI/INBOX	0	4933E4A8-551C-4905-9252-D9D7C3B10E0F@lsi.com
X-Sylpheed-End-Special-Headers: 1
Date: Mon, 5 Apr 2010 12:12:22 -0700
From: Andrew Sharp <andy.sharp@lsi.com>
To: "Limato, Dave" <Dave.Limato@lsi.com>
Cc: Richard Hardiman <Richard.Hardiman@lsi.com>, Svati Chandra
 <Svati.Chandra@lsi.com>, Larry Scheer <larry.scheer@lsi.com>, Ram Upendran
 <Ram.Upendran@lsi.com>
Subject: Re: Campbell Lab (Move DMA to same Network as DOG)
Message-ID: <20100405121222.43f70296@ripper.onstor.net>
In-Reply-To: <4933E4A8-551C-4905-9252-D9D7C3B10E0F@lsi.com>
References: <D7A889C980962746B30DE07864593C02CF31D4C4@cosmail02.lsi.com>
	<98BD48946A20FF48932378FFD26CE9057DF14022@cosmail01.lsi.com>
	<20100405110121.38ecf62f@ripper.onstor.net>
	<4933E4A8-551C-4905-9252-D9D7C3B10E0F@lsi.com>
Organization: LSI
X-Mailer: Sylpheed-Claws 2.6.0 (GTK+ 2.8.20; x86_64-pc-linux-gnu)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

On Mon, 5 Apr 2010 12:20:05 -0600 "Limato, Dave" <Dave.Limato@lsi.com>
wrote:

> Go right ahead and diagnose. I have not been able to pinpoint the  
> issue. You will need to get a wireshark trace on the problem when it  
> occurs.

I'm guessing that, if a network issue at all, it's something that
possibly Rich can figure out looking at stats on the switches/routers
involved.  A tcpdump would also be a good thing.  Sadly, I think the
DMA is Windows, and I don't know how to do a tcpdump on Winblows.
Cygwin?

> Btw. I am hearing this is what happens at LSI we span many tapes and  
> just die from a network error.

Excellent, so we are hitting a bug that is hurting our customers.

> Svati has also given me a number of tweaks that can be done on the
> DMA.

Sweet.  This team RULES.

> Dave
> 
> On Apr 5, 2010, at 11:01 AM, "Andrew Sharp" <andy.sharp@lsi.com>
> wrote:
> 
> > Hold on a second, guys.  There can't be anything here that would
> > cause a network timeout.  10.2 <--> 10.0 should be virtually
> > impossibly latency increase to measure.  If not, then we need to
> > diagnose that and
> > fix it, as well as fix the software to deal with small network
> > latencies.  From what I've heard so far, and maybe I'm out of the
> > loop a bit, the backup goes for quite a while and then suffers a
> > mysterious "network timeout."  I don't think this has anything to
> > do with 10.0 v. 10.2, quite frankly.  Let's diagnose the problem
> > before spending time moving the DMA and so forth.
> >
> > Cheers,
> >
> > a
> >
> >
> > On Mon, 5 Apr 2010 11:36:32 -0600 "Hardiman, Richard"
> > <Richard.Hardiman@lsi.com> wrote:
> >
> >> Hey Dave,
> >> I will move the client to the 10.0.0.x network.
> >> I will get back to you once the client has been moved.
> >> Thanks!
> >>
> >> ________________________________
> >> From: Limato, Dave
> >> Sent: Monday, April 05, 2010 10:20 AM
> >> To: help
> >> Cc: Hardiman, Richard; Sharp, Andy; Scheer, Larry
> >> Subject: Campbell Lab (Move DMA to same Network as DOG)
> >>
> >> Hey Gang, I think one thing that would help us get mightydog a
> >> complete backup is move the dma off 10.2 and over to 10.0 and
> >> subnet.
> >>
> >> We are getting network timeout issues. Would it be possible to fit
> >> this in today?
> >>
> >> DMA is client  in rack 57 currently 10.2.57.200.
> >>
> >> Thanks,
> >> Dave Limato - Sr. QA Engineer - LSI Corporation - ONStor Product
> >> Test
> >> - desk 408-433-8742  - cell 510.329.9994 -- dave.limato@lsi.com
> >>
