Launching soon: The world's first vendor agnostic bug scrubLearn more & join waitlist
OPERATIONAL DEFECT DATABASE
...
...
The MGCP process will remain in a Down state after the Router is back online from a reboot or power cycle. The following message is showing in the console logs while the Router is coming back online: %MGCP_APP-6-GEN_INIT_NO_IP_INTF_FAILED: Suspended initialization of MGCP services. No IP interface up yet After this message gets printed the MGCP process will not register with CUCM and remains in a Down state even when the IP Interfaces are in an UP state: Router#show ip interface brief | exc unassigned Interface IP-Address OK? Method Status Protocol GigabitEthernet0/0/0 x.x.x.x YES NVRAM up up Router#show ccm-manager Load for five secs: 46%/0%; one minute: 47%; five minutes: 41% MGCP Domain Name: Priority Status Host ============================================================ Primary Down x.x.x.x First Backup None Second Backup None
- ISR4300 Router platforms. - MGCP is configured without the "ccm-manager config" command. - "mgcp bind control source-interface [interface]" command is configured pointing to a physical interface or sub-interface - This only happens after a Reload or Power Cycle.
After the Router is online the following workarounds can be used: 1. Bounce the MGCP application: Router#configure terminal (config)#no mgcp (config)#mgcp 2. Enter "show running-config" command: Router#show running-config 3. shut / no shut the bound interfaces Router#configure terminal (Config)#interface [interface] (config-if)#shut (config-if)#no shut For a more permanent fix the following commands can be configured: (config)#ccm-manager config server [IP address or Domain name of XML configuration TFTP server] (config)#ccm-manager config The "ccm-manager config"command will force the Router to download the configuration file from CUCM hence reinitializing the MGCP process again after the physical interfaces are UP.
This issue has been identified to be affecting the ISR4300 platforms but it could potentially affect other platforms if the MGCP Application Process starts before the Physical Interfaces states are Up while booting up. The MGCP process will try to come up first before the bound interfaces are fully initialized in an UP state: 16:02:16.058: %MGCP_APP-6-GEN_INIT_NO_IP_INTF_FAILED: Suspended initialization of MGCP services. No IP interface up yet 16:02:27.263: %LINK-3-UPDOWN: Interface GigabitEthernet0/0/0, changed state to up In other platforms like ISR2900/3900 or ISR4400 the interfaces are initialized first and the %MGCP_APP-6-GEN_INIT_NO_IP_INTF_FAILED message is not shown.