Path: utzoo!attcan!uunet!cs.utexas.edu!sdd.hp.com!elroy.jpl.nasa.gov!ncar!boulder!daemon
From: schoff@psi.com (Martin Lee Schoffstall)
Newsgroups: comp.dcom.sys.cisco
Subject: Re: Serial problems with 8.0(6) to 8.1(*)
Message-ID: <30817@boulder.Colorado.EDU>
Date: 10 Dec 90 22:10:59 GMT
Sender: daemon@boulder.Colorado.EDU
Lines: 33

Are you both using DigitalLink Dl551VX's?

While there are other problems, the latest one that has been dug up
is an interoperability problem between them and the cisco's.

Marty
-------------


 The serial problem with the T1 link that you describe sounds exactly like the 
problem I am having, including all the steps you have taken and cisco's respons
e.  Our T1 line stopped working about 6 months ago and went into this abort err
or mode without us having changed anything.  Fortunately, I do have alternate p
aths to keep us limping along.

 One possible difference that we may have compared to your situation is heavy X
NS traffic in addtion to TCP/IP.  Perhaps because of this, I see the problem sh
owing up as a disruption of XNS traffic and not really of TCP/IP traffic.

 A symptom that may be relevant shows up when a transport connection is first e
stablished:  the first ten or so packets stream out at breakneck speed and from
 then on the whole connection stutters and stumbles along.  It is almost as if 
some resource gets used up and the connection then hobbles along, snatching som
e crumbs of needed capacity now and then.

 I have been waiting patiently for the new fast switching version of XNS, hopin
g that something in the XNS code would be tweaked and the problem would disappe
ar.  Hearing your tale makes me wonder if the assumption that the problem is XN
S related may be wrong and that the problem is wider in scope.

 I am eagerly awaiting responses that might clear up this mystery.

 --Max