cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Announcements

1973
Views
0
Helpful
5
Replies
Highlighted
Beginner

Issue: All site users hear buzzing on the line and are then disconnected. Intermittent with no apparent pattern.

Hi all,

Having some issues with our VOIP system where, intermittenly, people will hear a buzz and then be disconnected. Phone calls can't be made or received for a few seconds (in this latest instance, about 26 seconds).

Happens site-wide, but not other sites around the country.

Device Info:

IOS: Cisco IOS Software, 2800 Software (C2800NM-ADVIPSERVICESK9-M), Version 12.4(24)T4, RELEASE SOFTWARE (fc2)

Cisco 2821 (revision 53.51) with 245760K/16384K bytes of memory.
2 Gigabit Ethernet interfaces
31 Serial interfaces
1 Channelized/Clear E1/PRI port
2 Virtual Private Network (VPN) Modules
4 Voice FXS interfaces

Our router shows the following:

    sh controller e1 0/3/0 brief

    E1 0/3/0 is up.

      Applique type is Channelized E1 - balanced

      Cablelength is Unknown

      No alarms detected.

      alarm-trigger is not set

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

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

      Data in current interval (77 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 24 hours)

         0 Line Code Violations, 607 Path Code Violations,

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

         1 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 26 Unavail Secs

Note the slip, errored, and unavailable Secs.

I've read on some forums that you need participate and select configured.

We have both network-clock-participate and network-clock-select configured as follows:

network-clock-participate wic 3

network-clock-select 1 E1 0/3/0

At the time, our Syslog records the following for the router:

Feb 15 12:33:54: %CONTROLLER-5-UPDOWN: Controller E1 0/3/0, changed state to down (LOF detected)

Feb 15 12:33:54: %ISDN-6-DISCONNECT: Interface Serial0/3/0:6  disconnected from %sensored% , call lasted 1715 seconds

Feb 15 12:33:54: %ISDN-6-DISCONNECT: Interface Serial0/3/0:0  disconnected from %sensored% , call lasted 332 seconds

Feb 15 12:33:54: %ISDN-6-DISCONNECT: Interface Serial0/3/0:2  disconnected from %sensored% , call lasted 167 seconds

Feb 15 12:33:54: %ISDN-6-DISCONNECT: Interface Serial0/3/0:1  disconnected from %sensored% , call lasted 3 seconds

Feb 15 12:33:54: %ISDN-6-LAYER2DOWN: Layer 2 for Interface Se0/3/0:15, TEI 0 changed to down

Feb 15 12:33:54: %MARS_NETCLK-3-HOLDOVER: Entering Holdover for Controller E1 0/3/0

Feb 15 12:33:56: %LINK-3-UPDOWN: Interface Serial0/3/0:15, changed state to down

Feb 15 12:34:04: %MARS_NETCLK-3-HOLDOVER_TRANS: Holdover timer exceeded for Controller E1 0/3/0

Feb 15 12:34:04: %MARS_NETCLK-3-CLK_TRANS: Network clock source transitioned from priority 1 to priority 10

Feb 15 12:34:20: %CONTROLLER-5-UPDOWN: Controller E1 0/3/0, changed state to up

Feb 15 12:34:22: %LINK-3-UPDOWN: Interface Serial0/3/0:15, changed state to up

Feb 15 12:34:28: %ISDN-6-LAYER2UP: Layer 2 for Interface Se0/3/0:15, TEI 0 changed to up

Feb 15 12:34:30: %MARS_NETCLK-3-CLK_TRANS: Network clock source transitioned from priority 10 to priority 1

Feb 15 12:34:32: %ISDN-6-CONNECT: Interface Serial0/3/0:0 is now connected to %sensored% N/A

This tells me the issue lies with the Telco, "Clock Source is Line." in the above "sh controller"?

We logged the fault with the Telco who claim it's not their issue.

We persisted with them and now they want to have an outage so they can do a loopback test.

I'm concerned that it won't reveal itself during the test, being intermittent and all.

Has anyone solved this issue before - even from a Telco perspective?

Any suggestions or ideas on what I could try from here will be greatly appreciated?

PS. We have the identically configured router, on the other side of the country (same Telco, different state), which has had no reported issues.

5 REPLIES 5
Beginner

Re: Issue: All site users hear buzzing on the line and are then

Hi Brett,

It is rare they admit to a problem.  Usually you point something out to them, they test/reconfigure something and it works...without them indicating a problem existed.

