cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
9894
Views
5
Helpful
5
Replies

E1 Controller Problem - Entering Holdover for Controller E1 0/0/0 and Network clock source transitioned from priority 1 to priority 10

marcel.pludra
Level 1
Level 1

Hello everybody,

 

i got the following Warnings on my E1 Controller:

 

Oct  5 06:12:32.657: %MARS_NETCLK-3-HOLDOVER: Entering Holdover for Controller E1 0/0/0
Oct  5 06:12:42.905: %MARS_NETCLK-3-HOLDOVER_TRANS: Holdover timer exceeded for Controller E1 0/0/0
Oct  5 06:12:42.905: %MARS_NETCLK-3-CLK_TRANS: Network clock source transitioned from priority 1 to priority 10
Oct  5 06:12:53.405: %MARS_NETCLK-3-CLK_TRANS: Network clock source transitioned from priority 10 to priority 1

 

It's an 2951 ISR with an 1MFT T1/E1 Card.

 

Does anyone know what this means?

Is this an provider problem?

 

Thanks for helping

 

Best regards,

Marcel

1 Accepted Solution

Accepted Solutions

Solved: It was an provider issue.

 

 

View solution in original post

5 Replies 5

Jonathan Unger
Level 7
Level 7

Hi Marcel,

 

Very well could be a provider issue.

Can you post the output of "show controllers e1"?

E1 0/0/0 is up.
  Applique type is Channelized E1 - balanced
  No alarms detected.
  alarm-trigger is not set
  Version info FPGA Rev: 08121917, FPGA Type: PRK1
  Framing is CRC4, Line Code is HDB3, Clock Source is Line.
  International Bit: 1, National Bits: 11111
  Data in current interval (10 seconds elapsed):
     0 Line Code Violations, 0 Path Code Violations
     4 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins
     4 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 0 Unavail Secs
  Total Data (last 24 hours)
     0 Line Code Violations, 6 Path Code Violations,
     59161 Slip Secs, 73 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins,
     59226 Errored Secs, 1 Bursty Err Secs, 0 Severely Err Secs, 70 Unavail Secs

Solved: It was an provider issue.

 

 

I have the same prob, do you know what was the fix which ISP did at their end? 

The same problem, how did you know that the ISP was the problem?