OPERATIONAL DEFECT DATABASE
...
...
- MGCP GW keeps sending TFTP pull requests for a deleted port - TFTP download error counter is increased in the GW Configuration Download statistics: Download Attempted : 3 Download Successful : 2 Download Failed : 0 TFTP Download Failed : 2. ------>>>> Issue Configuration Attempted : 2 Configuration Successful : 2 Configuration Failed(Parsing): 0 From the logs: May 15 20:16:26.799: cmapp_xml_cfg_chg_msg: RESET May 15 20:16:26.799: cmapp_xml_send_msg_to_cmapp: ep_name = AALN/S0/SU1/0@ISR4351-PRAVI.cisco.com, msg = 0 May 15 20:16:26.799: cmapp_xml_find_ep_by_name: Checking for ep_name [AALN/S0/SU1/0@ISR4351-PRAVI.cisco.com] May 15 20:16:26.799: cmapp_xml_process_xml_event: ev_id = 0 May 15 20:16:26.800: cmapp_xml_init_ep: May 15 20:16:26.800: cmapp_xml_exec_fsm: Endpoint is [AALN/S0/SU1/0@ISR4351-PRAVI.cisco.com] May 15 20:16:26.800: cmapp_xml_exec_fsm: endpoint = AALN/S0/SU1/0@ISR4351-PRAVI.cisco.com state = CMAPP_XML_IDLE, event = CMAPP_XML_EVT_RESET_GW May 15 20:16:26.800: cmapp_xml_process_reset: state = CMAPP_XML_IDLE, event = CMAPP_XML_EVT_RESET_GW
- MGCP between GW and CUCM - User deletes a port from the CUCM
None
As per the current design, CUCM sends "RESET" event whenever an MGCP port is deleted. This happens without clicking on "apply config" . As a result of this, the GW resets the port and tries to download the fresh xml config from CUCM. Those TFTP pull requests fail because the port was already deleted in CUCM and this goes on in a loop.
Click on a version to see all relevant bugs
Cisco Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.
