Re: CRC Errors

Brian Moore (bem@cmc.net)
Tue, 15 Oct 1996 09:31:50 -0700 (PDT)

Well, it shouldn't be timing (unless the CSU's are hosed). Since this is a
leased line to a POP (not the 'net feed), we have one end providing the timing
for both, which works just fine and dandy on two of our lines... on one T1,
though, we're seeing Tons of Framing and Abort errors (with darn near zero CRC
errors), and ... we're seeing a similar thing on a 64k circuit, though not to
the same extent. The 64k CSU's are so mindless to set up, I don't think it's a
configuration issue on them. (Basically only one set of switches will work.)

I guess I'll have MCI play with the line this weekend and see what they find.

It will stay up and stable for a couple days, then have a fit and drop protocol
sometimes 3 times in an hour.

Fun Fun Fun.

> Brian:
> Gee, sure sounds like line problems. You might check to make sure
> both wires on the incoming line are good. You can often run on only 1
> wire, but you'll have errors.
> Also, we noticed after being connected to MCI for a bit that they must
> have their CSU/DSU set to take sync from the line, we did also and were
> getting some timing slips. We set ours to source sync and that went away.
> (at least that's the way I remember it).
>
> Chuck
>
>
> On Mon, 14 Oct 1996, Brian Moore wrote:
>
> > I'll freely admit to not grokking all the nuances of telephony. (But if
> > you need some C or Perl hacks, now that's my cup of tea.. or even more
> > fun, my old love, Z80 Assembly.... :))
> >
> > I am seeing some HUGE numbers for Frame Errors, damned near nothing for
> > CRC errors, a huge number of Abort Errors...
> >
> > Should I scream bloody murder to MCI? The CSU's (Kentrox Data Smarts)
> > don't seem to notice most of the problems, but eventually protocol stops
> > running down the line until the W1 port is reset (which means I make a
> > long distance call to the far end if I'm home, or unplug the line long
> > enough to make a red alarm if I'm here, which will reset W1 with no long
> > distance charge, but sorta screws up the stats the DataSmart keeps.
> >
> > And my router has a more creative name.. though the PM's need better
> > names.
> >
> > > Call your telco immediately. Chances are also that your CSU/DSU (if it
> > > is a T1) has recorded some errors such as errored seconds and
> > > code-violations. It might be a bad repeater in their system or a CO
> > > problem.
> > > You need a more creative name than irx1 also.
> > >
> > > >
> > > > Can someone tell me if there is any software out there to determine
> > > > where these CRC errors are coming from. I have done everything short
> > > > of buying all new hardware. I have replaced the cables already and
> > > > the 2 units worked fine before I changed over to the IRX-114.
> > > >
> >
> >