×

Warning message

  • Cisco Support Forums is in Read Only mode while the site is being migrated.
  • Cisco Support Forums is in Read Only mode while the site is being migrated.

E1 Clocking

Unanswered Question
Nov 22nd, 2013
User Badges:

Hello,

I have an MGCP gateway with 2 E1 PRI lines connected. One of them the slips and errors are incrementing. The clock source is line from the telco as per normal. I have also tried setting the clock source as internal but still there is a problem with clocking


Anything else I can try or do I need to report this to the telco?


There is one difference between the 2 PRI lines. One (E1 1/0 is a traditional e1 TDM circuit and the line with the error is a VOIP PRI i.e the E1 line is connected from my router E1 1/1 to the telco Cisco router E1 interface



CONFIG:


network-clock-participate slot 1

network-clock-select 1 E1 1/0



E1 1/0 is up.

  Applique type is Channelized E1 - balanced

No alarms detected.

  alarm-trigger is not set

  Version info Firmware: 20100222, FPGA: 255, spm_count = 0

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

  Current port master clock:recovered from backplane

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

  Total Data (last 1 15 minute intervals):

     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


E1 1/1 is up.

  Applique type is Channelized E1 - balanced

No alarms detected.

  alarm-trigger is not set

  Version info Firmware: 20100222, FPGA: 255, spm_count = 0

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

  Current port master clock:recovered from backplane

  Data in current interval (677 seconds elapsed):

     0 Line Code Violations, 0 Path Code Violations

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

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





  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
Gordon Ross Fri, 11/22/2013 - 02:14
User Badges:
  • Blue, 1500 points or more

You need to be clear who is the clock soure for interface 1/1. If you're not the clock source, then you need a "network-clock-select" command for the interface.


GTG


Please rate all helpful posts.

Aman Soi Fri, 11/22/2013 - 02:26
User Badges:
  • Purple, 4500 points or more
  • Cisco Designated VIP,

    2017 IP Telephony

Hi ,


can u share output of show network-clocks?


regds,

aman

CiscoRunner Fri, 11/22/2013 - 03:00
User Badges:

Hi Gordon,

I have tried putting network-clock-select 2 E1 1/1 but that doesnt make any difference...


Aman, show network-clocks:



Network Clock Configuration

  ---------------------------

  Priority      Clock Source    Clock State     Clock Type



     1          E1 1/0          GOOD            E1

     2          E1 1/1          GOOD            E1

    10          Backplane       GOOD            PLL



  Current Primary Clock Source

  ---------------------------

  Priority      Clock Source    Clock State     Clock Type



     1          E1 1/0          GOOD            E1

Gordon Ross Fri, 11/22/2013 - 03:04
User Badges:
  • Blue, 1500 points or more

In which case, are you and the other end sure you know who is producing the clock?


GTG


Please rate all helpful posts.

CiscoRunner Fri, 11/22/2013 - 03:23
User Badges:

I was under the impression it was the telco providing the source but seeing as I am still getting errors hence my question earlier :

"Anything else I can try or do I need to report this to the telco?"

Gordon Ross Fri, 11/22/2013 - 03:25
User Badges:
  • Blue, 1500 points or more

I'd speak to your Telco's tech support team.


GTG


Please rate all helpful posts.

Actions

This Discussion