03-06-2015 07:32 PM - edited 03-17-2019 02:14 AM
Hi,
I have 3 E1 bundled from same service provider and after a few months we had complaints regarding static noise heard over the the other line when we call someone from the office. This is random, at no particular time or day, but not always. When we check the E1 we see slip errors on all three E1 with the same amount of errors each.
I have searched here in the forums for solutions but all were suggesting different things, some say dont put "network-clock-participate" some says you need it. Some say to put the clocking on internal, some says on line (external).
I have 2 wic with 2 ports of E1. Here is my current config:
network-clock-participate wic 0
network-clock-participate wic 1
controller E1 0/0/0
clock source internal
pri-group timeslots 1-31
!
controller E1 0/0/1
clock source internal
pri-group timeslots 1-31
!
controller E1 0/1/0
clock source internal
pri-group timeslots 1-31
==================
router#sh network-clocks
Network Clock Configuration
---------------------------
Priority Clock Source Clock State Clock Type
10 Backplane GOOD PLL
Current Primary Clock Source
---------------------------
Priority Clock Source Clock State Clock Type
10 Backplane GOOD PLL
===================
router#sh controllers e1
E1 0/0/1 is up.
Applique type is Channelized E1 - balanced
No alarms detected.
alarm-trigger is not set
Version info FPGA Rev: 08121917, FPGA Type: PRK4
Framing is CRC4, Line Code is HDB3, Clock Source is Internal.
International Bit: 1, National Bits: 11111
Data in current interval (858 seconds elapsed):
0 Line Code Violations, 0 Path Code Violations
21 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins
21 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 0 Unavail Secs
Total Data (last 2 15 minute intervals):
0 Line Code Violations, 0 Path Code Violations,
45 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins,
45 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 0 Unavail Secs
E1 0/1/0 is up.
Applique type is Channelized E1 - balanced
No alarms detected.
alarm-trigger is not set
Version info FPGA Rev: 08121917, FPGA Type: PRK4
Framing is CRC4, Line Code is HDB3, Clock Source is Internal.
International Bit: 1, National Bits: 11111
Data in current interval (858 seconds elapsed):
0 Line Code Violations, 0 Path Code Violations
21 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins
21 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 0 Unavail Secs
Total Data (last 2 15 minute intervals):
0 Line Code Violations, 1 Path Code Violations,
45 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins,
46 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 0 Unavail Secs
03-06-2015 08:00 PM
Hi ejlbarcelon,
did you enter the 'network-clock-select' command?
For example:
network-clock-select 1 E1 0/0/0
Hope this helps.
03-06-2015 11:29 PM
not yet because on my previous installations i dont have this command but I dont have slip errors.
what exactly does this command do? as far as i know this is just to prioritize which clocking should all of you E1 follow, but mine is set as internal. correct me if I am wrong, but doesnt it mean that if all E1 are internal they follow the same clock?
03-07-2015 12:29 AM
Always use 'network-clock-select'
Otherwise the internal clock is used, which is not that accurate compared with the providers clock (in general)
03-07-2015 12:44 AM
hi j.huizinga,
but i am currently using clock source internal on all my controller. so should i change all of them to line and input the 'network-clock-select'?
03-07-2015 12:55 AM
Yes
Always
Don't use internal unless the other end does not provide clocking
The default is line if I am not mistaken
03-07-2015 02:12 AM
Hi j.huizinga,
we actually tried it before but still there are slip errors found.
i will try again to set it to line with the 'network-clock-select' command and see if it will stop.
Also do i need to configure 'network-clock-select 2 E1 0/0/1' and 'network-clock-select 3 E1 0/1/0'
03-07-2015 09:48 AM
as a backup
03-07-2015 03:45 PM
Hi ejlbarcelon,
this is an interesting document for you to read: Clock Configuration.
Hope this helps.
06-28-2015 07:22 PM
forgot to update, but after some troubleshooting it turns out to be a physical problem with the termination on the telco end.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide