Guest

Cisco Unified Communications Manager IM & Presence Service

System Error Messages for Cisco Unified Presence Release 8.5

Error Message:
CUP_REPL-GENERIC-4-ReplicationFailure: Cisco UP Replication Watcher detected replication failure
Explantion:
Cisco UP Replication Watcher has detected database replication failure on this node. If this node is currently starting, some services will be prevented from starting until replication is established.
Recommended Action:
Please check Cisco UP Replication Watcher logs for details. Replication status can be manually checked via the command line interface.

Error Message:
CUP_REPL-GENERIC-4-ReplicationFailureClear: Cisco UP Replication Watcher detected that replication has been successfully established on this node.
Explantion:
Cisco UP Replication Watcher has detected that replication has been successfully established on this node.
Recommended Action:
No action required. See Cisco UP Replication Watcher logs for details.

Error Message:
CUP_REPL-GENERIC-4-ReplicationFailureTimeout: Cisco UP Replication Watcher startup timeout. Cisco UP Replication Watcher is allowing services to continue startup although replication has not completed setup on this publisher node.
Explantion:
Cisco UP Replication Watcher startup timeout. Cisco UP Replication Watcher is allowing services to continue startup although replication has not completed setup on this publisher node.
Recommended Action:
Please check Cisco UP Replication Watcher logs for details. Replication status can be manually checked via the command line interface.

Error Message:
CCM_CALLMANAGER-GENERIC-0-OutOfMemory: Out of memory.
Explantion:
The process has requested memory from the operating system, and there was not enough memory available.
Recommended Action:
No action is required.

Error Message:
CCM_CALLMANAGER-GENERIC-6-PermissionDenied: Permission has been denied.
Explantion:
An operation could not be completed because the process did not have authority to perform it.
Recommended Action:
This alarm is for information purposes only; no action is required.

Error Message:
CCM_CALLMANAGER-GENERIC-0-ServiceNotInstalled: Service is not installed. ServiceName [String]
Explantion:
An executable is trying to start but cannot because it is not configured as a service in the service control manager. The service name is %s.
Recommended Action:
Reinstall the service.

Error Message:
CCM_CALLMANAGER-GENERIC-6-ServiceStopped: Service stopped. IPAddress [String] Hostname [String] ServiceName [String] ProcessID [ULong]
Explantion:
A service has stopped.
Recommended Action:
This alarm is for information purposes only; no action is required.

Error Message:
CCM_CALLMANAGER-GENERIC-6-ServiceStarted: Service started. IPAddress [String] IPV6Address [String] Hostname [String] ServiceName [String] VersionInfo [String] ProcessID [ULong]
Explantion:
A service has started.
Recommended Action:
This alarm is for information purposes only; no action is required.

Error Message:
CCM_CALLMANAGER-GENERIC-4-ServiceStartupFailed: Service startup failure. ServiceName [String]
Explantion:
An attempt to start the specified service failed.
Recommended Action:
Restart the service.

Error Message:
CCM_CALLMANAGER-GENERIC-0-FileWriteError: Cannot write into a file. PrimaryFilePath [String]
Explantion:
Failed to write into the primary file path.
Recommended Action:
Ensure that the primary file path is valid and the corresponding drive has sufficient disk space. Also, make sure that the path has security permissions similar to default log file path.

Error Message:
CUP_XCPCFG-GENERIC-4-CUPICSAXMLQueueAtWarningLevel: Cisco UP XCP Config Manager buffer has reached warning levels.
Explantion:
Cisco UP XCP Config Manager buffer has reached warning levels.
Recommended Action:
Halt configuration changes until Manager buffer has fallen below warning levels.

Error Message:
CUP_XCPCFG-GENERIC-4-CUPICSAXMLQueueBelowWarningLevel: Cisco UP XCP Config Manager buffer has fallen below warning levels.
Explantion:
Cisco UP XCP Config Manager buffer has fallen below warning levels.
Recommended Action:
System administrator may continue configuration of system.

Error Message:
CUP_XCPCFG-GENERIC-2-CUPICSAXMLQueueAtCriticalLevel: Cisco UP XCP Config Manager buffer has reached critical levels. System will halt until configuration stabilizes, then regenerate all files. Jabber will need to be restarted to become aware of these changes.
Explantion:
Cisco UP XCP Config Manager buffer has reached critical levels. System will halt until configuration stabilizes, then regenerate all files. Jabber will need to be restarted to become aware of these changes .
Recommended Action:
Restart Jabber once alarm is sent that configuration has been regnerated successfully.

Error Message:
CUP_XCPCFG-GENERIC-2-CUPICSAXMLJabberRestartRequired: Cisco UP XCP Config Manager has regenerated JabberXML files after system halt due to buffer size. Jabber must now be restarted to pick up changes.
Explantion:
Cisco UP XCP Config Manager buffer has regenerated JabberXML files after system halt due to buffer size. Jabber must now be restarted to pick up changes .
Recommended Action:
Restart Jabber.

Error Message:
CUP_XCPCFG-GENERIC-2-CUPICSAXMLCONFIGURATIONFAILURE: Cisco UP XCP Config Manager was unable to send configuration to a component. Please check logs. realm [String] component [String]
Explantion:
Cisco UP XCP Config Manager failed to successfully update XCP Configuration.
Recommended Action:
See Inter Cluster Sync Agent logs for further root cause.

Error Message:
CUP_XCPCFG-GENERIC-2-CUPXCPCONFIGMGRHostNameResolutionFailed: CUP XCP Config manager hostname resolution failed hostname [String]
Explantion:
Cisco UP XCP Config Manager could not resolve a DNS name to allow XCP Routers to connect to that node.
Recommended Action:
Please verify DNS resolvability of all Hostnames and FQDNs in both local and remote clusters. Restart XCP Config Manager then XCP Router after DNS is resolvable.

Error Message:
CCM_TOMCAT_APPS-LOGIN-4-AuthenticationFailed: Login Authentication failed. LoginFrom [String] TimeStamp [String] UserID [String] Interface [String]
Explantion:
Authentication failure for login attempt is detected.
Recommended Action:
If this event happens repeatedly, investigate the source of the failed login attempts.

Error Message:
CCM_TOMCAT_APPS-LOGIN-6-AuthenticationSucceeded: Login Authentication succeeded. LoginFrom [String] TimeStamp [String] UserID [String] Interface [String]
Explantion:
Authentication success for login attempt is detected.
Recommended Action:
If this event is expected, no action is required; otherwise, notify the administrator.

Error Message:
CUP_SIPD-GENERIC-6-ESPStarted: Cisco UP SIP Proxy service child process has been started Version [String]
Explantion:
Cisco UP SIP Proxy service child process has started successfully
Recommended Action:
Notification purposes only; no action is required

Error Message:
CUP_SIPD-GENERIC-0-ESPNoSWVersionLicense: Cisco Unified Presence SIP Proxy: failed to start
Explantion:
Cisco Unified Presence SIP Proxy: SW version license is needed.
Recommended Action:
Please acquire a SW Version license file and upload it before starting the PROXY

Error Message:
CUP_SIPD-GENERIC-2-ESPStopped: Cisco UP SIP Proxy service child process has been stopped Version [String]
Explantion:
Cisco UP SIP Proxy service child process has stopped
Recommended Action:
If the administrator has not manually stopped the Proxy service, this may indicate a problem. Please use RTMT to check for any related alarms

Error Message:
CUP_SIPD-GENERIC-2-ESPSharedMemCreateFailed: Failed to create shared memory
Explantion:
Failed to create shared memory segments while trying to initialize tables
Recommended Action:
Use RTMT to check system shared memory and check the Cisco UP SIP Proxy service trace log file for any detailed error messages

Error Message:
CUP_SIPD-GENERIC-2-ESPSharedMemSetPermFailed: Failed to set permissions on shared memory
Explantion:
Failed to set permissions on shared memory segments while trying to initialize tables
Recommended Action:
Use RTMT to check system shared memory and check the Cisco UP SIP Proxy service trace log file for any detailed error messages

Error Message:
CUP_SIPD-GENERIC-2-ESPSharedMemAllocFailed: Failed to allocate shared memory MySQL [String]
Explantion:
Failed to allocate shared memory segments while trying to initialize tables
Recommended Action:
Use RTMT to check system shared memory and check the Cisco UP SIP Proxy service trace log file for any detailed error messages

Error Message:
CUP_SIPD-GENERIC-3-ESPConfigError: Cisco UP SIP Proxy service configuration file error SharedMemorySize [String] NumberOfVsa [String] ENUM [String] NumberExpansion [String] NumberServices [String] Registry [String] Routing [String] Radius [String] RAS [String] RPMS [String] MethodRouting [String]
Explantion:
This may indicate a formatting error, invalid value, etc with the Cisco UP SIP Proxy service configuration file
Recommended Action:
Verify that the Cisco Unified Presence Config Agent service is running. This service is responsible for writing the Proxy configuration file

Error Message:
CUP_SIPD-GENERIC-3-ESPConfigNotFound: Cisco UP SIP Proxy service configuration file not found SipModule [String] SipAuthenModule [String] SipEnum [String] SipNumExpand [String] SipNumServices [String] SipRegistry [String] SipRouting [String] SipAcct [String] SipRpms [String] SipPrivacy [String] SipMethodRoute [String]
Explantion:
This may indicate a formatting error, invalid value, etc, or even a missing configuration file
Recommended Action:
Verify that the configuration files /usr/local/sip/conf/sipd.conf and /usr/local/sip/conf/dynamic.sipd.conf exist on the Cisco Unified Presence server

Error Message:
CUP_SIPD-GENERIC-3-ESPCreateLockFailed: Failed to create a lock file
Explantion:
Failed to create a lock file
Recommended Action:
Use RTMT to check the Cisco UP SIP Proxy service trace log file for any detailed error messages

Error Message:
CUP_SIPD-GENERIC-3-ESPSocketError: Network socket errors encountered Radius [String] RAS [String]
Explantion:
Network socket errors could be caused by binding errors, get socket address failures, etc
Recommended Action:
Use RTMT to check the Cisco UP SIP Proxy service trace log file for any detailed error messages

Error Message:
CUP_SIPD-GENERIC-3-ESPRadiusError: Radius related Error RadiasError [String]
Explantion:
Radias Error undefined vendor specific attribute id
Recommended Action:
Use RTMT to check the Cisco UP SIP Proxy service trace log file for any detailed error messages

Error Message:
CUP_SIPD-GENERIC-3-ESPStatsLogFileOpenFailed: Failed to open stats log file
Explantion:
Failed to open the Cisco UP SIP Proxy service stats log file
Recommended Action:
Use RTMT to check the Cisco UP SIP Proxy service trace log file for any detailed error messages

Error Message:
CUP_SIPD-GENERIC-3-ESPStatsInitFailed: Failed to initialize the performance interface
Explantion:
Failed to initialize the performance Interface
Recommended Action:
Use RTMT to check the Cisco UP SIP Proxy service trace log file for any detailed error messages