Do you have a way of isolating the ckt?  If the MFT card terminating the E1 is a 2 port card, a good test would be to move the ckt to that interface.  If nothing else, note the timestamp of the outage, and ask telco to investigate their logs during that time.  The 607 path code violations indicate a problem on the telco's eqpt.  Clear the counters on the controller and check periodically for incrementing PCVs.

HTH

Beau

Beginner

Re: Issue: All site users hear buzzing on the line and are then

Hi Beau,

Thanks for the info....yes - I am def. leaning towards the Telco to be at fault here.

We've given them some of the log info - might hit them up with some more.

Secondly, and unfortunately, our card is only a single port card - so no can do on that front.

PS. Do you think it could be a dodgy E1 crossover cable between our router and the Telco device? I don't think so - but I wasn't here when this site was installed and know that it was made by the (contracted) tech onsite at the time.

I've since made the cables for more recent deployments and have not had trouble with them ... yet.

Need to wait for a good time for an outage, I might swap over for one of mine and see what happens (but don't want to do it at the same time as the Telco)

Will continue to update this post as the saga continues.

Beginner

Re: Issue: All site users hear buzzing on the line and are then

Well - the carrier performed a quick test < 30 mins and 'found no fault'.


I've replaced the E1 crossover cable between the router and the carrier device and the issue happened again (once) since.

I feel I can, therefore, rule out a faulty cable on my side.

A check of the logs - it looks like it hasn't happened now for 14 consecutive days - but I'm not holding my breath.


The carrier has requested a 3 hour outage to perform some more testing. Will be a while before we can offer them that amount of time - but will post results when I have them.

Of note – I have also discovered the following in our logs - “(RAI detected)”, “(LOF detected)”, and “(AIS detected)”:

05407: Jan 14 10:46:50: %CONTROLLER-5-UPDOWN: Controller E1 0/3/0, changed state to down (RAI detected)

15368: Jan 25 18:18:46: %CONTROLLER-5-UPDOWN: Controller E1 0/3/0, changed state to down (AIS detected)

15378: Jan 25 18:36:46: %CONTROLLER-5-UPDOWN: Controller E1 0/3/0, changed state to down (LOF detected)

15388: Jan 25 18:42:22: %CONTROLLER-5-UPDOWN: Controller E1 0/3/0, changed state to down (LOF detected)

25585: Feb  7 10:01:04: %CONTROLLER-5-UPDOWN: Controller E1 0/3/0, changed state to down (LOF detected)

26530: Feb  8 03:48:06: %CONTROLLER-5-UPDOWN: Controller E1 0/3/0, changed state to down (LOF detected)

26942: Feb  8 10:07:12: %CONTROLLER-5-UPDOWN: Controller E1 0/3/0, changed state to down (LOF detected)

27739: Feb  8 21:16:26: %CONTROLLER-5-UPDOWN: Controller E1 0/3/0, changed state to down (LOF detected)

27749: Feb  8 21:18:00: %CONTROLLER-5-UPDOWN: Controller E1 0/3/0, changed state to down (LOF detected)

27759: Feb  8 23:56:08: %CONTROLLER-5-UPDOWN: Controller E1 0/3/0, changed state to down (LOF detected)

27773: Feb  9 00:41:26: %CONTROLLER-5-UPDOWN: Controller E1 0/3/0, changed state to down (LOF detected)

27783: Feb  9 00:58:46: %CONTROLLER-5-UPDOWN: Controller E1 0/3/0, changed state to down (LOF detected)

27795: Feb  9 04:05:06: %CONTROLLER-5-UPDOWN: Controller E1 0/3/0, changed state to down (LOF detected)

28002: Feb  9 08:43:36: %CONTROLLER-5-UPDOWN: Controller E1 0/3/0, changed state to down (AIS detected)

28637: Feb  9 13:10:52: %CONTROLLER-5-UPDOWN: Controller E1 0/3/0, changed state to down (LOF detected)

28675: Feb  9 13:15:46: %CONTROLLER-5-UPDOWN: Controller E1 0/3/0, changed state to down (LOF detected)

29291: Feb 10 09:36:16: %CONTROLLER-5-UPDOWN: Controller E1 0/3/0, changed state to down (LOF detected)

29313: Feb 10 09:43:12: %CONTROLLER-5-UPDOWN: Controller E1 0/3/0, changed state to down (LOF detected)

33830: Feb 15 12:33:54: %CONTROLLER-5-UPDOWN: Controller E1 0/3/0, changed state to down (LOF detected)

34729: Feb 16 09:51:23: %CONTROLLER-5-UPDOWN: Controller E1 0/3/0, changed state to down (LOF detected)

34810: Feb 16 10:18:44: %CONTROLLER-5-UPDOWN: Controller E1 0/3/0, changed state to down (LOF detected)

34843: Feb 16 10:27:50: %CONTROLLER-5-UPDOWN: Controller E1 0/3/0, changed state to down (LOF detected)

34880: Feb 16 10:34:45: %CONTROLLER-5-UPDOWN: Controller E1 0/3/0, changed state to down (LOF detected)

35397: Feb 16 14:22:16: %CONTROLLER-5-UPDOWN: Controller E1 0/3/0, changed state to down (LOF detected)

35508: Feb 16 15:04:04: %CONTROLLER-5-UPDOWN: Controller E1 0/3/0, changed state to down (LOF detected)

36680: Feb 17 15:52:17: %CONTROLLER-5-UPDOWN: Controller E1 0/3/0, changed state to down (LOF detected)

42217: Feb 24 12:22:19: %CONTROLLER-5-UPDOWN: Controller E1 0/3/0, changed state to down (AIS detected)

42676: Feb 25 02:39:17: %CONTROLLER-5-UPDOWN: Controller E1 0/3/0, changed state to down (LOF detected)

42779: Feb 25 06:56:47: %CONTROLLER-5-UPDOWN: Controller E1 0/3/0, changed state to down (AIS detected)

42892: Feb 25 08:46:28: %CONTROLLER-5-UPDOWN: Controller E1 0/3/0, changed state to down (LOF detected)

44236: Feb 28 09:11:52: %CONTROLLER-5-UPDOWN: Controller E1 0/3/0, changed state to down (LOF detected)

44318: Feb 28 09:44:35: %CONTROLLER-5-UPDOWN: Controller E1 0/3/0, changed state to down (LOF detected)

44339: Feb 28 09:48:27: %CONTROLLER-5-UPDOWN: Controller E1 0/3/0, changed state to down (RAI detected)

46471: Mar  1 22:43:34: %CONTROLLER-5-UPDOWN: Controller E1 0/3/0, changed state to down (LOF detected)

47226: Mar  2 12:35:01: %CONTROLLER-5-UPDOWN: Controller E1 0/3/0, changed state to down (LOF detected)

47239: Mar  2 12:35:38: %CONTROLLER-5-UPDOWN: Controller E1 0/3/0, changed state to down (RAI detected)

48270: Mar  3 11:19:55: %CONTROLLER-5-UPDOWN: Controller E1 0/3/0, changed state to down (AIS detected)

48682: Mar  3 14:55:27: %CONTROLLER-5-UPDOWN: Controller E1 0/3/0, changed state to down (LOF detected)

48694: Mar  3 14:57:32: %CONTROLLER-5-UPDOWN: Controller E1 0/3/0, changed state to down (LOF detected)

49751: Mar  4 14:10:24: %CONTROLLER-5-UPDOWN: Controller E1 0/3/0, changed state to down (RAI detected)

54954: Mar 11 13:47:29: %CONTROLLER-5-UPDOWN: Controller E1 0/3/0, changed state to down (LOF detected)

56217: Mar 14 20:32:27: %CONTROLLER-5-UPDOWN: Controller E1 0/3/0, changed state to down (LOF detected)

56227: Mar 14 20:37:27: %CONTROLLER-5-UPDOWN: Controller E1 0/3/0, changed state to down (LOF detected)

62443: Mar 21 14:31:09: %CONTROLLER-5-UPDOWN: Controller E1 0/3/0, changed state to down (LOF detected)

68459: Mar 28 13:42:36: %CONTROLLER-5-UPDOWN: Controller E1 0/3/0, changed state to down (RAI detected)

Enthusiast

Issue: All site users hear buzzing on the line and are then disc

Hi Brett

I am having same issue can you please let me know what was the problem in you case

Thanks

Beginner

Re: Issue: All site users hear buzzing on the line and are then

In the end it just went away - I'm still going to put it down to carrier.

Interestingly - the issue has cropped up again but this time at another site on the other side of the country (Brisbane).

A look at the logs shows it happened a couple of times on Sunday, a couple of times on Wednesday, and a shedload of times yesterday. Nothing yet today.

This just makes me believe the carrier has an issue - advice - keep pushing back on the carrier or migrate to SIP trunks and do away with ISDN altogether.

We're, co-incidentally, replacing this router as part of a refresh in the next 2 to 3 weeks - if the problem persists over the next couple of days, we'll likely expedite this in order to rule out hardware on our side for this instance.

But yeah - basically I haven't found anything on our side from past experience that indicates anything other than issue at carrier.

zcat bri-rtr00-2013-09-0* | egrep -i 'clk|layer2|lof|rai|ais'

bri-rtr00 Sep  1 11:46:02 2013 83367: Sep  1 13:46:02 AET: %CONTROLLER-5-UPDOWN: Controller E1 0/3/0, changed state to down (LOF detected)

bri-rtr00 Sep  1 11:46:02 2013 83368: Sep  1 13:46:02 AET: %ISDN-6-LAYER2DOWN: Layer 2 for Interface Se0/3/0:15, TEI 0 changed to down

bri-rtr00 Sep  1 11:46:03 2013 83369: Sep  1 13:46:02 AET: %MARS_NETCLK-3-HOLDOVER: Entering Holdover for Controller E1 0/3/0

bri-rtr00 Sep  1 11:46:04 2013 83371: Sep  1 13:46:03 AET: %ISDN-6-LAYER2UP: Layer 2 for Interface Se0/3/0:15, TEI 0 changed to up

bri-rtr00 Sep  1 11:46:06 2013 83372: Sep  1 13:46:05 AET: %MARS_NETCLK-3-HOLDOVER: Exiting Holdover for Controller E1 0/3/0

bri-rtr00 Sep  3 04:04:07 2013 83511: Sep  3 06:04:07 AET: %CONTROLLER-5-UPDOWN: Controller E1 0/3/0, changed state to down (LOF detected)

bri-rtr00 Sep  3 04:04:07 2013 83512: Sep  3 06:04:07 AET: %ISDN-6-LAYER2DOWN: Layer 2 for Interface Se0/3/0:15, TEI 0 changed to down

bri-rtr00 Sep  3 04:04:08 2013 83513: Sep  3 06:04:07 AET: %MARS_NETCLK-3-HOLDOVER: Entering Holdover for Controller E1 0/3/0

bri-rtr00 Sep  3 04:04:09 2013 83515: Sep  3 06:04:08 AET: %ISDN-6-LAYER2UP: Layer 2 for Interface Se0/3/0:15, TEI 0 changed to up

bri-rtr00 Sep  3 04:04:12 2013 83516: Sep  3 06:04:10 AET: %MARS_NETCLK-3-HOLDOVER: Exiting Holdover for Controller E1 0/3/0

bri-rtr00 Sep  5 09:45:54 2013 84097: .Sep  5 11:45:53 AET: %CONTROLLER-5-UPDOWN: Controller E1 0/3/0, changed state to down (RAI detected)

bri-rtr00 Sep  5 09:45:54 2013 84098: .Sep  5 11:45:53 AET: %ISDN-6-LAYER2DOWN: Layer 2 for Interface Se0/3/0:15, TEI 0 changed to down

bri-rtr00 Sep  5 09:45:55 2013 84099: .Sep  5 11:45:53 AET: %MARS_NETCLK-3-HOLDOVER: Entering Holdover for Controller E1 0/3/0

bri-rtr00 Sep  5 09:46:05 2013 84101: .Sep  5 11:46:03 AET: %MARS_NETCLK-3-HOLDOVER_TRANS: Holdover timer exceeded for Controller E1 0/3/0

bri-rtr00 Sep  5 09:46:05 2013 84102: .Sep  5 11:46:03 AET: %MARS_NETCLK-3-CLK_TRANS: Network clock source transitioned from priority 1 to priority 10

bri-rtr00 Sep  5 09:46:40 2013 84104: .Sep  5 11:46:38 AET: %ISDN-6-LAYER2UP: Layer 2 for Interface Se0/3/0:15, TEI 0 changed to up

bri-rtr00 Sep  5 09:46:40 2013 84105: .Sep  5 11:46:38 AET: %ISDN-6-LAYER2DOWN: Layer 2 for Interface Se0/3/0:15, TEI 0 changed to down

bri-rtr00 Sep  5 09:46:45 2013 84107: .Sep  5 11:46:43 AET: %ISDN-6-LAYER2UP: Layer 2 for Interface Se0/3/0:15, TEI 0 changed to up

bri-rtr00 Sep  5 09:46:48 2013 84108: .Sep  5 11:46:47 AET: %CONTROLLER-5-UPDOWN: Controller E1 0/3/0, changed state to down (RAI detected)

bri-rtr00 Sep  5 09:46:49 2013 84109: .Sep  5 11:46:47 AET: %ISDN-6-LAYER2DOWN: Layer 2 for Interface Se0/3/0:15, TEI 0 changed to down

bri-rtr00 Sep  5 09:47:32 2013 84113: .Sep  5 11:47:30 AET: %MARS_NETCLK-3-CLK_TRANS: Network clock source transitioned from priority 10 to priority 1

bri-rtr00 Sep  5 09:47:33 2013 84114: .Sep  5 11:47:31 AET: %ISDN-6-LAYER2UP: Layer 2 for Interface Se0/3/0:15, TEI 0 changed to up

bri-rtr00 Sep  5 09:49:53 2013 84115: .Sep  5 11:49:52 AET: %CONTROLLER-5-UPDOWN: Controller E1 0/3/0, changed state to down (RAI detected)

bri-rtr00 Sep  5 09:49:53 2013 84116: .Sep  5 11:49:52 AET: %ISDN-6-LAYER2DOWN: Layer 2 for Interface Se0/3/0:15, TEI 0 changed to down

bri-rtr00 Sep  5 09:49:54 2013 84117: .Sep  5 11:49:52 AET: %MARS_NETCLK-3-HOLDOVER: Entering Holdover for Controller E1 0/3/0

bri-rtr00 Sep  5 09:50:04 2013 84119: .Sep  5 11:50:02 AET: %MARS_NETCLK-3-HOLDOVER_TRANS: Holdover timer exceeded for Controller E1 0/3/0

bri-rtr00 Sep  5 09:50:04 2013 84120: .Sep  5 11:50:02 AET: %MARS_NETCLK-3-CLK_TRANS: Network clock source transitioned from priority 1 to priority 10

bri-rtr00 Sep  5 09:50:39 2013 84122: .Sep  5 11:50:37 AET: %ISDN-6-LAYER2UP: Layer 2 for Interface Se0/3/0:15, TEI 0 changed to up

bri-rtr00 Sep  5 09:50:49 2013 84124: .Sep  5 11:50:47 AET: %MARS_NETCLK-3-CLK_TRANS: Network clock source transitioned from priority 10 to priority 1

bri-rtr00 Sep  5 13:57:42 2013 84259: .Sep  5 15:57:41 AET: %CONTROLLER-5-UPDOWN: Controller E1 0/3/0, changed state to down (RAI detected)

bri-rtr00 Sep  5 13:57:42 2013 84260: .Sep  5 15:57:41 AET: %ISDN-6-LAYER2DOWN: Layer 2 for Interface Se0/3/0:15, TEI 0 changed to down

bri-rtr00 Sep  5 13:57:43 2013 84261: .Sep  5 15:57:41 AET: %MARS_NETCLK-3-HOLDOVER: Entering Holdover for Controller E1 0/3/0

bri-rtr00 Sep  5 13:57:53 2013 84263: .Sep  5 15:57:52 AET: %MARS_NETCLK-3-HOLDOVER_TRANS: Holdover timer exceeded for Controller E1 0/3/0

bri-rtr00 Sep  5 13:57:53 2013 84264: .Sep  5 15:57:52 AET: %MARS_NETCLK-3-CLK_TRANS: Network clock source transitioned from priority 1 to priority 10

bri-rtr00 Sep  5 13:59:32 2013 84266: .Sep  5 15:59:30 AET: %ISDN-6-LAYER2UP: Layer 2 for Interface Se0/3/0:15, TEI 0 changed to up

bri-rtr00 Sep  5 13:59:42 2013 84268: .Sep  5 15:59:41 AET: %MARS_NETCLK-3-CLK_TRANS: Network clock source transitioned from priority 10 to priority 1

bri-rtr00 Sep  5 14:10:22 2013 84269: .Sep  5 16:10:21 AET: %CONTROLLER-5-UPDOWN: Controller E1 0/3/0, changed state to down (RAI detected)

bri-rtr00 Sep  5 14:10:22 2013 84270: .Sep  5 16:10:21 AET: %ISDN-6-LAYER2DOWN: Layer 2 for Interface Se0/3/0:15, TEI 0 changed to down

bri-rtr00 Sep  5 14:10:23 2013 84271: .Sep  5 16:10:21 AET: %MARS_NETCLK-3-HOLDOVER: Entering Holdover for Controller E1 0/3/0

bri-rtr00 Sep  5 14:10:33 2013 84273: .Sep  5 16:10:32 AET: %MARS_NETCLK-3-HOLDOVER_TRANS: Holdover timer exceeded for Controller E1 0/3/0

bri-rtr00 Sep  5 14:10:33 2013 84274: .Sep  5 16:10:32 AET: %MARS_NETCLK-3-CLK_TRANS: Network clock source transitioned from priority 1 to priority 10

bri-rtr00 Sep  5 14:11:09 2013 84276: .Sep  5 16:11:07 AET: %ISDN-6-LAYER2UP: Layer 2 for Interface Se0/3/0:15, TEI 0 changed to up

bri-rtr00 Sep  5 14:11:18 2013 84278: .Sep  5 16:11:17 AET: %MARS_NETCLK-3-CLK_TRANS: Network clock source transitioned from priority 10 to priority 1

bri-rtr00 Sep  5 14:12:55 2013 84279: .Sep  5 16:12:54 AET: %CONTROLLER-5-UPDOWN: Controller E1 0/3/0, changed state to down (RAI detected)

bri-rtr00 Sep  5 14:12:55 2013 84280: .Sep  5 16:12:54 AET: %ISDN-6-LAYER2DOWN: Layer 2 for Interface Se0/3/0:15, TEI 0 changed to down

bri-rtr00 Sep  5 14:12:56 2013 84281: .Sep  5 16:12:54 AET: %MARS_NETCLK-3-HOLDOVER: Entering Holdover for Controller E1 0/3/0

bri-rtr00 Sep  5 14:13:06 2013 84283: .Sep  5 16:13:05 AET: %MARS_NETCLK-3-HOLDOVER_TRANS: Holdover timer exceeded for Controller E1 0/3/0

bri-rtr00 Sep  5 14:13:06 2013 84284: .Sep  5 16:13:05 AET: %MARS_NETCLK-3-CLK_TRANS: Network clock source transitioned from priority 1 to priority 10

bri-rtr00 Sep  5 14:18:08 2013 84286: .Sep  5 16:18:06 AET: %CONTROLLER-5-UPDOWN: Controller E1 0/3/0, changed state to down (RAI detected)

bri-rtr00 Sep  5 14:18:11 2013 84290: .Sep  5 16:18:10 AET: %CONTROLLER-5-UPDOWN: Controller E1 0/3/0, changed state to down (LOF detected)

bri-rtr00 Sep  5 14:18:54 2013 84294: .Sep  5 16:18:52 AET: %ISDN-6-LAYER2UP: Layer 2 for Interface Se0/3/0:15, TEI 0 changed to up

bri-rtr00 Sep  5 14:19:04 2013 84296: .Sep  5 16:19:03 AET: %MARS_NETCLK-3-CLK_TRANS: Network clock source transitioned from priority 10 to priority 1

bri-rtr00 Sep  5 14:20:09 2013 84297: .Sep  5 16:20:08 AET: %CONTROLLER-5-UPDOWN: Controller E1 0/3/0, changed state to down (LOF detected)

bri-rtr00 Sep  5 14:20:09 2013 84298: .Sep  5 16:20:08 AET: %ISDN-6-LAYER2DOWN: Layer 2 for Interface Se0/3/0:15, TEI 0 changed to down

bri-rtr00 Sep  5 14:20:10 2013 84299: .Sep  5 16:20:08 AET: %MARS_NETCLK-3-HOLDOVER: Entering Holdover for Controller E1 0/3/0

bri-rtr00 Sep  5 14:20:20 2013 84301: .Sep  5 16:20:19 AET: %MARS_NETCLK-3-HOLDOVER_TRANS: Holdover timer exceeded for Controller E1 0/3/0

bri-rtr00 Sep  5 14:20:20 2013 84302: .Sep  5 16:20:19 AET: %MARS_NETCLK-3-CLK_TRANS: Network clock source transitioned from priority 1 to priority 10

bri-rtr00 Sep  5 14:21:25 2013 84304: .Sep  5 16:21:23 AET: %ISDN-6-LAYER2UP: Layer 2 for Interface Se0/3/0:15, TEI 0 changed to up

bri-rtr00 Sep  5 14:21:35 2013 84306: .Sep  5 16:21:34 AET: %MARS_NETCLK-3-CLK_TRANS: Network clock source transitioned from priority 10 to priority 1

CreatePlease to create content
Content for Community-Ad
August's Community Spotlight Awards