Slip Errors on VWIC2-2MFT-E1 Cisco 2811

Answered Question
Jul 31st, 2007
User Badges:

I am receiving slip errors on both E1 controllers despite following the recommended configuration steps found @ cisco.com. I have tried switching the line primary command from one controller to the other and setting one clock source to internal but i am still receiving errors. I suspect that this is causing voice problems on my network. Any help would be appreciated.


The current configuration i have is below


network-clock-participate wic 0

!

controller E1 0/0/0

clock source line primary

channel-group 0 timeslots 1-31

!

controller E1 0/0/1

framing NO-CRC4

pri-group timeslots 1-16


2811#sh controller e1

E1 0/0/0 is up.

Applique type is Channelized E1 - balanced

No alarms detected.

alarm-trigger is not set

Version info Firmware: 20060926, FPGA: 13, spm_count = 0

Framing is CRC4, Line Code is HDB3, Clock Source is Line Primary.

CRC Threshold is 320. Reported from firmware is 320.

Data in current interval (255 seconds elapsed):

0 Line Code Violations, 0 Path Code Violations

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

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

Total Data (last 1 15 minute intervals):

0 Line Code Violations, 0 Path Code Violations,

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

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

E1 0/0/1 is up.

Applique type is Channelized E1 - balanced

No alarms detected.

alarm-trigger is not set

Version info Firmware: 20060926, FPGA: 13, spm_count = 0

Framing is NO-CRC4, Line Code is HDB3, Clock Source is Line.

CRC Threshold is 320. Reported from firmware is 320.

Data in current interval (254 seconds elapsed):

0 Line Code Violations, 8 Path Code Violations

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

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

Total Data (last 1 15 minute intervals):

0 Line Code Violations, 12 Path Code Violations,

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

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

Correct Answer by paolo bevilacqua about 9 years 11 months ago

Hi,


please add:

network-clock-select 1 E1 0/0/1 (or 0/0/0, try both). Clock source should be line if you are connecting to PSTN.


Hope this helps, please rate post if it does.



  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 4 (1 ratings)
Loading.
Correct Answer
paolo bevilacqua Tue, 07/31/2007 - 08:47
User Badges:
  • Super Gold, 25000 points or more
  • Hall of Fame,

    Founding Member

Hi,


please add:

network-clock-select 1 E1 0/0/1 (or 0/0/0, try both). Clock source should be line if you are connecting to PSTN.


Hope this helps, please rate post if it does.



cmcinally Tue, 07/31/2007 - 09:28
User Badges:

Thanks I managed to get it sorted in the meantime. I added network-clock-select 1 E1 0/0/1 and then changed the clock source for controller e1 0/0/1 to internal and it seems to be clean for the last 10 minutes. Many thanks you were certainly on the right track.

paolo bevilacqua Tue, 07/31/2007 - 09:42
User Badges:
  • Super Gold, 25000 points or more
  • Hall of Fame,

    Founding Member

Glad it helped, thanks and good luck!

Actions

This Discussion