Error Message:
CUP_SIPD-GENERIC-3-ESPMallocFailure: Failed to allocate memory SIPProtocol [String] NumberExpansion [String] SipRegistry [String] SipRouting [String] RAS [String] RPMS [String]
Explantion:
Failed to allocate memory. This may indicate a low/no memory issue with the server
Recommended Action:
Use RTMT to check the Cisco UP SIP Proxy service trace log file for any detailed error messages

Error Message:
CUP_SIPD-GENERIC-3-ESPWrongIPAddress: Wrong IP address provided ProxyIPAddrTab [String] IPAddrNotMine [String] DNSReturnedBadIP [String] ProxyLoopbackIPA [String] InvalidRASIPAddr [String] InvalidRPMSIPAddr [String]
Explantion:
Wrong/invalid IP address was provided
Recommended Action:
Use RTMT to check the Cisco UP SIP Proxy service trace log file for any detailed error messages

Error Message:
CUP_SIPD-GENERIC-3-ESPWrongHostName: Wrong host name
Explantion:
This problem could be due to an invalid IP address, or an unresolvable hostname
Recommended Action:
Use RTMT to check the Cisco UP SIP Proxy service trace log file for any detailed error messages

Error Message:
CUP_SIPD-GENERIC-3-ESPMySQLConnectionError: The connection to MySQL database failed MySQPError [String]
Explantion:
MySQL database connection(s) failed. This could be caused by lost connections, and failed reconnects
Recommended Action:
Use RTMT to check the Cisco UP SIP Proxy service trace log file for any detailed error messages

Error Message:
CUP_SIPD-GENERIC-3-ESPPassedParamInvalid: Invalid parameter specified MySQL [String] ENUM [String] NumberExpansion [String] RAS [String]
Explantion:
Invalid parameters were specified. This could be because the parameters were NULL
Recommended Action:
Use RTMT to check the Cisco UP SIP Proxy service trace log file for any detailed error messages

Error Message:
CUP_SIPD-GENERIC-3-ESPNumsvRouteError: Number services route error NumberServicesRoute [String]
Explantion:
Number services route error encountered
Recommended Action:
Use RTMT to check the Cisco UP SIP Proxy service trace log file for any detailed error messages

Error Message:
CUP_SIPD-GENERIC-3-ESPConnectToProvisioningServer: Failed to connect to the provisioning Server
Explantion:
Failed to connect to the provisioning Server
Recommended Action:
Use RTMT to check the Cisco UP SIP Proxy service trace log file for any detailed error messages

Error Message:
CUP_SIPD-GENERIC-3-ESPNAPTRInvalidRecord: NAPTR record format error ENUM [String]
Explantion:
This error may indicate invalid flag fields, missing delimiter, etc
Recommended Action:
Use RTMT to check the Cisco UP SIP Proxy service trace log file for any detailed error messages

Error Message:
CUP_SIPD-GENERIC-3-ESPASNLibInitError: Failed to initialize ASN encode/decode libraries
Explantion:
Fialed to initialize ASN encode/decode libraries
Recommended Action:
Use RTMT to check the Cisco UP SIP Proxy service trace log file for any detailed error messages

Error Message:
CUP_SIPD-GENERIC-3-ESPE164Error: E164 number errors RAS [String]
Explantion:
The root cause could be a NULL (or empty) E164 number
Recommended Action:
Use RTMT to check the Cisco UP SIP Proxy service trace log file for any detailed error messages

Error Message:
CUP_SIPD-GENERIC-3-ESPRASSendMessageFailed: RAS message send failure RAS [String]
Explantion:
Failed to send RAS message
Recommended Action:
Use RTMT to check the Cisco UP SIP Proxy service trace log file for any detailed error messages

Error Message:
CUP_SIPD-GENERIC-3-ESPVirtualProxyError: Virtual_Proxy_Domain related error.
Explantion:
Virtual_Proxy_Domain related error.
Recommended Action:
Use RTMT to check the Cisco UP SIP Proxy service trace log file for any detailed error messages

Error Message:
CUP_SIPD-GENERIC-3-ESPRegistryError: SIP Registry failure InvalidContact [String] ExceedMax [String] RegistryDatabaseError [String]
Explantion:
Unable to add registration to the SIP Registry because a resource limit was exceeded
Recommended Action:
Use RTMT to check the Cisco UP SIP Proxy service trace log file for any detailed error messages

Error Message:
CUP_SIPD-GENERIC-3-ESPRegistryInitFailed: SIP Registry initialization failure RegistryInit [String]
Explantion:
Unable to initialize the SIP Registry due to an internal error
Recommended Action:
Use RTMT to check the Cisco UP SIP Proxy service trace log file for any detailed error messages

Error Message:
CUP_SIPD-GENERIC-3-ESPRegistryLockFailed: SIP lock registry failure
Explantion:
SIP lock registry failure
Recommended Action:
Use RTMT to check the Cisco UP SIP Proxy service trace log file for any detailed error messages

Error Message:
CUP_SIPD-GENERIC-3-ESPRoutingError: SIP route interface error ExceedMax [String] RoutingDatabaseError [String]
Explantion:
SIP Route Interface resource limit exceeded error
Recommended Action:
Use RTMT to check the Cisco UP SIP Proxy service trace log file for any detailed error messages

Error Message:
CUP_SIPD-GENERIC-3-ESPRouteInitFailed: SIP Route interface initialization failure RoutingInit [String]
Explantion:
SIP Route interface initialization failed
Recommended Action:
Use RTMT to check the Cisco UP SIP Proxy service trace log file for any detailed error messages

Error Message:
CUP_SIPD-GENERIC-3-ESPRouteLockFailed: Failed to lock the Routing Information Base
Explantion:
Failed to lock the Routing Information Base
Recommended Action:
Use RTMT to check the Cisco UP SIP Proxy service trace log file for any detailed error messages

Error Message:
CUP_SIPD-GENERIC-3-ESPSIPURLWrong: Wrong SIP URL
Explantion:
Wrong SIP URL
Recommended Action:
Use RTMT to check the Cisco UP SIP Proxy service trace log file for any detailed error messages

Error Message:
CUP_SIPD-GENERIC-2-IPPMStopped: Cisco IP Phone Messenger application stopped Version [String]
Explantion:
Cisco IP Phone Messenger application stopped
Recommended Action:
Use RTMT to check for alarms. Verify whether this application was stopped manually by administrator

Error Message:
CUP_SIPD-GENERIC-3-IPPMSCBFindFailed: SCB find failure SCBFindFailure [String]
Explantion:
A call to find_scb() returned NULL which indicates the SCB lookup failed
Recommended Action:
Use RTMT to check the Cisco UP SIP Proxy service trace log file for any detailed error messages

Error Message:
CUP_SIPD-GENERIC-3-IPPMSCBGetFailed: SCB get or create failure SCBGetFailure [String]
Explantion:
A call to tcbtable_acquire_tcb() returned NULL which indicates a SCB get/create failure
Recommended Action:
Use RTMT to check the Cisco UP SIP Proxy service trace log file for any detailed error messages

Error Message:
CUP_SIPD-GENERIC-3-UASCBFindFailed: SCB find failure SCBFindFailure [String]
Explantion:
A call to find_scb() returned NULL which indicates the SCB lookup failed
Recommended Action:
Use RTMT to check the Cisco UP SIP Proxy service trace log file for any detailed error messages

Error Message:
CUP_SIPD-GENERIC-3-UASCBGetFailed: SCB get or create failure SCBGetFailure [String]
Explantion:
A call to tcbtable_acquire_tcb() returned NULL which indicates a SCB get/create failure
Recommended Action:
Use RTMT to check the Cisco UP SIP Proxy service trace log file for any detailed error messages

Error Message:
CUP_SIPD-GENERIC-3-IPPMSCBInitFailed: SCB initialization failure
Explantion:
SCB initialization failed
Recommended Action:
Use RTMT to check the Cisco UP SIP Proxy service trace log file for any detailed error messages

Error Message:
CUP_SIPD-GENERIC-3-IPPMReadConnectionError: Connection read error NonSupported [String]
Explantion:
IPPM reported a read error on the connection
Recommended Action:
Use RTMT to check the Cisco UP SIP Proxy service trace log file for any detailed error messages

Error Message:
CUP_SIPD-GENERIC-6-CTIGWStarted: Cisco CTI Gateway application started
Explantion:
Cisco CTI Gateway application started
Recommended Action:
Notification purposes only; no action is required

Error Message:
CUP_SIPD-GENERIC-6-CTIGWStopped: Cisco CTI Gateway application stopped
Explantion:
Cisco CTI Gateway application stopped
Recommended Action:
Notification purposes only; no action is required

Error Message:
CUP_SIPD-GENERIC-6-CTIGWRestarted: Cisco CTI Gateway application restarted
Explantion:
Cisco CTI Gateway application restarted
Recommended Action:
Notification purposes only; no action is required

Error Message:
CUP_SIPD-GENERIC-4-CTIGWModuleNotEnabled: Cisco CTI Gateway application module is either not configured or enabled
Explantion:
The Cisco CTI Gateway application is either not fully configured or enabled
Recommended Action:
Configure and enable the Cisco CTI Gateway application using the Cisco Unified Presence Administration GUI CTI Gateway Settings page

Error Message:
CUP_SIPD-GENERIC-6-CTIGWConnectionRestarted: CTI connection was restarted
Explantion:
The CTI/QBE connection was restarted
Recommended Action:
Notification purposes only; no action is required

Error Message:
CUP_SIPD-GENERIC-2-CTIGWProviderDown: CTI provider is down
Explantion:
The CTI provider is currently unavailable
Recommended Action:
Check the connection to the configured Cisco Unified Callmanager nodes and verify the Cisco CTI Gateway application is enabled on the Cisco Unified Presence Administration GUI CTI Settings page

Error Message:
CUP_SIPD-GENERIC-4-CTIGWUserNotLicenced: User has no license
Explantion:
User failed to authorize due to no license available
Recommended Action:
Check the Cisco CTI Gateway application license and user configuration

Error Message:
CUP_SIPD-GENERIC-4-CTIGWUserNotAuthorized: User not authorized by CTI Gateway
Explantion:
User failed to authorized due to wrong device or line DN
Recommended Action:
Verify user device configuration and MOC settings

Error Message:
CUP_SIPD-GENERIC-2-CTIGWProviderFailedToOpen: CTI Provider failed to open
Explantion:
CTI Provider failed to open due to a configuration error
Recommended Action:
Verify the Cisco Unified Callmanager address(es), and application user credentials on the Cisco Unified Presence Administration GUI CTI Settings page

Error Message:
CUP_SIPD-GENERIC-3-CTIGWQBEFailedRequest: QBE Request failure
Explantion:
The Cisco CTI Gateway application received a failed response to a request
Recommended Action:
Use RTMT to check the Cisco UP SIP Proxy service trace log file for any detailed error messages

