[c-nsp] Trouble with a NM-2CT1-CSU module

[Eric Kagan]

Confirm the router with the CT controller card is set to 64k not 56k.  There
is a speed command option on the controller channel-group.  I get burned
with this on the VWIC-xMFT-T1 all the time !

controller T1 1/1
<snip>
channel-group 0 timeslots 1-24  speed 64  <---- note speed 64.  I think
default is 56k.

Eric



> -----Original Message-----
> From: cisco-nsp-bounces at puck.nether.net 
> [mailto:cisco-nsp-bounces at puck.nether.net] On Behalf Of james edwards
> Sent: Wednesday, August 03, 2005 7:30 PM
> To: bep at whack.org
> Cc: cisco-nsp at puck.nether.net
> Subject: Re: [c-nsp] Trouble with a NM-2CT1-CSU module
> 
> 
> 
> 
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA1
> >
> > james edwards wrote:
> > |>If those numbers are increasing, then this circuit is getting 
> > |>clocking errors IMHO.
> > |
> > |
> > |
> > | cmcs-NMS>sho controllers t1 1/0 brief
> > | T1 1/0 is up.
> > |   Applique type is Channelized T1
> > |   Cablelength is long gain36 0db
> > |   No alarms detected.
> > |   alarm-trigger is not set
> > |   Framing is ESF, FDL is ansi, Line Code is B8ZS, Clock Source is
> Internal.
> > |   Data in current interval (392 seconds elapsed):
> > |      0 Line Code Violations, 0 Path Code Violations
> > |      0 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins
> > |      0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 0 
> > | Unavail
> Secs
> > |   Total Data (last 11 15 minute intervals):
> > |      1326 Line Code Violations, 0 Path Code Violations,
> > |      2 Slip Secs, 167 Fr Loss Secs, 4 Line Err Secs, 0 
> Degraded Mins,
> > |      1 Errored Secs, 0 Bursty Err Secs, 17 Severely Err Secs, 150
> Unavail
> > | Secs
> > | cmcs-NMS>
> > |
> > | Clock slips are not increasing; I suspect the recorded 
> clock slips 
> > | are
> do to
> > | me futzing with the clocking
> > | a bit today. I have tried internel on one side and line on the 
> > | other,
> vice
> > | versa also. I have set clocking
> > | the line/network on both sides as a desperation move as I know no 
> > | one is providing external timing to this circuit. the 
> Tberd does not 
> > | indicate any clocking on this line when I have both
> sides
> > | disconnected from their routers.
> > |
> >
> > The framing errors at the interface level and the Frame 
> Loss seconds 
> > indicate that the routers are not getting the data framed 
> the same at 
> > both ends either due to 1) clocking not in sync; or 2) mismatched 
> > frame types between themselves or the circuit.  I'm skeptical of #2.
> >
> > Have you looped the circuit at either end either with the router or 
> > with the T-Berd to see if one side or the other will come up 
> > succesfully?
> 
> Hmmm..... I want to say we hard looped the router & it came 
> up. I will recheck this tomarrow and we are going to see if 
> we can hear LEC timing on this T-1 with the Tberd.
> 
> j
> 
> 
> 
> >
> > Since this is a T1 within a DS3, I don't recall OTOMH 
> whether it could 
> > really be clocked externally or not.
> 
> _______________________________________________
> 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/
>