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

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

New Member

Line Code Violation and Error at E1 link.

Cisco gateway 3845 have 2 ports E1 Connectivity. one of the E1 link keeps dropping . At E1 controller interface we received the Line Code Violations

another port E1 are up and running  normally.

#sh controllers e1 4/0   1
E1 4/1 is up.
  Applique type is Channelized E1 - balanced
  No alarms detected.
  alarm-trigger is not set
  Version info Firmware: 20030723, FPGA: 255, spm_count = 0
  Framing is NO-CRC4, Line Code is HDB3, Clock Source is Line Primary.
  Current port master clock:recovered from controller 4/1
  Data in current interval (583 seconds elapsed):
     150963 Line Code Violations, 0 Path Code Violations
     0 Slip Secs, 0 Fr Loss Secs, 583 Line Err Secs, 10 Degraded Mins
     583 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 0 Unavail Secs
  Data in Interval 1:
     220907 Line Code Violations, 0 Path Code Violations
     0 Slip Secs, 0 Fr Loss Secs, 900 Line Err Secs, 15 Degraded Mins
     900 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 0 Unavail Secs
  Data in Interval 2:
     211835 Line Code Violations, 0 Path Code Violations
     0 Slip Secs, 0 Fr Loss Secs, 900 Line Err Secs, 15 Degraded Mins
     900 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 0 Unavail Secs
  Data in Interval 3:
     255647 Line Code Violations, 0 Path Code Violations
     0 Slip Secs, 0 Fr Loss Secs, 900 Line Err Secs, 15 Degraded Mins
     900 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 0 Unavail Secs
  Data in Interval 4:
     316410 Line Code Violations, 0 Path Code Violations
     0 Slip Secs, 0 Fr Loss Secs, 900 Line Err Secs, 15 Degraded Mins
     900 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 0 Unavail Secs
  Data in Interval 5:
     316645 Line Code Violations, 0 Path Code Violations
     0 Slip Secs, 0 Fr Loss Secs, 900 Line Err Secs, 15 Degraded Mins
     900 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 0 Unavail Secs
  Data in Interval 6:
     362512 Line Code Violations, 0 Path Code Violations
     0 Slip Secs, 0 Fr Loss Secs, 900 Line Err Secs, 15 Degraded Mins
     900 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 0 Unavail Secs
  Data in Interval 7:
     379349 Line Code Violations, 0 Path Code Violations
     0 Slip Secs, 0 Fr Loss Secs, 900 Line Err Secs, 15 Degraded Mins
     900 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 0 Unavail Secs
  Data in Interval 8:
     364701 Line Code Violations, 0 Path Code Violations
     0 Slip Secs, 0 Fr Loss Secs, 900 Line Err Secs, 15 Degraded Mins
     900 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 0 Unavail Secs
  Data in Interval 9:
     388329 Line Code Violations, 0 Path Code Violations
     0 Slip Secs, 0 Fr Loss Secs, 900 Line Err Secs, 15 Degraded Mins