Error Message:
CUP_SIPD-GENERIC-3-CTIGWSystemError: Cisco CTI Gateway application system errors CSTAError [String] InternalError [String] GeneralError [String]
Explantion:
Cisco CTI Gateway application system errors
Recommended Action:
Use RTMT to check the Cisco UP SIP Proxy service trace log file for any detailed error messages

Error Message:
CUP_SIPD-GENERIC-2-CALBackendCalDisc: Calendar server connection failure
Explantion:
Connection to the calendar server was lost. Meeting information will not be available
Recommended Action:
Use RTMT to check the Cisco UP SIP Proxy service trace log file for any detailed error messages

Error Message:
CUP_SIPD-GENERIC-2-CALMtngPlSvrDisc: MeetingPlace server connection failure
Explantion:
Connection to the MeetingPlace server was lost. Callback functionality will not be available
Recommended Action:
Use RTMT to check the Cisco UP SIP Proxy service trace log file for any detailed error messages

Error Message:
CUP_SIPD-GENERIC-6-CALBackendCalConn: Calendar server connection was established
Explantion:
Connection to the calendar server was established
Recommended Action:
Notification purposes only; no action is required

Error Message:
CUP_SIPD-GENERIC-6-CALMtngPlSvrConn: MeetingPlace server connection was established
Explantion:
Connection to the MeetingPlace server was established
Recommended Action:
Notification purposes only; no action is required

Error Message:
CUP_SIPD-GENERIC-2-CALExchangeTrustCertReadFailure: Failed to read calendar server certificate
Explantion:
The Cisco UP SIP Proxy service was unable to read the calendar server root trust certificate
Recommended Action:
Reload the calendar server root certificate and restart the Cisco UP SIP Proxy service

Error Message:
CUP_SIPD-GENERIC-2-CALMtngPlTrustCertReadFailure: Failed to read MeetingPlace server certificate
Explantion:
The Cisco UP SIP Proxy service was unable to read the MeetingPlace server root trust certificate
Recommended Action:
Reload the MeetingPlace server root certificate and restart the Cisco UP SIP Proxy service

Error Message:
CUP_SIPD-GENERIC-2-CALMtngPlSystemFailure: Failed to decrypt the user MeetingPlace password
Explantion:
The Cisco UP SIP Proxy service was unable to decrypt the MeetingPlace user password
Recommended Action:
Reconfigure the MeetingPlace user password

Error Message:
CUP_SIPD-GENERIC-3-PWSSCBFindFailed: SCB find failure SCBFindFailure [String]
Explantion:
A call to find_scb() returned NULL which indicates the SCB lookup failed
Recommended Action:
Use RTMT to check the Cisco UP SIP Proxy service trace log file for any detailed error messages

Error Message:
CUP_SIPD-GENERIC-3-PWSSCBInitFailed: SCB init failure SCBInitFailure [String]
Explantion:
SCB init failed
Recommended Action:
Restart the Cisco UP SIP Proxy service

Error Message:
CUP_SIPD-GENERIC-5-PWSBelowCPULimit: CPU utilization has fallen below the max CPU limit BelowCPULimit [String]
Explantion:
CPU utilization has fallen below the max CPU limit, new requests will no longer be blocked
Recommended Action:
Notification purposes only; no action is required

Error Message:
CUP_SIPD-GENERIC-4-PWSAboveCPULimit: Indicates the Presence Web Service has exceeded a CPU utilization threshold AboveCPULimit [String]
Explantion:
The Presence Web Service module running in the Cisco UP SIP Proxy service has detected that the CPU utilization has exceeded the configured threshold. During this time new requests will be blocked until the CPU utilization drops below the configured threshold
Recommended Action:
Using RTMT, inspect the Cisco UP SIP Proxy service logs for more details

Error Message:
CUP_SIPD-GENERIC-4-PWSRequestLimitReached: Proxy service request per second limit reached RequestLimitReached [String]
Explantion:
The Cisco UP SIP Proxy service request per second limit has been reached
Recommended Action:
You may need to throttle back the incoming request rate

Error Message:
CUP_SIPD-GENERIC-4-PWSAboveSipSubscriptionLimit: Indicates the Presence Web Service subscription count has exceeded the maximum limit AboveSipSubscriptionLimit [String]
Explantion:
The Presence Web Service running in the Cisco UP SIP Proxy service has detected that the subscription count has exceeded the configured limit. During this time the Presence Web Service will block new incoming SIP subscriptions until the subscription count drops below the configured limit
Recommended Action:
Using RTMT, inspect the Cisco UP SIP Proxy service logs for more details

Error Message:
CUP_SIPD-GENERIC-5-PWSBelowSipSubscriptionLimit: Subscriptions have fallen below the max limit BelowSipSubscriptionLimit [String]
Explantion:
The Presence Web Service running in the Cisco UP SIP Proxy service has detected that the subscription count has fallen below the configured limit
Recommended Action:
Notification purposes only; no action is required

Error Message:
CUP_SRM-GENERIC-2-SRMFailover: Cisco UP SRM is performing an automatic failover FromNode [String] ToNode [String] Reason [String]
Explantion:
Cisco UP SRM is performing an automatic failover
Recommended Action:
Please verify that the failed node is up and that critical services are running.

Error Message:
CUP_SRM-GENERIC-2-SRMFailed: Cisco UP Server Recovery Manager is in the failed state
Explantion:
Cisco UP SRM is in the failed state
Recommended Action:
Please restart the Cisco UP Server Recovery Manager.

Error Message:
CUP_PE-GENERIC-4-PENotifyTimeout: Timeout occurred when sending a SIP NOTIFY message to a client DialogInformation [String]
Explantion:
Cisco UP Presence Engine service attempted to send a SIP NOTIFY message to a client but the message timed out
Recommended Action:
Verify that the client is running and accepting SIP traffic on the configured port

Error Message:
CUP_PE-GENERIC-0-PENoSWVersionLicense: Cisco Unified Presence Engine: failed to start
Explantion:
Cisco Unified Presence Engine: SW version license is needed.
Recommended Action:
Please acquire a SW Version license file and upload it before starting the Presense Engine

Error Message:
CUP_PE-GENERIC-2-PEDatabaseError: Information lookup failed DatabaseErrorMessage [String]
Explantion:
An error occurred while retrieving information. This may indicate a problem with the Cisco DB service
Recommended Action:
Verify that the Cisco DB service is activated and running. Use RTMT to check the Cisco UP Presence service logs for errors

Error Message:
CUP_PE-GENERIC-2-PEPeerNodeFailure: The Cisco UP Presence Engine service on the peer node of a subcluster has failed PeerFailedMessage [String]
Explantion:
The Cisco UP Presence Engine service in the peer node is not responding
Recommended Action:
Use Cisco Unified Serviceability to verify the Cisco UP Presence Engine serivce is activated and running

Error Message:
CUP_PE-GENERIC-3-PEAutoRecoveryFailed: Cisco UP Presence Engine service auto-recovery failure AutorecoveryFailedMessage [String]
Explantion:
An error occurred during the startup sequence of the Cisco UP Presence Engine service
Recommended Action:
This error may indicate a possible configuration issue. Please correct the problem identified in the failure message

Error Message:
CUP_PE-GENERIC-5-PEPeerNodeFailureCleared: Cisco UP Presence Engine service on the clusters peer node has returned to normal operation PeerFailureCleared [String]
Explantion:
The Cisco UP Presence Engine service running on the cluster peer node has returned to normal operation
Recommended Action:
Notification purposes only; no action is required

Error Message:
CUP_PE-GENERIC-4-PELoadHighWaterMark: Indicates the Cisco UP Presence Engine service has exceeded a CPU utilization threshold HighWaterMarkMessage [String]
Explantion:
The Cisco UP Presence Engine service has detected that the CPU utilization has exceeded the configured threshold. During this time the Cisco UP Presence Engine service will reject/redirect SIP SUBSCRIBE requests until the CPU utilization drops below the configured threshold
Recommended Action:
Using RTMT, inspect the number of active subscription counters: ActiveSubscriptions, ActiveViews, SubscriptionActiveReceivedFromForeign and SubscriptionActiveSentForeign. If this condition persists, you may consider moving users to a different Cisco Unified Presence node in the cluster

Error Message:
CUP_PE-GENERIC-5-PELoadHighWaterMarkCleared: Cisco UP Presence Engine service high water threshold has cleared HighWaterMarkCleared [String]
Explantion:
The Cisco UP Presence Engine service has cleared the previous high water threshold (which was caused by high CPU utilization), and is now accepting SIP requests
Recommended Action:
Notification purposes only; no action is required

Error Message:
CUP_PE-GENERIC-2-PEIDStoTimestenDatabaseSyncError: Synchronization between the Cisco Unified Presence database and the Cisco Unified Presence Engine database has failed PEMessage [String]
Explantion:
An error has occurred synchronizing the Cisco Unified Presence data with the Cisco Unified Presence Engine database
Recommended Action:
See associated error message and log files. Please restart the Cisco UP Presence Engine service when convenient

Error Message:
CUP_PE-GENERIC-5-PEIDStoTimestenDatabaseSyncErrorCleared: Synchronization between the Cisco Unified Presence database and the Cisco Unified Presence Engine database established
Explantion:
The Cisco UP Presence Engine service has established synchronization between Cisco Unified Presence database and the Cisco Unified Presence Engine database
Recommended Action:
Notification purposes only; no action is required

Error Message:
CUP_PE-GENERIC-2-PEIDSSubscribeError: The Cisco UP Presence Engine service was unable to subscribe for Cisco Unified Presence database change notifications PEMessage [String]
Explantion:
An error has occurred subscribing to Cisco Unified Presence database change notifications
Recommended Action:
See associated error message and log files. Please restart the Cisco UP Presence Engine service when convenient

Error Message:
CUP_PE-GENERIC-2-PEIDSQueryError: The Cisco UP Presence Engine service has detected an error while querying the Cisco Unified Presence database PEMessage [String]
Explantion:
An error has occurred whilst querying the Cisco Unified Presence database
Recommended Action:
See associated error message and log files. Please restart the Cisco UP Presence Engine service when convenient

Error Message:
CUP_PE-GENERIC-4-PEMemoryHighCondition: Indicates the Cisco UP Presence Engine service has hit a high memory threshold HighMemoryCondition [String]
Explantion:
The Cisco UP Presence Engine service has encountered a high memory condition. The Cisco UP Presence Engine service will reject or redirect SIP SUBSCRIBE requests until the memory condition has cleared
Recommended Action:
Inspect the number of active subscription counters: ActiveSubscriptions, ActiveViews, SubscriptionActiveReceivedFromForeign and SubscriptionActiveSentForeign with RTMT. If this condition occurs consistently, consider offloading some users to a different CUP node in the cluster

