Path: utzoo!attcan!uunet!zaphod.mps.ohio-state.edu!ncar!boulder!daemon
From: Maxim_Bohlmann.XSIS-HQ@xerox.com
Newsgroups: comp.dcom.sys.cisco
Subject: Re: Serial problems with 8.0(6) to 8.1(*)
Message-ID: <30811@boulder.Colorado.EDU>
Date: 10 Dec 90 19:57:39 GMT
Sender: daemon@boulder.Colorado.EDU
Lines: 11

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 response.  Our T1 line stopped working about 6 months ago and went into this abort error mode without us having changed anything.  Fortunately, I do have alternate paths to keep us limping along.

One possible difference that we may have compared to your situation is heavy XNS traffic in addtion to TCP/IP.  Perhaps because of this, I see the problem showing 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 established:  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 some crumbs of needed capacity now and then.

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

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

--Max