> On Tue, 15 Oct 1996, Charles Scott wrote:
>
> > > 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.
> >
> > So if they know you're sourcing sync, why would they set theirs to
> > "internal"? I think this discussion could use a good authoritative
> > response from some network guru.
>
> What the UUNET guy told me was "you want one end (only one end) set to get
> timing from the loop." I'm guessing that the CSU at their end is now
> generating a timing signal and transmitting it out on the line to be used
> by our CSU. Of course, the docs from our Kentrox are quite vague on the
> signifigance of timing source...so I have no idea if any of this is
> right. All I know is how I have the thing set. i.e. where all the
> dipswitches are.
OH! (silly me) I read your earlier post wrong. You did say that you were
set to "clock on the loop". So they would be correct.
Chuck