Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Attention: The Community will be in read-only mode on 12/14/2017 from 12:00 am pacific to 11:30 am.

During this time you will only be able to see content. Other interactions such as posting, replying to questions, or marking content as helpful will be disabled for few hours.

We apologize for the inconvenience while we perform important updates to the Community.

New Member

Slips and other errors on T1 Controller

I'm getting a lot of errors on two different T1s on the same 3662 router. I think I have something set wrong but since I'm a rookie but I don't know where. Both links are full point to point T1s. I've played with Cablelength to see if it resolves the issue but it doesn't seem to make a difference. Any ideas?

T1 3/2 is up.

Applique type is Channelized T1

Cablelength is short 266

Description: T1 to Sacramento

No alarms detected.

alarm-trigger is not set

Version info Firmware: 20000922, FPGA: 15

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

Current port master clock: recovered from controller 3/1

Data in current interval (706 seconds elapsed):

8139 Line Code Violations, 18207 Path Code Violations

706 Slip Secs, 0 Fr Loss Secs, 678 Line Err Secs, 12 Degraded Mins

706 Errored Secs, 679 Bursty Err Secs, 0 Severely Err Secs, 0 Unavail Secs

T1 3/1 is up.

Applique type is Channelized T1

Cablelength is short 133

Description: T1 to Las Vegas

No alarms detected.

alarm-trigger is not set

Version info Firmware: 20000922, FPGA: 15

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

Current port master clock: recovered from controller 3/1

Data in current interval (107 seconds elapsed):

2759 Line Code Violations, 5419 Path Code Violations

97 Slip Secs, 0 Fr Loss Secs, 96 Line Err Secs, 2 Degraded Mins

77 Errored Secs, 76 Bursty Err Secs, 20 Severely Err Secs, 0 Unavail Secs

3 REPLIES
New Member

Re: Slips and other errors on T1 Controller

It looks like a timing issue. There should be one clock source for each T1 and every device should sync to that same source. Usually, on a P2P T1 the clocking is not supplied by the carrier (assuming there is a carrier). In this case, one end of the circuit should supply timing (clock source internal) and the other end should sync to it (clock source line).

I see that your local controllers are set for 'clock source line'. Are the other end set to 'internal'? A quick way to check if this is the issue is to set your local end to 'internal' and clear the interface counters. Give it a try, see what happens.

New Member

Re: Slips and other errors on T1 Controller

First, thanks for the response. I did try it locally on one of the T1s but it then showed the "T1 3/1 is down" message which scared me into putting back.

Should I have waited longer than about 15 secs for it to come back up?

T1 3/1 is down.

Applique type is Channelized T1

Cablelength is short 133

Description: T1 to Las Vegas

Receiver has remote alarm.

New Member

Re: Slips and other errors on T1 Controller

Usually 15 seconds is enough. Are you sure it was 15 seconds. 1.5 seconds can seem like 15 seconds when the network is down.

What do you have at the other end? Note that when you tried it, the remote end had the trouble ('Receiver has remote alarm'). You may have to schedule some down time to do some loopback testing.

324
Views
0
Helpful
3
Replies
CreatePlease to create content