sho controllers t1

T1 1/0 is up.

Applique type is Channelized T1

Cablelength is short 133

No alarms detected.

alarm-trigger is not set

Version info Firmware: 20031216, FPGA: 11

Framing is ESF, Line Code is B8ZS, Clock Source is Line.

CRC Threshold is 320. Reported from firmware is 0.

Current port master clock: recovered from controller 1/1

Data in current interval (41 seconds elapsed):

0 Line Code Violations, 0 Path Code Violations

41 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins

41 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 0 Unavail Secs

Total Data (last 54 15 minute intervals):

54 Line Code Violations, 11 Path Code Violations,

48127 Slip Secs, 0 Fr Loss Secs, 10 Line Err Secs, 1 Degraded Mins,

48128 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 25 Unavail Secs

T1 1/1 is up.

Applique type is Channelized T1

Cablelength is short 133

No alarms detected.

alarm-trigger is not set

Version info Firmware: 20031216, FPGA: 11

Framing is ESF, Line Code is B8ZS, Clock Source is Line.

CRC Threshold is 320. Reported from firmware is 0.

Current port master clock: recovered from controller 1/1

Data in current interval (44 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 54 15 minute intervals):

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

I forgot to mention that this is dual card ..and both 1/0 and 1/1 shows UP/DOWN

Thanks

Especially given the number of slip seconds recorded on the controller I would guess that there is a problem about clocking on the line. What do you have configured for clocking on the controller?

HTH

Rick

how do I find that ?

Thanks

scan the config, it should be right a top where controllers lines are showing.

Sam

You should see something at the top of your config that says:

controller t1 0/0

clock source line

controller t1 0/1

clock source line

Posting the "show controllers" shows that it's receiving clocking from the line, which is generally what it should be.

John

controller T1 1/0

framing esf

linecode b8zs

cablelength short 133

channel-group 0 timeslots 1-24 speed 64

!

controller T1 1/1

framing esf

linecode b8zs

cablelength short 133

channel-group 0 timeslots 1-24 speed 64

sho controllers show that ?

do I need to put different command ?

Thanks

try adding clock source line under controller.

I have the same config on an other 3660 router and it is up/up.. and does not show what you mentioned ...

controller T1 4/0

framing esf

linecode b8zs

cablelength short 133

channel-group 0 timeslots 1-24 speed 64

!

controller T1 4/1

framing esf

linecode b8zs

cablelength short 133

channel-group 0 timeslots 1-24 speed 64

is this provided by a telco ? if so ask them for a loop so u can validate if it is not their problem.

as far as I recall from my days playing with E1 and T1, BW i.e timeslots needs to be same at both ends. this used to be a common error alongside different encapsulation at both each side.

Sam

I totaly agree w/ ya ,,.

i had telco provide a loop from point a to z..

a router ---T1------NIU-------T1--------z router

I am able to see the loop facing to A router w/hclp encap and it look good , when the telco put the loop facing Z.. I do not see the loop .. I was told its the card and I did that . still can't see the loop from NIU to the router. change the NIU card and the cable going to s1/1 and 1/0 and still no loop , I created a hardloop plug and put on the card with HDLC config and still no loop on the router... that is the 1 million dollar question ,, why there is no loop on the interface if hardloop plug is in ?

Thanks for all your help

u could ask Telco to provide loop facing A , but this time as close to Z as possible. then you would know which segment is faulty.

May be faulty loop plug?

Also, when using such a thing, set clock internal.

To avoid slips, use "network-clock-participate" and "network-clock-select". But that is not your main problem.