Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

New Member

MGCP PRI - UpDown logs difference between Telco Issue and Network issue

Hi,

Setup is remote site MGCP Gateway and CUCM is on HQ. I'm suspecting the below logs and what caused its flap but not 100% sure, is this correct?

Logs caused by connection to Telco

021987: Jan 14 18:15:45.708: %CONTROLLER-5-UPDOWN: Controller E1 0/3/0, changed state to down (AIS detected)

021988: Jan 14 18:15:45.712: %CONTROLLER-5-UPDOWN: Controller E1 0/3/1, changed state to down (AIS detected)

021989: Jan 14 18:15:46.692: %CONTROLLER-5-UPDOWN: Controller E1 0/2/0, changed state to down (AIS detected)

021990: Jan 14 18:15:46.692: %CONTROLLER-5-UPDOWN: Controller E1 0/2/1, changed state to down (AIS detected)

021991: Jan 14 18:15:46.692: %CONTROLLER-5-UPDOWN: Controller E1 0/2/2, changed state to down (AIS detected)

021992: Jan 14 18:15:46.696: %CONTROLLER-5-UPDOWN: Controller E1 0/2/3, changed state to down (AIS detected)

021993: Jan 14 18:15:46.912: %MARS_NETCLK-3-HOLDOVER: Entering Holdover for Controller E1 0/2/0

021994: Jan 14 18:15:47.708: %LINK-3-UPDOWN: Interface Serial0/3/0:15, changed state to down

021995: Jan 14 18:15:47.712: %LINK-3-UPDOWN: Interface Serial0/3/1:15, changed state to down

021996: Jan 14 18:15:48.692: %LINK-3-UPDOWN: Interface Serial0/2/1:15, changed state to down

021997: Jan 14 18:15:48.696: %LINK-3-UPDOWN: Interface Serial0/2/2:15, changed state to down

021998: Jan 14 18:15:48.696: %LINK-3-UPDOWN: Interface Serial0/2/3:15, changed state to down

021999: Jan 14 18:15:49.692: %CONTROLLER-5-UPDOWN: Controller E1 0/2/0, changed state to up

022000: Jan 14 18:15:49.700: %CONTROLLER-5-UPDOWN: Controller E1 0/2/1, changed state to up

022001: Jan 14 18:15:49.708: %CONTROLLER-5-UPDOWN: Controller E1 0/2/3, changed state to up

022002: Jan 14 18:15:51.700: %LINK-3-UPDOWN: Interface Serial0/2/1:15, changed state to up

022003: Jan 14 18:15:51.708: %LINK-3-UPDOWN: Interface Serial0/2/3:15, changed state to up

022004: Jan 14 18:15:52.164: %MARS_NETCLK-3-HOLDOVER: Exiting Holdover for Controller E1 0/2/0

022005: Jan 14 18:15:53.692: %CONTROLLER-5-UPDOWN: Controller E1 0/2/2, changed state to up

022006: Jan 14 18:15:53.708: %CONTROLLER-5-UPDOWN: Controller E1 0/3/0, changed state to up

022007: Jan 14 18:15:53.716: %CONTROLLER-5-UPDOWN: Controller E1 0/3/1, changed state to up

022008: Jan 14 18:15:55.692: %LINK-3-UPDOWN: Interface Serial0/2/2:15, changed state to up

022009: Jan 14 18:15:55.708: %LINK-3-UPDOWN: Interface Serial0/3/0:15, changed state to up

022010: Jan 14 18:15:55.716: %LINK-3-UPDOWN: Interface Serial0/3/1:15, changed state to up

Logs caused by network connectivity issue between CUCM and MGCP Gateway

021869: Jan  7 10:05:00.763: %LINK-5-CHANGED: Interface Serial0/2/2:15, changed state to administratively down

021870: Jan  7 10:05:01.371: %SYS-5-CONFIG_I: Configured from console by console

021871: Jan  7 10:05:02.575: %SYS-5-CONFIG_I: Configured from console by console

021872: Jan  7 10:05:02.667: %LINK-5-CHANGED: Interface Serial0/2/3:15, changed state to administratively down

021873: Jan  7 10:05:03.275: %SYS-5-CONFIG_I: Configured from console by console

021874: Jan  7 10:05:04.479: %SYS-5-CONFIG_I: Configured from console by console

021875: Jan  7 10:05:04.571: %LINK-5-CHANGED: Interface Serial0/3/0:15, changed state to administratively down

021876: Jan  7 10:05:05.179: %SYS-5-CONFIG_I: Configured from console by console