Error Message:
CUP_PE-GENERIC-5-PEMemoryHighConditionCleared: Indicates that the Cisco UP Presence Engine service has cleared the high memory condition HighMemoryConditionCleared [String]
Explantion:
The Cisco UP Presence Engine service has cleared high memory condition and will now accept SIP messages
Recommended Action:
Notification purposes only; no action is required

Error Message:
CUP_PE-GENERIC-2-PESipSgHostUnavailable: Cisco UP Presence Engine service could not reach server group SipSgHost [String]
Explantion:
Cisco UP Presence Engine service could not contact the outbound proxy server group
Recommended Action:
Verify that outbound proxy is configured correctly and listening on the configured ports

Error Message:
CUP_PE-GENERIC-5-PESipSgHostUnavailableClear: Cisco UP Presence Engine service can now contact the outbound proxy server group SipSgHost [String]
Explantion:
Cisco UP Presence Engine service can now contact the outbound proxy server group
Recommended Action:
Notification purposes only; no action is required

Error Message:
CUP_PE-GENERIC-6-PESipMessageTimeout: Timeout occurred on SIP message transmission SipMessageCallID [String]
Explantion:
The transmission of an Cisco UP Presence Engine service SIP message timed out
Recommended Action:
Look for possible network latency problems

Error Message:
CUP_PE-GENERIC-2-PESipSocketBindFailure: Cisco UP Presence Engine service was unable to connect to the SIP listener interface SipSocketInterface [String]
Explantion:
Cisco UP Presence Engine service was unable to connect to the configured interface. No SIP traffic can be processed on this interface
Recommended Action:
Verify that the Cisco UP Presence Engine service listen interface is configured correctly on the Cisco Unified Presence Administration GUI Application Listener page. Verify that no other process is listening on the same port using netstat

Error Message:
CUP_PE-GENERIC-2-PEOamInitialConfigFileError: Cisco UP Presence Engine service configuration file not found or malformed PEOamConfigFileURI [String] PEOamErrorMessage [String]
Explantion:
Cisco UP Presence Engine service configuration file is missing or malformed
Recommended Action:
Verify that the Cisco UP OAM Agent service is activated and running

Error Message:
CUP_PE-GENERIC-2-PEOamInvalidInitialConfigFile: Cisco UP Presence Engine service configuration file not found or malformed PEOamConfigFileURI [String] PEOamErrorMessage [String]
Explantion:
Cisco UP Presence Engine service configuration file is missing or malformed
Recommended Action:
Verify that the Cisco UP OAM Agent service is activated and running

Error Message:
CUP_PE-GENERIC-5-PEOamInitialConfigFileClear: Cisco UP Presence Engine service configuration file now appears to be valid PEOamConfigFileURI [String]
Explantion:
Cisco UP Presence Engine service configuration file is now correct
Recommended Action:
Notification purposes only; no action is required

Error Message:
CUP_PE-GENERIC-2-PEOamConfigFileError: Cisco UP OAM Agent service configuration file is invalid PEOamConfigFileURI [String] PEOamErrorMessage [String]
Explantion:
Cisco UP OAM Agent service configuration file is invalid
Recommended Action:
Verify that the Cisco UP OAM Agent service is activated and running

Error Message:
CUP_PE-GENERIC-2-PEOamInvalidConfigFile: Cisco UP Presence Engine service configuration file is invalid PEOamConfigFileURI [String] PEOamErrorMessage [String]
Explantion:
Cisco UP Presence Engine service configuration file is invalid
Recommended Action:
Verify that the Cisco UP OAM agent serivce is activated and running

Error Message:
CUP_PE-GENERIC-2-PEConfigNotificationFailure: Cisco UP Presence Engine service cannot connect to socket used for communications between with the Cisco UP OAM Agent service PEOamXmlRpcSocketPort [String] PEOamXmlRpcSocketHostname [String]
Explantion:
The Cisco UP Presence Engine service cannot bind to the socket that is used for communication with the Cisco UP OAM Agent service via XML-RPC
Recommended Action:
Verify that the Cisco UP OAM Agent service listen interface is configured correctly on the Cisco Unified Presence Administration GUI Application Listener page. Verify that no other process is listening on the same port using netstat

Error Message:
CUP_PE-GENERIC-6-PEStateStopped: Cisco UP Presence Engine service is terminating
Explantion:
Cisco UP Presence Engine service is terminating
Recommended Action:
Notification purposes only; no action is required

Error Message:
CUP_PE-GENERIC-4-PEStateLocked: Cisco UP Presence Engine service is administratively prohibited from processing traffic
Explantion:
Cisco UP Presence Engine service is administratively prohibited from processing traffic
Recommended Action:
Notification purposes only; no action is required

Error Message:
CUP_PE-GENERIC-6-PEStateShuttingdown: Cisco UP Presence Engine service is shutting down
Explantion:
Cisco UP Presence Engine service is shutting down but will continue to process existing transactions. However, no new transactions will be processed
Recommended Action:
Notification purposes only; no action is required

Error Message:
CUP_PE-GENERIC-6-PEStateUnlocked: Cisco UP Presence Engine service is administratively permitted to process traffic
Explantion:
Cisco UP Presence Engine service is administratively permitted to process traffic
Recommended Action:
Notification purposes only; no action is required

Error Message:
CUP_PE-GENERIC-4-PEStateDisabled: Cisco UP Presence Engine service is inoperable and unable to process traffic
Explantion:
Cisco UP Presence Engine service is inoperable and unable to process traffic
Recommended Action:
Check the log files and monitor the Cisco UP Presence Engine service with RTMT

Error Message:
CUP_PE-GENERIC-5-PEStateEnabled: Cisco UP Presence Engine service is now able to process traffic
Explantion:
Cisco UP Presence Engine service is now able to process traffic
Recommended Action:
Notification purposes only; no action is required

Error Message:
CUP_PE-GENERIC-3-PECalendarConnectionLoss: Indicates that the Cisco UP Presence Engine service cannot connect to the Calendar Server CalendarConnectionLossMessage [String]
Explantion:
The Cisco UP Presence Engine service cannot connect to the Calendar Server and will fail all calendar transactions until the connection is restored
Recommended Action:
Verify the Calendar Server is running and that the gateway configuration is correct on the Cisco Unified Presence Administration GUI Presence Gateways page

Error Message:
CUP_PE-GENERIC-5-PECalendarConnectionLossCleared: Cisco UP Presence Engine service has regained connection to the Calendar Server CalendarConnectionLossCleared [String]
Explantion:
The Cisco UP Presence Engine service has successfully committed a transaction to the Calendar Server. The connection has been restored
Recommended Action:
Notification purposes only; no action is required

Error Message:
CUP_PE-GENERIC-3-PEWebDAVInitializationFailure: Cisco UP Presence Engine service attempt to init the WebDAV library failed WebDAVInitializationFailure [String]
Explantion:
The Cisco UP Presence Engine service has failed to initialize the WebDAV library. The Calendaring feature will not work without WebDAV
Recommended Action:
Restart the Cisco UP Presence Engine service

Error Message:
CCM_DB_LAYER-DB-3-kDbConnectionFailed: Database connection failed. AdditionalInfo [String]
Explantion:
An attempt to connect to database failed.
Recommended Action:
Enable trace for the database layer monitor to get specific error information.

Error Message:
CCM_DB_LAYER-DB-1-NoDbConnectionAvailable: No database connection available.
Explantion:
Database layer could not find any working database connection.
Recommended Action:
In Cisco Unified Serviceability, enable Detailed level traces in the Trace Configuration window for the Cisco Database Layer Monitor service. Check network connectivity and operation of SQL Server services.

Error Message:
CCM_DB_LAYER-DB-2-ErrorChangeNotifyClientBlock: A change notification client is busy (blocked). If the change notification client continues to be blocked for 10 minutes, the system automatically clears the block and change notification should resume successfully.
Explantion:
Changes made to the database are not being consumed by one of the recipients. This does not always represent an issue. However, if the change notification client continues to be blocked for 10 minutes, the system automatically clears the block for all clients except the blocked one, which means that change notifications should resume successfully for all other clients. To clear the blocked client, you must restart the server.
Recommended Action:
At the command line interface (CLI) on the database server, execute the following command: show tech notify. The CLI command output will provide information about the block. Use Cisco Unified Serviceability to restart the server that was indicated in the alarm. You may also want to gather traces to examine them for anomalous activity during the time that client was blocked. In Cisco Unified Serviceability, enable Detailed level traces in the Trace Configuration window for the Cisco Database Layer Monitor service. Also, use RTMT to look for error messages that may have occurred around the time of the alarm.

Error Message:
CCM_DB_LAYER-DB-3-ErrorReadingInstalledRPMS: Could not read installed RPMs to populate component version table
Explantion:
The function that reads the rpm version information and populates database failed
Recommended Action:
Please report this error to the administrator.

Error Message:
CCM_DB_LAYER-DB-3-ErrorChangeNotifyClientTimeout: A change notification client was responding slowly and has been removed.
Explantion:
A change notification recipient hasn't responded to change notification in several minutes and was thus removed. This may delay call processing features, such as call forwarding and so on.
Recommended Action:
Rebooting the box will clear this situation. Alternatively, dbnotify trace could be analyzed to find the client that was removed and that service could be restarted in Cisco Unified Serviceability.

Error Message:
CCM_DB_LAYER-DB-1-ErrorChangeNotifyReconcile: A change notification shared memory reconciliation has occurred.
Explantion:
The change notification buffers in shared memory have been rebuilt due to conflicts.
Recommended Action:
This problem may have been already corrected. If unexpected behavior is observed, restart all Cisco services in the cluster.

Error Message:
CCM_DB_LAYER-DB-6-IDSEngineDebug: Indicates debug events from IDS database engine. class_id [String] class_msg [String] specific_msg [String]
Explantion:
This alarm provides low-level debugging information from IDS database engine. System administrator can disregard this alarm.
Recommended Action:
This is for debug information purposes only; no action is required.

Error Message:
CCM_DB_LAYER-DB-6-IDSEngineInformation: No error has occurred but some routine event completed in IDS database engine. class_id [String] class_msg [String] specific_msg [String]
Explantion:
This alarm is informational. No error has occurred but some routine event completed in IDS database engine.
Recommended Action:
This is for information purposes only; no action is required.

Error Message:
CCM_DB_LAYER-DB-3-IDSEngineCritical: Pay Attention. This alarm does not compromise data or prevent the use of the system. class_id [String] class_msg [String] specific_msg [String]
Explantion:
Pay Attention. This alarm does not compromise data or prevent the use of the system.
Recommended Action:
This alarm needs monitoring by the db admin

Error Message:
CCM_DB_LAYER-DB-3-IDSEngineFailure: Combined alarm for emergency and error situations. Something unexpected occurred that might compromise data or access to data or cause IDS to fail class_id [String] class_msg [String] specific_msg [String]
Explantion:
This alarm indicates combined alarm for emergency and error situations. Something unexpected occurred that might compromise data or access to data or cause IDS to fail
Recommended Action:
Requires db admin intervention

