Solved

e1 automatic restart

Posted on 2010-11-25
1
946 Views
Last Modified: 2012-05-10
*Nov 22 22:36:59.799 UTC: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/2/0:0, changed state to down
*Nov 22 22:36:59.811 UTC: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/2/0:1, changed state to down
*Nov 22 22:36:59.811 UTC: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/2/0:2, changed state to down
*Nov 22 22:36:59.811 UTC: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/2/0:3, changed state to down
*Nov 22 22:36:59.811 UTC: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/2/0:4, changed state to down
*Nov 22 22:36:59.811 UTC: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/2/0:5, changed state to down
*Nov 22 22:36:59.811 UTC: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/2/0:6, changed state to down
*Nov 22 22:36:59.811 UTC: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/2/0:7, changed state to down
*Nov 22 22:36:59.811 UTC: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/2/0:8, changed state to down
*Nov 22 22:36:59.811 UTC: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/2/0:9, changed state to down
*Nov 22 22:36:59.811 UTC: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/2/0:10, changed state to down
*Nov 22 22:36:59.811 UTC: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/2/0:11, changed state to down
*Nov 22 22:36:59.811 UTC: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/2/0:12, changed state to down
*Nov 22 22:36:59.811 UTC: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/2/0:13, changed state to down
*Nov 22 22:36:59.815 UTC: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/2/0:14, changed state to down
*Nov 22 22:36:59.815 UTC: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/2/0:16, changed state to down
*Nov 22 22:36:59.815 UTC: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/2/0:17, changed state to down
*Nov 22 22:36:59.815 UTC: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/2/0:18, changed state to down
*Nov 22 22:36:59.815 UTC: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/2/0:19, changed state to down
*Nov 22 22:36:59.819 UTC: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/2/0:20, changed state to down
*Nov 22 22:36:59.819 UTC: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/2/0:21, changed state to down
*Nov 22 22:36:59.819 UTC: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/2/0:22, changed state to down
*Nov 22 22:36:59.819 UTC: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/2/0:23, changed state to down
*Nov 22 22:36:59.827 UTC: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/2/0:24, changed state to down
*Nov 22 22:36:59.827 UTC: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/2/0:25, changed state to down
*Nov 22 22:36:59.827 UTC: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/2/0:26, changed state to down
*Nov 22 22:36:59.827 UTC: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/2/0:27, changed state to down
*Nov 22 22:36:59.827 UTC: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/2/0:28, changed state to down
*Nov 22 22:36:59.827 UTC: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/2/0:29, changed state to down
*Nov 22 22:36:59.827 UTC: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/2/0:30, changed state to down
*Nov 22 22:36:59.827 UTC: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/2/0:15, changed state to down
*Nov 22 22:37:02.743 UTC: %LINK-3-UPDOWN: Interface 0/2/0:15(1), changed state to up
*Nov 22 22:37:02.743 UTC: %LINK-3-UPDOWN: Interface 0/2/0:15(2), changed state to up
*Nov 22 22:37:02.743 UTC: %LINK-3-UPDOWN: Interface 0/2/0:15(3), changed state to up
*Nov 22 22:37:02.743 UTC: %LINK-3-UPDOWN: Interface 0/2/0:15(4), changed state to up
*Nov 22 22:37:02.743 UTC: %LINK-3-UPDOWN: Interface 0/2/0:15(5), changed state to up
*Nov 22 22:37:02.743 UTC: %LINK-3-UPDOWN: Interface 0/2/0:15(6), changed state to up
*Nov 22 22:37:02.743 UTC: %LINK-3-UPDOWN: Interface 0/2/0:15(7), changed state to up
*Nov 22 22:37:02.743 UTC: %LINK-3-UPDOWN: Interface 0/2/0:15(8), changed state to up
*Nov 22 22:37:02.743 UTC: %LINK-3-UPDOWN: Interface 0/2/0:15(9), changed state to up
*Nov 22 22:37:02.743 UTC: %LINK-3-UPDOWN: Interface 0/2/0:15(10), changed state to up
*Nov 22 22:37:02.747 UTC: %LINK-3-UPDOWN: Interface 0/2/0:15(11), changed state to up
*Nov 22 22:37:02.747 UTC: %LINK-3-UPDOWN: Interface 0/2/0:15(12), changed state to up
*Nov 22 22:37:02.747 UTC: %LINK-3-UPDOWN: Interface 0/2/0:15(13), changed state to up
*Nov 22 22:37:02.747 UTC: %LINK-3-UPDOWN: Interface 0/2/0:15(14), changed state to up
*Nov 22 22:37:02.747 UTC: %LINK-3-UPDOWN: Interface 0/2/0:15(15), changed state to up
*Nov 22 22:37:02.747 UTC: %LINK-3-UPDOWN: Interface 0/2/0:15(17), changed state to up
*Nov 22 22:37:02.747 UTC: %LINK-3-UPDOWN: Interface 0/2/0:15(18), changed state to up
*Nov 22 22:37:02.747 UTC: %LINK-3-UPDOWN: Interface 0/2/0:15(19), changed state to up
*Nov 22 22:37:02.747 UTC: %LINK-3-UPDOWN: Interface 0/2/0:15(20), changed state to up
*Nov 22 22:37:02.747 UTC: %LINK-3-UPDOWN: Interface 0/2/0:15(21), changed state to up
*Nov 22 22:37:02.747 UTC: %LINK-3-UPDOWN: Interface 0/2/0:15(22), changed state to up
*Nov 22 22:37:02.747 UTC: %LINK-3-UPDOWN: Interface 0/2/0:15(23), changed state to up
*Nov 22 22:37:02.747 UTC: %LINK-3-UPDOWN: Interface 0/2/0:15(24), changed state to up
*Nov 22 22:37:02.747 UTC: %LINK-3-UPDOWN: Interface 0/2/0:15(25), changed state to up
*Nov 22 22:37:02.747 UTC: %LINK-3-UPDOWN: Interface 0/2/0:15(26), changed state to up
*Nov 22 22:37:02.747 UTC: %LINK-3-UPDOWN: Interface 0/2/0:15(27), changed state to up
*Nov 22 22:37:02.747 UTC: %LINK-3-UPDOWN: Interface 0/2/0:15(28), changed state to up
*Nov 22 22:37:02.747 UTC: %LINK-3-UPDOWN: Interface 0/2/0:15(29), changed state to up
*Nov 22 22:37:02.747 UTC: %LINK-3-UPDOWN: Interface 0/2/0:15(30), changed state to up
*Nov 22 22:37:02.747 UTC: %LINK-3-UPDOWN: Interface 0/2/0:15(31), changed state to up
*Nov 22 22:37:03.707 UTC: %CMAPP-6-CONFIG_DONE: Configuration by CCM is done