900 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 0 Unavail Secs
  Data in Interval 10:
     419701 Line Code Violations, 0 Path Code Violations
     0 Slip Secs, 0 Fr Loss Secs, 900 Line Err Secs, 15 Degraded Mins
     900 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 0 Unavail Secs
  Data in Interval 11:
     408693 Line Code Violations, 0 Path Code Violations
     0 Slip Secs, 0 Fr Loss Secs, 900 Line Err Secs, 15 Degraded Mins
     900 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 0 Unavail Secs
  Data in Interval 12:
     415419 Line Code Violations, 0 Path Code Violations
     0 Slip Secs, 0 Fr Loss Secs, 900 Line Err Secs, 15 Degraded Mins
     900 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 0 Unavail Secs
  Data in Interval 13:
     415551 Line Code Violations, 0 Path Code Violations
     0 Slip Secs, 0 Fr Loss Secs, 900 Line Err Secs, 15 Degraded Mins
     900 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 0 Unavail Secs
  Data in Interval 14:
     407938 Line Code Violations, 0 Path Code Violations
     0 Slip Secs, 0 Fr Loss Secs, 900 Line Err Secs, 15 Degraded Mins
     900 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 0 Unavail Secs
  Data in Interval 15:
     394814 Line Code Violations, 0 Path Code Violations
     0 Slip Secs, 0 Fr Loss Secs, 900 Line Err Secs, 15 Degraded Mins
     900 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 0 Unavail Secs
  Data in Interval 16:
     405223 Line Code Violations, 0 Path Code Violations
     0 Slip Secs, 0 Fr Loss Secs, 900 Line Err Secs, 15 Degraded Mins
     900 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 0 Unavail Secs
  Data in Interval 17:
     392347 Line Code Violations, 0 Path Code Violations
     0 Slip Secs, 0 Fr Loss Secs, 900 Line Err Secs, 15 Degraded Mins
     900 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 0 Unavail Secs
  Data in Interval 18:
     438873 Line Code Violations, 1 Path Code Violations
     0 Slip Secs, 0 Fr Loss Secs, 900 Line Err Secs, 15 Degraded Mins
     900 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 0 Unavail Secs
  Data in Interval 19:
     429874 Line Code Violations, 0 Path Code Violations
     0 Slip Secs, 0 Fr Loss Secs, 900 Line Err Secs, 15 Degraded Mins
     900 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 0 Unavail Secs
  Data in Interval 20:
     361366 Line Code Violations, 0 Path Code Violations
     0 Slip Secs, 0 Fr Loss Secs, 900 Line Err Secs, 15 Degraded Mins
     900 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 0 Unavail Secs

......................

Data in Interval 95:
     4499810 Line Code Violations, 566 Path Code Violations
     98 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins
     0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 900 Unavail Secs
  Data in Interval 96:
     5160484 Line Code Violations, 658 Path Code Violations
     98 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins
     0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 900 Unavail Secs
  Total Data (last 24 hours)
     44750719 Line Code Violations, 1453 Path Code Violations,
     301 Slip Secs, 0 Fr Loss Secs, 83634 Line Err Secs, 1394 Degraded Mins,
     2147480820 Errored Secs, 0 Bursty Err Secs, 835 Severely Err Secs, 2147399996 Unavail Secs

Thanks in advance .

1 ACCEPTED SOLUTION

Accepted Solutions
Silver

Re: Line Code Violation and Error at E1 link

The answer is yes and no.  As long as the line code and framing are the same on both controllers you should be able to swap the cables and see if it helps the probllem - just don't try to send any calls - which you don't need to do anyway for this troubleshooting exercise.  Even if you have different isdn switch types on the two serial controllers it should not matter at the controller level.

HTH - if so please rate.

Art

4 REPLIES

Re: Line Code Violation and Error at E1 link.

Follow up on the following link:


http://www.cisco.com/en/US/tech/tk713/tk628/technologies_tech_note09186a00800f99bb.shtml

see how you go, if you are sure all your settings are correct, book it out to your SP, alternatively book it out anyway, as they are not always very prompt picking it up

Please remember to rate useful posts, by clicking on the stars below.

Silver

Re: Line Code Violation and Error at E1 link.

Hi,

I've seen line code errors caused by a bad cable and other physical issues.  If you are able (after hours) swap the two E1s - if the issue moves with the cables you know it is either the cables or the carrier gear...

HTH, please rate if so.

Cheers,

Art

New Member

Re: Line Code Violation and Error at E1 link

Hi,

Thanks for your response , One thing i would like to know , Among Two E1 Controller have different Configuration. for example One of E1 have timeslots 1-31 as MGCP configuration another E1 timeslots 1-12 setup according to the Product vendor . if we swap the two E1s it will not give  error mismatch cofiguration as it contain different setup.

Thanks

Silver

Re: Line Code Violation and Error at E1 link

The answer is yes and no.  As long as the line code and framing are the same on both controllers you should be able to swap the cables and see if it helps the probllem - just don't try to send any calls - which you don't need to do anyway for this troubleshooting exercise.  Even if you have different isdn switch types on the two serial controllers it should not matter at the controller level.

HTH - if so please rate.

Art

4352
Views
10
Helpful
4
Replies