Error Message:
CCM_DB_LAYER-DB-6-IDSReplicationInformation: Information about IDS replication class_id [String] class_msg [String] specific_msg [String]
Explantion:
This alarm provides information about IDS replication.
Recommended Action:
Informational purposes only; no action is required

Error Message:
CCM_DB_LAYER-DB-3-IDSReplicationFailure: Combined alarm for emergency and error situations. IDS Replication has failed class_id [String] class_msg [String] specific_msg [String]
Explantion:
This alarm indicates combined alarm for emergency and error situations. It indicates failure in IDS Replication
Recommended Action:
Requires db admin intervention

Error Message:
CUP_SOAP-GENERIC-4-LegacyCUPCLogin: A legacy Cisco Unified Personal Communicator client attempted to login to the Cisco UP Client Profile Agent service userid [String] version [String]
Explantion:
A legacy Cisco Unified Personal Communicator client attempted to login to the Cisco UP Client Profile Agent service. Login was denied
Recommended Action:
Please upgrade the legacy Cisco Unified Personal Communicator client as it is currently not supported

Error Message:
CCM_TOMCAT_APPS-LOGIN-5-ServiceActivated: Service Activated. ServiceName [String]
Explantion:
This service is now activated.
Recommended Action:
No action is required.

Error Message:
CCM_TOMCAT_APPS-LOGIN-5-ServiceDeactivated: Service Deactivated. ServiceName [String]
Explantion:
This service is now deactivated.
Recommended Action:
No action is required.

Error Message:
CCM_TOMCAT_APPS-LOGIN-1-ServiceActivationFailed: Failed to activate a service. ServiceName [String] Reason [String] ErrorString [String]
Explantion:
Failed to activate this service.
Recommended Action:
Activate the service again

Error Message:
CCM_TOMCAT_APPS-LOGIN-1-ServiceDeactivationFailed: Failed to deactivate a service. ServiceName [String] Reason [String] ErrorString [String]
Explantion:
Failed to deactivate this service.
Recommended Action:
Deactivate the service again

Error Message:
CCM_TOMCAT_APPS-LOGIN-2-ServiceFailed: Service terminated. ServiceName [String] Reason [String] ProcessID [Int]
Explantion:
The Service has terminated abruptly. Service Manager will try to restart it.
Recommended Action:
Monitor the state of the service.

Error Message:
CCM_TOMCAT_APPS-LOGIN-2-ServiceStartFailed: Failed to start service. ServiceName [String] Reason [String]
Explantion:
Failed to start this service. Service Manager will attempt to start the service again.
Recommended Action:
Monitor the state of the service.

Error Message:
CCM_TOMCAT_APPS-LOGIN-2-ServiceStopFailed: Failed to stop service. ServiceName [String] Reason [String]
Explantion:
Unable to stop the specified service after serveral retries. The service will be marked stopped.
Recommended Action:
Check the syslog for system error code.

Error Message:
CCM_TOMCAT_APPS-LOGIN-2-ServiceRestartFailed: Failed to Restart service. ServiceName [String] Reason [String]
Explantion:
Unable to restart the specified service.
Recommended Action:
No action is required.

Error Message:
CCM_TOMCAT_APPS-LOGIN-1-ServiceExceededMaxRestarts: Service failed to start and exceeded maximum allowed restarts. ServiceName [String] RestartCount [Int]
Explantion:
Service failed to start, even after the max restarts attempts.
Recommended Action:
Start the service manually.

Error Message:
CCM_TOMCAT_APPS-LOGIN-0-FailedToReadConfig: Service Manager failed to read configuration file. Filename [String] Reason [String]
Explantion:
Failed to read configuration file. Configuration file might be corrupted.
Recommended Action:
Re-install CUCM

Error Message:
CCM_TOMCAT_APPS-LOGIN-1-MemAllocFailed: Memory allocation failed. MemAllocFailure [String]
Explantion:
Failure to allocate memory.
Recommended Action:
(1) Check the syslog for the system error number. (2) If the Alert is seen repeatedly, restart Service Manager (3) If the problem still persist, reboot the CUCM node.

Error Message:
CCM_TOMCAT_APPS-LOGIN-1-SystemResourceError: A System call failed. SystemCall [String] Service [String] Reason [String]
Explantion:
System call failed.
Recommended Action:
(1) Check the syslog for the system error number.(2) If the Alert is seen repeatedly, restart Service Manager (3) If the problem still persist, reboot the node.

Error Message:
CUP_SA-GENERIC-2-CUPSyncAgentAXLConnectionFailed: Cisco UP Sync Agent service failed authentication
Explantion:
Cisco UP Sync Agent service failed authentication to the remote Cisco Unified Communications Manager publisher and therefore is unable to connect
Recommended Action:
Please verify the AXL credentials are correct and whether the Cisco AXL Web service is activated and running on the remote Cisco Unified Communications Manager publisher

Error Message:
CUP_SA-GENERIC-2-CUPSyncAgentCucmDbmonConnectionFailed: Cisco UP Sync Agent service lost connection to the Cisco Database Layer Monitor service
Explantion:
Cisco UP Sync Agent service lost the connection to the Cisco Database Layer Monitor service. This error can cause the data on the Cisco Unified Presence cluster to get out-of-sync with the data on the Cisco Unified Communications Manager cluster
Recommended Action:
Verify the Cisco Unified Communications Manager server is active and the Cisco Unified Communications Manager publisher has opened port 8001

Error Message:
CUP_SA-GENERIC-2-DbmonQueueWorkerExistWithError: Cisco UP Sync Agent service unable to process change notifications from the Cisco Unified Communications Manager cluster
Explantion:
Cisco UP Sync Agent service is no longer processing change notifications from the Cisco Unified Communications Manager cluster. This error can cause the data on the Cisco Unified Presence cluster to get out-of-sync with the data on the Cisco Unified Communications Manager cluster
Recommended Action:
Please verify the Cisco Unified Communications Manager server is active. A restart of the Cisco UP Sync Agent service may be required

Error Message:
CUP_SA-GENERIC-2-CupNotInCucmAppServerListError: Cisco UP Sync Agent failed to start up due to Cisco Unified Presence Server node is not in the application server list on the Cisco Unified Communications Manager publisher.
Explantion:
Cisco Unified Presence Server node is not in the application server list on the Cisco Unified Communications Manager publisher.
Recommended Action:
Please add Cisco Unified Presence Server node in the application server list on the Cisco Unified Communications Manager server and start Cisco UP Sync Agent service.

Error Message:
CUP_XCP-GENERIC-3-XcpDBConnectError: Cisco UP XCP data acces layer was unable to connect to the DB.
Explantion:
Cisco UP XCP data access layer was unable to connect to the DB. This may indicate that the local or external database is down or the network connetivity to the external database is lost.
Recommended Action:
Please check the System Troubleshooter for more information. Also check that the external database is running healthy and if there is any problem with the network connectivity to the external database server.

Error Message:
CUP_XCP-GENERIC-6-XcpDBConnectRestore: Cisco UP XCP data access layer was able to restore connection to the DB.
Explantion:
Cisco UP XCP data access layer was able to restore connection to the DB. The alert condition, if any, caused by the connection failure will be cleared.
Recommended Action:
None.

Error Message:
CUP_XCP-GENERIC-3-XcpComponentConnectError: The XCP component failed to connect to the XCP Router. The component is shutting down.
Explantion:
The concerned XCP component failed to connect to the XCP Router. The component is shutting down after reaching it~Rs configured number of reconnect attempts.
Recommended Action:
Please check the component log file for more details.

Error Message:
CUP_XCP-GENERIC-3-XcpComponentConfigError: The XCP component detected a bad configuration.
Explantion:
The concerned XCP component failed to load the configuration due to an error. This may be due to an invalid element in the configuration file.
Recommended Action:
Please check the component log file for more details.

Error Message:
CUP_XCP-GENERIC-3-XcpMdnsStartError: The XCP Router failed to startup the MDNS.
Explantion:
The XCP Router failed to startup the MDNS (Multicast Domain Name Service). This can cause connectivity failures to other routers in the cluster.
Recommended Action:
Please check the XCP Router log file for more details.

Error Message:
CUP_XCP-GENERIC-3-XcpCmPauseSockets: The XCP Router has directed the XCP Connection Manager (CM) to pause listening on its socket due to load on the system.
Explantion:
Outstanding XCP internal packet or database requests have reached configured limit. Client connections will be paused until pending requests have dropped back below threshold. Users will experience lag until issue is resolved. Users may be disconnected if configured timeout is reached before resolution.
Recommended Action:
Please check the XCP Router log file for more details. Watch for client disconnecting due to timeout from the XCP Connection Managers.

Error Message:
CUP_XCP-GENERIC-6-XcpCmResumeSockets: Outstanding internal packet or database requests have dropped back below configured threshold.
Explantion:
XCP Connection Manager has been notified to resume listening on client connections.
Recommended Action:
Please check the XCP Router log file for more details.

Error Message:
CUP_XCP-GENERIC-3-XcpCmStartupError: The XCP Connection Manager service failed to startup.
Explantion:
The XCP Connection Manager (CM) service failed to startup. One of the configured CM Directors may have failed to startup.
Recommended Action:
Please check the CM log file for more details.

Error Message:
CUP_XCP-GENERIC-3-XcpCmHttpdError: The XCP Connection Manager service has errors in the HTTP interface.
Explantion:
The XCP Connection Manager (CM) service has errors in the HTTP interface. This can cause connectivity failures to HTTP based clients.
Recommended Action:
Please check the CM log file for more details.

Error Message:
CUP_XCP-GENERIC-3-XcpCmXmppdError: The XCP Connection Manager service has errors in the XMPP interface.
Explantion:
The XCP Connection Manager (CM) service has errors in the XMPP interface. This can cause connectivity failures to XMPP based clients.
Recommended Action:
Please check the CM log file for more details.

Error Message:
CUP_XCP-GENERIC-3-XcpTxtConfGearError: The XCP Text Conference Manager Service failed to load a configured gear.
Explantion:
The XCP Text Conference Manager (TC) Service has failed to load a configured component. This can prevent the service to start or behave as expected.
Recommended Action:
Please check the XCP Text Conference log file for more details.

Error Message:
CUP_XCP-GENERIC-6-XcpTxtConfRoomLimitError: This server has a limit on the maximum number of supported text conference rooms.
Explantion:
There is a maximum limit of 16500 text conference rooms per server. This limit is the combined total of both persistent chat rooms and adhoc chat rooms.
Recommended Action:
In order to increase the maximum supported text chat room capacity, additional servers must be deployed.

Error Message:
CUP_XCP-GENERIC-2-XcpSIPGWStackResourceError: The number of concurrent S2S SIP Federation subscriptions or call-legs has reached the maximum limit specified by the configuration.
Explantion:
The number of concurrent S2S SIP Federation subscriptions or call-legs has reached the maximum limit specified by the configuration. It will not be possible to create any more subscriptions or call-legs at the time.
Recommended Action:
Increase the Pre-allocated SIP stack memory Service Parameter for the Cisco UP XCP SIP Federation Connection Manager. Note - If changing this setting, make sure that you have the memory available. If not, you may have reached the limit of your hardware's capability.

