> 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).
Hmm...that sounds familiar. We've had our T1 going up and down like a
cheap whore for the past month. We've been terminated to the same
hardware at UUNET for about 3 months, and it was quite reliable at first.
Before that, we were terminated to a different UUNET POP for about a year
with excellent service. This past month though, service has sucked
hard...and UUNET has done lots of finger pointing at the telcos, and the
telcos have pointed back at UUNET.
Today, I got a call from UUNET operations, and they noticed that they had
the CSU at their end set to clock on the loop...so was ours (and ours has
since day 1 when UUNET delivered it). They set their end to internal
clock source today...and maybe that will solve it...maybe it won't.
With both ends trying to sync on the loop, and no stable timing offered by
the telcos, is it conceivable that the T1 would work normally for a month
or two and then crap out for hours (as many as 18) at a time?
------------------------------------------------------------------
Jon Lewis <jlewis@fdt.net> | Unsolicited commercial e-mail will
Network Administrator | be proof-read for $199/hr.
________Finger jlewis@inorganic5.fdt.net for PGP public key_______