/mcpError Message %UC_RTMT-3-AlertEmailNotifyFailure: %[FailureReason=String][AppID=String][ClusterID=String] [NodeID=String]: Alert Email Notification Failure.. Explanation Alert notification mechanism using e-mails has failed. Recommended Action Email notification of alerts failed due to a mis-configured SMTP Settings/SMTP server down. Check SMTP Server configuration and Examine the AMC service log files to determine the exact reason for failure. Error Message %UC_RTMT-3-ServiceabilityConnectivityInterruptions: %[AdditionalInformation=String][AppID=String] [ClusterID=String][NodeID=String]: Serviceability connectivity interruptions have been detected in the cluster. Explanation Connectivity interruptions have been detected in the cluster. These connectivity interruptions can result in generation of incorrect notifications and alerts. Recommended Action Connectivity interruptions have occurred because of underlying network issues. Communication streams between the ports involved needs to be analyzed to determine the exact cause of failure. The CLI command "utils network capture" or third-party tools can be used to capture the packet stream between the ports for analysis. Error Message %UC_CDRREP-3-CDRFileDeliveryFailed: %[BillingServerAddress=String][AppID=String] [ClusterID=String][NodeID=String]: (s)FTP delivery of CDR files to the outside billing server failed.. Explanation (s)FTP develiry of CDR files to the Billing Server outside of the cluster failed because of timeout or other reasons. Email alert will be sent to the admin. Recommended Action 1. Check network link status. 2. Check if billing server is alive. 3. Check if (s)FTP Server on the billing server is running and accepting request. 4. Check if CDRM Configuration is correct - under Serviceability->Tools. 5. check CDR Repository Manager trace. Error Message %UC_CDRREP-3-CDRAgentSendFileFailed: %[CDRRepositoryNodeAddress=String] [CDRAgentNodeAddress=String][AppID=String][ClusterID=String][NodeID=String]: CDR Agent cannot send CDR files from CCM node to CDR Repository node within the CCM cluster. Explanation CDR Agent cannot send CDR files from CCM node to CDR Repository node within the cluster because of timeout or other reasons. Email alert will be sent to the admin. Recommended Action 1. Check network link status. 2. Check if CDR Repository node (first node in the cluster) is alive. 3. Check if CDR Repository Manager is activated on the first node. 4. Check CDRM Configuration under Serviceability->Tools. 5. Check CDR Agent trace on the specific node where error occurred. 6. Check CDR Repository Manager trace. 7. Check if the Publisher is being upgraded. If the CDRAgentSendFileFailureContinues alarm is no longer present, the condition is corrected. Error Message %UC_CDRREP-4-CDRHWMExceeded: %[DiskUsageInMB=String][AppID=String][ClusterID=String] [NodeID=String]: High Water Mark for CDR files reached, some successfully delivered CDR files have been deleted. Explanation The CDR files disk usage has exceeded the High Water Mark. CDRM deleted some successfully delivered CDR files that are still within the preservation duration, in order to bring the disk 5/24/26, 3:34 AM System Error Messages for Cisco Unified Communications Manager 15 - Cisco https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/err_msgs/15_x/ccmalarms15.html 88/343