Error Message:
CUP_XCP-GENERIC-3-XcpThirdPartyComplianceConnectError: Cisco XCP Router is unable to connect to Third Party Compliance Server
Explantion:
Cisco XCP Router is unable to connect to Third Party Compliance Server. This may be because of a network problem or a Third Party Compliance Server config or licensing problem
Recommended Action:
This is a serious error that breaks IM on CUP. Check network connection to and configuration(including licensing) on Third Party Compliance Server. To restore IM services set the Compliance Settings option in the Admin GUI to "Not Configured" until the connection failure cause has been identified

Error Message:
CUP_XCP-GENERIC-6-XcpThirdPartyComplianceConnectRestore: Cisco XCP Router is reconnected to Third Party Compliance Server
Explantion:
Cisco XCP Router is reconnected to Third Party Compliance Server. This indicates an initial connection or reconnection
Recommended Action:
None.

Error Message:
CCM_DRF_MASTER-DRF-3-DRFTruststoreMissing: DRF uses ipsec truststore certificate for securing communication between the MA and LA service. This certificate is missing on the node Reason [String]
Explantion:
DRF uses ipsec truststore certificate for securing communication between the MA and LA service. This certificate is missing on the node, DRF LA will not be able to connect to MA
Recommended Action:
Download ipsec.pem file from Publisher and upload it as ipsec-trust only on the missing node then restart Cisco DRF Local service.

Error Message:
CCM_DRF_MASTER-DRF-3-DRFUnknownClient: The DRF Master Agent running on the Publisher has received a Client connection request from an unknown server outside the cluster.The request has been rejected Reason [String]
Explantion:
The DRF Master Agent running on the Publisher has received a Client connection request from an unknown server outside the cluster.The request has been rejected.
Recommended Action:
Remove the suspect server from the network. Refer to the Reason section for suspect servers: Hostname and IP Address

Error Message:
CCM_DRF_MASTER-DRF-3-DRFSecurityViolation: The DRF System has detected a malicious pattern which could result in a security violation Reason [String]
Explantion:
The DRF Network Message contains a malicious pattern which could result in a security violation like code injection or directory traversal. DRF Network Message has been blocked.
Recommended Action:
Stop the Cisco DRF Master and Cisco DRF Local Agent Services

Error Message:
CCM_DRF_MASTER-DRF-3-DRFMasterAgentStartFailure: DRF Master Agent was unable to start because it was unable to open port 4040. Reason [String]
Explantion:
DRF Master Agent was unable to start because it was unable to open port 4040.
Recommended Action:
Check if port 4040 is not already in use.

Error Message:
CCM_DRF_MASTER-DRF-3-DRFLocalAgentStartFailure: DRF Local Agent was not able to start because it was unable to connect to the Master Agent on port 4040 Reason [String]
Explantion:
DRF Local Agent was not able to start because it was unable to connect to the Master Agent on port 4040
Recommended Action:
Check if the CiscoDRFMaster and CiscoDRFLocal services are running

Error Message:
CCM_DRF_MASTER-DRF-3-DRFLA2MAFailure: DRF Local Agent is not able to connect to Master Agent. Reason [String]
Explantion:
DRF Local Agent is not able to connect to Master Agent.
Recommended Action:
Check if the Master Agent is up and the port is authorized.

Error Message:
CCM_DRF_MASTER-DRF-3-DRFMA2LAFailure: Master Agent was unable to send a backup/restore request to the local agent. Reason [String]
Explantion:
Master Agent was unable to send a backup/restore request to the local agent.
Recommended Action:
Restart the corresponding local agents and the master agent.

Error Message:
CCM_DRF_MASTER-DRF-3-DRFBackupFailure: Cisco DRF Backup process failed. Reason [String]
Explantion:
DRF Backup process encountered errors.
Recommended Action:
Check DRF logs for further details.

Error Message:
CCM_DRF_MASTER-DRF-3-DRFRestoreFailure: DRF Restore process failed. Reason [String]
Explantion:
DRF Restore process encountered errors.
Recommended Action:
Check DRF logs for further details.

Error Message:
CCM_DRF_MASTER-DRF-3-DRFBackupDeviceError: DRF Backup process is failed due to backup device error. Reason [String]
Explantion:
DRF Backup process is failed due to backup device error.
Recommended Action:
Check if the proper device has been specified in the DRF configurations.

Error Message:
CCM_DRF_MASTER-DRF-3-DRFTapeDeviceError: DRF is unable to access tape device. Reason [String]
Explantion:
DRF is unable to access tape device.
Recommended Action:
Check if tape drive is working properly and it contains a valid tape.

Error Message:
CCM_DRF_MASTER-DRF-3-DRFLocalDeviceError: DRF is unable to access local device. Reason [String]
Explantion:
DRF is unable to access local device.
Recommended Action:
Check if local location exists and is accessible.

Error Message:
CCM_DRF_MASTER-DRF-3-DRFInternalProcessFailure: DRF internal process has encountered an error. Reason [String]
Explantion:
DRF internal process has encountered an error.
Recommended Action:
Check DRF logs for details.

Error Message:
CCM_DRF_MASTER-DRF-3-DRFRestoreInternalError: DRF Restore operation has encountered an error. Restore cancelled internally. Reason [String]
Explantion:
DRF Restore operation has encountered an error. Restore cancelled internally.
Recommended Action:
Check DRF logs for details.

Error Message:
CCM_DRF_MASTER-DRF-3-DRFMABackupComponentFailure: DRF was unable to backup at least one component. Reason [String]
Explantion:
DRF requested a component to backup its' data. However, there was an error during the backup process and the component was not backed up.
Recommended Action:
Please check the component backup logs and contact support if needed.

Error Message:
CCM_DRF_MASTER-DRF-3-DRFMARestoreComponentFailure: DRF was unable to restore at least one component. Reason [String]
Explantion:
DRF requested a component to restore its' data. However, there was an error during the restore process and the component was not restored.
Recommended Action:
Please check the component restore logs and contact support if needed.

Error Message:
CCM_DRF_MASTER-DRF-3-DRFMABackupNodeDisconnect: The node being backed up disconnected from the Master Agent prior to being fully backed up. Reason [String]
Explantion:
The DRF Master Agent was running a backup operation on a CCM cluster, when one of the nodes disconnected before the backup operation was completed.
Recommended Action:
Please check the computer that disconnected during backup. If the computer was accidentally shutdown, restart the backup.

Error Message:
CCM_DRF_MASTER-DRF-3-DRFNoRegisteredComponent: No registered components available, backup failed. Reason [String]
Explantion:
DRF backup failed since no registered components are available.
Recommended Action:
Ensure at least one component is registered before attempting a backup.

Error Message:
CCM_DRF_MASTER-DRF-3-DRFNoRegisteredFeature: No feature selected for backup. Reason [String]
Explantion:
No feature selected for backup
Recommended Action:
Ensure at least one feature is configured before attempting a backup.

Error Message:
CCM_DRF_MASTER-DRF-3-DRFMARestoreNodeDisconnect: The node being restored disconnected from the Master Agent prior to being fully restored. Reason [String]
Explantion:
The DRF Master Agent was running a restore operation on a CCM cluster, when one of the nodes disconnected before the restore operation was completed.
Recommended Action:
Please check the computer that disconnected during restore. If the computer was accidentally shutdown, restart the restore.

Error Message:
CCM_DRF_MASTER-DRF-3-DRFSftpFailure: DRF sftp operation has failed. Reason [String]
Explantion:
DRF sftp operation has failed.
Recommended Action:
Ensure that the destination server is available, has appropriate permissions and sftp daemon is running.

Error Message:
CCM_DRF_MASTER-DRF-3-DRFRegistrationFailure: DRF Registration operation failed. Reason [String]
Explantion:
DRF Registration operation failed.
Recommended Action:
DRF Registration failed for a component due to some internal error. Check the DRF logs and contact support if needed.

Error Message:
CCM_DRF_MASTER-DRF-3-DRFBackupCancelInternalError: DRF Backup operation has encountered an error. Backup cancelled internally. Reason [String]
Explantion:
DRF Backup operation has encountered an error. Backup cancelled internally.
Recommended Action:
Check DRF logs for details.

Error Message:
CCM_DRF_MASTER-DRF-4-DRFLogDirAccessFailure: DRF couldn't access the log directory. Reason [String]
Explantion:
DRF couldn't access the log directory.
Recommended Action:
Ensure that the DRF user has required permission/enough space on DRF Log and Trace directory

Error Message:
CCM_DRF_MASTER-DRF-4-DRFComponentDeRegistered: DRF succesfully de-registered the requested component. Reason [String]
Explantion:
DRF succesfully de-registered the requested component.
Recommended Action:
Ensure that the component deregistered is not needed for further backup/restore operation.

Error Message:
CCM_DRF_MASTER-DRF-4-DRFDeRegistrationFailure: DRF de-registration request for a component failed. Reason [String]
Explantion:
DRF de-registration request for a component failed.
Recommended Action:
Please check the DRF logs and contact support if needed.

Error Message:
CCM_DRF_MASTER-DRF-4-DRFDeRegisteredServer: DRF automatically de-registered all the components for a server. Reason [String]
Explantion:
This server might have got disconnected from CCM cluster.
Recommended Action:
Nothing.

Error Message:
CCM_DRF_MASTER-DRF-4-DRFSchedulerDisabled: DRF Scheduler is disabled because no configured features available for backup. Reason [String]
Explantion:
DRF Scheduler is disabled because no configured features available for backup.
Recommended Action:
Ensure at least one feature is configured for the scheduled backup to run.

Error Message:
CCM_DRF_MASTER-DRF-6-DRFComponentRegistered: DRF Succesfully Registered the requested component. Reason [String]
Explantion:
DRF Succesfully Registered the requested component.
Recommended Action:
Ensure that the registered component is needed for backup/restore operation.

Error Message:
CCM_DRF_MASTER-DRF-6-DRFSchedulerUpdated: DRF Scheduled backup configurations is updated automatically due to feature DeRegistration. Reason [String]
Explantion:
DRF Scheduled backup configurations is updated automatically due to feature DeRegistration.
Recommended Action:
Ensure that the new configurations is appropriate one for the backup/restore operation.

Error Message:
CCM_DRF_MASTER-DRF-6-DRFBackupCompleted: DRF backup completed successfully. Reason [String]
Explantion:
DRF backup completed successfully.
Recommended Action:
Ensure that the backup operation completed successfully.

Error Message:
CCM_DRF_MASTER-DRF-6-DRFRestoreCompleted: DRF restore completed successfully. Reason [String]
Explantion:
DRF restore completed successfully.
Recommended Action:
Ensure that the restore operation completed successfully.

