Input errors on T1 interface

[alison.hou]

  The T1 interface on a MPLS router kept buncing recently. the local carrier said he looped to  the smart jack and it was clean. As soon as it connected our router and it showed errors. We have swapped T1 cable. I am asking the carrier to check its T1 jack. In the meantime, I wanted to make sure our router is good. I attached the "show tech" here. Can someone please take a look and see if the router hardware has any issues?

thanks.

Alison

[John Blakley]

Alison,

You're getting a ton of CRCs on S0/1/0. The counters were last cleared 15 hours ago per your post. I would have the telco run an intrusive test on the circuit to see what the issue is. I know they stated that it was clean, but in my experience, they won't do any extensive testing unless you specifically ask for it.

Serial0/1/0 is up, line protocol is up

Last clearing of "show interface" counters 15:52:14

112319 input errors, 112318 CRC, 46975 frame, 19248 overrun, 0 ignored, 59013 abort

HTH,
John

*** Please rate all useful posts ***

[JohnTylerPearce]

Alison,

Can you run the following command and post the results.

show service-module serial performance-statistics ?

This will show intervals of 15 minutes, so you can do 1 to 10 so to speak.

[alison.hou]

thanks. here is the result.

RTR_COLUMBUS_OH#show service-module s0/1/0 performance-statistics 1 - 10

Total Data (last 74 15 minute intervals):

    130165 Line Code Violations, 7620 Path Code Violations

    11 Slip Secs, 7724 Fr Loss Secs, 29 Line Err Secs, 152 Degraded Mins

    1747 Errored Secs, 1185 Bursty Err Secs, 3 Severely Err Secs, 7745 Unavail Secs

Data in current interval (45 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

Data in Interval 1:

    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

Data in Interval 2:

    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

Data in Interval 3:

    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

Data in Interval 4:

    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

Data in Interval 5:

    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

Data in Interval 6:

    18278 Line Code Violations, 1016 Path Code Violations

    0 Slip Secs, 131 Fr Loss Secs, 4 Line Err Secs, 7 Degraded Mins

    58 Errored Secs, 36 Bursty Err Secs, 2 Severely Err Secs, 129 Unavail Secs

Data in Interval 7:

    0 Line Code Violations, 14 Path Code Violations

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

    9 Errored Secs, 1 Bursty Err Secs, 0 Severely Err Secs, 0 Unavail Secs

Data in Interval 8:

    0 Line Code Violations, 7 Path Code Violations

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

    5 Errored Secs, 2 Bursty Err Secs, 0 Severely Err Secs, 0 Unavail Secs

Data in Interval 9:

    0 Line Code Violations, 4 Path Code Violations

    0 Slip Secs, 405 Fr Loss Secs, 0 Line Err Secs, 1 Degraded Mins

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

Data in Interval 10:

    0 Line Code Violations, 9 Path Code Violations

    2 Slip Secs, 270 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins

    3 Errored Secs, 2 Bursty Err Secs, 0 Severely Err Secs, 270 Unavail Secs

RTR_COLUMBUS_OH#

[alison.hou]

thanks for posting. I have asked my carrier to check its network again.

[JohnTylerPearce]

I agree with John, they need to do intrusive testing, and you can provide them the output of that command as well. I run into these issues all the time.

[alison.hou]

Thanks, guys.

I updated the ticket with the output. there are so many line code and path code violations....

[vmiller]

Double check your clock source. You should be getting it from the network.

[vmiller]

Some light reading on T-1's

http://www.cisco.com/c/en/us/support/docs/wan/t1-e1-t3-e3/14171-T1-error.html