I'm getting these messages in logs of one of my device where an E1 (in an mgcp gateway) automatically restarts. It shows in the end that 'configuration by ccm is done' indicating tht its done by users from call manager whereas its not actually done from call manager. is there something configured in call manager where it would automatically restart the E1 ?
0
Comment
Question by:nabeel92
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
1 Comment
 
LVL 10

Accepted Solution

by:
ampranti earned 500 total points
ID: 34217720
Are you doing changes to callmanager affecting that router? If yes, callmanager restart the interface (through MGCP protocol) to apply changes....

If happens randomly, then might be a problem with e1 (you have to call your provider to check it)
0

Featured Post

Microsoft Certification Exam 74-409

Veeam® is happy to provide the Microsoft community with a study guide prepared by MVP and MCT, Orin Thomas. This guide will take you through each of the exam objectives, helping you to prepare for and pass the examination.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

Title # Comments Views Activity
How do I allow multiple VLANs internet access on a Cisco ASA 5505? 8 78
Home internet speed 20 57
AS-Path BGP Attribute 7 44
Need to cut my Verizon home cost 3 67
Implementing Avaya's One-X portal is pretty painless, until you want to deploy this to the Android and iPhone clients when these clients are outside of your network. The clients will also work within your local network. Here is our experience and so…
In the world of WAN, QoS is a pretty important topic for most, if not all, networks. Some WAN technologies have QoS mechanisms built in, but others, such as some L2 WAN's, don't have QoS control in the provider cloud.
After creating this article (http://www.experts-exchange.com/articles/23699/Setup-Mikrotik-routers-with-OSPF.html), I decided to make a video (no audio) to show you how to configure the routers and run some trace routes and pings between the 7 sites…
After creating this article (http://www.experts-exchange.com/articles/23699/Setup-Mikrotik-routers-with-OSPF.html), I decided to make a video (no audio) to show you how to configure the routers and run some trace routes and pings between the 7 sites…

752 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question