Error Message:
CCM_DRF_MASTER-DRF-3-DRFFailure: DRF Backup or Restore process has failed. Reason [String]
Explantion:
DRF Backup or Restore process encountered errors.
Recommended Action:
Check DRF logs for further details.

Error Message:
CCM_DRF_MASTER-DRF-4-DRFNoBackupTaken: A valid backup of the current system was not found. Reason [String]
Explantion:
A valid backup of the current system was not found after an Upgarde/Migration or Fresh Install.
Recommended Action:
It is recommended to perform a Backup using the Disaster Recovery System.

Error Message:
CCM_TCT-LPMTCT-4-LogPartitionLowWaterMarkExceeded: The percentage of used disk space in the log partition has exceeded the configured low water mark. UsedDiskSpace [String] MessageString [String]
Explantion:
The percentage of used disk space in the log partition has exceeded the configured low water mark.
Recommended Action:
Login into RTMT and check the configured threshold value for LogPartitionLowWaterMarkExceeded alert in Alert Central. If the configured value is set to a lower than the default threshold value unintentionally, change the value to default. Also, examine the trace and log file setting for each of the application in trace configuration page under CCM Serviceability. If the number of configured traces / logs is set to greater than 1000, adjust the trace settings from trace configuration page to default. Also, clean up the trace files that are less than a week old. You can clean up the traces using cli "file delete" or using Remote Browse from RTMT Trace and Log Central function.

Error Message:
CCM_TCT-LPMTCT-2-LogPartitionHighWaterMarkExceeded: The percentage of used disk space in the log partition has exceeded the configured high water mark. UsedDiskSpace [String] MessageString [String]
Explantion:
The percentage of used disk space in the log partition has exceeded the configured high water mark. Some of the core file and / or trace files will be purged until the percentage of used disk space in the log partition gets below the configured low water mark.
Recommended Action:
Login into RTMT and check the configured threshold value for LogPartitionHighWaterMarkExceeded alert in Alert Central. If the configured value is set to a lower than the default threshold value unintentionally, change the value to default. If you continue to receive this alert for half an hour after receiving the 1st alert, check for the disk usage for Common partition under "Disk Usage" tab in RTMT. If the disk usage shown under that tab is higher than configured value in LogPartitionLowWaterMarkExceeded alert configuration, contact Cisco TAC to troubleshoot the cause of high disk usage in Common partition.

Error Message:
CCM_TCT-LPMTCT-6-LogFileSearchStringFound: The search string has been found in the log file. SearchString [String]
Explantion:
Trace and Log Central has found the search string that the user has configured
Recommended Action:
If sysadmin is interested in collecting the traces around the time of generation of alert, use Trace and Log Central to collect the traces for that service.

Error Message:
CCM_TCT-LPMTCT-4-LogCollectionJobLimitExceeded: The number of Log Collection Jobs have excceded the allowed limit JobType [String]
Explantion:
The number of concurrent trace collection from the server has exceeded the allowed limit of trace collection. The allowed limit is defined in the documentation for Trace and Log Central, however this limit can not be changed by sysadmin.
Recommended Action:
Cancel one or more of the currently running queries and try again to configure the trace collection.

Error Message:
CCM_TCT-LPMTCT-3-ScheduledCollectionError: An error occurred while executing scheduled collection. JobID [String] Reason [String]
Explantion:
Scheduled collection encountered an error during execution.
Recommended Action:
Review configuration for scheduled collection job under Job Status window.

Error Message:
CCM_TCT-LPMTCT-2-CoreDumpFileFound: The new core dump file(s) have been found in the system. TotalCoresFound [String] CoreDetails [String] Core1 [String] Core2 [String] Core3 [String] Core4 [String] Core5 [String] Core6 [String]
Explantion:
One of the component has crashed and generated a core dump. Use admin cli or RTMT to featch the backtrace.
Recommended Action:
This serious internal error should be investigated by the Cisco Technical Assistance Center (TAC). Before contacting TAC, Login to cli on CCM serve and run "active analyze core file name" to generate the backtrace of the core dump. The core file name is listed in the alert details. After the analyze command is executed, collect the backtrace using cli command "file get activelog analyze" or "Collect Traces" option from RTMT. Send these backtraces to Cisco TAC for further analysis.

Error Message:
CCM_TCT-LPMTCT-3-SparePartitionLowWaterMarkExceeded: The percentage of used disk space in the spare partition has exceeded the configured low water mark. UsedDiskSpace [String] MessageString [String]
Explantion:
The percentage of used disk space in the spare partition has exceeded the configured low water mark.
Recommended Action:
Login into RTMT and check the configured threshold value for SparePartitionLowWaterMarkExceeded alert in Alert Central. If the configured value is set to a lower than the default threshold value unintentionally, change the value to default. Also, examine the trace and log file setting for each of the application in trace configuration page under CCM Serviceability. If the number of configured traces / logs is set to greater than 1000, adjust the trace settings from trace configuration page to default. Also, clean up the trace files that are less than a week old. You can clean up the traces using cli "file delete" or using Remote Browse from RTMT Trace and Log Central function.

Error Message:
CCM_TCT-LPMTCT-4-SparePartitionHighWaterMarkExceeded: The percentage of used disk space in the spare partition has exceeded the configured high water mark. UsedDiskSpace [String] MessageString [String]
Explantion:
The percentage of used disk space in the spare partition has exceeded the configured high water mark. Some of the trace files will be purged until the percentage of used disk space in the spare partition gets below the configured low water mark
Recommended Action:
Login into RTMT and cheek the configured threshold value for SparePartitionHighWaterMarkExceeded alert in Alert Central. If the configured value is set to a lower than the default threshold value unintentionally, change the value to default. If you continue to receive this alert for half an hour after receiving the 1st alert, check for the disk usage for Spare partition under "Disk Usage" tab in RTMT. If the disk usage shown under that tab is higher than configured value in SparePartitionLowWaterMarkExceeded alert configuration, contact Cisco TAC to troubleshoot the cause of high disk usage in Common partition.

Error Message:
CCM_TOMCAT_APPS-LOGIN-6-CLM_IPSecCertUpdated: IPSec self-signed cert updated. NodeName [String]
Explantion:
The IPSec self-signed cert from a peer node in the cluster has been imported due to a change.
Recommended Action:
No action is required.

Error Message:
CCM_TOMCAT_APPS-LOGIN-6-CLM_IPAddressChange: IP address change in cluster. NodeName [String] NodeOldIP [String] NodeNewIP [String]
Explantion:
The IP address of a peer node in the cluster has changed.
Recommended Action:
No action is required.

Error Message:
CCM_TOMCAT_APPS-LOGIN-6-CLM_PeerState: Current ClusterMgr session state. NodeName [String] NodeState [String]
Explantion:
The ClusterMgr session state with another node in the cluster has changed to the current state.
Recommended Action:
No action is required.

Error Message:
CCM_TOMCAT_APPS-LOGIN-1-CLM_MsgIntChkError: ClusterMgr message integrity check error. NodeIP [String]
Explantion:
ClusterMgr has received a message which has failed a message integrity check. This can be an indication that another node in the cluster is configured with the wrong security password.
Recommended Action:
Verify message is coming from an expected IP address. Verify the security password on that node.

Error Message:
CCM_TOMCAT_APPS-LOGIN-3-CLM_UnrecognizedHost: ClusterMgr unrecognized host. NodeIP [String]
Explantion:
ClusterMgr has received a message from an IP address which is not configured as a node in this cluster.
Recommended Action:
Verify that this IP address is currently configured as a server in this cluster.

Error Message:
CCM_TOMCAT_APPS-LOGIN-4-CLM_ConnectivityTest: CLM Connectivity Test Failed. NodeIP [String] ErrorString [String]
Explantion:
Cluster Manager detected a network error.
Recommended Action:
Verify connectivity between cluster nodes and fix any network issues.

Error Message:
CCM_RTMT-RTMT-3-RTMT_ALERT: RTMT Alert AlertName [String] AlertDetail [String]
Explantion:
A Real-Time Monitoring Tool (RTMT) process in the AMC service uses the alarm mechanism to facilitate delivery of RTMT alerts in RTMT AlertCentral or via email.
Recommended Action:
Check AlertCentral in RTMT or any alerts that you have received via email to determine what issue has occurred and learn the recommended actions to resolve it. In AlertCentral, right-click the alert to open the alert information.

Error Message:
CUP_CA-GENERIC-3-EspConfigAgentMemAllocError: Cisco UP Config Agent service was unable to allocate memory Location [String]
Explantion:
Cisco UP Config Agent service failed to allocate memory
Recommended Action:
Using RTMT, verify system memory is low or exhausted. This alarm may indicate the system is overloaded which may require reassigning users to other nodes in the Cisco Unified Presence cluster. You can reassign users to other nodes using the Topology page on the Cisco Unified Presence Administration GUI

Error Message:
CUP_CA-GENERIC-3-EspConfigAgentFileWriteError: Cisco UP Config Agent service was unable to write to the filesystem Reason [String]
Explantion:
Cisco UP Config Agent service failed to write to a file. This may indicate the system is out of memory
Recommended Action:
Using RTMT, verify disk space is low or exhausted. This alarm may indicate the system is overloaded which may require reassigning users to other nodes in the Cisco Unified Presence cluster. You can reassign users to other nodes using the Topology page on the Cisco Unified Presence Administration GUI

Error Message:
CUP_CA-GENERIC-3-EspConfigAgentSharedMemoryStaticRouteError: Cisco UP Config Agent service could not access static route shared memory
Explantion:
Cisco UP Config Agent service failed to access static routes in shared memory. This may indicate the system is out of memory
Recommended Action:
Using RTMT, verify system shared memory is low or exhausted. This alarm may indicate the system is overloaded which may require reassigning users to other nodes in the Cisco Unified Presence cluster. You can reassign users to other nodes using the Topology page on the Cisco Unified Presence Administration GUI

Error Message:
CUP_CA-GENERIC-5-EspConfigAgentServiceStartFailed: Cisco UP Config Agent failed to start a feature service
Explantion:
Cisco UP Config Agent failed to start one of the feature services
Recommended Action:
Please use the serviceability page to check status and start the service manually

Error Message:
CUP_CA-GENERIC-5-EspConfigAgentServiceStopFailed: Cisco UP Config Agent failed to stop a feature service
Explantion:
Cisco UP Config Agent failed to stop one of the feature services
Recommended Action:
Please use the serviceability page to check status and stop the service manually

Error Message:
CUP_CA-GENERIC-4-EspConfigAgentNetworkOutage: Cisco UP Config Agent network outage
Explantion:
Cisco UP Config Agent noticed a network outage
Recommended Action:
Using RTMT, verify system health and network connectivity.

Error Message:
CUP_CA-GENERIC-4-EspConfigAgentNetworkRestored: Cisco UP Config Agent network restored
Explantion:
Cisco UP Config Agent noticed network was restored
Recommended Action:
Using RTMT, verify system health and network connectivity.

