[c-nsp] CT3 Timing issue

[Lee Starnes]

In our experience with the TA908e CPEs, we had to set the timing on the
cisco side to network (or slave) and the TA908e be the master. This is
because Adtran only uses 1 clock on the CPE. This was the only way we could
solve the issue when spread across DS3 circuits. We have about 40 of these
in service and they are running solid like this.

-Lee

On Tue, Jun 5, 2012 at 7:53 PM, Natambu Obleton
<nobleton at fasttrackcomm.net>wrote:

> I changed the PA-MC-T3s to line clocking, but still getting errors. If I
> connect both T1s to the same DS3, everything is fine. It's only if I spread
> the MLPPP T1's across the PA-MC-T3. I don't have the spread them, but it
> does the customer some redundancy. The CPE is an Adtran TA908e.
>
> Since I know the Adtran uses the same clock for both T1s and the
> PA-MC-T3's aren't, I have changed the T1 ports on the PA-MC-T3 to line and
> changed the adtran to internal and the slips have stopped. I do feel better
> with the PA-MC-T3 set to line on the DS3. Common clock achieved, sorta. :)
>
>
>
>
> On Jun 5, 2012, at 4:41 PM, Natambu Obleton wrote:
>
> > Yeah. We have external BITS clocks, and secondary timing from the local
> exchange carrier. I will try line timing after hours tonight. If I
> terminate the T1's the same PA-MC-T3 I don't have slips, so the PA-MC-T3
> must have a clock on the card....
> >
> > --
> >
> > Natambu Obleton, CISSP CCNA
> > Senior Network Engineer
> > FastTrack Communications, Inc.
> > 970.828.1009
> >
> > -----Original Message-----
> > From: Walter Keen [mailto:walter.keen at rainierconnect.net]
> > Sent: Tuesday, June 05, 2012 3:59 PM
> > To: Natambu Obleton
> > Cc: cisco-nsp at puck.nether.net
> > Subject: Re: [c-nsp] CT3 Timing issue
> >
> > In most cases, a topology like this will have the ONS's synced to GPS
> time, or some accurate clock  (or line clocking if your ONS connects to
> another provider, but GPS is typically preferred) and then I would
> DEFINITELY use line clocking on the PA-MC-T3, unless you have the
> capability through a clock card to connect the 7204 to the same timing
> source as the ONS uses (ie: GPS derived clock) Whenever possible, keep all
> devices in sync with a common clock
> >
> >
> >
> >
> > ----- Original Message -----
> >
> > From: "Natambu Obleton" <nobleton at fasttrackcomm.net>
> > To: cisco-nsp at puck.nether.net
> > Sent: Tuesday, June 5, 2012 2:17:54 PM
> > Subject: [c-nsp] CT3 Timing issue
> >
> > Hello,
> >
> > I have a customer with a 2xT1 MPPP link to my 7204. The T1 come in to
> the 7204 on different PA-MC-T3 cards. The PA-MC-T3 cards plug into my ONS
> 15454 SONET network. When I have timing set on the CPE to one of the T1s
> the other T1 gets slips and vice versa. Both of the PA-MC-T3 are set for
> internal timing. Shouldn't their timing be the same or should I have these
> setup for line timing? Thanks.
> >
> > --
> >
> > Natambu Obleton, CISSP CCNA
> > Senior Network Engineer
> > FastTrack Communications, Inc.
> > 970.828.1009
> >
> > _______________________________________________
> > cisco-nsp mailing list cisco-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> > archive at http://puck.nether.net/pipermail/cisco-nsp/
> >
> > _______________________________________________
> > cisco-nsp mailing list  cisco-nsp at puck.nether.net
> > https://puck.nether.net/mailman/listinfo/cisco-nsp
> > archive at http://puck.nether.net/pipermail/cisco-nsp/
>
>
> _______________________________________________
> cisco-nsp mailing list  cisco-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/
>