021877: Jan  7 10:05:06.475: %LINK-5-CHANGED: Interface Serial0/3/1:15, changed state to administratively down

021878: Jan  7 10:05:08.391: %SYS-5-CONFIG_I: Configured from console by console

021879: Jan  7 10:05:09.603: %SYS-5-CONFIG_I: Configured from console by console

021880: Jan  7 10:05:10.815: %SYS-5-CONFIG_I: Configured from console by console

021881: Jan  7 10:05:11.591: %LINK-3-UPDOWN: Interface Serial0/2/1:15, changed state to up

021882: Jan  7 10:05:12.027: %SYS-5-CONFIG_I: Configured from console by console

021883: Jan  7 10:05:12.803: %LINK-3-UPDOWN: Interface Serial0/2/2:15, changed state to up

021884: Jan  7 10:05:13.239: %SYS-5-CONFIG_I: Configured from console by console

021885: Jan  7 10:05:14.015: %LINK-3-UPDOWN: Interface Serial0/2/3:15, changed state to up

021886: Jan  7 10:05:14.451: %SYS-5-CONFIG_I: Configured from console by console

021887: Jan  7 10:05:15.227: %LINK-3-UPDOWN: Interface Serial0/3/0:15, changed state to up

021888: Jan  7 10:05:16.439: %LINK-3-UPDOWN: Interface Serial0/3/1:15, changed state to up

021889: Jan  7 10:05:39.379: %SYS-5-CONFIG_I: Configured from console by console

021890: Jan  7 10:05:40.079: %SYS-5-CONFIG_I: Configured from console by console

021891: Jan  7 10:05:41.783: %SYS-5-CONFIG_I: Configured from console by console

021892: Jan  7 10:05:42.483: %SYS-5-CONFIG_I: Configured from console by console

021893: Jan  7 10:05:43.779: %LINK-5-CHANGED: Interface Serial0/2/1:15, changed state to administratively down

021894: Jan  7 10:05:44.187: %SYS-5-CONFIG_I: Configured from console by console

021895: Jan  7 10:05:44.887: %SYS-5-CONFIG_I: Configured from console by console

021896: Jan  7 10:05:46.183: %LINK-5-CHANGED: Interface Serial0/2/2:15, changed state to administratively down

021897: Jan  7 10:05:46.591: %SYS-5-CONFIG_I: Configured from console by console

021898: Jan  7 10:05:47.291: %SYS-5-CONFIG_I: Configured from console by console

021899: Jan  7 10:05:48.587: %LINK-5-CHANGED: Interface Serial0/2/3:15, changed state to administratively down

021900: Jan  7 10:05:48.995: %SYS-5-CONFIG_I: Configured from console by console

021901: Jan  7 10:05:49.695: %SYS-5-CONFIG_I: Configured from console by console

021902: Jan  7 10:05:50.991: %LINK-5-CHANGED: Interface Serial0/3/0:15, changed state to administratively down

021903: Jan  7 10:05:51.399: %SYS-5-CONFIG_I: Configured from console by console

021904: Jan  7 10:05:52.099: %SYS-5-CONFIG_I: Configured from console by console

021905: Jan  7 10:05:53.395: %LINK-5-CHANGED: Interface Serial0/3/1:15, changed state to administratively down

021906: Jan  7 10:05:55.811: %SYS-5-CONFIG_I: Configured from console by console

021907: Jan  7 10:05:57.023: %SYS-5-CONFIG_I: Configured from console by console

021908: Jan  7 10:05:58.235: %SYS-5-CONFIG_I: Configured from console by console

021909: Jan  7 10:05:59.011: %LINK-3-UPDOWN: Interface Serial0/2/1:15, changed state to up

021910: Jan  7 10:05:59.447: %SYS-5-CONFIG_I: Configured from console by console

021911: Jan  7 10:06:00.223: %LINK-3-UPDOWN: Interface Serial0/2/2:15, changed state to up

021912: Jan  7 10:06:00.659: %SYS-5-CONFIG_I: Configured from console by console

021913: Jan  7 10:06:01.435: %LINK-3-UPDOWN: Interface Serial0/2/3:15, changed state to up

021914: Jan  7 10:06:01.871: %SYS-5-CONFIG_I: Configured from console by console

021915: Jan  7 10:06:02.647: %LINK-3-UPDOWN: Interface Serial0/3/0:15, changed state to up

021916: Jan  7 10:06:03.859: %LINK-3-UPDOWN: Interface Serial0/3/1:15, changed state to up

thanks in advance!!

6 REPLIES

MGCP PRI - UpDown logs difference between Telco Issue and Networ

