Path: utzoo!censor!geac!torsqnt!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!elroy.jpl.nasa.gov!ncar!boulder!daemon
From: asp@uunet.UU.NET (Andrew Partan)
Newsgroups: comp.dcom.sys.cisco
Subject: Serial problems with 8.0(6) to 8.1(*)
Message-ID: <30777@boulder.Colorado.EDU>
Date: 7 Dec 90 23:17:51 GMT
Sender: daemon@boulder.Colorado.EDU
Lines: 34

We switched from 8.0(6) to 8.1(14) about 6 months ago and have been
having serial line problems on 1 T1 ever since.  This was a T1 that had
been working just fine for over a year prior to this.

We first thought that it was a serial line problem or perhaps bad
boards or bad CSU/DSUs, but we have done the following since:
	- reterminate both ends of the T1
	- had the local phone company give us a brand new T1
	- swapped *every* cable and interface and board on each end
	- installed a brand new cisco at each end
	- swapped CSU/DSUs (both the same type and to a different
		manufacturor)
	- upgraded to 8.1(19) or to 8.1(25)
	- tried different switch settings on the CSU/DSUs
	- basically swapped every piece of hardware or software that we
	  can find.
All to *no* avail - we are still getting errors - to the tune of 100 -
1000 (nearly) *every* 5 minutes.  Most of these error are cisco abort
errors.

The only thing 'special' about this T1 (different from other T1s
attached to the same cisco or elsewhere in our network) is that this T1
is the most used - about 200K almost all of the time.

cisco has been of little or no real help.  They keep on saying that it
must be either the T1 or the CSU/DSUs.  [The only bug report number
that has ever been given to me by cisco for this problem is 901120235.
I almost never get a number for any of the calls that I make.]

Does anyone have any suggestions?  Or have similar problems?

Thanks,
	--asp@uunet.uu.net (Andrew Partan)
	ASN.1 Object Identifier: "{joint-iso-ccitt mhs(6) group(6) 157}"