Error Message:
CUP_CA-GENERIC-4-EspConfigAgentHighMemoryUtilization: Virtual memory utilization has exceeded the configured threshold
Explantion:
Available free virtual memory is low
Recommended Action:
Use RTMT to monitor memory use and reduce system load to improve performance if necessary. The memory watermark can be configured through the Cisco Unified Presence Administration GUI Service Parameters for the Cisco UP Config Agent

Error Message:
CUP_CA-GENERIC-5-EspConfigAgentHighMemoryUtilizationClear: Virtual memory utilization is below the configured low watermark
Explantion:
Virtual memory use exceeded the high memory use watermark, but has since fallen below the low memory watermark
Recommended Action:
Notification purposes only; no action is required

Error Message:
CUP_CA-GENERIC-4-EspConfigAgentHighCPUUtilization: CPU utilization has exceeded the configured threshold
Explantion:
CPU use is high
Recommended Action:
Use RTMT to monitor CPU use and reduce system load to improve performance if necessary. The CPU watermark can be configured through the Cisco Unified Presence Administration GUI Service Parameters for the Cisco UP Config Agent

Error Message:
CUP_CA-GENERIC-5-EspConfigAgentHighCPUUtilizationClear: CPU utilization is below the configured low watermark
Explantion:
CPU use exceeded the high CPU use watermark, but has since fallen below the low CPU watermark
Recommended Action:
Notification purposes only; no action is required

Error Message:
CUP_CA-GENERIC-3-EspConfigAgentLocalDBAccessError: Cisco UP Config Agent service was unable to access the local CUP database
Explantion:
Cisco UP Config Agent service failed to read or write to the local CUP database. This may indicate a DB health issue.
Recommended Action:
Using RTMT, verify system health. Verify that the service "A Cisco DB" is running.

Error Message:
CUP_CA-GENERIC-4-EspConfigAgentRemoteDBAccessError: Cisco UP Config Agent service was unable to access a remote CUP database
Explantion:
Cisco UP Config Agent service failed to read or write to a remote CUP database in the local cluster. This may indicate the system a DB health issue.
Recommended Action:
Verify that the service "A Cisco DB" is running on the node specified in the alert. Sometimes these errors can be transient. In some cases the Config Agent may be accessing remote nodes that are not available for some reason. If that is the case then this error is expected. This would happen in a user reassignment to a node that is not installed or available.

Error Message:
CUP_CA-GENERIC-4-EspConfigAgentProxyDomainNotConfigured: Cisco UP Config Agent service requires the Proxy Domain service paramter for service Cisco UP Proxy to be configured.
Explantion:
Cisco UP Config Agent service uses the Proxy Domain to properly generate ACLs. If not configured this could lead to routing failures.
Recommended Action:
Go to the Service Parameters drop down menu on the CUP publisher. Select the Cisco UP Proxy service. Enter the CUP domain into the Proxy Domain service parameter and save.

Error Message:
CCM_CALLMANAGER-CALLMANAGER-4-TotalProcessesAndThreadsExceededThresholdStart: The current total number of processes and threads has exceeded the maximum number of tasks configured for Cisco RIS Data Collector service parameter. This situation could indicate some process is leaking or some process has thread leaking. NumberOfProcesses [String] NumberOfThreads [String] Reason [String] ProcessWithMostInstances [String] ProcessWithMostThreads [String]
Explantion:
The current total number of processes and threads has exceeded the maximum number of tasks. This situation could indicate some process is leaking or some process has thread leaking.
Recommended Action:
Check the Cisco RIS Data Collector service parameter, Maximum Number of Processes and Threads, to see if the parameter has been set to a low value. If it has been, set the value higher or use the default value. Another possible action is that when a new Cisco product is integrated into Cisco Unified Communications Manager (Unified CM), new processes or threads are added to the system. Even in the normal process load situation, it's possible that the total number of processes and threads has exceeded the configured or default value of the Cisco RIS Data Collector service parameter, Maximum Number of Processes and Threads. Set that parameter to the maximum allowed value. You can also review the details of this alarm to check the ProcessWithMostThreads description and the ProcessWithMostInstances description to discover which processes have the most threads and the most instances. Determine whether these values are reasonable for this process; if not, contact the owner of the process for troubleshooting the reasons why the thread count or the number of process instances is so high. It is also possible that Cisco RIS Data Collector sent a false alarm, which would indicate a defect in the Cisco RIS Data Collector service. To determine if this is the cause of the alarm - after you have checked all the other recommended actions described here - use RTMT to check the System object for performance counters Total Threads and Total Processes to confirm that the values in those counters do not exceed the value configured in the Cisco RIS Data Collector service parameter, Maximum Number of Processes and Threads. If the counters do not show a value that is higher than what is configured in the service parameter, restart Cisco RIS Data Collector service. If the alarm persists after restarting the service, go to Cisco Unified Serviceability and collect trace logs (Trace > Configuration) for Cisco Syslog, Cisco RIS Data Collector, Cisco AMC Service, and Cisco RIS Perfmon Logs and contact Cisco Technical Assistance Center (TAC) for detailed assistance.

Error Message:
CCM_CALLMANAGER-CALLMANAGER-5-TotalProcessesAndThreadsExceededThresholdEnd: The current total number of processes and threads is less than the maximum number of tasks configured in the Cisco RIS Data Collector service parameter, Maximum Number of Processes and Threads. NumberOfProcesses [String] NumberOfThreads [String] Reason [String]
Explantion:
The current total number of processes and threads is less than the maximum number of tasks that has been configured in the Cisco RIS Data Collector service parameter, Maximum Number of Processes and Threads. This can occur because a product which was integrated into Cisco Unified Communications Manager has been disabled or deactivated, which reduces the total number of processes and threads running on the system. Another cause for the number of processes or thread to decrease is that one or more processes has been stopped, which reduces the total number of processes and threads running on the system.
Recommended Action:
This alarm is for information purposes only; no action is required.

Error Message:
CUP_ICSA-GENERIC-2-CUPInterclusterSyncAgentAXLConnectionFailed: Cisco UP Intercluster Sync Agent service failed authentication hostname [String]
Explantion:
Cisco UP Intercluster Sync Agent service failed authentication to the remote Cisco Unified Presence cluster and therefore is unable to connect
Recommended Action:
Please verify the AXL credentials are correct and whether the Cisco AXL Web service is activated and running on the remote Cisco Unified Presence cluster

Error Message:
CUP_ICSA-GENERIC-2-CUPInterclusterSyncAgentPeerSyncFailed: Cisco UP Intercluster Sync Agent service failed to sync remote peer data hostname [String] exceptionMessage [String]
Explantion:
Cisco UP Intercluster Sync Agent service failed to sync user location data from the remote Cisco Unified Presence cluster
Recommended Action:
Verify that the remote Cisco Unified Presence peer is not also configured as a node in the local cluster and run the Cisco Unified Presence System Troubleshooter for more information regarding this issue

Error Message:
CUP_ICSA-GENERIC-2-CUPInterclusterSyncAgentFailedToSendCN: Cisco UP Intercluster Sync Agent service failed to send change notification to remote cluster hostname [String]
Explantion:
Cisco UP Intercluster Sync Agent service failed to send change notifications to the remote Cisco Unified Presence cluster
Recommended Action:
Please verify the AXL credentials are correct and whether the Cisco AXL Web service is activated and running on the remote Cisco Unified Presence cluster

Error Message:
CUP_ICSA-GENERIC-6-CUPICSACertificateDBDeletionFailed: Cisco UP Intercluster Sync Agent service failed to remove certificate information
Explantion:
Cisco UP Intercluster Sync Agent service failed to remove Certificate information from the database because it was non-existent
Recommended Action:
Notification purposes only; no action is required

Error Message:
CUP_ICSA-GENERIC-3-CUPInterclusterSyncAgentDuplicateUser: Cisco UP Intercluster Sync Agent service has detected a duplicate user between two (or more) Cisco Unified Presence clusters userid [String] servers [String]
Explantion:
Cisco UP Intercluster Sync Agent service has detected a duplicate licensed user between two (or more) Cisco Unified Presence clusters. Duplicate users across clusters may cause presence outage issues
Recommended Action:
Run the Cisco Unified Presence System Troubleshooter for more details related to this issue

Error Message:
CUP_ICSA-GENERIC-2-CUPInterclusterSyncAgentPeerDuplicate: Cisco UP Intercluster Sync Agent service failed to sync with remote peer hostname [String] existingPeer [String]
Explantion:
Cisco UP Intercluster Sync Agent service failed to sync user location data from a remote peer. The remote peer is from a Cisco Unified Presence cluster which already has a peer in the local cluster
Recommended Action:
Verify that the hostname of the remote peer is not a secondary node from the identified existing peer. If the new peer is a secondary node, then remote this peer from the Cisco Unified Presence Administration GUI Inter-cluster details page. You can also run the System Troubleshooter for more details

Error Message:
CUP_ICSA-GENERIC-2-CUPICSACertificateFingerPrintMisMatch: Cisco UP Intercluster Sync Agent service detected a fingerprint mismatch on the certificate being processed SubjectCN [String] IssuerCN [String]
Explantion:
Cisco UP Intercluster Sync Agent service detected a fingerprint mismatch on the certificate being processed
Recommended Action:
Use the Cisco Unified Presence Platform GUI to compare the certificates loaded on this server with the certificates on the source server. It may necessary to delete the problem certificates and reload them

Error Message:
CUP_ICSA-GENERIC-2-CUPICSACertificateValidationFailure: Cisco UP Intercluster Sync Agent service detected a validation error on the certificate being processed SubjectCN [String] IssuerCN [String] ErrorCode [String]
Explantion:
Cisco UP Intercluster Sync Agent service detected a validation error on the certificate being processed
Recommended Action:
Use the Cisco Unified Presence Platform GUI to compare the certificates loaded on this server with the certificates on the source server. It may necessary to delete the problem certificates and reload them

Error Message:
CUP_ICSA-GENERIC-4-CUPICSACertificateCASignedTrustCertFound: Cisco UP Intercluster Sync Agent service detected a signed CA trust certificate SubjectCN [String] IssuerCN [String]
Explantion:
Cisco UP Intercluster Sync Agent service detected a signed CA trust certificate
Recommended Action:
Signed CA trust certificates are not allowed. Only unsigned CA trust certificates are allowed

Error Message:
CUP_ICSA-GENERIC-2-CUPInterclusterSyncAgentFailedToCleanUpPeer: Cisco UP Intercluster Sync Agent service failed to successfuly clean up after a peer was removed during a sync. hostname [String]
Explantion:
Cisco UP Intercluster Sync Agent service failed to successfully clean up data after a peer was removed during a sync.
Recommended Action:
Verify that the Cisco DB service is still up and accepting connections. See Inter Cluster Sync Agent logs for further root cause.