give us the sh controller e1 output as well please.

Voice CCIE #37771
New Member

MGCP PRI - UpDown logs difference between Telco Issue and Networ

Here it is.. what is it you're looking for? i'm suspecting the above difference between %LINK-5-CHANGED (network issue) vs %LINK-3-UPDOWN (telco issue)

E1 0/2/0 is up.

  Applique type is Channelized E1 - balanced

  Description:

  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 Line.

  International Bit: 1, National Bits: 11111

  Data in current interval (71 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, 330 Path Code Violations,

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

     7 Errored Secs, 5 Bursty Err Secs, 2 Severely Err Secs, 2147417995 Unavail Secs

E1 0/2/1 is up.

  Applique type is Channelized E1 - balanced

  Description:

  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 Line.

  International Bit: 1, National Bits: 11111

  Data in current interval (72 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, 314 Path Code Violations,

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

     8 Errored Secs, 6 Bursty Err Secs, 2 Severely Err Secs, 2147418015 Unavail Secs

E1 0/2/2 is up.

  Applique type is Channelized E1 - balanced

  Description:

  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 Line.

  International Bit: 1, National Bits: 11111

  Data in current interval (75 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, 344 Path Code Violations,

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

     16 Errored Secs, 4 Bursty Err Secs, 5 Severely Err Secs, 2147418015 Unavail Secs

E1 0/2/3 is up.

  Applique type is Channelized E1 - balanced

  Description:

  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 Line.

  International Bit: 1, National Bits: 11111

  Data in current interval (103 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, 448 Path Code Violations,

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

     7 Errored Secs, 5 Bursty Err Secs, 2 Severely Err Secs, 2147418002 Unavail Secs

E1 0/3/0 is up.

  Applique type is Channelized E1 - balanced

  Description:

  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 Line.

  International Bit: 1, National Bits: 11111

  Data in current interval (104 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, 299 Path Code Violations,

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

     11 Errored Secs, 5 Bursty Err Secs, 0 Severely Err Secs, 2147418017 Unavail Secs

MGCP PRI - UpDown logs difference between Telco Issue and Networ

have a look at the following discussion maybe it can help you with your issue.

http://www.voiceie.com/cgi-bin/ultimatebb.cgi?ubb=print_topic;f=8;t=001319

Default MGCP Config Template I use:

network-clock-participate wic 2

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

isdn switch-type primary-net5

controller E1 0/2/0

pri-group timeslots 1-6,16 service mgcp

interface Serial0/2/0:15

no ip address

encapsulation hdlc

isdn switch-type primary-net5

isdn incoming-voice voice

isdn bind-l3 ccm-manager

isdn outgoing display-ie

no cdp enable

ccm-manager fallback-mgcp

ccm-manager redundant-host 172.22.102.101

ccm-manager mgcp

ccm-manager fax protocol cisco

ccm-manager music-on-hold

!

mgcp

mgcp call-agent 172.22.102.102 service-type mgcp version 0.1

mgcp dtmf-relay voip codec all mode out-of-band

mgcp ip qos dscp cs3 signaling

mgcp sdp simple

mgcp fax t38 ecm

mgcp bind control source-interface Vlan132

mgcp bind media source-interface Vlan132

!

mgcp profile default

  ccm-manager fallback-mgcp
ccm-manager redundant-host 172.22.102.101
ccm-manager mgcp
ccm-manager fax protocol cisco
ccm-manager music-on-hold
!

Voice CCIE #37771
New Member

MGCP PRI - UpDown logs difference between Telco Issue and Networ

Thanks but the question is just how to identify updown logs that's triggered by PSTN carrier and updown logs triggered by network issue considering gateway runs on MGCP connection.

Any ideas??

MGCP PRI - UpDown logs difference between Telco Issue and Networ

Mate, 

if you see your E1 controller  clocking up Alarm interrupted seconds (AIS), the it is either calbling from your E1 port to the MDF and or a Telco issue. Dont waste too much time on it, book it out to your provider.

the second part of your log; administratively shutdown: yes cause by someone logging onto the box and doing for instance a shut no shut.  or  restarting the port from the CUCM admin pages.



=============================
Please remember to rate useful posts, by clicking on the stars below. 

=============================

Please remember to rate useful posts, by clicking on the stars below.

New Member

MGCP PRI - UpDown logs difference between Telco Issue and Networ

thanks Dennis, One last question for the admin caused logs, could it also be caused by network outage and causing the mgcp pri to switch to h323?

935
Views
0
Helpful
6
Replies
CreatePlease login to create content