Note

Optional parameter is indicated with the notation {Optional}. Application or Component may decide not to use that parameter in the alarm message.

Order of the parameters in an alarm message can change and it is decided by the Application or Component.

If the error message contains UNKNOWN_PARAMNAME, the parameter immediately following the UNKNOWN_PARAMNAME has not yet been updated in the alarm catalog. If this occurs, the error message is given a severity-level of 3, irrespective of the default severity-level for that error message.

%UC_CMI-6-CMIServiceStatus: %[Priority=String][AppID=String][ClusterID=String][NodeID=String]: Service is running and working properly.

Explanation   CMI service is running and working properly

Recommended Action   Informational purpose only; no action is required

Error Message

%UC_CMI-1-StopBitConfigurationError: %[StopBit=String][AppID=String][ClusterID=String][NodeID=String]: The Cisco Messaging Interface service parameter, Stop Bits, has an invalid configuration.

Explanation   An invalid stop bit has been configured for the serial port that CMI uses to connect to the voice messaging system. It is possible that the Stop Bits value has been updated via AXL or a CLI command where validation of the value was not performed. For this reason, it is best to set this value in the Service Parameter Configuration window in Cisco Unified CM Administration so that the value can be validated against the accepted range of values for this field.

Recommended Action   Verify that the Cisco Messaging Interface service parameter Stop Bits is set to a valid (allowable) value

Error Message

%UC_CMI-1-ParityConfigurationError: %[Parity=String][AppID=String][ClusterID=String][NodeID=String]: The CMI service parameter, Parity, has an invalid configuration.

Explanation   An invalid parity has been configured for the serial port that CMI uses to connect to the voice messaging system. It is possible that the parity value has been updated via AXL or a CLI command where validation of the value was not performed. For this reason, it is best to set this value in the Service Parameter Configuration window in Cisco Unified CM Administration so that the value can be validated against the accepted range of values for this field.

Recommended Action   Verify that the Cisco Messaging Interface service parameter Parity is set to a valid (allowable) value

Error Message

%UC_CMI-5-SMDIMessageError: %[InvalidDN=String][AppID=String][ClusterID=String][NodeID=String]: SMDI message contains invalid DN.

Explanation   Some voice messaging systems send SMDI messages to Cisco Unified Communications Manager (Unified CM) with an invalid DN specifically for the purpose of verifying that Unified CM is functioning properly. In such cases, if the Validate DNs service parameter is set to True, CMI triggers this alarm because the DN cannot be found in the Unified CM database.

Recommended Action   Verify that the Cisco Messaging Interface service parameter Validate DNs is set to false

Error Message

%UC_CMI-5-SMDICmdError: %[SMDICmd=String][AppID=String][ClusterID=String][NodeID=String]: CMI receives an invalid incoming SMDI message.

Explanation   There are two kinds of incoming messages that Cisco Unified Communications Manager can accept from the voice messaging system; they are OP:MWI(SP)nnnnnnn!(D) and RMV:MWI(SP)nnnnnnn!(D) (where:nnnnnnnnnn = station number (can be 7 or 10 digits), (D) = End Of Transmission, (SP) = space). The first message activates the message waiting indicator (MWI). The second deactivates the message waiting indicator. CMI triggers this alarm if the received MWI message doesn't have one of the acceptable formats as described.

Recommended Action   Contact the vendor of the third-party voice messaging system and discover why it is sending SMDI message with an invalid format

Error Message

%UC_CMI-1-SerialPortOpeningError: %[OpeningError=String][AppID=String][ClusterID=String][NodeID=String]: When CMI tries to open the serial port, the operating system returns an error.

Explanation   For a system running CMI, the serial port through which the voice messaging system is connected is always USB0, and that value is configured in the Cisco Messaging Interface service parameter, Serial Port. It is possible that the Serial Port value has been updated via AXL or a CLI command where validation of the value was not performed. CMI triggers this alarm if the value in the Serial Port service parameter is anything other than USB0.

Recommended Action   Ensure that USB0 is configured in the Cisco Messaging Interface service parameter Serial Port. Also, physically confirm that the cable is firmly connected to the USB0 port.

Error Message

%UC_CMI-3-SerialPortGetStatusError: %[GetStatusError=String][AppID=String][ClusterID=String][NodeID=String]: When CMI tries to get the status of serial port, the operating system returns an error.

Explanation   CMI triggers this alarm when it can't get the status of the serial port. An inability to receive serial port status information could be caused by a loose or disconnected USB cable.

Recommended Action   Make sure that the cable connecting the USB0 port and voice messaging system is firmly connected.

Error Message

%UC_CMI-3-SerialPortSetStatusError: %[SetStatusError=String][AppID=String][ClusterID=String][NodeID=String]: When CMI tries to set the status of serial port, the operating system returns an error.

Explanation   CMI triggers this alarm when it can't set the status of the serial port. An inability to receive serial port status information could be caused by a loose or disconnected USB cable.

Recommended Action   Make sure that the cable connecting the USB0 port and voice messaging system is firmly connected.

Error Message

%UC_CMI-3-WritingFileFailure: %[ErrorInfo=String][AppID=String][ClusterID=String][NodeID=String]: CMI failed to write SMDI messages to the serial port.

Explanation   CMI opened the serial port, however it failed to successfully write data to the serial port because the serial port returned an invalid handle value to CMI. The serial port may have returned an invalid handle because the system did not properly detect the USB cable.

Recommended Action   Make sure that the cable connecting the USB0 port and voice messaging system is firmly connected.

Error Message

%UC_CMI-3-ReadingFileFailure: %[ErrorInfo=String][AppID=String][ClusterID=String][NodeID=String]: CMI failed to read SMDI messages from the serial port.

Explanation   CMI opened the serial port, however it failed to successfully read data from the serial port because the serial port returned an invalid handle value to CMI. The serial port may have returned an invalid handle because the system did not properly detect the USB cable.

Recommended Action   Make sure that the cable connecting the USB0 port and voice messaging system is firmly connected.

Error Message

%UC_CMI-3-InvalidPortHandle: %[ErrorInfo=String][AppID=String][ClusterID=String][NodeID=String]: The handle for the opened serial port is invalid.

Explanation   CMI cannot read/write to the serial port because the serial port returned an invalid handle value to CMI. The serial port may have returned an invalid handle because the system did not properly detect the USB cable.

Recommended Action   Make sure that the cable connecting the USB0 port and voice messaging system is firmly connected.

Error Message

%UC_CMI-1-VMDNConfigurationError: %[VoiceMailDN=String][AppID=String][ClusterID=String][NodeID=String]: The Voice Mail DN for CMI is invalid.

Explanation   CMI can't register with Cisco Unified Communications Manager because of an invalid Voice Mail DN. This alarm occurs because the Cisco Messaging Interface service parameter, Voice Mail DN, is empty or has invalid characters other than digits (0-9). It is possible that the Voice Mail DN value has been updated via AXL or a CLI command where validation of the value was not performed. For this reason, it is best to set this value in the Service Parameter Configuration window in Cisco Unified CM Administration so that the value can be validated against the accepted range of values for this field.

Recommended Action   Check the CMI service parameter Voice Mail DN to confirm that a valid directory number has been configured.

Error Message

%UC_CMI-4-ThreadKillingError: %[ErrorInfo=String][AppID=String][ClusterID=String][NodeID=String]: An error occurred when CMI tried to stop the CMI service.

Explanation   As a normal part of the process of stopping the CMI service, open threads are closed (killed). This alarm indicates that a timeout occurred which means that the shutdown process is taking longer than expected, causing the operating system to return an error.

Recommended Action   Try restarting the CMI service. If the problem persists, collect the system/application event logs and the performance (perfmon) logs and report to Cisco Technical Assistance Center (TAC).

Error Message

%UC_CMI-4-MemAllocFailed: %[MemAllocFailure=String][AppID=String][ClusterID=String][NodeID=String]: CMI tried to allocate memory and failed.

Explanation   Cisco Unified Communications Manager tried to read the Cisco Messaging Interface service parameters but not enough memory was allocated for the task and so the information could not be read.

Recommended Action   Use the Real-Time Monitoring Tool to check performance counters related to system memory to learn whether any memory leaks or spikes in CPU are occurring. Correct any anomalous memory issues you find. If you do not find any issues with memory, collect the system/application event logs and the performance (perfmon) logs and report this alarm to the Cisco Technical Assistance Center (TAC).

Error Message

%UC_CMI-1-DBLException: %[DBLException=String][AppID=String][ClusterID=String][NodeID=String]: Unable to connect to the DB.

Explanation   When CMI service is started, it tries to read CMI Service Parameters from DB. During this, if CMI cannot connect to the database, it triggers this alarm.

Recommended Action   Check Database connection, then restart CMI.

Error Message

%UC_CMI-1-CMIException: %[CMIException=String][AppID=String][ClusterID=String][NodeID=String]: Error while reading the database.

Explanation   This alarm is always associated with other alarms, which are triggered due to configuring CMI service parameter with invalid values or due to invalid handle value returned by the serial port.

Recommended Action   Refer to the associated alarm for further information.

Error Message

%UC_CMI-1-UnknownException: %[AppID=String][ClusterID=String][NodeID=String]: Unknown error while connecting to DB.

Explanation   When CMI service is started, it tries to read CMI service parameters from DB. During this, if there is an unknown error, CMI triggers this alarm.

Recommended Action   Report to Customer Service representative.

Error Message

%UC_CMI-5-CMIServiceStarted: %[AppID=String][ClusterID=String][NodeID=String]: Service is now running.

Explanation   CMI service has been started and running

Recommended Action   Informational purpose only; no action is required

Error Message

%UC_CMI-5-CMIServiceStopped: %[AppID=String][ClusterID=String][NodeID=String]: Service is now stopping..

Explanation   CMI Service has been stopped.

Recommended Action   Informational purpose only; no action is required.

Error Message

%UC_CMI-7-CMIDebugAlarm: %[DebugMsg=String][AppID=String][ClusterID=String][NodeID=String]: This alarm is generated only for the purpose of debugging.

Explanation   CMI has several debug messages which simulate the real-time situations

Recommended Action   Report to Customer Service representative

Error Message

%UC_CMI-3-CCMConnectionError: %[Cisco Unified Communications Manager Name=String][AppID=String][ClusterID=String][NodeID=String]: CMI can't establish connection with the Cisco Unified Communications Manager.

Explanation   CMI can't establish connection with the Unified Communications Manager

Recommended Action   Check the address/status of the CallManager and the network

Error Message

%UC_CMI-3-DisconnectionToCCM: %[Cisco Unified Communications Manager Name=String][AppID=String][ClusterID=String][NodeID=String]: CMI loses the connection with Unified Communications Manager.

Explanation   CMI loses the connection with the Cisco Unified Communications Manager

Recommended Action   Check the status of the Unified Communications Manager and the Network

Error Message

%UC_CMI-2-WSAStartupFailed: %[ErrorInfo=String][AppID=String][ClusterID=String][NodeID=String]: Windows Socket startup failed.

Explanation   WinSock could not be started

Recommended Action   Report to Customer Service representative.

Error Message

%UC_CMI-5-ConfigParaNotFound: %[ParaNameInfo=String][AppID=String][ClusterID=String][NodeID=String]: CMI service configuration parameter is not found in Database.

Explanation   CMI cannot find this process configuration parameter in process configuration table.

Recommended Action   Report to Customer Service representative to get the database upgrade

Error Message

%UC_CMI-1-COMException: %[COMException=String][AppID=String][ClusterID=String][NodeID=String]: CMI catches an COM exception..

Explanation   CMI cannot find this process configuration parameter in process configuration table.

Recommended Action   Check system setting and resource, then restart system.

Error Message

%UC_CTI-4-ApplicationConnectionDropped: %[LastPDUNumber=UInt ][AppID=String][ClusterID=String][NodeID=String]: Application has dropped the connection to CTIManager.

Explanation   TCP or TLS connection between CTIManager and Application is disconnected

Recommended Action   Possible causes include Application server power outage, network power outage, network configuration error, network delay, packet drops or packet corruption. It is also possible to get this error if the Unified CM node or application server is experiencing high CPU usage. Verify the application is up and running, verify network connectivity between the application server and Unified CM, and verify the CPU utilization is in the safe range for application server and Unified CM (this can be monitored using RTMT via CPU Pegging Alert)

Error Message

%UC_CTI-4-CtiMaxConnectionReached: %[AppID=String][ClusterID=String][NodeID=String]: Maximum number of application connections is reached; application connection rejected.

Explanation   Maximum number of CTI connections has been reached, no new connection will be accepted unless an existing connection is closed

Recommended Action   Check the CTI Manager service parameter Maximum CTI Connections for the maximum number of connections. Carefully consider increasing the service parameter value or disconnecting CTI applications that are unnecessary. Refer to Unified CM Solution Reference Network Design document in www.cisco.com based on the version you are using for maximum number of applications and devices supported by CTI

Error Message

%UC_CTI-4-InvalidQBEMessage: %[CTIConnectionType=String][InstanceNumber=Long][PDUNumber=Long][AppID=String][ClusterID=String][NodeID=String]: An invalid QBE PDU is received.

Explanation   QBE PDU from application is invalid

Recommended Action   This alarm indicates that TSP/JTAPI has reported a QBE PDU that cannot be recognized by CTIManager. Contact the support organization for the affected application, install the JTAPI or TSP plugin and restart the application. JTAPI/TSP plugins are available from the Find and List Plugins window in Cisco Unified CM Administration (Application > Plugins)

Error Message

%UC_CTI-3-CtiProviderOpenFailure: %[CTIconnectionId=Long][LoginUserId=String][Reason=Enum][IPaddress=String][IPv6address=String][AppID=String][ClusterID=String][NodeID=String]: CTI application failed to open provider; application startup failed.

Explanation   The application is unable to open provider. The IP address is shown in either IPv4 or IPv6 format depending on the Application's IP addressing mode

Recommended Action   Review the reason code and the recommended action within the reason code

Reason Code - Enum Definitions

Enum Definitions - Reason

%UC_CTI-4-CtiQbeFailureResponse: %[ErrorCode=ULong][SeqNumber=Long][ErrorMessageString=String][AppID=String][ClusterID=String][NodeID=String]: Requested operation from the application has failed.

Explanation   The requested operation from the application could not be performed because of a normal or abnormal condition

Recommended Action   Verify whether the affected application is experiencing a problem. Contact the support organization for the affected application if the problem persists and provide sequence number and error message for further investigation

Error Message

%UC_CTI-6-CtiProviderClosed: %[LoginUserId=String][SeqNumber=Long][CTIconnectionId=Long][IPAddress=String][IPv6Address=String][Reason=Enum][AppID=String][ClusterID=String][NodeID=String]: CTI application connection has been closed.

Explanation   Application closed the provider. The IP address is shown in either IPv4 or IPv6 format depending on the Application's IP addressing mode

Recommended Action   This alarm is for informational purposes only; no action is required.

Reason Code - Enum Definitions

Enum Definitions - Reason

%UC_CTI-6-CtiProviderOpened: %[LoginUserId=String][SeqNumber=Long][Version=String][CTIconnectionId=Long][IPAddress=String][IPv6Address=String][CmAssignedAppID=Long][AppID=String][ClusterID=String][NodeID=String]: CTI application connection opened..

Explanation   Application opened the provider successfully. The IP address is shown in either IPv4 or IPv6 format depending on the Application's IP addressing mode.

Recommended Action   This alarm is for informational purposes only; no action is required.

Error Message

%UC_CTI-3-UnableToRegisterwithCallManagerService: %[CmNodeID=Long][AppID=String][ClusterID=String][NodeID=String]: Unable to communicate with the Cisco CallManager service.

Explanation   CTI cannot communicate with Cisco CallManager service to register supplementary service features

Recommended Action   Check the status of the Cisco CallManager service in Cisco Unified Serviceability > Tools > Control Center - Featured Services. At least one Cisco CallManager service should be running in the cluster for CTIManager to register feature managers. Restart the CTIManager service if the problem persists. If CallManager service is active, verify network connectivity between the Unified CM node that hosts CTIManager service and Unified CM node that hosts CallManager service

Error Message

%UC_CTI-4-CtiProviderCloseHeartbeatTimeout: %[AppID=String][ClusterID=String][NodeID=String]: CTI heartbeat timed out; application disconnected.

Explanation   CTI heartbeat timeout occurred causing CTIManager to close the application connection

Recommended Action   Heartbeat timeout could occur due to high CPU usage or network connectivity problems. Check for and fix any network issues or high CPU usage on the application server. If the application server is running the Microsoft Windows OS use Task Manager or Perfmon to determine the CPU usage. For applications in Linux use the top command to review CPU usage

Error Message

%UC_CTI-4-CtiProviderClosePeerCertExpired: %[AppID=String][ClusterID=String][NodeID=String]: CTI Peer Certificate Expired; Application Disconnected.

Explanation   CTI Peer certificate expired causing CTIManager to close the application connection

Recommended Action   The validity period of the peer certificate used for making SSL connection is expired. Please update the certificate

Error Message

%UC_CTI-4-CtiProviderPeerCertExpireSoon: %[AppID=String][ClusterID=String][NodeID=String]: CTI Peer Certificate will expire soon; If expired, application will disconnect.

Explanation   CTI Peer certificate expire soon.

Recommended Action   The validity period of the peer certificate used for making SSL connection will expire soon. Please update the new certificate for getting continous service

Error Message

%UC_CTI-4-CtiIncompatibleProtocolVersion: %[MsgVersion=VoidPtr][CompatibleVersions=VoidPtr][CurrentVersion=VoidPtr][CMVersion=String][IPAddress=String][IPv6Address=String][AppID=String][ClusterID=String][NodeID=String]: Incompatible protocol version.

Explanation   The JTAPI/TAPI application version is not compatible with this version of CTIManager, so the received message has been rejected. The IP address is shown in either IPv4 or IPv6 format depending on the Application's IP addressing mode

Recommended Action   Verify that the correct version of the application is being used. If you're unsure of the correct version, contact the application vendor and upgrade the JTAPI/TSP to the version provided by Cisco Unified Communications Manager. JTAPI/TSP plugins are available in Cisco Unified CM Administration (Application > Plugins)

Error Message

%UC_CTI-6-CtiDeviceOpened: %[DeviceName=String][SeqNumber=Long][DeviceId=Long][DeviceType=Long][CTIconnectionId=Long][MediaControlled=Bool][AssociatedCMIPAddr=String][CmAssignedAppID=Long][AppID=String][ClusterID=String][NodeID=String]: Device opened.

Explanation   Application opened a device

Recommended Action   This alarm is for informational purposes only; no action is required

Error Message

%UC_CTI-6-CtiDeviceClosed: %[DeviceName=String][DeviceId=Long][DeviceType=Long][CTIconnectionId=Long][MediaControlled=Bool][AssociatedCMIpAddr=String][Reason=Enum][AppID=String][ClusterID=String][NodeID=String]: Device closed.

Explanation   Application closed a device

Recommended Action   This alarm is for informational purposes only; no action is required

Reason Code - Enum Definitions

Enum Definitions - Reason

%UC_CTI-4-CtiDeviceOpenFailure: %[CTIconnectionId=Long][DeviceName=String][Reason=Enum][AppID=String][ClusterID=String][NodeID=String]: Device Open failed.

Explanation   Application is unable to open the device

Recommended Action   Check the reason code and take appropriate action to resolve the issue

Reason Code - Enum Definitions

Enum Definitions - Reason

%UC_CTI-6-CtiDeviceOutofService: %[DeviceId=Long][CTIconnectionId=Long][DeviceName=String][AppID=String][ClusterID=String][NodeID=String]: Device is out of service.

Explanation   Device is out of service

Recommended Action   This alarm is for informational purposes only; no action is required

Error Message

%UC_CTI-6-CtiDeviceInService: %[DeviceId=Long][CTIconnectionId=Long][DeviceName=String][callManagerId=Long][AppID=String][ClusterID=String][NodeID=String]: Device in service..

Explanation   Device is back in service

Recommended Action   This alarm is for informational purposes only; no action is required

Error Message

%UC_CTI-6-CtiLineOpened: %[SeqNumber=Long][DirNum=String][Partition=String][DeviceName=String][CTIconnectionId=Long][AppID=String][ClusterID=String][NodeID=String]: Line opened.

Explanation   Application opened the line

Recommended Action   This alarm is for informational purposes only; no action is required

Error Message

%UC_CTI-4-CtiLineOpenFailure: %[CTIconnectionId=Long][DeviceName=String][DirNum=String][Partition=String][Reason=Enum][AppID=String][ClusterID=String][NodeID=String]: Unable to open the line.

Explanation   Application is unable to open the line

Recommended Action   Review the reason code and take appropriate action to resolve the issue

Reason Code - Enum Definitions

Enum Definitions - Reason

%UC_CTI-6-CtiLineClosed: %[DirNum=String][Partition=String][CTIconnectionId=Long][DeviceName=String][Reason=Enum][AppID=String][ClusterID=String][NodeID=String]: Line closed..

Explanation   Application closed the line

Recommended Action   This alarm is for informational purposes only; no action is required

Reason Code - Enum Definitions

Enum Definitions - Reason

%UC_CTI-6-CtiLineOutOfService: %[DirNum=String][Partition=String][CTIconnectionId=Long][DeviceName=String][AppID=String][ClusterID=String][NodeID=String]: Line is out of service.

Explanation   Line is going out of service

Recommended Action   This alarm is for informational purposes only; no action is required

Error Message

%UC_CTI-6-CtiLineInService: %[LineId=Long][CTIconnectionId=Long][AppID=String][ClusterID=String][NodeID=String]: Line in service.

Explanation   Line is back in service

Recommended Action   This alarm is for informational purposes only; no action is required

Error Message

%UC_CTI-4-UnableToSetorResetMWI: %[DirNum=String][AppID=String][ClusterID=String][NodeID=String]: Error in setting message waiting indicator.

Explanation   An error occurred when setting the message waiting indication (MWI) lamp

Recommended Action   The line issuing the request to set the MWI lamp on the target line might not have the proper partitions/calling search space settings to allow it to reach the target line. Check the partitions and calling search space of the line that is requesting to set MWI on the target line. The target line should be able to receive a call from the line that is attempting to set MWI

Error Message

%UC_CTI-6-RedirectCallRequestFailed: %[SeqNumber=Long][DirNum=String][Partition=String][AppID=String][ClusterID=String][NodeID=String]: Request from application to redirect a call has failed.

Explanation   CTIManager is unable to redirect a call

Recommended Action   This alarm is for informational purposes only; no action is required

Error Message

%UC_CTI-4-MaxDevicesPerProviderExceeded: %[AppID=String][ClusterID=String][NodeID=String]: Application has opened more devices than allowed.

Explanation   An application has opened more devices than the limit set in the CTIManager service parameter, Maximum Devices Per Provider

Recommended Action   The application is controlling more devices than the CTI support allows. Review the application configuration and remove devices that are not required to be controlled. The stability of the system will be impacted if the application does not restrict support to the device limit specified by CTI in the CTIManager service parameter, Maximum Devices Per Provider

Error Message

%UC_CTI-4-MaxDevicesPerNodeExceeded: %[AppID=String][ClusterID=String][NodeID=String]: Application has opened more devices than the limit for each node.

Explanation   An application has opened more devices than the limit set in the CTIManager service parameter, Maximum Devices Per Node.

Recommended Action   One or more applications are controlling more devices than the CTI support allows on the specified Unified CM node. Review the application configuration and remove devices that are not required to be controlled. The stability of the system will be impacted if the total number of devices controlled by applications is not properly restricted to the device limit specified by the CTIManager service parameter, Maximum Devices Per Node

Error Message

%UC_CTI-4-ApplicationConnectionError: %[CTIConnectionType=String][InstanceNumber=Long][AppID=String][ClusterID=String][NodeID=String]: CTIManager is unable to allow connections from Applications..

Explanation   CTIManager is unable to accept connections from applications

Recommended Action   CTIManager has encountered problems initializing TCP connections. Restart the CTIManager service to resolve this problem

Error Message

%UC_CTI-3-kCtiQbeLengthMisMatch: %[AppID=String][ClusterID=String][NodeID=String]: OutputQbeMessage: length mismatch..

Explanation   QBE header length mismatch exists.

Recommended Action   This alarm indicates that TSP/JTAPI is incompatible with the version of CTIManager. Contact the support organization for the affected application, install the JTAPI or TSP plugin and restart the application. JTAPI/TSP plugins are available from the Find and List Plugins window in Cisco Unified CM Administration (Application > Plugins).

Error Message

%UC_CTI-3-kCtiInvalidQbeSizeAndOffsets: %[AppID=String][ClusterID=String][NodeID=String]: InvalidQBESizeAndOffsets; QBE message decoding encountered illegal size or offset..

Explanation   QBE Packet received from the application is not encoded correctly.

Recommended Action   A TSP/JTAPI interface error occurred; the QBE message may not be formatted correctly. TSP/JTAPI might be incompatible with the version of CTIManager. Install the JTAPI or TSP plugin (Cisco Unified CM Administration > Application > Plugins) and restart the application.

Error Message

%UC_CTI-3-kCtiSsRegisterManagerErr: %[AppID=String][ClusterID=String][NodeID=String]: Unable to register CtiLine with SSAPI..

Explanation   CTI cannot register CtiLine with SSAPI.

Recommended Action   Check the status of the Cisco CallManager service in Cisco Unified Serviceability > Tools > Control Center - Featured Services. At least one Cisco CallManager service should be running in the cluster for CTIManager to register feature managers. Restart the CTIManager service if the problem persists.

Error Message

%UC_CTI-4-kCtiMytcpErrSocketBroken: %[AppID=String][ClusterID=String][NodeID=String]: Socket connection has been broken..

Explanation   The TCP connection has been lost.

Recommended Action   Although connection to the application is lost, no action is required if lost connection was intentional. If loss of connectivity was unintentional, investigate what might have caused connectivity to be lost and restore the connection.

Error Message

%UC_CTI-4-kCtiDirectoryLoginFailure: %[SeqNumber=Long][AppID=String][ClusterID=String][NodeID=String]: CTI directory login failure..

Explanation   CTI Manager is unable to login to directory. As a result, the application may not be able to access the controlled device list.

Recommended Action   In Cisco Unified CM Administration, verify that the correct username and password has been configured and is being used for CTIManager login. If LDAP is used for authentication, check to confirm that the LDAP synchronization is configured and is working.

Error Message

%UC_CTI-4-kCtiDeviceOpenFailAccessDenied: %[LoginUserId=String][DeviceName=String][DeviceType=Long][AppID=String][ClusterID=String][NodeID=String]: DeviceOpenRequest failure..

Explanation   Application is trying to access a device that is not in its control.

Recommended Action   Check the application sending the request or add the device to the user control list.

Error Message

%UC_CTI-3-kCtiIllegalQbeHeader: %[AppID=String][ClusterID=String][NodeID=String]: Illegal QBE header..

Explanation   Because of illegal QBE header, QBE message has been rejected.

Recommended Action   QBE header could be fragmented due to TCP fragmentation. Review your network configuration to fix any TCP fragmentation issue.

Error Message

%UC_CTI-4-kCtiLineOpenFailAccessDenied: %[SeqNumber=Int][DirNum=String][Partition=String][DeviceName=String][UserName=String][AppID=String][ClusterID=String][NodeID=String]: Line open failed..

Explanation   Application failed to open a line.

Recommended Action   Add the device associated with the line to the user device control list.

Error Message

%UC_CTI-4-kCtiIllegalEnumHandle: %[EnumHandle=Long][EnumObjectType=String][AppID=String][ClusterID=String][NodeID=String]: Enumeration handle is not valid..

Explanation   The enumeration handle associated with the process of enumerating devices, lines or DNs is invalid.

Recommended Action   Check whether all devices, lines or DNs configured for the application are available to the application. If the application uses an End User, check the Device Association section under the End User Configuration in Cisco Unified CM Administration (User Management > End User). If the application uses an Application User, check under Device Information section for that Application User in Cisco Unified CM Administration (User Management > Application User).

Error Message

%UC_CTI-4-kCtiQbeMessageTooLong: %[CTIConnectionType=String][InstanceNumber=Long][QBEMessageLength=Long][AppID=String][ClusterID=String][NodeID=String]: Incoming QBE message exceeds input buffer size.

Explanation   An incoming QBE message exceeds the input buffer size and then gets dropped.

Recommended Action   The size of the QBE packet could exceed the suggested size when the JTAPI/TSP version is not compatible with the version of CTIManager. Contact the application vendor and verify that the application is compatible with the version of Cisco Unified Communications Manager (Unified CM). If the application vendor requests you to, install the JTAPI or TSP plugin (Cisco Unified CM Administration > Application > Plugins) and restart the application.

Error Message

%UC_CTI-4-kCtiNullTcpHandle: %[PDU_Number=Long][AppID=String][ClusterID=String][NodeID=String]: TranslateCtiQbeInputMessage: NULL TCP HANDLE!!! (QBE packet is dropped).

Explanation   A null TCP handle is preventing the QBE packets to be reported to applications.

Recommended Action   This problem typically happens due to a network connectivity failure. Check for and resolve any connectivity issues in your network.

Error Message

%UC_CTI-3-kCtiEnvProcDevListRegTimeout: %[AppID=String][ClusterID=String][NodeID=String]: Directory change notification request time out..

Explanation   CTIManager registration request to EnvProcDevList timed out; CTIManager will send another registration request.

Recommended Action   Check and resolve network connectivity problems between Cisco Unified Communications Manager nodes.

Error Message

%UC_CTI-3-kCtiMYTCPSendError: %[AppID=String][ClusterID=String][NodeID=String]: MYTCP_Send: send error..

Explanation   TCP socket connection has been broken.

Recommended Action   This problem occurs when an application is abruptly shut down or has lost network connectivity to CTIManager. Review your application and network connectivity and resolve any issues.

Error Message

%UC_CTI-2-kCtiSdlErrorvException: %[AppID=String][ClusterID=String][NodeID=String]: Failed to create an internal process that is required to service CTI applications..

Explanation   An unexpected internal SDL error caused a failure in creating CTIManager Service SDL Process.

Recommended Action   An internal CTIManager error has occurred. Try Restarting the CTIManager service to resolve this problem, if it does resolve the problem restart the Unified CM Server.

Error Message

%UC_CTI-3-kCtiTcpInitError: %[ErrorCode=Int][AppID=String][ClusterID=String][NodeID=String]: CTIManager service is unable to initialize TCP connection.

Explanation   CTIManager service is unable to initialize TCP connection

Recommended Action   CTIManager has encountered difficulty initializing TCP connections. Restart the CTIManager service to resolve this problem.

Error Message

%UC_CTI-3-kCtiIllegalFilterSize: %[AppID=String][ClusterID=String][NodeID=String]: ProviderOpenRequest; illegal filter size..

Explanation   ProviderOpenRequest has an illegal filter size.

Recommended Action   The application is using an incompatible version of JTAPI/TSP and Cisco Unified Communications Manager. Install the JTAPI or TSP plugin (Cisco Unified CM Administration > Application > Plugins) and restart the application.

Error Message

%UC_CTI-4-kCtiNewCallNotifyArrayOverflow: %[AppID=String][ClusterID=String][NodeID=String]: Possible internal array overflow condition while generating CTI NewCall event..

Explanation   An unexpected internal error occurred.

Recommended Action   Restart the CTIManager service if the problem persists.

Error Message

%UC_CTI-4-kCtiExistingCallNotifyArrayOverflow: %[AppID=String][ClusterID=String][NodeID=String]: Possible internal array overflow condition while generating CTI ExistingCall event..

Explanation   An unexpected internal error occurred.

Recommended Action   Restart the CTIManager service if the problem persists.

Error Message

%UC_CTI-4-kCtiLineCallInfoResArrayOverflow: %[AppID=String][ClusterID=String][NodeID=String]: Possible internal array overflow condition while generating response to application request for call information..

Explanation   An unexpected internal error occurred.

Recommended Action   Restart the CTIManager service if the problem persists.

Error Message

%UC_CTI-4-kCtiUnknownConnectionHandle: %[CTIConnectionType=String][InstanceNumber=Long][AppID=String][ClusterID=String][NodeID=String]: Connection handle is not valid..

Explanation   A message has been received from an unknown connection, and then dropped.

Recommended Action   This alarm occurs when a QBE packet is received from a connection that is already disconnected. This packet will be ignored by CTIManager and no action is required.

Error Message

%UC_CTI-3-kCtiProviderOpenInvalidUserNameSize: %[UserNameSize=Long][AppID=String][ClusterID=String][NodeID=String]: Invalid userName size in ProviderOpen request..

Explanation   User name length is invalid.

Recommended Action   Ask user of CTI application to use correct userName and to check the user name in configuration. It should not be more than 31 characters.

Error Message

%UC_DB-3-kDbConnectionFailed: %[AdditionalInfo=String][AppID=String][ClusterID=String][NodeID=String]: Database connection failed..

Explanation   An attempt to connect to database failed.

Recommended Action   Enable trace for the database layer monitor to get specific error information.

Error Message

%UC_DB-1-NoDbConnectionAvailable: %[AppID=String][ClusterID=String][NodeID=String]: No database connection available..

Explanation   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

%UC_DB-2-ErrorChangeNotifyClientBlock: %[AppID=String][ClusterID=String][NodeID=String]: 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..

Explanation   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

%UC_DB-3-ErrorReadingInstalledRPMS: %[AppID=String][ClusterID=String][NodeID=String]: Could not read installed RPMs to populate component version table.

Explanation   The function that reads the rpm version information and populates database failed

Recommended Action   Please report this error to the administrator.

Error Message

%UC_DB-3-ErrorChangeNotifyClientTimeout: %[AppID=String][ClusterID=String][NodeID=String]: A change notification client was responding slowly and has been removed..

Explanation   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

%UC_DB-1-ErrorChangeNotifyReconcile: %[AppID=String][ClusterID=String][NodeID=String]: A change notification shared memory reconciliation has occurred..

Explanation   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

%UC_DB-6-IDSEngineDebug: %[class_id=String][class_msg=String][specific_msg=String][AppID=String][ClusterID=String][NodeID=String]: Indicates debug events from IDS database engine..

Explanation   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

%UC_DB-6-IDSEngineInformation: %[class_id=String][class_msg=String][specific_msg=String][AppID=String][ClusterID=String][NodeID=String]: No error has occurred but some routine event completed in IDS database engine..

Explanation   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

%UC_DB-3-IDSEngineCritical: %[class_id=String][class_msg=String][specific_msg=String][AppID=String][ClusterID=String][NodeID=String]: Pay Attention. This alarm does not compromise data or prevent the use of the system..

Explanation   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

%UC_DB-3-IDSEngineFailure: %[class_id=String][class_msg=String][specific_msg=String][AppID=String][ClusterID=String][NodeID=String]: Combined alarm for emergency and error situations. Something unexpected occurred that might compromise data or access to data or cause IDS to fail.

Explanation   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

%UC_DB-6-IDSReplicationInformation: %[class_id=String][class_msg=String][specific_msg=String][AppID=String][ClusterID=String][NodeID=String]: Information about IDS replication.

Explanation   This alarm provides information about IDS replication.

Recommended Action   Informational purposes only; no action is required

Error Message

%UC_DB-3-IDSReplicationFailure: %[class_id=String][class_msg=String][specific_msg=String][AppID=String][ClusterID=String][NodeID=String]: Combined alarm for emergency and error situations. IDS Replication has failed.

Explanation   This alarm indicates combined alarm for emergency and error situations. It indicates failure in IDS Replication

Recommended Action   Requires db admin intervention

Error Message

%UC_DB-3-CUPImportFailure: %[class_id=String][class_msg=String][specific_msg=String][AppID=String][ClusterID=String][NodeID=String]: Combined alarm for Integration, CUP import files has failed.

Explanation   Combined alarm for Integration, CUP import files has failed

Recommended Action   Check the network and files in the CUP server

Error Message

%UC_DB-3-DBUserLimitExceeded: %[user=String][AppID=String][ClusterID=String][NodeID=String]: An application or endpoint is using too many database resources.

Explanation   This alarm indicates an error situation. Resources are not exhausted. The application will not be granted more connections to the database until the ones used are freed up.

Recommended Action   Collect the trace using file get activelog cm/trace/dbl/sdi/limitexceeded*.tar.gz or by collecting the Cisco Database Layer Monitor trace in RTMT to determine the application or endpoint causing issues.

Error Message

%UC_GENERIC-0-OutOfMemory: %[AppID=String][ClusterID=String][NodeID=String]: Out of memory..

Explanation   The process has requested memory from the operating system, and there was not enough memory available.

Recommended Action   No action is required.

Error Message

%UC_GENERIC-6-PermissionDenied: %[AppID=String][ClusterID=String][NodeID=String]: Permission has been denied..

Explanation   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

%UC_GENERIC-0-ServiceNotInstalled: %[ServiceName=String][AppID=String][ClusterID=String][NodeID=String]: Service is not installed..

Explanation   An executable is trying to start but cannot because it is not configured as a service in the service control manager.

Recommended Action   Reinstall the service.

Error Message

%UC_GENERIC-6-ServiceStopped: %[IPAddress=String][Hostname=String][ServiceName=String][ProcessID=ULong][AppID=String][ClusterID=String][NodeID=String]: Service stopped..

Explanation   A service has stopped.

Recommended Action   This alarm is for information purposes only; no action is required.

Error Message

%UC_GENERIC-6-ServiceStarted: %[ProcessID=ULong][IPAddress=String][IPV6Address=String][Hostname=String][ServiceName=String][VersionInfo=String][AppID=String][ClusterID=String][NodeID=String]: Service started..

Explanation   A service has started.

Recommended Action   This alarm is for information purposes only; no action is required.

Error Message

%UC_GENERIC-4-ServiceStartupFailed: %[ServiceName=String][AppID=String][ClusterID=String][NodeID=String]: Service startup failure..

Explanation   An attempt to start the specified service failed.

Recommended Action   Restart the service.

Error Message

%UC_GENERIC-0-FileWriteError: %[PrimaryFilePath=String][AppID=String][ClusterID=String][NodeID=String]: Cannot write into a file..

Explanation   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

%UC_GENERIC-3-CipherListXmlParsingFailed: %[ErrorMsg=String][XmlFileParsed=String][AppID=String][ClusterID=String][NodeID=String]: The system was unable to parse the cipher list for all interfaces.

Explanation   This Alarm Indicates that there was a failure parsing the list of supported ciphers.

Recommended Action   Try saving the Cipher Control List in Operating Systems Administration or deleting the ciphers configured from all interfaces then restart the system and reconfigure the desired cipher control list. If this issue persists contact Cisco Technical Assistance Center (TAC) for further support.

Error Message

%UC_GENERIC-6-CiphersConfiguredForanInterfaceApplied: %[InterfaceConfigured=String][AppID=String][ClusterID=String][NodeID=String]: Security ciphers configured for the configured Interface have been applied.

Explanation   This alarm indicates a new cipher list has been applied to the interface as a result of a UI change to the configured ciphers followed by a service restart.

Recommended Action   Check the application logs for the interface to find details of the ciphers configured.

Error Message

%UC_IPVMS-3-kReadCfgUserLocaleEnterpriseSvcParm: %[AppID=String][ClusterID=String][NodeID=String]: Error reading enterprise default user locale configuration.

Explanation   A database exception was encountered when reading the default Enterprise User Locale setting. Default of US English will be used.

Recommended Action   Verify that the Enterprise parameter setting for User Locale is configured using the CCM Admin web page. Restart the Cisco IP Voice Media Streaming App service.

Error Message

%UC_IPVMS-6-kANNICMPErrorNotification: %[CID=ULong][PID=ULong][IP=String][Port=ULong][AppID=String][ClusterID=String][NodeID=String]: ANN stream ICMP port unreachable error..

Explanation   An announcement RTP stream had an ICMP (Internet Control Message Protocol) port unreachable error. The stream has been terminated. This ICMP error is a result of the destination end-point not having the receiving UDP/RTP port open to receive packets.

Recommended Action   No action is required. This may occur at times when connections are being stopped or redirected.

Error Message

%UC_IPVMS-3-kANNDeviceRecordNotFound: %[AppID=String][ClusterID=String][NodeID=String]: ANN device record not found..

Explanation   A device record for the announcer device was not found in the database. The ANN device is normally automatically added when the server is added to the database.

Recommended Action   To add the ANN device to database you will need to remove/delete the server and re-add the server. WARNING: This may result in having to manually reconfigure many different settings such as Media Resource Groups, CallManager Groups and many others.

Error Message

%UC_IPVMS-3-kPWavMgrThreadxFailed: %[Error=ULong][ErrorText=String][AppID=String][ClusterID=String][NodeID=String]: WAV playing manager thread creation failed.

Explanation   The process component used for playing WAV files failed to start, possibly due to low system resources.

Recommended Action   Restart the Cisco IP Voice Media Streaming App service or restart server.

Error Message

%UC_IPVMS-3-ANNDeviceRecoveryCreateFailed: %[Error=Int][ErrorText=String][AppID=String][ClusterID=String][NodeID=String]: ANN device recovery create failure..

Explanation   The ANN device startup failed, possibly due to lack of memory. If the error code is non-zero it may help determine the cause of the error. The announcement device will not be available.

Recommended Action   Restart the Cisco IP Voice Media Streaming App service or restart server.

Error Message

%UC_IPVMS-3-kReadCfgANNListUnknownException: %[DeviceName=String][AppID=String][ClusterID=String][NodeID=String]: Unknown exception..

Explanation   An unknown exception occurred while trying to read ANN device Cisco Unified Communications Manager list information.

Recommended Action   Device will not start; fix problem and restart service.

Error Message

%UC_IPVMS-3-kReadCfgANNListComException: %[DeviceName=String][Description=String][AppID=String][ClusterID=String][NodeID=String]: COM error..

Explanation   A COM error occurred while trying to read ANN device Cisco Unified Communications Manager list information.

Recommended Action   Device will not start; fix problem and restart service.

Error Message

%UC_IPVMS-3-kReadCfgANNListDblException: %[DeviceName=String][ExceptionStr=String][ExceptionID=ULong][AppID=String][ClusterID=String][NodeID=String]: Database exception..

Explanation   A database exception occurred while trying to read ANN device Cisco Unified Communications Manager list information.

Recommended Action   Device will not start; fix database problem and restart service.

Error Message

%UC_IPVMS-3-kReadCfgANNUnknownException: %[DeviceName=String][AppID=String][ClusterID=String][NodeID=String]: Unknown exception..

Explanation   An unknown exception occurred while trying to read ANN device configuration information.

Recommended Action   Device will not start; fix problem and restart service.

Error Message

%UC_IPVMS-3-kReadCfgANNComException: %[DeviceName=String][Description=String][AppID=String][ClusterID=String][NodeID=String]: COM error..

Explanation   A COM error occurred while trying to read ANN device configuration information.

Recommended Action   Device will not start; fix problem and restart service.

Error Message

%UC_IPVMS-3-kReadCfgANNDblException: %[DeviceName=String][ExceptionStr=String][ExceptionID=ULong][AppID=String][ClusterID=String][NodeID=String]: Database exception..

Explanation   A database exception occurred while trying to read ANN device configuration information.

Recommended Action   Device will not start; fix database problem and restart service.

Error Message

%UC_IPVMS-3-kReadCfgEnterpriseException: %[AppID=String][ClusterID=String][NodeID=String]: Enterprisewide configuration exception.

Explanation   An unknown exception occured reading Enterjprisewide configuration settings.

Recommended Action   Verify the enterprise configuration settings and restart the IP Media Streaming Service.

Error Message

%UC_IPVMS-3-kCfgListUnknownException: %[AppID=String][ClusterID=String][NodeID=String]: Unknown Configuration Exception.

Explanation   An exception error was generated reading the service parameter settings.

Recommended Action   Restart the server.

Error Message

%UC_IPVMS-3-kCfgListComException: %[Description=String][AppID=String][ClusterID=String][NodeID=String]: Configuration COM Exception.

Explanation   A COM exception error was generated reading the service parameter settings for devices.

Recommended Action   Verify that service parameters can be viewed using CCM Administration. If they can then restart the service or server.

Error Message

%UC_IPVMS-3-kCfgListDblException: %[Description=String][ExceptionID=ULong][AppID=String][ClusterID=String][NodeID=String]: Configuration DBL Exception.

Explanation   An exception error was generated reading the service parameter settings for devices.

Recommended Action   Verify that service parameters can be viewed using CCM Administration. If they can then restart the service or server.

Error Message

%UC_IPVMS-4-kANNDeviceStartingDefaults: %[Field=String][Value=String][AppID=String][ClusterID=String][NodeID=String]: ANN device configuration not found.

Explanation   A service parameter for Cisco IP Voice Media Streaming App service related to the ANN device configuration was not found. The system will start with the given default setting.

Recommended Action   Review the service parameter settings and configure the ANN device settings properly using the CUCM Administration.

Error Message

%UC_IPVMS-3-kRequestedANNStreamsFailed: %[Requested=ULong][Allocated=ULong][AppID=String][ClusterID=String][NodeID=String]: ANN requested streams failure..

Explanation   The requested resources for the configured number of annunciator calls (Call Count service parameter) was not available. If the value shown as "Allocated" is non-zero

Recommended Action   Verify the ANN Call Count service parameter is correct. A server restart may be needed to recover resources.

Error Message

%UC_IPVMS-4-kANNAudioCreateDirFailed: %[Error=ULong][ErrorText=String][Path=String][AppID=String][ClusterID=String][NodeID=String]: ANN create local path error.

Explanation   Unable to create a subdirectory to contain announcement files. This may be caused by insufficient disk storage. Announcements may not play correctly as a result of this error.

Recommended Action   Check for available free space on the common data storage area. If full, take action to remove old trace files to free space. Restart the Cisco IP Voice Media Streaming App service.

Error Message

%UC_IPVMS-3-kANNAudioThreadWaitFailed: %[Error=ULong][AppID=String][ClusterID=String][NodeID=String]: ANN TFTP event wait error.

Explanation   An error was reported while waiting for a list of events. Announcement files will not be automatically updated.

Recommended Action   Restart the Cisco IP Voice Media Streaming App service. If the error continues, restart the serverr.

Error Message

%UC_IPVMS-3-kANNAudioThreadException: %[ExceptionCode=ULong][AXReg=ULong][BXReg=ULong][CXReg=ULong][DXReg=ULong][SIReg=ULong][DIReg=ULong][IPReg=ULong][SPReg=ULong][BPReg=ULong][Flags=ULong][CSSeg=ULong][DSSeg=ULong][ESSeg=ULong][SSSeg=ULong][FSSeg=ULong][GSSeg=ULong][AppID=String][ClusterID=String][NodeID=String]: ANN TFTP transfer exception failure.

Explanation   An unknown program exception has caused the background TFTP file transfer processing for announcement files to terminate. Announcement files will not be automatically updated.

Recommended Action   Restart the Cisco IP Media Streaming App service and if the problem continues, report it to Cisco. Include CMS traces and Application Event log.

Error Message

%UC_IPVMS-3-kANNAudioThreadxFailed: %[Error=ULong][AppID=String][ClusterID=String][NodeID=String]: ANN TFTP transfer thread creation failed.

Explanation   The ANN background TFTP file transfer processing thread failed to create possibly due to low system resources.

Recommended Action   Reboot server.

Error Message

%UC_IPVMS-3-kANNAudioComException: %[Filename=String][Reason=String][AppID=String][ClusterID=String][NodeID=String]: ANN TFTP COM exception.

Explanation   A COM exception occured while processing the specified file.

Recommended Action   Review the file for possible format errors or missing elements.

Error Message

%UC_IPVMS-3-kANNAudioXmlLoadFailed: %[Filename=String][Reason=String][AppID=String][ClusterID=String][NodeID=String]: ANN XML parsing error.

Explanation   There is a syntax error in the specified file.

Recommended Action   Correct the syntax error.

Error Message

%UC_IPVMS-3-kANNAudioXmlSyntax: %[Filename=String][AppID=String][ClusterID=String][NodeID=String]: ANN XML invalid element .

Explanation   There is an invalid element in the specified file.

Recommended Action   Correct the error.

Error Message

%UC_IPVMS-3-kANNAudioTftpFileMissing: %[Filename=String][AppID=String][ClusterID=String][NodeID=String]: ANN TFTP file missing.

Explanation   A file was not found on the TFTP server to be downloaded to the announcement server.

Recommended Action   Correct the error.

Error Message

%UC_IPVMS-3-kANNAudioTftpMgrStartFailed: %[FileName=String][AppID=String][ClusterID=String][NodeID=String]: TFTP start file transfer failed.

Explanation   Unable to start transfering a file from TFTP server.

Recommended Action   Verify the file name exists on the TFTP server.

Error Message

%UC_IPVMS-3-kANNAudioTftpMgrCreate: %[TFTPServer=String][AppID=String][ClusterID=String][NodeID=String]: Unable to create TFTP client.

Explanation   Unable to create a client TFTP session with the TFTP server.. This may be due to the server not running, or an incorrect server name configuration setting in service paramenters. This operation will be retried periodically.

Recommended Action   Verify the TFTP server is operating and configuration settings are correct.

Error Message

%UC_IPVMS-3-kANNAudioOpenFailed: %[Error=ULong][ErrorText=String][FileName=String][AppID=String][ClusterID=String][NodeID=String]: Open announcement file failed.

Explanation   An error was reported when attempting to open an announcement file for reading.

Recommended Action   Verify the file exists and the Cisco IP Voice Media Streaming App service has proper access rights to open the file for reading.

Error Message

%UC_IPVMS-4-kANNAudioUndefinedLocale: %[LocaleID=ULong][Type=String][AppID=String][ClusterID=String][NodeID=String]: Unknown ANN Locale.

Explanation   The requested Locale for an announcement is not installed. For network locale you use the platform CLI interface to run (run sql select * from typecountry where enum = #), #=locale. This will tell you what country locale is being requested.

Recommended Action   Install the locale package or check device settings for an incorrect locale value.

Error Message

%UC_IPVMS-4-kANNAudioUndefinedAnnID: %[Locale=ULong][AnnID=ULong][AppID=String][ClusterID=String][NodeID=String]: Requested announcement not found.

Explanation   The requested announcement is unknown. This may be caused by using an incorrect announcement identifier for a custom announcement. Use the CUCM Admin to view a list of custom announcement identifiers and verify the correct one is being used.

Recommended Action   Correct the announcement identifier chosen from the custom announcement list.

Error Message

%UC_IPVMS-3-CFBDeviceRecoveryCreateFailed: %[Error=Int][ErrorText=String][AppID=String][ClusterID=String][NodeID=String]: CFB device recovery create failure..

Explanation   The CFB device startup failed, possibly due to lack of memory. If the error code is non-zero it may help determine the cause of the error. The conference bridge device will not be available.

Recommended Action   Restart the Cisco IP Voice Media Streaming App service or restart server.

Error Message

%UC_IPVMS-3-UnableToOpenMohAudioSource: %[MohAudioSourceFileName=String][MohAudioSourceId=UInt][Error=Int][ErrorText=String][AppID=String][ClusterID=String][NodeID=String]: Music On Hold Audio Source file cannot be opened.

Explanation   This alarm occurs when Music On Hold fails because the MOH audio source file cannot be opened. The caller will hear silence instead of the desired Music on Hold audio.

Recommended Action   Use the CUCM Administration interface for "MOH Audio File Management" on this specific MOH CUCM server to check that the Music On Hold Audio Source file has been uploaded to this specific server. Note that MOH audio files must be uploaded using the CUCM Administration page of each MOH server in the cluster before that server can play the audio file. If you need to upload the file you will need to reset this MOH device after the upload so it will be accessable by the MOH device.

Error Message

%UC_IPVMS-3-kCFBDeviceRecordNotFound: %[AppID=String][ClusterID=String][NodeID=String]: CFB device record not found..

Explanation   A device record for the software conference bridge device was not found in the database. The CFB device is normally automatically added when the server is added to the database.

Recommended Action   To add the CFB device to database you will need to remove/delete the server and re-add the server. WARNING: This may result in having to manually reconfigure many different settings such as Media Resource Groups, CallManager Groups and many others.

Error Message

%UC_IPVMS-4-kCFBDeviceStartingDefualts: %[Field=String][Value=String][AppID=String][ClusterID=String][NodeID=String]: CFB device configuration not found..

Explanation   A service parameter for Cisco IP Voice Media Streaming App service related to the CFB device configuration was not found. The system will use the given default setting.

Recommended Action   Review the service parameter settings and configure the CFB device settings properly using the CUCM Administration.

Error Message

%UC_IPVMS-6-kCFBICMPErrorNotification: %[CID=ULong][PID=ULong][IP=String][Port=ULong][AppID=String][ClusterID=String][NodeID=String]: CFB stream ICMP error..

Explanation   A SW CFB RTP stream had an ICMP (Internet Control Message Protocol) port unreachable error. The stream has been terminated. This ICMP error is a result of the destination end-point does not have the receiving UDP/RTP port open to receive packets.

Recommended Action   No action is required. This may occur at times when connections are being stopped or redirected.

Error Message

%UC_IPVMS-4-kChangeNotifyServiceCreationFailed: %[Error=Int][ErrorText=String][AppID=String][ClusterID=String][NodeID=String]: Database change notification subsystem not starting..

Explanation   The background process to activate database changes has failed to start. Database changes affecting the Cisco IP Voice Media Streaming App service will not automatically take effect.

Recommended Action   Restart the Cisco IP Voice Media Streaming App service to get the DB notification reenabled.

Error Message

%UC_IPVMS-4-kChangeNotifyServiceGetEventFailed: %[Error=Int][ErrorText=String][AppID=String][ClusterID=String][NodeID=String]: Invalid notification event returned by database change notification..

Explanation   The change notification subsystem returned an invalid notification event. The Cisco IP Voice Media Streaming App service will terminate. The SW media devices (ANN, CFB, MOH, MTP) will be temporarily out of service and calls in progress may be dropped.

Recommended Action   Check the current status of the Cisco IP Voice Media Streaming App service and monitor for repeated occurances.

Error Message

%UC_IPVMS-4-kChangeNotifyServiceRestartFailed: %[Error=Int][ErrorText=String][AppID=String][ClusterID=String][NodeID=String]: Database change notification restart failure..

Explanation   The change notification subsystem failed to restart.

Recommended Action   This service has change notification disabled, it may be reenabled at a later time or restart Cisco IP Voice Media Streaming App service to reenable immediately.

Error Message

%UC_IPVMS-3-kCreateAudioSourcesFailed: %[Error=Int][ErrorText=String][AppID=String][ClusterID=String][NodeID=String]: Creating audio source class failed..

Explanation   Unable to create audio source subcombonent to provide audio for streaming. This may be due to lack of memory.

Recommended Action   Restart the Cisco IP Voice Media Streaming App service or restart the server.

Error Message

%UC_IPVMS-3-kCreateControlFailed: %[AudioSourceID=ULong][CodecType=String][Error=Int][ErrorText=String][AppID=String][ClusterID=String][NodeID=String]: Stream Control create failure..

Explanation   Create stream control subcomponent. The error may possibly be due to lack of memory.

Recommended Action   Reset the MOH device. If continues to fail restart the Cisco IP Voice Media Streaming App service or restart the server.

Error Message

%UC_IPVMS-6-kReadCfgIpTosMediaResourceToCmNotFound: %[AppID=String][ClusterID=String][NodeID=String]: IP TOS MediaResource to Cm value not found..

Explanation   The IP Type-of-Service Media Resource To Call Manager service parameter value was not found in the database. Defaulting its value to 0x60 for CS3(precedence 3) DSCP (011000).

Recommended Action   Set the Ip Type-of-Service Media Resource To Call Manager service parameter for the Cisco IP Voice Media Streaming App service.

Error Message

%UC_IPVMS-4-kDeviceDriverError: %[Error=String][AppID=String][ClusterID=String][NodeID=String]: IP voice media streaming device driver error..

Explanation   The IP voice media streaming device driver returned an error. This may indicate a significant media error or resource shortage.

Recommended Action   Restarting the Cisco IP Voice Media Streaming App service or possibly restarting the server may resolve the error condition.

Error Message

%UC_IPVMS-4-kDeviceMgrCreateFailed: %[DeviceName=String][ServerNumber=ULong][ServerName=String][AppID=String][ClusterID=String][NodeID=String]: Device connection manager failed to start..

Explanation   The device controller was unable to start a connection to control device registration with CallManager. This is possibly due to lack of memory.

Recommended Action   Restart the Cisco IP Voice Media Streaming App service or restart the CUCM server.

Error Message

%UC_IPVMS-4-kDeviceMgrExitEventCreationFailed: %[DeviceName=String][TraceName=String][Error=ULong][ErrorText=String][AppID=String][ClusterID=String][NodeID=String]: Creation of device manager exit event failed..

Explanation   An error was reported when allocating an exit-control event for a SW media device. The device will not be registered with CallManager or active.

Recommended Action   This error may be due to a memory resource shortage. Restart the Cisco IP Voice Media Streaming App service or restart the CUCM server.

Error Message

%UC_IPVMS-6-kDeviceMgrLockoutWithCallManager: %[TraceName=String][AppID=String][ClusterID=String][NodeID=String]: Cisco Unified Communications Manager in lockout..

Explanation   The specified Cisco Unified Communications Manager has failed to respond to control messages. The TCP control connection to CUCM is being suspended. This will cause a switch to another CUCM if one is available otherwise the device will be unavailable. There may be a shortage of CPU resource or some other error condition on the CUCM server.

Recommended Action   Check the status of the Cisco Unified Communications Manager service. You may have to restart the CUCM service or the CUCM server.

Error Message

%UC_IPVMS-5-kDeviceMgrMoreThan50SocketEvents: %[TraceName=String][AppID=String][ClusterID=String][NodeID=String]: More than 50 events returned from TCP link..

Explanation   The specified Cisco Unified Communications Manager TCP link has returned a large number of TCP events. This indicates an unexpected flood of events.

Recommended Action   No action is required. Monitor for reoccurance. This could be an indication of a security issue.

Error Message

%UC_IPVMS-4-kDeviceMgrOpenReceiveFailedOutOfStreams: %[TraceName=String][CID=ULong][PID=ULong][AppID=String][ClusterID=String][NodeID=String]: Open receive failure..

Explanation   The open receive channel failed. This may indicate a missmatch of media resources between Cisco Unified Call Manager and the Cisco IP Voice Media Streaming App service.

Recommended Action   Check the performance monitor counters for resource availability on CUCM and on Cisco IP Voice Media Streaming App. Also, you might run the Platform CLI command "Show Media Streams" to identify possible media connection resource leaks. Possibly reset the media device or restart Cisco IP Voice Media Streaming App or restart the CUCM server.

Error Message

%UC_IPVMS-4-kDeviceMgrRegisterKeepAliveResponseError: %[TraceName=String][AppID=String][ClusterID=String][NodeID=String]: Cisco Unified Communications Manager not responding..

Explanation   The specified Cisco Unified Communications Manager is not responding to the keepalive messages. The connection with CUCM is being terminated and the media device will reregister with another Cisco Unified Call Manager if a secondary is configured. Otherwise, the media device will be unavailable until the device is able to reregister with CUCM.

Recommended Action   Cisco Unified Communications Manager may have gone down or is unable to respond. Check status of CUCM. The media device should automatically reregister.

Error Message

%UC_IPVMS-6-kDeviceMgrRegisterWithCallManager: %[TraceName=String][AppID=String][ClusterID=String][NodeID=String]: Registered with Cisco Unified Communications Manager..

Explanation   The software media device registered with the specified Cisco Unified Communications Manager.

Recommended Action   No action is required.

Error Message

%UC_IPVMS-4-kDeviceMgrRegisterWithCallManagerError: %[TraceName=String][AppID=String][ClusterID=String][NodeID=String]: Connection error with Cisco Unified Communications Manager..

Explanation   The media device was registered with the specified Cisco Unified Communications Manager and received a socket error or disconnect. This may occur normally when Cisco Unified Communications Manager is stopped.

Recommended Action   No action is required. The media device will reregister.

Error Message

%UC_IPVMS-4-kDeviceMgrSocketDrvNotifyEvtCreateFailed: %[DeviceName=String][TraceName=String][Error=ULong][ErrorText=String][AppID=String][ClusterID=String][NodeID=String]: Create driver notification event failure..

Explanation   An error was returned when creating a signaling event for communication with the media streaming kernel driver. This may be due to memory or system resource shortage.

Recommended Action   Restart the Cisco IP Voice Media Streaming App service or restart the CUCM server.

Error Message

%UC_IPVMS-4-kDeviceMgrSocketNotifyEventCreateFailed: %[DeviceName=String][TraceName=String][Error=ULong][ErrorText=String][AppID=String][ClusterID=String][NodeID=String]: Creation socket event failure..

Explanation   An error was reported when creating a notification event for a socket interface. This may be due to a resource shortage. The media device will remain unavailable.

Recommended Action   Restart the Cisco IP Voice Media Streaming App service and monitor for reoccurance or restart the CUCM server.

Error Message

%UC_IPVMS-4-kDeviceMgrStartTransmissionOutOfStreams: %[TraceName=String][CID=ULong][PID=ULong][AppID=String][ClusterID=String][NodeID=String]: Start transmission failure..

Explanation   An error was encountered while starting an RTP transmission audio stream. This may indicate a missmatch of resources between Cisco Unified Communications Manager and Cisco IP Voice Media Streaming App service.

Recommended Action   Check the performance counters for the media resources on CUCM and Cisco IP Voice Media Streaming App to determine if there is a resource leak. You should also use the platform CLI command "Show Media Streams" to check for orphaned media RTP connections.

Error Message

%UC_IPVMS-6-kDeviceMgrThreadWaitFailed: %[TraceName=String][Error=Int][ErrorText=String][AppID=String][ClusterID=String][NodeID=String]: Wait call failure in device manager thread..

Explanation   An error was reported during a system request to wait on an event, the media device will be restarted.

Recommended Action   No action is required.

Error Message

%UC_IPVMS-4-kDeviceMgrThreadxFailed: %[DeviceName=String][TraceName=String][Error=Int][ErrorText=String][AppID=String][ClusterID=String][NodeID=String]: Creation of thread failure..

Explanation   An error was reported when starting a process for the specified media device. This may be due to a system resource shortage.

Recommended Action   Restart the Cisco IP Voice Media Streaming App service or restart the CUCM server to recover from this error.

Error Message

%UC_IPVMS-6-kDeviceMgrUnregisterWithCallManager: %[TraceName=String][AppID=String][ClusterID=String][NodeID=String]: Unregister with Cisco Unified Communications Manager..

Explanation   A media device has unregistered with the specified Cisco Unified Communications Manager.

Recommended Action   No action is required. The media device will automatically reregister.

Error Message

%UC_IPVMS-4-kFixedInputCreateControlFailed: %[AudioSourceID=ULong][CodecType=String][AppID=String][ClusterID=String][NodeID=String]: Fixed MOH stream control failed to start..

Explanation   The audio stream control subsystem for the Fixed MOH audio source failed to start. Audio from the MOH Fixed audio source will not be provided for streaming out. This may be due to resource shortage such as memory or availability of the Fixed MOH audio source device.

Recommended Action   Reset MOH device, if failure continues restart the server. Monitor for errors in trace files and system log.

Error Message

%UC_IPVMS-4-kFixedInputCreateSoundCardFailed: %[AudioSourceID=ULong][CodecType=String][AppID=String][ClusterID=String][NodeID=String]: Fixed stream sound card interface failed to start..

Explanation   An error was encountered when starting the interface to access the sound card for providing MOH fixed audio. The audio source will not play possibly due to shortage of memory.

Recommended Action   Reset MOH device, or restart the Cisco IP Voice Media Streaming App service, or restart the server. Check the system log and possibly the traces for Cisco IP Voice Media Streaming App service.

Error Message

%UC_IPVMS-4-kFixedInputInitSoundCardFailed: %[AudioSourceID=ULong][ErrorCode=ULong][ErrorCodeText=String][DeviceName=String][AppID=String][ClusterID=String][NodeID=String]: Fixed stream sound card interface initialization failure..

Explanation   Initialization of sound card failed. Fixed audio source will not play possibly due to missing or unconfigured USB sound device.

Recommended Action   Check that the USB sound is installed. Reset MOH device, or restart Cisco IP Voice Media Streaming App service, or restart the server. The system log and traces from Cisco IP Voice Media Streaming App may contain additionsl information.

Error Message

%UC_IPVMS-4-kFixedInputCodecStreamFailed: %[AudioSourceID=ULong][ErrorCode=ULong][ErrorCodeText=String][CodecType=String][AppID=String][ClusterID=String][NodeID=String]: Fixed input codec stream initialization failure..

Explanation   Initialization of sound card codec source transcoding process failed. The fixed audio source will not play possibly due to memory or resource shortage.

Recommended Action   Reset MOH device, or restart Cisco IO Voice Media Streaming App service, or restart server.

Error Message

%UC_IPVMS-4-kFixedInputTranscoderFailed: %[AudioSourceID=ULong][ErrorCode=ULong][ErrorCodeText=String][AppID=String][ClusterID=String][NodeID=String]: Fixed input audio stream transcoder failure..

Explanation   An error was encountered while transcoding audio from the sound card. The audio source will not play possibly due an error accessing the sound card.

Recommended Action   Check that the USB sound device is properly installed. Unplug the USB sound device and replug back into the USB connector. Reset MOH device, restart Cisco IP Voice Media Streaming App service, or restart the server.

Error Message

%UC_IPVMS-4-kGetFileNameFailed: %[AudioSourceID=ULong][CodecType=String][AppID=String][ClusterID=String][NodeID=String]: Get audio source file name failure..

Explanation   The Music-on-Hold audio source is not assigned to an audio file.

Recommended Action   Assign the audio source to an audio file or change the value of the MOH audio source to a value that has been configured.

Error Message

%UC_IPVMS-3-kIPVMSDeviceDriverNotFound: %[AppID=String][ClusterID=String][NodeID=String]: Cisco IP voice media streaming driver not found..

Explanation   The Cisco IP voice media streaming driver was not found or is not installed. The Cisco IP Voice Media Streaming App service cannot run until this error is resolved. All software media devices (ANN, CFB, MOH, MTP) for this server will not be available.

Recommended Action   Check the system log for an error when the system attempted to load IpVms driver at the last server startup. A server restart is required to cause the driver to be loaded.

Error Message

%UC_IPVMS-4-kIPVMSMgrEventCreationFailed: %[Error=ULong][ErrorText=String][AppID=String][ClusterID=String][NodeID=String]: Creation of required signaling event failed..

Explanation   An error was encountered when creating a signaling event component. This may be due to a resource shortage. The Cisco IP Voice Media Streaming App service will terminate.

Recommended Action   Check the trace files for more information. The service should automatically be restarted. If this error continues to reoccur the server may need to be restarted.

Error Message

%UC_IPVMS-4-kIpVmsMgrThreadWaitFailed: %[AppID=String][ClusterID=String][NodeID=String]: Error while waiting for asynchronous notifications of events..

Explanation   An error was reported while the primary control process for Cisco IP Voice Media Streaming App was waiting on asynchronous events to be signaled. The service will terminate and should automatically be restarted. This will cause a temporary loss of availability for the software media devices (ANN, CFB, MOH, MTP).

Recommended Action   Monitor the service and status of the software media devices. The service should automatically restart. If the problem continues, review the trace files for additional information. A server restart may be required if this repeats.

Error Message

%UC_IPVMS-3-kIpVmsMgrNoLocalHostName: %[AppID=String][ClusterID=String][NodeID=String]: Unable to retrieve the local host server name..

Explanation   Unable to obtain the local host server name. The Cisco IP Voice Media Streaming App service will terminate. No software media devices (ANN, CFB, MOH, MTP) will be available while the service is stopped.

Recommended Action   Check the configuration settings for the server name, DHCP, or DNS. Monitor the status of Cisco IP Voice Media Streaming App service. The service will not operate without a valid server name.

Error Message

%UC_IPVMS-3-kIpVmsMgrNoLocalNetworkIPAddr: %[AppID=String][ClusterID=String][NodeID=String]: Unable to retrieve the network IP address for host server..

Explanation   Unable to obtain the network IP (dotted) address. The Cisco IP Voice Media Streaming App service will terminate. The software media devices (ANN, CFB, MOH, MTP) will be unavailable while this service is stopped.

Recommended Action   Monitor the status of the Cisco IP Voice Media Streaming App service. It should be automatically restarted. If the error occurs again, check the server IP configuration (DHCP, IP address).

Error Message

%UC_IPVMS-4-kIPVMSMgrThreadxFailed: %[Error=ULong][ErrorText=String][AppID=String][ClusterID=String][NodeID=String]: Creation of the IPVMSMgr thread failed..

Explanation   An error was encountered while starting a process thread. The Cisco IP Voice Media Streaming App service will terminate. The software media devices (ANN, CFB, MOH, MTP) will be unavailable while the service is stopped.

Recommended Action   Monitor the status of the Cisco IP Voice Media Streaming App service. It should automatically be restarted. If the error reoccurs, restart the server.

Error Message

%UC_IPVMS-3-kIPVMSMgrWrongDriverVersion: %[Found=ULong][Need=ULong][AppID=String][ClusterID=String][NodeID=String]: Wrong version of device driver..

Explanation   An incompatible device driver was found. The Cisco IP Voice Media Streaming App service will terminate. The software media devices (ANN, CFB, MOH, MTP) will be unavailable while the service is stopped.

Recommended Action   Restart the server to ensure the most recent driver is started. If the error continues, then reinstall Cisco Unified Communications Manager to get the proper driver version installed.

Error Message

%UC_IPVMS-6-kIPVMSStarting: %[Version=String][IPAddress=String][Hostname=String][ServiceName=String][ProcessID=ULong][AppID=String][ClusterID=String][NodeID=String]: IP voice media streaming application starting..

Explanation   The Cisco IP Voice Media Streaming App service is starting.

Recommended Action   No action is required.

Error Message

%UC_IPVMS-6-kIPVMSStopping: %[Version=String][IPAddress=String][Hostname=String][ServiceName=String][ProcessID=ULong][AppID=String][ClusterID=String][NodeID=String]: The IP voice media streaming application shutting down..

Explanation   The Cisco IP Voice Media Streaming App service is shutting down.

Recommended Action   No action is required.

Error Message

%UC_IPVMS-4-kMOHBadMulticastIP: %[AudioSourceID=ULong][ConferenceID=ULong][CodecType=String][IPAddress=String][Port=ULong][AppID=String][ClusterID=String][NodeID=String]: Invalid multicast IP address..

Explanation   An invalid multicast IP address (out of range) was found.

Recommended Action   Correct the setting on the Music-on-Hold device configuration for multicast address.

Error Message

%UC_IPVMS-4-kMOHDeviceRecordNotFound: %[AppID=String][ClusterID=String][NodeID=String]: MOH device record not found..

Explanation   A Music-on-Hold device was not found for this server. This device is normally automatically added when a server is added to the configuration.

Recommended Action   If Music-on-Hold functionality is required, you will need to remove and readd server to the database. WARNING: This may impact many other configuration settings (CM Groups, Media Resource Groups, etc...).

Error Message

%UC_IPVMS-6-kMOHICMPErrorNotification: %[CID=ULong][PID=ULong][IP=String][Port=ULong][AppID=String][ClusterID=String][NodeID=String]: MOH stream ICMP error..

Explanation   A Music-on-Hold transmission stream had an ICMP (Internet Control Message Protocol) port unreachable error. The stream has been terminated. This may occur occasionally depending on call termination sequences.

Recommended Action   No action is required.

Error Message

%UC_IPVMS-4-kMOHMgrCreateFailed: %[Error=ULong][ErrorText=String][AppID=String][ClusterID=String][NodeID=String]: Error starting MOH Audio source subcomponent..

Explanation   A error was encountered by the Music-on-Hold device while starting the sub-component that provides audio from files or sound card. This may be due to shortage of resources (memory).

Recommended Action   Restart the Cisco IP Voice Media Streaming App service or restart the server.

Error Message

%UC_IPVMS-4-kMOHMgrExitEventCreationFailed: %[Error=ULong][ErrorText=String][AppID=String][ClusterID=String][NodeID=String]: Creation of MOH manager exit event failed..

Explanation   An error was encountered when allocating a signaling event. This may be caused by a resource shortage.

Recommended Action   Restart the Cisco IP Voice Media Streaming App service or restart the server.

Error Message

%UC_IPVMS-6-kMOHMgrIsAudioSourceInUseThisIsNULL: %[AppID=String][ClusterID=String][NodeID=String]: Synchronization error detected in MOH audio manager..

Explanation   A synchronization error was detected. Condition has been resolved automatically.

Recommended Action   No action is required.

Error Message

%UC_IPVMS-6-kMOHMgrThreadWaitFailed: %[Error=ULong][ErrorText=String][AppID=String][ClusterID=String][NodeID=String]: Wait call failure in MOH manager thread..

Explanation   An error was encountered in Music-on-Hold audio manager subcomponent while waiting for aynchronous event signaling. The MOH device will be restarted.

Recommended Action   No action is required.

Error Message

%UC_IPVMS-4-kMOHMgrThreadxFailed: %[Error=ULong][ErrorText=String][AppID=String][ClusterID=String][NodeID=String]: Starting of MOH audio manager failed..

Explanation   An error was encountered when starting the Music-on-Hold audio manager subcomponent. Music-on-Hold audio services will not be avaliable.

Recommended Action   Restart the Cisco IP Voice Media Streaming App service.

Error Message

%UC_IPVMS-6-kMOHRewindStreamControlNull: %[AudioSourceID=ULong][CodecType=String][AppID=String][ClusterID=String][NodeID=String]: Attempted to rewind an inactive MOH audio source..

Explanation   An attempt was made to rewind or restart the Music-on-Hold audio source that is inactive. This has been ignored.

Recommended Action   No action required.

Error Message

%UC_IPVMS-6-kMOHRewindStreamMediaPositionObjectNull: %[AudioSourceID=ULong][CodecType=String][AppID=String][ClusterID=String][NodeID=String]: Error rewinding MOH audio source that is not playing..

Explanation   An attempt was made to rewind or restart a Music-on-Hold wav file that was not being played. This has been ignored.

Recommended Action   No action is required.

Error Message

%UC_IPVMS-3-kMOHTFTPGoRequestFailed: %[ErrorText=String][File=String][SrcPath=String][DstPath=String][OSError=Int][OSErrorText=String][AppID=String][ClusterID=String][NodeID=String]: Transfer of MOH source file to working path failed..

Explanation   An error was encountered when trying to copy or update a Music-on-Hold audio source file.

Recommended Action   Use the Platform CLI to verify the source path and file exist. If the file does not exist then use CUCMAdmin to reupload the missing audio source to this specific server. Reinstall the Cisco Unified Communications Manager to have all required paths created.

Error Message

%UC_IPVMS-4-kMTPDeviceRecordNotFound: %[AppID=String][ClusterID=String][NodeID=String]: MTP device record not found..

Explanation   A device record for the software media termination point device was not found in the database. This is normally automatically added to the database when a server is added to the database. The software MTP device will be disabled.

Recommended Action   If MTP functionality is required, you will need to delete the server and re-add the server back to the database using CCMAdmin. WARNING: This may require many additional configuration settings to be reapplied such as CallManager Groups, Media Resource groups and more.

Error Message

%UC_IPVMS-6-kMTPDeviceStartingDefualts: %[CallCount=ULong][RunFlag=String][AppID=String][ClusterID=String][NodeID=String]: MTP device configuration not found, starting with defaults..

Explanation   One or more Cisco IP Voice Media Streaming App service parameter settings for the MTP device were not found in the database. The default values are included here.

Recommended Action   Configure the service parameter settings for the MTP device.

Error Message

%UC_IPVMS-3-kReadCfgCFBComException: %[DeviceName=String][Description=String][AppID=String][ClusterID=String][NodeID=String]: COM error..

Explanation   A COM error occurred while trying to read CFB configuration information.

Recommended Action   Device will not start; fix problem and restart service.

Error Message

%UC_IPVMS-3-kReadCfgCFBDblException: %[DeviceName=String][ExceptionStr=String][ExceptionID=ULong][AppID=String][ClusterID=String][NodeID=String]: Database exception..

Explanation   A database exception occurred while trying to read CFB configuration information.

Recommended Action   Device will not start; fix database problem and restart service.

Error Message

%UC_IPVMS-3-kReadCfgCFBListComException: %[DeviceName=String][Description=String][AppID=String][ClusterID=String][NodeID=String]: COM error..

Explanation   A COM error occurred while trying to read CFB Cisco Unified Communications Manager list information.

Recommended Action   Device will not start; fix problem and restart service.

Error Message

%UC_IPVMS-3-kReadCfgCFBListDblException: %[DeviceName=String][ExceptionStr=String][ExceptionID=ULong][AppID=String][ClusterID=String][NodeID=String]: Database exception..

Explanation   A database exception occurred while trying to read CFB Cisco Unified Communications Manager list information.

Recommended Action   Device will not start; fix database problem and restart service.

Error Message

%UC_IPVMS-3-kReadCfgCFBListUnknownException: %[DeviceName=String][AppID=String][ClusterID=String][NodeID=String]: Unknown exception..

Explanation   An unknown exception occurred while trying to read CFB Cisco Unified Communications Manager list information.

Recommended Action   Device will not start; fix problem and restart service.

Error Message

%UC_IPVMS-3-kReadCfgCFBUnknownException: %[DeviceName=String][AppID=String][ClusterID=String][NodeID=String]: Unknown exception..

Explanation   An unknown exception occurred while trying to read CFB configuration information.

Recommended Action   Device will not start; fix problem and restart service.

Error Message

%UC_IPVMS-6-kReadCfgDblGetChgNotifyFailed: %[AppID=String][ClusterID=String][NodeID=String]: Get change notification port failure..

Explanation   The database layer was unable to find change notification port and is using default.

Recommended Action   If default change notification is incorrect or change notification does not work, add value into database and restart service.

Error Message

%UC_IPVMS-3-kReadCfgDblGetNodeNameFailed: %[AppID=String][ClusterID=String][NodeID=String]: Database layer select my process node failed..

Explanation   The database layer was unable to find/determine the current node on which this service is running.

Recommended Action   Make sure the database is configured properly.

Error Message

%UC_IPVMS-3-kReadCfgMOHAudioSourceComException: %[DeviceName=String][Description=String][AppID=String][ClusterID=String][NodeID=String]: COM error..

Explanation   A COM error occurred while trying to read MOH audio sources.

Recommended Action   Audio sources will be disabled; fix problem and restart service.

Error Message

%UC_IPVMS-3-kReadCfgMOHAudioSourceDblException: %[DeviceName=String][ExceptionStr=String][ExceptionID=ULong][AppID=String][ClusterID=String][NodeID=String]: Database exception..

Explanation   A database exception occurred while trying to read MOH audio sources.

Recommended Action   Audio sources will be disabled; fix database problem and restart service.

Error Message

%UC_IPVMS-3-kReadCfgMOHAudioSourceUnknownException: %[DeviceName=String][AppID=String][ClusterID=String][NodeID=String]: Unknown exception..

Explanation   An unknown exception occurred while trying to read MOH audio sources.

Recommended Action   Audio sources will be disabled; fix problem and restart service.

Error Message

%UC_IPVMS-3-kReadCfgMOHComException: %[DeviceName=String][Description=String][AppID=String][ClusterID=String][NodeID=String]: COM error..

Explanation   A COM error occurred while trying to read MOH configuration information.

Recommended Action   Device will not start; fix problem and restart service.

Error Message

%UC_IPVMS-3-kReadCfgMOHDblException: %[DeviceName=String][ExceptionStr=String][ExceptionID=ULong][AppID=String][ClusterID=String][NodeID=String]: Database exception..

Explanation   A database exception occurred while trying to read MOH configuration information.

Recommended Action   Device will not start; fix database problem and restart service.

Error Message

%UC_IPVMS-6-kReadCfgMOHEnabledCodecsNotFound: %[AppID=String][ClusterID=String][NodeID=String]: MOH enabled codecs not found..

Explanation   The Music-on-Hold service parameter for codec selection could not be read from database. Defaulting to G.711 mu-law codec.

Recommended Action   Set the Music-on-Hold service parameter for Cisco IP Voice Media Streaming App service.

Error Message

%UC_IPVMS-3-kReadCfgEnterpriseComException: %[Description=String][AppID=String][ClusterID=String][NodeID=String]: COM error..

Explanation   A COM error occurred while trying to read clsterwide service parameters.

Recommended Action   MOH or ANN audio sources may be unavailable; fix problem and restart service.

Error Message

%UC_IPVMS-3-kReadCfgEnterpriseDblException: %[ExceptionStr=String][ExceptionID=ULong][AppID=String][ClusterID=String][NodeID=String]: Database exception..

Explanation   A database exception occurred while trying to read clusterwide service parameters.

Recommended Action   MOH or ANN audio sources may be unavailable; fix database problem and restart service.

Error Message

%UC_IPVMS-3-kReadCfgEnterpriseUnknownException: %[AppID=String][ClusterID=String][NodeID=String]: Unknown exception..

Explanation   An unknown exception occurred while tring to read clusterwide service parameters.

Recommended Action   MOH or ANN audio sources may be unavailable; fix problem and restart service.

Error Message

%UC_IPVMS-3-kReadCfgMOHListComException: %[DeviceName=String][Description=String][AppID=String][ClusterID=String][NodeID=String]: COM error..

Explanation   A COM error occurred while trying to read MOH Cisco Unified Communications Manager list information.

Recommended Action   Device will not start; fix problem and restart service.

Error Message

%UC_IPVMS-3-kReadCfgMOHListDblException: %[DeviceName=String][ExceptionStr=String][ExceptionID=ULong][AppID=String][ClusterID=String][NodeID=String]: Database exception..

Explanation   A database exception occurred while trying to read MOH Cisco Unified Communications Manager list information.

Recommended Action   Device will not start; fix database problem and restart service.

Error Message

%UC_IPVMS-3-kReadCfgMOHListUnknownException: %[DeviceName=String][AppID=String][ClusterID=String][NodeID=String]: Unknown exception..

Explanation   An unknown exception occurred while trying to read MOH Cisco Unified Communications Manager list information.

Recommended Action   Device will not start; fix problem and restart service.

Error Message

%UC_IPVMS-3-kReadCfgMOHServerComException: %[DeviceName=String][Description=String][AppID=String][ClusterID=String][NodeID=String]: COM error..

Explanation   A COM error occurred while trying to read MOH device information.

Recommended Action   Device will not start; fix problem and restart service.

Error Message

%UC_IPVMS-3-kReadCfgMOHServerDblException: %[DeviceName=String][ExceptionStr=String][ExceptionID=ULong][AppID=String][ClusterID=String][NodeID=String]: Database exception..

Explanation   A database exception occurred while trying to read MOH device information.

Recommended Action   Device will not start; fix database problem and restart service.

Error Message

%UC_IPVMS-3-kReadCfgMOHServerUnknownException: %[DeviceName=String][AppID=String][ClusterID=String][NodeID=String]: Unknown exception..

Explanation   An unknown exception occurred while trying to read MOH device information.

Recommended Action   Device will not start; fix problem and restart service.

Error Message

%UC_IPVMS-3-kReadCfgMOHTFTIPAddressNotFound: %[AppID=String][ClusterID=String][NodeID=String]: MOH TFTP IP address not found..

Explanation   The default MOH TFTP IP address was not found in the database.

Recommended Action   Audio sources may be unavailable; create proper value in database and restart service.

Error Message

%UC_IPVMS-3-kReadCfgMOHUnknownException: %[DeviceName=String][AppID=String][ClusterID=String][NodeID=String]: Unknown exception..

Explanation   An unknown exception occurred while trying to read MOH configuration information.

Recommended Action   Device will not start; fix problem and restart service.

Error Message

%UC_IPVMS-3-kReadCfgMTPComException: %[DeviceName=String][Description=String][AppID=String][ClusterID=String][NodeID=String]: COM error..

Explanation   A COM error occurred while trying to read MTP configuration information.

Recommended Action   Device will not start; fix problem and restart service.

Error Message

%UC_IPVMS-3-kReadCfgMTPDblException: %[DeviceName=String][ExceptionStr=String][ExceptionID=ULong][AppID=String][ClusterID=String][NodeID=String]: Database exception..

Explanation   A database exception occurred while trying to read MTP configuration information.

Recommended Action   Device will not start; fix database problem and restart service.

Error Message

%UC_IPVMS-3-kReadCfgMTPListComException: %[DeviceName=String][Description=String][AppID=String][ClusterID=String][NodeID=String]: COM error..

Explanation   A COM error occurred while trying to read MTP Cisco Unified Communications Manager list information.

Recommended Action   Device will not start; fix problem and restart service.

Error Message

%UC_IPVMS-3-kReadCfgMTPListDblException: %[DeviceName=String][ExceptionStr=String][ExceptionID=ULong][AppID=String][ClusterID=String][NodeID=String]: Database exception..

Explanation   A database exception occurred while trying to read MTP Cisco Unified Communications Manager list information.

Recommended Action   Device will not start; fix database problem and restart service.

Error Message

%UC_IPVMS-3-kReadCfgMTPListUnknownException: %[DeviceName=String][AppID=String][ClusterID=String][NodeID=String]: Unknown exception..

Explanation   An unknown exception occurred while trying to read MTP Cisco Unified Communications Manager list information.

Recommended Action   Device will not start; fix problem and restart service.

Error Message

%UC_IPVMS-3-kReadCfgMTPUnknownException: %[DeviceName=String][AppID=String][ClusterID=String][NodeID=String]: Unknown exception..

Explanation   An unknown exception occurred while trying to read MTP configuration information.

Recommended Action   Device will not start; fix problem and restart service.

Error Message

%UC_IPVMS-4-kRequestedCFBStreamsFailed: %[Requested=ULong][Allocated=ULong][AppID=String][ClusterID=String][NodeID=String]: CFB requested streams failure..

Explanation   The resources for the number of requested full-duplex streams was not available.

Recommended Action   Verify the Cisco IP Voice Media Streaming App service parameter for number of CFB calls. Restart the server to reset the stream resources.

Error Message

%UC_IPVMS-4-kRequestedMOHStreamsFailed: %[Requested=ULong][Allocated=ULong][AppID=String][ClusterID=String][NodeID=String]: MOH requested streams failure..

Explanation   The resources for the number of requested streams was not available.

Recommended Action   Verify the number of calls configuration setting for Music-on-Hold device. Restart the server to reset the resources.

Error Message

%UC_IPVMS-4-kRequestedMTPStreamsFailed: %[Requested=ULong][Allocated=ULong][AppID=String][ClusterID=String][NodeID=String]: MTP requested streams failure..

Explanation   The resources for the number of requested full-duplex Media Termination Point streams was not available.

Recommended Action   Verify the Cisco IP Voice Media Streaming App service parameter setting for number of MTP calls is correct. Restart the server to reset the available resources.

Error Message

%UC_IPVMS-4-MOHDeviceRecoveryCreateFailed: %[Error=ULong][ErrorText=String][AppID=String][ClusterID=String][NodeID=String]: MOH device recovery create failure..

Explanation   An error was encountered restarting the Music-on-Hold device. This may be caused by a shortage of memory resources.

Recommended Action   Check the status of the Music-on-Hold device. If the MOH device is not registered and available, Restart the Cisco IP Voice Media Streaming App service or restart the server.

Error Message

%UC_IPVMS-4-MTPDeviceRecoveryCreateFailed: %[Error=ULong][ErrorText=String][AppID=String][ClusterID=String][NodeID=String]: MTP device recovery create failure..

Explanation   An error was encountered trying to restart the Media Termination Point device. This may be due to a shortage of application memory.

Recommended Action   Restart the IP Voice Media Streaming App service or restart the server.

Error Message

%UC_IPVMS-4-SoftwareLicenseNotValid: %[AppID=String][ClusterID=String][NodeID=String]: Invalid Software License..

Explanation   There is no valid software license; the Cisco IP Voice Media Streaming App service requires a valid software license to operate.

Recommended Action   Install a valid software license and restart Cisco IP Voice Media Streaming App service.

Error Message

%UC_IPVMS-6-SoftwareLicenseValid: %[AppID=String][ClusterID=String][NodeID=String]: Valid Software License Found..

Explanation   A valid software license has been detected by the IP Voice Media Streaming App service.

Recommended Action   No action required. This informational message indicates alarm SoftwareLicenseNotValid is cleared.

Error Message

%UC_IPVMS-4-kANNAudioFileMissing: %[Filename=String][AnnouncementID=ULong][UserLocale=ULong][NetworkLocale=ULong][AppID=String][ClusterID=String][NodeID=String]: Announcement file not found..

Explanation   The annunciator was unable to access an announcement audio file. This may be caused by not uploading a custom announcement to each server in the cluster or a locale has not been installed on the server.

Recommended Action   Upload the custom announcement to the server or install the missing locale package.

Error Message

%UC_IPVMS-3-CryptoCapabilityFailed: %[Devicename=String][AppID=String][ClusterID=String][NodeID=String]: Failed to initialize sRTP crypto..

Explanation   The media device shown in this alarm attempted to load and initialize crypto capabilities within the operating system kernel, however, a failure, such as the OS lacking encryption configuration, a memory shortage, or crypto self-test failure, occurred during initialization. Secure media encryption for this device has been disabled as a result, but unencrypted media is still supported. All media streams are non-secure (unencrypted) for this device. This alarm is capable of occurring when the crypto failure occurs because the Cisco IP Voice Media Streaming App service parameter Force Annunciator to be Non-secure or Force MOH to be Non-secure is enabled.

Recommended Action   Use the Cisco Unified Real-Time Monitoring Tool (RTMT) to retrieve the system log. Review the system log and respond to error messages containing sRTP or IpVms.

Error Message

%UC_IPVMS-4-PlayAnnouncementFailure: %[ReasonCode=ULong][Identifier=String][Locale=String][AnnouncementEnum=ULong][FileName=String][CustomFileName=String][AppID=String][ClusterID=String][NodeID=String]: Unable to play a requested announcement or tone.

Explanation   Reason code explanations: [1] Announcement requested is undefined. The announcement enum number is unknown. [2] Locale requested is unknown. The requested locale has not been installed on this node. [3] The customized announcement file does not exist on this server node for the locale. If a default system announcement is assigned, it will be used in place of the customized announcement. [4] Internal annunciator resource shortage has caused the announcement to fail. [5] System announcement or tone file not found.

Recommended Action   Recommendations based on reason code: [1] this is usually a system design issue and cannot be resolved by normal means; [2] Be sure the requested locale is installed on each CUCM server node; [3] Upload the customized announcement wav file to this server node using CCM Administration on this node; [4] Review the annunciator device configuration for maximum number of calls and/or schedule an annunciator device reset as a temporary workaround to ensure orphanned resources are released or restart the Cisco IP Voice Media Streaming App service; [5] Check locale is installed on CUCM server node or possible missing file not installed properly.

Error Message

%UC_TFTP-1-CreateThreadFailed: %[Error=Int][Reason=String][AppID=String][ClusterID=String][NodeID=String]: Failed to create a new thread. See Reason string for where it failed..

Explanation   This usually happens when there are system issues such as running out of memory resources.

Recommended Action   Use RTMT to monitor the system memory resources and consumption and correct any system issues that might be contributing to a reduced amount of system resources.

Error Message

%UC_TFTP-1-SDIControlLayerFailed: %[Error=Int][Reason=String][AppID=String][ClusterID=String][NodeID=String]: Failed to update trace logging or alarm subsystem for new settings..

Explanation   This usually indicates a lack of system resources or a failure in database access by the trace logging or alarm subsystem.

Recommended Action   In Cisco Unified Serviceability, enable Detailed level traces in the Trace Configuration window for TFTP and Cisco Database Layer Monitor services. Also, use RTMT to look for error messages that may have occurred around the time of the alarm. Ensure that the database server is running, and that the Cisco Database Layer Monitor service is running without problems. If this alarm persists, contact the Cisco Technical Assistance Center (TAC) with TFTP service and database trace files.

Error Message

%UC_TFTP-3-ConfigThreadReadConfigurationFailed: %[AppID=String][ClusterID=String][NodeID=String]: Failed to retrieve enterprise parameter values from database at TFTP service startup..

Explanation   This is usually caused by database access failure.

Recommended Action   In Cisco Unified Serviceability, enable Detailed level traces in the Trace Configuration window for TFTP and Cisco Database Layer Monitor services. Also, use RTMT to look for error messages that may have occurred around the time of the alarm.

Error Message

%UC_TFTP-3-ConfigThreadBuildFileFailed: %[AppID=String][ClusterID=String][NodeID=String]: Failed to build all device configuration files at TFTP service startup..

Explanation   This is usually caused by database access failure.

Recommended Action   In Cisco Unified Serviceability, enable Detailed level traces in the Trace Configuration window for TFTP and Cisco Database Layer Monitor services. Also, use RTMT to look for error messages that may have occurred around the time of the alarm.

Error Message

%UC_TFTP-1-ConfigThreadChangeNotifyServerInstanceFailed: %[AppID=String][ClusterID=String][NodeID=String]: Failed to allocate resources to handle configuration change notification from database..

Explanation   This usually indicates a lack of memory when there is a system issue such as running out of resources.

Recommended Action   Use RTMT to monitor the system memory resources and consumption and correct any system issues that might be contributing to a reduced amount of system resources.

Error Message

%UC_TFTP-1-ConfigThreadChangeNotifyServerSingleFailed: %[AppID=String][ClusterID=String][NodeID=String]: Failed to allocate resources to handle configuration change notification from database..

Explanation   This usually indicates a lack of memory when there is a system issue such as running out of resources.

Recommended Action   Use RTMT to monitor the system memory resources and consumption and correct any system issues that might be contributing to a reduced amount of system resources.

Error Message

%UC_TFTP-1-ConfigThreadChangeNotifyServerStartFailed: %[AppID=String][ClusterID=String][NodeID=String]: Failed to start listening to configuration change notification from database..

Explanation   This usually indicates a lack of memory when there is a system issue such as running out of resources.

Recommended Action   Use RTMT to monitor the system memory resources and consumption and correct any system issues that might be contributing to a reduced amount of system resources.

Error Message

%UC_TFTP-3-ConfigThreadCNCMGrpBuildFileFailed: %[AppID=String][ClusterID=String][NodeID=String]: Failed to rebuild configuration files for changes in Cisco Unified Communications Manager Group settings..

Explanation   This is usually caused by a failure to access the Cisco Unified Communications Manager database.

Recommended Action   In Cisco Unified Serviceability, enable Detailed level traces in the Trace Configuration window for TFTP and Cisco Database Layer Monitor services. Also, use RTMT to look for error messages that may have occurred around the time of the alarm.

Error Message

%UC_TFTP-3-ConfigThreadCNGrpBuildFileFailed: %[AppID=String][ClusterID=String][NodeID=String]: Failed to rebuild configuration files for changes at group level settings such as Device Pool or Common Device Config settings..

Explanation   This is usually caused by a failure to access the Cisco Unified Communications Manager database.

Recommended Action   In Cisco Unified Serviceability, enable Detailed level traces in the Trace Configuration window for TFTP and Cisco Database Layer Monitor services. Also, use RTMT to look for error messages that may have occurred around the time of the alarm.

Error Message

%UC_TFTP-3-ConfigThreadUnknownExceptionCaught: %[AppID=String][ClusterID=String][NodeID=String]: An exception is caught in the main processing routine..

Explanation   This alarm is sent in conjunction with other alarms for failure when building configuration files or when the TFTP service is attempting to retrieve the values in the system's enterprise parameters.

Recommended Action   In Cisco Unified Serviceability, enable Detailed level traces in the Trace Configuration window for TFTP service. Also, use RTMT to look for error messages that may have occurred around the time of the alarm.

Error Message

%UC_TFTP-3-ReadConfigurationUnknownException: %[AppID=String][ClusterID=String][NodeID=String]: An exception is caught while retrieving enterprise parameters value from database at TFTP service startup..

Explanation   This is usually caused by a failure to access the Cisco Unified Communications Manager database.

Recommended Action   In Cisco Unified Serviceability, enable Detailed level traces in the Trace Configuration window for TFTP and Cisco Database Layer Monitor services. Also, use RTMT to look for error messages that may have occurred around the time of the alarm.

Error Message

%UC_TFTP-3-ConfigItAllReadConfigurationFailed: %[AppID=String][ClusterID=String][NodeID=String]: Failed to retrieve enterprise parameter values from database when rebuilding all configuration files..

Explanation   This is usually caused by a failure to access the Cisco Unified Communications Manager database.

Recommended Action   In Cisco Unified Serviceability, enable Detailed level traces in the Trace Configuration window for TFTP and Cisco Database Layer Monitor services. Also, use RTMT to look for error messages that may have occurred around the time of the alarm.

Error Message

%UC_TFTP-3-ConfigItAllBuildFilesFailed: %[AppID=String][ClusterID=String][NodeID=String]: A complete rebuild of all device configuration files has failed..

Explanation   Probable causes of this alarm could be failure to access the Cisco Unified Communications Manager database, or misconfiguration of some devices.

Recommended Action   In Cisco Unified Serviceability, enabled Detailed level traces in the Trace Configuration window for TFTP and Cisco Database Layer Monitor services. Also, use RTMT to look for error messages that may have occurred around the time of the alarm.

Error Message

%UC_TFTP-1-SocketError: %[nError=Int][Reason=String][AppID=String][ClusterID=String][NodeID=String]: Failed to open network connection for receiving file requests..

Explanation   This usually happens when the IP address that the TFTP service uses to open the network connection is invalid.

Recommended Action   Verify that the TFTP service parameter, TFTP IP Address, accurately specifies the IP address of the NIC card to use for serving files via TFTP. See the help for the (advanced) TFTP IP Address service parameter for more information. If the problem persists, go to Cisco Unified Serviceability and enable Detailed level traces in the Trace Configuration window for the TFTP service and contact the Cisco Technical Assistance Center (TAC).

Error Message

%UC_TFTP-1-TFTPServerListenSetSockOptFailed: %[nError=Int][IPAddress=String][Port=Int][AppID=String][ClusterID=String][NodeID=String]: Failed to increase the size of the network buffer for receiving file requests..

Explanation   This usually indicates a lack of memory when there is a system issue such as running out of resources.

Recommended Action   Use RTMT to monitor the system memory resources and consumption and correct any system issues that might be contributing to a reduced amount of system resources.

Error Message

%UC_TFTP-1-TFTPServerListenBindFailed: %[nError=Int][IPAddress=String][Port=Int][AppID=String][ClusterID=String][NodeID=String]: Fail to connect to the network port through which file requests are received..

Explanation   This usually happens if the network port is being used by other applications on the system or if the port was not closed properly in the last execution of TFTP server.

Recommended Action   Verify that the port is not in use by other application. After stopping the TFTP server, at the command line interface (CLI) on the TFTP server, execute the following command: show network status listen. If the port number specified in this alarm is shown in this CLI command output, the port is being used. Restart the Cisco Unified Communications Manager system, which may help to release the port. If the problem persists, go to Cisco Unified Serviceability and enable Detailed level traces in the Trace Configuration window for the TFTP service and contact the Cisco Technical Assistance Center (TAC).

Error Message

%UC_TFTP-4-NoCallManagerFound: %[Error=String][AppID=String][ClusterID=String][NodeID=String]: No Cisco Unified Communications Manager (Unified CM, formerly known as Cisco Unified CallManager) node has been configured..

Explanation   A Cisco Unified Communications Manager Group exists but it has no Unified CM node configured as its group member.

Recommended Action   In Cisco Unified CM Administration (System > Cisco Unified CM Group), configure at least one Unified CM node for the Unified CM Group referenced in this alarm. The Unified CM Group is part of the device pool to which the specified phone belongs.

Error Message

%UC_TFTP-3-CNFFBuffWriteToFilefopenfailed: %[FileName=String][AppID=String][ClusterID=String][NodeID=String]: Failed to create Config File on disk or update existing Config File on disk..

Explanation   This may happen if disk is full or the file is in use.

Recommended Action   Using RTMT, check the disk utilization and correct any issue discovered. If you do not discover a disk space issue, try restarting the TFTP service from Cisco Unified Serviceability (Tools > Control Center - Feature Services). Stopping and restarting the TFTP service is useful because the Config File that the TFTP service is trying to save might be an existing file that is in use. If you still get this error, go to Cisco Unified Serviceability and enable Detailed level traces in the Trace Configuration window for the TFTP service and contact the Cisco Technical Assistance Center (TAC).

Error Message

%UC_TFTP-3-CNFFBuffWriteToFilefwritefailed: %[FileName=String][AppID=String][ClusterID=String][NodeID=String]: Failed to save Config File to disk..

Explanation   This may happen if disk is full or the file is in use.

Recommended Action   Using RTMT, check the disk utilization and correct any issue discovered. If you do not discover a disk space issue, try restarting the TFTP service from Cisco Unified Serviceability (Tools > Control Center - Feature Services). Stopping and restarting the TFTP service is useful because the Config File that the TFTP service is trying to save might be an existing file that is in use. If you still get this error, go to Cisco Unified Serviceability and enable Detailed level traces in the Trace Configuration window for the TFTP service and contact the Cisco Technical Assistance Center (TAC).

Error Message

%UC_TFTP-4-ServingFileWarning: %[ErrorNumber=Int][FileName=String][IPAddress_Port=String][Mode=String][OpCode=Int][Reason=String][AppID=String][ClusterID=String][NodeID=String]: There was an error during processing of file request..

Explanation   This could happen if the requested file is not found by the server, or other error indicated by the "Reason" clause when processing the file request.

Recommended Action   You can safely ignore this alarm if the reason shown in this alarm is "File not found" and if that file is the MAC address-based file name for a phone that you are auto-registering; in that case, the phone is not yet registered with the database and so it is normal for the phone's file not be found. In the case that auto-registration is disabled, this alarm shows that the phone or device is not added to Cisco Unified Communications Manager (Unified CM). Either add the phone to Unified CM or remove the phone from the network. If you still get this error after removing the phone(s), go to Cisco Unified Serviceability and enable Detailed level traces in the Trace Configuration window for the TFTP service and contact the Cisco Technical Assistance Center (TAC).

Error Message

%UC_TFTP-3-ThreadPoolProxyUnknownException: %[AppID=String][ClusterID=String][NodeID=String]: Unknown exception was caught while processing file request..

Explanation   This usually indicates a lack of memory when there is a system issue such as running out of resources.

Recommended Action   Use RTMT to monitor the system memory resources and consumption and correct any system issues that might be contributing to a reduced amount of system resources.

Error Message

%UC_TFTP-6-BuildStat: %[DeviceCount=Int][DeviceTime=Int][UnitCount=Int][UnitTime=Int][SoftkeyCount=Int][SoftkeyTime=Int][FeatureControlPolicyTime=Int][FeatureControlPolicyCount=Int][DialruleCount=Int][DialruleTime=Int][TotalTime=Int][BuildStatus=String][AppID=String][ClusterID=String][NodeID=String]: Device configuration files are being built..

Explanation   This alarm provides information about the BUILD ALL operation to build all types of configuration files.

Recommended Action   This alarm is for information purposes only; no action is required.

Error Message

%UC_TFTP-3-IPv6InterfaceNotInstalled: %[AppID=String][ClusterID=String][NodeID=String]: IPv6 network interface is not installed..

Explanation   IPv6 option is enabled for TFTP service but the IPv6 network interface/address has not been configured on the system. Until the IPv6 network is functioning, devices that have been configured with IPv6-only will not be able to register. Devices that have been configured to use either IPv6 or IPv4 will register using IPv4. When the IPv6 network is online, IPv6-capable devices that have registered as IPv4 will remain IPv4 until they are reset, at which time they will use IPv6 if available.

Recommended Action   Install IPv6 network interface and then restart TFTP service.

Error Message

%UC_TFTP-5-ITLFileRegenerated: %[AppID=String][ClusterID=String][NodeID=String]: ITL file regeneration.

Explanation   This is for regeneration of ITLFile

Recommended Action   Use RTMT to monitor the system memory resources and consumption and correct any system issues that might be contributing to a reduced amount of system resources.

Error Message

%UC_TCD-0-IPAddressResolveError: %[HostName=String][AppID=String][ClusterID=String][NodeID=String]: The IP Address for host was NOT RESOLVED.

Explanation   The IP Address for host was NOT RESOLVED

Recommended Action   NONE

Error Message

%UC_TCD-0-NoCMEntriesInDB: %[AppID=String][ClusterID=String][NodeID=String]: There are no CallManager entries in the database..

Explanation   There are no CallManager entries in the database.

Recommended Action   NONE

Error Message

%UC_TCD-6-LoadShareDeActivateTimeout: %[AppID=String][ClusterID=String][NodeID=String]: There was timeout during wait for DeActivateLoadShare acknowledgement.

Explanation   There was timeout during wait for DeActivateLoadShare acknowledgement

Recommended Action   NONE

Error Message

%UC_TCD-0-LineStateSrvEngCreationError: %[AppID=String][ClusterID=String][NodeID=String]: There was an error during the LineStateSrvEng Creation.

Explanation   There was an error during the LineStateSrvEng Creation

Recommended Action   NONE

Error Message

%UC_TCD-0-GlobalSPUtilsCreationError: %[AppID=String][ClusterID=String][NodeID=String]: There was an error during the GlobalSPUtils creation.

Explanation   There was an error during the GlobalSPUtils creation

Recommended Action   NONE

Error Message

%UC_TCD-0-TapiLinesTableCreationError: %[AppID=String][ClusterID=String][NodeID=String]: There was an error during the TapiLinesTable creation.

Explanation   There was an error during the TapiLinesTable creation

Recommended Action   NONE

Error Message

%UC_TCD-0-HuntGroupControllerCreationError: %[AppID=String][ClusterID=String][NodeID=String]: There was an error during the HuntGroupController creation.

Explanation   There was an error during the HuntGroupController creation

Recommended Action   NONE

Error Message

%UC_TCD-0-HuntGroupCreationError: %[AppID=String][ClusterID=String][NodeID=String]: There was an error during the Hunt Group creation.

Explanation   There was an error during the Hunt Group creation

Recommended Action   NONE

Error Message

%UC_TCD-0-CallDirectorCreationError: %[AppID=String][ClusterID=String][NodeID=String]: There was an error during the CallDirector creation.

Explanation   There was an error during the CallDirector creation

Recommended Action   NONE

Error Message

%UC_TCD-0-SysControllerCreationError: %[AppID=String][ClusterID=String][NodeID=String]: There was an error during the SysController creation.

Explanation   There was an error during the SysController creation

Recommended Action   NONE

Error Message

%UC_TCD-0-TimerServicesCreationError: %[AppID=String][ClusterID=String][NodeID=String]: There was an error during the TimerServices creation.

Explanation   There was an error during the TimerServices creation

Recommended Action   NONE

Error Message

%UC_TCD-3-DBLGetVersionInfoError: %[AppID=String][ClusterID=String][NodeID=String]: DBL GetVersionInfo function returned NULL.

Explanation   DBL GetVersionInfo function returned NULL

Recommended Action   NONE

Error Message

%UC_TCD-0-ExcceptionInInitSDIConfiguration: %[AppID=String][ClusterID=String][NodeID=String]: Exception occured in InitSDIConfiguration function.

Explanation   Exception occured in InitSDIConfiguration function

Recommended Action   NONE

Error Message

%UC_TCD-0-SyncDBCreationError: %[AppID=String][ClusterID=String][NodeID=String]: There was an error during the SyncDB creation in SysController.

Explanation   There was an error during the SyncDB creation in SysController

Recommended Action   NONE

Error Message

%UC_TCD-0-LostConnectionToCM: %[AppID=String][ClusterID=String][NodeID=String]: Connection to CallManager was lost.

Explanation   Connection to CallManager was lost

Recommended Action   NONE

Error Message

%UC_TCD-6-UserLoginSuccess: %[UserID=String][AppID=String][ClusterID=String][NodeID=String]: User successfully logged in..

Explanation   User successfully logged in.

Recommended Action   NONE

Error Message

%UC_TCD-3-UserLoginFailed: %[UserID=String][AppID=String][ClusterID=String][NodeID=String]: User log in failed because of bad user id or password..

Explanation   User log in failed because of bad user id or password.

Recommended Action   NONE

Error Message

%UC_TCD-6-UserAlreadyLoggedIn: %[UserID=String][AppID=String][ClusterID=String][NodeID=String]: User is already logged in.

Explanation   User is already logged in

Recommended Action   NONE

Error Message

%UC_TCD-6-UserLoggedOut: %[UserID=String][AppID=String][ClusterID=String][NodeID=String]: User logged out.

Explanation   User logged out

Recommended Action   NONE

Error Message

%UC_TCD-6-AgentOnline: %[AppID=String][ClusterID=String][NodeID=String]: Agent online.

Explanation   Agent online

Recommended Action   NONE

Error Message

%UC_TCD-6-AgentOffline: %[AppID=String][ClusterID=String][NodeID=String]: Agent offline.

Explanation   Agent offline

Recommended Action   NONE

Error Message

%UC_JAVAAPPLICATIONS-6-IPMAStarted: %[ServletName=String][Reason=String][AppID=String][ClusterID=String][NodeID=String]: IPMA Application started .

Explanation   Application started successfully

Recommended Action   No action required.

Error Message

%UC_JAVAAPPLICATIONS-3-UserSyncFail: %[Userid=String][Reason=String][AppID=String][ClusterID=String][NodeID=String]: User is not Synced.

Explanation   While updating the data in db for User Db gave exception

Recommended Action   Check the reason for exception and proceed accordingly.

Error Message

%UC_JAVAAPPLICATIONS-4-IPMAStopped: %[ServletName=String][Reason=String][AppID=String][ClusterID=String][NodeID=String]: IPMA Application stopped.

Explanation   Application was unloaded from Tomcat

Recommended Action   Check if Tomcat service is up.

Error Message

%UC_JAVAAPPLICATIONS-0-IPMANotStarted: %[ServletName=String][Reason=String][AppID=String][ClusterID=String][NodeID=String]: IPMA Application not started.

Explanation   Error occurred while starting application

Recommended Action   See application logs for error

Error Message

%UC_JAVAAPPLICATIONS-3-IPMAApplicationError: %[ServletName=String][Reason=String][AppID=String][ClusterID=String][NodeID=String]: IPMA Application error.

Explanation   IPMA application error

Recommended Action   See application logs for details

Error Message

%UC_JAVAAPPLICATIONS-4-IPMAManagerLogout: %[ServletName=String][Reason=String][AppID=String][ClusterID=String][NodeID=String]: IPMA Manager Logged out.

Explanation   IPMA Manager Logged out by application

Recommended Action   To re-login the user, click update in the CCMAdmin IPMA Service configuration page for this user.

Error Message

%UC_JAVAAPPLICATIONS-3-IPMAOverloaded: %[ServletName=String][Reason=String][AppID=String][ClusterID=String][NodeID=String]: IPMA Application overloaded.

Explanation   IPMA application overloaded

Recommended Action   See application logs for details

Error Message

%UC_JAVAAPPLICATIONS-3-IPMAFilteringDown: %[ServletName=String][Reason=String][AppID=String][ClusterID=String][NodeID=String]: IPMA Application filtering is down.

Explanation   IPMA Application filtering is down

Recommended Action   Restart Cisco IP Manager Assistant Service

Error Message

%UC_JAVAAPPLICATIONS-6-IPMAInformation: %[ServletName=String][Reason=String][AppID=String][ClusterID=String][NodeID=String]: IPMA Information .

Explanation   Application information

Recommended Action   No action required.

Error Message

%UC_JAVAAPPLICATIONS-6-BDIStarted: %[AppID=String][ClusterID=String][NodeID=String]: BDI Application started .

Explanation   Application started successfully

Recommended Action   No action required.

Error Message

%UC_JAVAAPPLICATIONS-4-BDIStopped: %[AppID=String][ClusterID=String][NodeID=String]: BDI Application stopped.

Explanation   Application was unloaded from Tomcat

Recommended Action   Check if Tomcat service is up.

Error Message

%UC_JAVAAPPLICATIONS-0-BDINotStarted: %[Reason=String][AppID=String][ClusterID=String][NodeID=String]: BDI Application not started.

Explanation   Error occurred while starting application

Recommended Action   See application logs for error

Error Message

%UC_JAVAAPPLICATIONS-3-BDIApplicationError: %[Reason=String][AppID=String][ClusterID=String][NodeID=String]: BDI Application error.

Explanation   BDI application error

Recommended Action   See application logs for details

Error Message

%UC_JAVAAPPLICATIONS-3-BDIOverloaded: %[Reason=String][AppID=String][ClusterID=String][NodeID=String]: BDI Application overloaded.

Explanation   BDI application overloaded

Recommended Action   See application logs for details

Error Message

%UC_JAVAAPPLICATIONS-6-WDStarted: %[ServletName=String][Reason=String][AppID=String][ClusterID=String][NodeID=String]: WebDialer Application started .

Explanation   Application started successfully

Recommended Action   No action required.

Error Message

%UC_JAVAAPPLICATIONS-4-WDStopped: %[ServletName=String][Reason=String][AppID=String][ClusterID=String][NodeID=String]: WebDialer Application stopped.

Explanation   Application was unloaded from Tomcat

Recommended Action   Check if Tomcat service is up.

Error Message

%UC_JAVAAPPLICATIONS-0-WDNotStarted: %[ServletName=String][Reason=String][AppID=String][ClusterID=String][NodeID=String]: Failed to startup WebDialer application.

Explanation   Error occurred while starting application

Recommended Action   See application logs for error

Error Message

%UC_JAVAAPPLICATIONS-3-WDApplicationError: %[ServletName=String][Reason=String][AppID=String][ClusterID=String][NodeID=String]: WebDialer Application error.

Explanation   WebDialer application error

Recommended Action   See application logs for details

Error Message

%UC_JAVAAPPLICATIONS-3-WDOverloaded: %[ServletName=String][Reason=String][AppID=String][ClusterID=String][NodeID=String]: WebDialer Application overloaded.

Explanation   WebDialer application overloaded

Recommended Action   See application logs for details

Error Message

%UC_JAVAAPPLICATIONS-6-WDInformation: %[ServletName=String][Reason=String][AppID=String][ClusterID=String][NodeID=String]: WebDialer informational alarm.

Explanation   WebDialer application informational alarm

Recommended Action   No action required

Error Message

%UC_JAVAAPPLICATIONS-6-CiscoDirSyncStarted: %[AppID=String][ClusterID=String][NodeID=String]: Cisco DirSync Application started .

Explanation   Application started successfully

Recommended Action   No action required.

Error Message

%UC_JAVAAPPLICATIONS-0-CiscoDirSyncStartFailure: %[AppID=String][ClusterID=String][NodeID=String]: Cisco DirSymc application failed to start successfully.

Explanation   Error occurred while starting application

Recommended Action   See application logs for error, may require restarting the application

Error Message

%UC_JAVAAPPLICATIONS-6-CiscoDirSyncProcessStarted: %[AgreementId=String][AppID=String][ClusterID=String][NodeID=String]: LDAPSync process started on particular sync agreement.

Explanation   LDAPSync process started to sync user data on the configured agreement id

Recommended Action   No action required

Error Message

%UC_JAVAAPPLICATIONS-2-CiscoDirSyncProcessFailToStart: %[AgreementId=String][AppID=String][ClusterID=String][NodeID=String]: LDAPSync process failed to start on particular sync agreement.

Explanation   LDAPSync process failed to start on the configured agreement id

Recommended Action   See application logs for error

Error Message

%UC_JAVAAPPLICATIONS-6-CiscoDirSyncProcessCompleted: %[AgreementId=String][AppID=String][ClusterID=String][NodeID=String]: LDAPSync process completed on particular sync agreement.

Explanation   LDAPSync process completed to sync user data on the configured agreement id

Recommended Action   No action required

Error Message

%UC_JAVAAPPLICATIONS-6-CiscoDirSyncProcessStoppedManually: %[AgreementId=String][AppID=String][ClusterID=String][NodeID=String]: LDAPSync process stopped manually on particular sync agreement.

Explanation   LDAPSync process stopped manually on the configured agreement id

Recommended Action   No action required

Error Message

%UC_JAVAAPPLICATIONS-6-CiscoDirSyncProcessStoppedAuto: %[AgreementId=String][AppID=String][ClusterID=String][NodeID=String]: LDAPSync process stopped automatically on particular sync agreement.

Explanation   LDAPSync process stopped automatically on the configured agreement id, it will be restarted automatically

Recommended Action   No action required

Error Message

%UC_JAVAAPPLICATIONS-3-CiscoDirSyncProcessFailedRetry: %[AgreementId=String][Reason=String][AppID=String][ClusterID=String][NodeID=String]: LDAPSync process failed on particular sync agreement.

Explanation   LDAPSync process failed to sync user data on the configured agreement id

Recommended Action   No action required. The sync process will automatic retry See application logs for details

Error Message

%UC_JAVAAPPLICATIONS-3-CiscoDirSyncProcessFailedNoRetry: %[AgreementId=String][Reason=String][AppID=String][ClusterID=String][NodeID=String]: LDAPSync process failed on particular sync agreement.

Explanation   LDAPSync process failed to sync user data on the configured agreement id

Recommended Action   See application logs for details, the application will try to sync again in the next scheduled time

Error Message

%UC_JAVAAPPLICATIONS-3-CiscoDirSyncProcessConnectionFailed: %[AgreementId=String][LDAPHost=String][Reason=String][AppID=String][ClusterID=String][NodeID=String]: LDAPSync process failed to connect to LDAP server.

Explanation   LDAPSync process failed to connect to LDAP host

Recommended Action   Please make sure the LDAP server is online. If SSL is used, please make sure the required certificate is available on local CM server. The application will automatically retry

Error Message

%UC_JAVAAPPLICATIONS-3-CiscoDirSyncDBAccessFailure: %[AgreementId=String][Reason=String][AppID=String][ClusterID=String][NodeID=String]: LDAPSync process failed to access local database.

Explanation   CiscoDirSync failed to access local database

Recommended Action   Please make sure the local CallManager database is working properly. The failed sync process will restart at the next scheduled time.

Error Message

%UC_JAVAAPPLICATIONS-6-CiscoDirsyncZeroUsersSynced: %[AgreementId=String][Reason=String][AppID=String][ClusterID=String][NodeID=String]: LDAPSync process synced zero users for the sync agreement.

Explanation   CiscoDirSync synced zero users

Recommended Action   Check the application logs for details

Error Message

%UC_JAVAAPPLICATIONS-6-UserUpdated: %[AgreementId=String][Userid=String][Reason=String][AppID=String][ClusterID=String][NodeID=String]: LDAPSync process found a user with the same userid synced from a different LDAP agreement. Updated the already existing user in the DB with the new user synced .

Explanation    LDAPSync process found a user with the same userid synced from a different LDAP agreement. Updated the already existing user in the DB with the new user synced

Recommended Action   No action required

Error Message

%UC_JAVAAPPLICATIONS-4-DirSyncNoSchedulesFound: %[ScheduleTable=String][AppID=String][ClusterID=String][NodeID=String]: No schedules found in DB for directory synchronization.

Explanation   No automatic LDAP directory synchronization possible

Recommended Action   Check the DirSync configuration

Error Message

%UC_JAVAAPPLICATIONS-6-DirSyncScheduledTaskOver: %[ScheduleID=String][TaskID=String][AppID=String][ClusterID=String][NodeID=String]: Directory synchronization operation got over.

Explanation   Information of the directory synchronization started

Recommended Action   No action required

Error Message

%UC_JAVAAPPLICATIONS-4-DirSyncScheduledTaskTimeoutOccured: %[ScheduleID=String][TaskID=String][AppID=String][ClusterID=String][NodeID=String]: Timeout occurred for directory synchronization task.

Explanation   Timeout occurred for directory synchronization task

Recommended Action   Check the DirSync configuration

Error Message

%UC_JAVAAPPLICATIONS-3-DirSyncScheduledTaskFailed: %[ScheduleID=String][ErrorMessage=String][AppID=String][ClusterID=String][NodeID=String]: Directory synchronization task failed.

Explanation   Directory synchronization task failed

Recommended Action   Check the DirSync configuration and logs

Error Message

%UC_JAVAAPPLICATIONS-3-DirSyncSchedulerFailedToGetDBSchedules: %[Message=String][AppID=String][ClusterID=String][NodeID=String]: Failed to get directory synchronization schedules from DB.

Explanation   Failed to get directory synchronization schedules from DB

Recommended Action   Check the DirSync configuration and logs

Error Message

%UC_JAVAAPPLICATIONS-3-DirSyncSchedulerInvalidEventReceived: %[Action=String][Message=String][AppID=String][ClusterID=String][NodeID=String]: Invalid event received by DirSync scheduler from database.

Explanation   Invalid event received by DirSync scheduler from database

Recommended Action   Check the DirSync configuration and logs

Error Message

%UC_JAVAAPPLICATIONS-3-DirSyncInvalidScheduleFound: %[ScheduleID=String][AppID=String][ClusterID=String][NodeID=String]: Invalid schedule read by DirSync scheduler from database.

Explanation   Invalid schedule read by DirSync scheduler from database

Recommended Action   Check the DirSync configuration and logs

Error Message

%UC_JAVAAPPLICATIONS-3-DirSyncSchedulerFailedToRegisterDBEvents: %[ScheduleTable=String][AppID=String][ClusterID=String][NodeID=String]: DirSync scheduler failed to register DB notifications.

Explanation   Invalid schedule read by DirSync scheduler from database

Recommended Action   Check the DirSync configuration and logs

Error Message

%UC_JAVAAPPLICATIONS-3-DirSyncSchedulerEngineFailedToStart: %[ScheduleTable=String][AppID=String][ClusterID=String][NodeID=String]: DirSync scheduler engine failed to start.

Explanation   DirSync scheduler engine failed to start

Recommended Action   Check the DirSync configuration and logs

Error Message

%UC_JAVAAPPLICATIONS-6-DirSyncSchedulerEngineStopped: %[Version=String][AppID=String][ClusterID=String][NodeID=String]: DirSync scheduler engine stopped.

Explanation   DirSync scheduler engine stopped

Recommended Action   No action required

Error Message

%UC_JAVAAPPLICATIONS-3-DirSyncScheduleDeletionFailed: %[ScheduleID=String][AppID=String][ClusterID=String][NodeID=String]: DirSync schedule deletion request failed.

Explanation   DirSync schedule deletion request failed

Recommended Action   Check the DirSync configuration and logs

Error Message

%UC_JAVAAPPLICATIONS-6-DirSyncNewScheduleInserted: %[ScheduleID=String][AppID=String][ClusterID=String][NodeID=String]: New schedule inserted in the DirSync Scheduler Engine.

Explanation   New schedule inserted in the DirSync Scheduler Engine

Recommended Action   No Action Required

Error Message

%UC_JAVAAPPLICATIONS-3-DirSyncScheduleUpdateFailed: %[ScheduleID=String][AppID=String][ClusterID=String][NodeID=String]: DirSync schedule update request failed.

Explanation   DirSync schedule deletion update failed

Recommended Action   Check the DirSync configuration and logs

Error Message

%UC_JAVAAPPLICATIONS-3-CiscoDRFDBAccessFailure: %[Reason=String][AppID=String][ClusterID=String][NodeID=String]: DRF process failed to access local database.

Explanation   CiscoDirSync failed to access local database

Recommended Action   Please make sure the local CallManager database is working properly. The failed sync process will restart at the next scheduled time.

Error Message

%UC_JAVAAPPLICATIONS-3-CiscoDRFMasterAgentStartFailure: %[Reason=String][AppID=String][ClusterID=String][NodeID=String]: DRF Master Agent was not able to start.

Explanation   DRF Master Agent might be down

Recommended Action   Check if the Master Agent is running or port 4040 is in use.

Error Message

%UC_JAVAAPPLICATIONS-3-CiscoDRFLocalAgentStartFailure: %[Reason=String][AppID=String][ClusterID=String][NodeID=String]: DRF Local Agent was not able to start.

Explanation   DRF Local Agent might be down

Recommended Action   Check if the Local Agent is running or port 4343 is in use.

Error Message

%UC_JAVAAPPLICATIONS-6-CiscoDRFLA2MAFailure: %[Reason=String][AppID=String][ClusterID=String][NodeID=String]: DRF LA to MA connection has some problems..

Explanation   DRF LA to MA connection has some problems.

Recommended Action   Check if the Master Agent is up and the port is authorized.

Error Message

%UC_JAVAAPPLICATIONS-6-CiscoDRFMA2LAFailure: %[Reason=String][AppID=String][ClusterID=String][NodeID=String]: DRF MA to LA connection has some problems..

Explanation   DRF MA to LA connection has some problems.

Recommended Action   Check if the Local Agent is up and the port is authorized.

Error Message

%UC_JAVAAPPLICATIONS-3-CiscoDRFBackupFailure: %[Reason=String][AppID=String][ClusterID=String][NodeID=String]: DRF Backup process has some problems..

Explanation   DRF Backup process has some problems.

Recommended Action   Check if the disk is full or tape is not online.

Error Message

%UC_JAVAAPPLICATIONS-3-CiscoDRFRestoreFailure: %[Reason=String][AppID=String][ClusterID=String][NodeID=String]: DRF Restore process has some problems..

Explanation   DRF Restore process has some problems.

Recommended Action   Check if the disk is full or tape is not online.

Error Message

%UC_JAVAAPPLICATIONS-4-CiscoDRFUnknownMessage: %[Reason=String][AppID=String][ClusterID=String][NodeID=String]: DRF process has received an unknown message, and discard..

Explanation   DRF process has received an unknown message, and discard.

Recommended Action   None.

Error Message

%UC_JAVAAPPLICATIONS-3-CiscoDRFDeviceError: %[Reason=String][AppID=String][ClusterID=String][NodeID=String]: DRF process has the problem with device..

Explanation   DRF process has the problem with device.

Recommended Action   Check if the proper device has been defined in the DB.

Error Message

%UC_JAVAAPPLICATIONS-3-CiscoDRFInternalProcessFailure: %[Reason=String][AppID=String][ClusterID=String][NodeID=String]: DRF internal process has some problems..

Explanation   DRF internal process has some problems.

Recommended Action   Check the reason, and restart Master Agent.

Error Message

%UC_JAVAAPPLICATIONS-6-CiscoDRFHistory: %[Reason=String][AppID=String][ClusterID=String][NodeID=String]: DRF History Report..

Explanation   DRF History Report.

Recommended Action   None.

Error Message

%UC_JAVAAPPLICATIONS-3-CiscoDhcpdFailure: %[Reason=String][AppID=String][ClusterID=String][NodeID=String]: DHCP Daemon stop running..

Explanation   DHCP Daemon can't be brought up due to configuration error or crashed when it's running

Recommended Action   Check application log for error message and correct the configuration. May require restarting the application if nothing found during the previous steps

Error Message

%UC_JAVAAPPLICATIONS-6-CiscoDhcpdRestarted: %[Reason=String][AppID=String][ClusterID=String][NodeID=String]: DHCP Daemon restarted..

Explanation   DHCP Daemon restarted successfully.

Recommended Action   None.

Error Message

%UC_JAVAAPPLICATIONS-3-CiscoLicenseManagerDown: %[Reason=String][AppID=String][ClusterID=String][NodeID=String]: License Manager Down.

Explanation   License Manager down - license provisioning will fail

Recommended Action   Restart License Manager service on specified node

Error Message

%UC_JAVAAPPLICATIONS-1-CiscoLicenseOverDraft: %[Reason=String][AppID=String][ClusterID=String][NodeID=String]: Overdraft licenses in use.

Explanation   Overdraft licenses in use

Recommended Action   None

Error Message

%UC_JAVAAPPLICATIONS-1-CiscoLicenseApprochingLimit: %[Reason=String][AppID=String][ClusterID=String][NodeID=String]: License units consumption approaching its authorized limit.

Explanation   License units consumption approaching its authorized limit

Recommended Action   None

Error Message

%UC_JAVAAPPLICATIONS-3-CiscoLicenseRequestFailed: %[Reason=String][AppID=String][ClusterID=String][NodeID=String]: License Request Unsuccessful.

Explanation   License Manager cannot fulfill the license request

Recommended Action   See application logs for error

Error Message

%UC_JAVAAPPLICATIONS-3-CiscoLicenseDataStoreError: %[Reason=String][AppID=String][ClusterID=String][NodeID=String]: License Database error.

Explanation   License application cannot fulfill the request - database error

Recommended Action   See application logs for error

Error Message

%UC_JAVAAPPLICATIONS-3-CiscoLicenseInternalError: %[Reason=String][AppID=String][ClusterID=String][NodeID=String]: Licensing Internal Error.

Explanation   License application internal error

Recommended Action   See application logs for error

Error Message

%UC_JAVAAPPLICATIONS-3-CiscoLicenseFileError: %[Reason=String][AppID=String][ClusterID=String][NodeID=String]: License File Error.

Explanation   Invalid or tampered license file

Recommended Action   See application logs, verify that the license file is proper

Error Message

%UC_JAVAAPPLICATIONS-4-CiscoElmNotConnected: %[Reason=String][AppID=String][ClusterID=String][NodeID=String]: The system has not synchronized successfully with Enterprise License Manager for many days..

Explanation   The system has not synchronized successfully to the Enterprise License Manager.

Recommended Action   Check if Enterprise License Manager is connected to the product

Error Message

%UC_JAVAAPPLICATIONS-3-CiscoNoProvisionTimeout: %[Reason=String][AppID=String][ClusterID=String][NodeID=String]: The system is operating with an insufficient number of licenses..

Explanation   The system is operating with an insufficient number of licenses.

Recommended Action   Configure additional licenses in your Enterprise License Manager in order to restore the ability to provision users and devices. Check if Enterprise License Manager is connected to the product.

Error Message

%UC_JAVAAPPLICATIONS-6-CiscoSystemTimeChange: %[Reason=String][AppID=String][ClusterID=String][NodeID=String]: System time has changed.

Explanation   System Time has changed.

Recommended Action   Check why the system time changed

Error Message

%UC_JAVAAPPLICATIONS-6-CiscoGraceTimeLeft: %[Reason=String][AppID=String][ClusterID=String][NodeID=String]: Grace period countdown towards no provisioning allowed.

Explanation   Grace period countdown towards no provisioning allowed.

Recommended Action   Upload additional licenses. Check if Enterprise License Manager is connected to the product.

Error Message

%UC_JAVAAPPLICATIONS-4-CiscoSystemInOverage: %[Reason=String][AppID=String][ClusterID=String][NodeID=String]: The system is operating with an insufficient number of licenses..

Explanation   The system is operating with an insufficient number of licenses. If additional licenses to cover the shortage are not configured in your Enterprise License Manager within a few days, you will no longer be able to provision users and devices.

Recommended Action   Configure additional licenses in your Enterprise License Manager. Check if Enterprise License Manager is connected to the product.

Error Message

%UC_JAVAAPPLICATIONS-3-CiscoSystemSecurityMismatch: %[Reason=String][AppID=String][ClusterID=String][NodeID=String]: Due to a certificate mismatch, the system has not synchronized successfully with Enterprise License Manager for many days..

Explanation   Certficate Mismatch between Cisco Unified Communications Manager and Enterprise License Manager

Recommended Action   Verify Enterprise License Manager certificates. This could be a man-in-the-middle attack.

Error Message

%UC_JAVAAPPLICATIONS-4-CiscoSystemInDemo: %[Reason=String][AppID=String][ClusterID=String][NodeID=String]: The system is operating on demo licenses that will expire soon..

Explanation   License files have not been uploaded on the Enterprise License Manager.

Recommended Action   Upload license files on Enterprise License Manager. Check if Enterprise License Manager is connected to the product.

Error Message

%UC_JAVAAPPLICATIONS-6-CiscoLicenseFileInvalid: %[Reason=String][AppID=String][ClusterID=String][NodeID=String]: License File Invalid.

Explanation   Invalid license file due to MAC Address

Recommended Action   License files need to be rehosted.

Error Message

%UC_JAVAAPPLICATIONS-6-CiscoHardwareLicenseInvalid: %[Reason=String][AppID=String][ClusterID=String][NodeID=String]: Invalid / Obsolete Hardware. Cannot upload license files. .

Explanation   Installation on invalid / obsolete hardware. Cannot upload license files.

Recommended Action   Please obtain correct hardware and re-install.

Error Message

%UC_JAVAAPPLICATIONS-3-DirSyncSchedulerFailedToUpdateNextExecTime: %[Message=String][AppID=String][ClusterID=String][NodeID=String]: Scheduler failed to update next execution time.

Explanation   Scheduler failed to update next execution time

Recommended Action   Check the DirSync configuration and logs

Error Message

%UC_JAVAAPPLICATIONS-6-DirSyncScheduleInsertFailed: %[ScheduleID=String][AppID=String][ClusterID=String][NodeID=String]: DirSync schedule insertion failed.

Explanation   DirSync schedule insertion failed

Recommended Action   Check the DirSync configuration and logs

Error Message

%UC_JAVAAPPLICATIONS-6-DirSyncSchedulerEngineStarted: %[Version=String][AppID=String][ClusterID=String][NodeID=String]: DirSync scheduler engine started.

Explanation   DirSync scheduler engine started

Recommended Action   No action required

Error Message

%UC_JAVAAPPLICATIONS-3-SendEmailAuthenticationError: %[SMTP=String][Reason=String][AppID=String][ClusterID=String][NodeID=String]: Unable to autheticate to the SMTP server.

Explanation   Unable to autheticate to the SMTP server

Recommended Action   See application logs for details

Error Message

%UC_JAVAAPPLICATIONS-3-SendEmailNotificationError: %[SMTP=String][Reason=String][AppID=String][ClusterID=String][NodeID=String]: Send Email error.

Explanation   Send Email error

Recommended Action   See application logs for details

Error Message

%UC_JAVAAPPLICATIONS-3-SendEmailNotificationUnknownError: %[SMTP=String][Reason=String][AppID=String][ClusterID=String][NodeID=String]: Send Email error.

Explanation   Send Email error

Recommended Action   See application logs for details

Error Message

%UC_JAVAAPPLICATIONS-4-DuplicateUserHomeCluster: %[UserID=String][HomeCluster=String][AppID=String][ClusterID=String][NodeID=String]: User has more than one cluster marked as their home cluster.

Explanation   User has more than one cluster marked as their home cluster

Recommended Action   Select only one home cluster for a user

Error Message

%UC_JAVAAPPLICATIONS-6-DNAliasServiceStarted: %[AppName=String][AppID=String][ClusterID=String][NodeID=String]: Cisco Directory Number Alias Service started .

Explanation   Application started successfully

Recommended Action   No action required.

Error Message

%UC_JAVAAPPLICATIONS-2-DNAliasServiceAllLDAPServersDown: %[AppName=String][LDAPIpAddress=String][Error=String][AppID=String][ClusterID=String][NodeID=String]: Connectivity to all configured external Call Routing LDAP servers is down.

Explanation   Connectivity to all configured external Call Routing LDAP servers is down

Recommended Action   No action recommended. The system will try connecting to the server once it is online.

Error Message

%UC_JAVAAPPLICATIONS-3-DNAliasServicePrimaryLDAPServerDown: %[AppName=String][LDAPIpAddress=String][Error=String][AppID=String][ClusterID=String][NodeID=String]: Connectivity to the configured Primary External Call Routing LDAP server is down .

Explanation   Connectivity to the configured Primary External Call Routing LDAP server is down

Recommended Action   No action recommended. The system will try connecting to the server once it is online.

Error Message

%UC_JAVAAPPLICATIONS-3-DNAliasServiceSecondaryLDAPServerDown: %[AppName=String][LDAPIpAddress=String][Error=String][AppID=String][ClusterID=String][NodeID=String]: Connectivity to the configured Secondary External Call Routing LDAP server is down.

Explanation   Connectivity to the configured Secondary External Call Routing LDAP server is down

Recommended Action   No action recommended. The system will try connecting to the server once it is online.

Error Message

%UC_JAVAAPPLICATIONS-6-DNAliasServicePrimaryLDAPServerOnline: %[AppName=String][LDAPIpAddress=String][AppID=String][ClusterID=String][NodeID=String]: The configured Primary External Call Routing LDAP server is online and connected.

Explanation   The configured Primary External Call Routing LDAP server is online and connected

Recommended Action   No recommended action

Error Message

%UC_JAVAAPPLICATIONS-6-DNAliasServiceSecondaryLDAPServerOnline: %[AppName=String][LDAPIpAddress=String][AppID=String][ClusterID=String][NodeID=String]: The configured Secondary External Call Routing LDAP server is online and connected.

Explanation   The configured Secondary External Call Routing LDAP server is online and connected

Recommended Action   No recommended action

Error Message

%UC_JAVAAPPLICATIONS-6-DNAliasServiceLDAPSearchFailed: %[AppName=String][LDAPIpAddress=String][UID=String][Error=String][AppID=String][ClusterID=String][NodeID=String]: Search operation from the External Call Routing LDAP server failed.

Explanation   The Directory Number queried is not found in the External Call Routing LDAP server

Recommended Action   No recommended actions if connectivity to all the configured External Call Routing LDAP servers are intact

Error Message

%UC_JAVAAPPLICATIONS-4-DNAliasServiceImproperLDAPFormat: %[AppName=String][LDAPIpAddress=String][ErrorType=String][AppID=String][ClusterID=String][NodeID=String]: Malformed LDAP response from the External Call Routing LDAP server.

Explanation   Malformed LDAP response from the External Call Routing LDAP server

Recommended Action   Network admin should examine the External Call Routing LDAP database and take necessary corrective action

Error Message

%UC_JAVAAPPLICATIONS-2-DNAliasServiceUnauthorizedAccessToLDAPServer: %[AppName=String][LDAPIpAddress=String][ErrorType=String][AppID=String][ClusterID=String][NodeID=String]: Unauthorized access attempt to the External Call Routing LDAP server.

Explanation   Three consecutive unsuccessful bind attempts within 30 seconds to the External Call Routing LDAP server

Recommended Action   Network admin should examine the External Call Routing LDAP database and take necessary corrective action

Error Message

%UC_JAVAAPPLICATIONS-4-DNAliasServiceErrorThresholdExceeded: %[AppName=String][LDAPIpAddress=String][ErrorType=String][AppID=String][ClusterID=String][NodeID=String]: Too many errors from the configured External Call Routing LDAP server.

Explanation   The number of errors of all kinds from the External Call Routing LDAP server have exceeded the threshold

Recommended Action   Network admin should examine the External Call Routing LDAP database and take necessary corrective action

Error Message

%UC_JAVAAPPLICATIONS-4-DNAliasServiceLDAPAddFailed: %[AppName=String][LDAPIpAddress=String][UID=String][Error=String][AppID=String][ClusterID=String][NodeID=String]: Add operation to the External Call Routing LDAP server failed.

Explanation   The Directory Number Alias record could not be added to the External Call Routing LDAP server

Recommended Action   Network admin should examine the External Call Routing LDAP database and take necessary corrective action

Error Message

%UC_JAVAAPPLICATIONS-4-DNAliasServiceLDAPUpdateFailed: %[AppName=String][LDAPIpAddress=String][UID=String][Error=String][AppID=String][ClusterID=String][NodeID=String]: Update operation to the configured External Call Routing LDAP server failed.

Explanation   The Directory Number Alias record in the External Call Routing LDAP server could not be updated

Recommended Action   Network admin should examine the External Call Routing LDAP database and take necessary corrective action

Error Message

%UC_JAVAAPPLICATIONS-4-DNAliasServiceLDAPDeleteFailed: %[AppName=String][LDAPIpAddress=String][UID=String][Error=String][AppID=String][ClusterID=String][NodeID=String]: Delete operation to the configured External Call Routing LDAP server failed.

Explanation   The Directory Number Alias record in the External Call Routing LDAP server could not be deleted

Recommended Action   Network admin should examine the External Call Routing LDAP database and take necessary corrective action

Error Message

%UC_JAVAAPPLICATIONS-4-DNAliasServiceLDAPTimeExceeded: %[AppName=String][LDAPIpAddress=String][Operation=String][Time=String][AppID=String][ClusterID=String][NodeID=String]: Time limit to perform an LDAP operation exceeded.

Explanation   The LDAP operation has exceeded the time limit set for its successful completion

Recommended Action   Network admin should examine the External Call Routing LDAP database and take necessary corrective action

Error Message

%UC_JAVAAPPLICATIONS-2-DNAliasServiceInitiatingFailover: %[AppName=String][LDAPIpAddress=String][ToLDAPIpAddress=String][AppID=String][ClusterID=String][NodeID=String]: Failover initiated from the current External Call Routing LDAP server to the next External Call Routing LDAP server.

Explanation   Failover initiated from the current External Call Routing LDAP server to the next External Call Routing LDAP server

Recommended Action   Network admin should examine the External Call Routing LDAP database and take necessary corrective action

Error Message

%UC_JAVAAPPLICATIONS-5-DNAliasServiceInitiatingFailback: %[AppName=String][LDAPIpAddress=String][ToLDAPIpAddress=String][AppID=String][ClusterID=String][NodeID=String]: Failback initiated from the current External Call Routing LDAP server to the previous External Call Routing LDAP server.

Explanation   Failback initiated from the current External Call Routing LDAP server to the previous External Call Routing LDAP server

Recommended Action   No recommended action

Error Message

%UC_JAVAAPPLICATIONS-6-DNAliasServiceStopped: %[AppName=String][AppID=String][ClusterID=String][NodeID=String]: Cisco Directory Number Alias Service stopped .

Explanation   Application stopped successfully

Recommended Action   No action required.

Error Message

%UC_JAVAAPPLICATIONS-2-DNAliasServiceWatchdogInitRestart: %[AppName=String][AppID=String][ClusterID=String][NodeID=String]: Cisco Directory Number Alias Service Restarting.

Explanation   Application is being restarted due to too many unresponsive threads.

Recommended Action   Please note the time stamp when the alarm is raised, collect the logs corresponding to the time stamp using either CLI or RTMT and contact Cisco TAC for support. CLI : "file search activelog cm/trace/dnaliassync/log4j time stamp" gives the file number and "file get activelog /cm/trace/dnaliassync/log4j/log-name" is to be run to get the files. RTMT : follow the path "Trace Log Central > Remote Browse > Cisco Directory Number Alias Sync" and select the files corresponding to the time stamp.

Error Message

%UC_JAVAAPPLICATIONS-3-DNAliasServiceNewProcessingThreadStarted: %[AppName=String][Cause=String][AppID=String][ClusterID=String][NodeID=String]: Cisco Directory Number Alias Service has initiated a new thread.

Explanation   Application has started a new instance of the main Processing Thread as the previous instance was detected to be hung and out of service.

Recommended Action   Network admin should contact Cisco TAC for support if the problem persists and this alarm is issued more than 5 times after the service is started.

Error Message

%UC_JAVAAPPLICATIONS-3-SmartCallHomeMessageSendFailed: %[MessageName=String][MessageDetail=String][AppID=String][ClusterID=String][NodeID=String]: This alarm will be raised when call home messages do not reach Cisco backend server due to one of the below condtions mentioned : 1) User selected Secure Web(HTTPS) option in 'Send to TAC' field for sending the messages : Smart Call Home backend server is down/unreachable or DNS settings done by the user are not correct.2) User selected email option in 'Send to TAC' field for sending the messages : SMTP server is down/unreachable or is not configured correctly so the messages did not reach Smart Call Home backend server.3) User selected Secure Web(HTTPS) through Proxy option in 'Send to TAC' field for sending the messages : Proxy settings are not correct or Proxy server is unreachable so the messages did not reach Smart Call Home backend server..

Explanation   Smart Call Home messages could not be sent to SCH backend server due to connectivity issues

Recommended Action   1) Please check if DNS is configured and reachable and you have valid certificates if you are using Secure Web(HTTPS) option for sending Smart Call Home Messages.2) Please check if SMTP server is configured and reachable if you are using email option for sending Smart Call Home Messages.3) Please check if Proxy server is up and running if you are using Secure Web(HTTPS) through Proxy option for sending Smart Call Home Messages

Error Message

%UC_JAVAAPPLICATIONS-6-CiscoDirSyncProcessCompletedWithError: %[AgreementId=String][Reason=String][AppID=String][ClusterID=String][NodeID=String]: LDAPSync process completed on particular sync agreement with errors

Explanation   Completed LDAP sync with some errors. Please check the logs for more details.

Recommended Action   No action required

Error Message

%UC_JAVAAPPLICATIONS-3-JabberClientAlarm: %[Type=String][ErrorDescription=String][TrackingId=String][SessionId=String][UserJid=String][OtherInfo=String][AppID=String][ClusterID=String][NodeID=String]: This is an alarm generated by Jabber Client

Explanation   There was an error that occurred on Jabber Client side

Recommended Action   Refer to the Type, Error Description fields for more details

Error Message

%UC_JAVAAPPLICATIONS-6-CiscoDirSyncZeroOrgsSynced: %[AgreementId=String][Reason=String][AppID=String][ClusterID=String][NodeID=String]: This is alarm to indicate the ldapsearch resulted in zero orgs when searched

Explanation   Unable to fetch any orgs from LDAP server. Please check the logs for more details.

Recommended Action   Please check DirSync logs for more information on LDAP search results and also how the entries are configured on the LDAP server

Error Message

%UC_JAVAAPPLICATIONS-3-CiscoDirSyncOrgFetchFailedForUser: %[AgreementId=String][UserId=String][AppID=String][ClusterID=String][NodeID=String]: This is alarm to indicate the ldapsearch resulted in zero orgs for user

Explanation   Unable to fetch any orgs from LDAP server. Please check the logs for more details.

Recommended Action   Please check DirSync logs for more information on LDAP search results and also how the entries are configured on the LDAP server

Error Message

%UC_JAVAAPPLICATIONS-6-DevActStarted: %[ServletName=String][Reason=String][AppID=String][ClusterID=String][NodeID=String]: Device Activation Application started

Explanation   Unable to fetch any orgs from LDAP server. Please check the logs for more details.

Recommended Action   Please check DirSync logs for more information on LDAP search results and also how the entries are configured on the LDAP server

Error Message

%UC_JAVAAPPLICATIONS-4-DevActStopped: %[ServletName=String][Reason=String][AppID=String][ClusterID=String][NodeID=String]: Device Activation Application stopped

Explanation   Application was unloaded from Tomcat

Recommended Action   Check if Tomcat service is up.

Error Message

%UC_JAVAAPPLICATIONS-3-DevActApplicationError: %[ServletName=String][Reason=String][AppID=String][ClusterID=String][NodeID=String]: Device Activation Application error

Explanation   Device activation application error

Recommended Action   See application logs for details

Error Message

%UC_JAVAAPPLICATIONS-3-DevActApplicationOnboardFailure: %[ServletName=String][Reason=String][IP=String][AppID=String][ClusterID=String][NodeID=String]: Device Activation Failed

Explanation   An attempt to activate an IP Phone using an activation code has failed. Refer to the "Reason" parameter for a specific cause of the failure. This failure has invalidated the activation code that was used.

Recommended Action   Generate a new activation code before retrying the device on-boarding.

Error Message

%UC_JAVAAPPLICATIONS-6-DevActInformation: %[ServletName=String][Reason=String][AppID=String][ClusterID=String][NodeID=String]: Device activation informational alarm

Explanation   Device activation application informational alarm

Recommended Action   No action required

Error Message

%UC_CEF-4-QRTRequest: %[Category=String][ReasonCode=String][TimeStamp=String][DeviceName=String][IPAddress=String][DN=String][AppID=String][ClusterID=String][NodeID=String]: User submitted problem report using Quality Report Tool..

Explanation   Application started successfully

Recommended Action   No action required.

Error Message

%UC_RTMT-3-RTMT_ALERT: %[AlertName=String][AlertDetail=String][AppID=String][ClusterID=String][NodeID=String]: RTMT Alert.

Explanation   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

%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 usage down to below HWM. Email alert will be sent to the admin.

Recommended Action   1. The preservation duration may be too long. Reduce it at Serviceability->Tools->CDR Management. 2. Or to raise maximum allocated disk space and/or HWM for CDR files.

Error Message

%UC_CDRREP-2-CDRMaximumDiskSpaceExceeded: %[DiskUsageInMB=String][AppID=String][ClusterID=String][NodeID=String]: The CDR files disk usage exceeded maximum disk allocation. Some undelivered files may have been deleted to bring disk usage down..

Explanation   The CDR files disk usage has exceeded the maximum allocated disk space. CDRM may have deleted some CDR files that have not been sent to the outside billing servers yet, in order to bring the disk usage down to below High Water Mark. The decision whether to delete undelivered files or not depends on how deletionDisable flag is configured at CDRM Configuration page. Email alert will be sent to the admin.

Recommended Action   1. Check if there are too many undelivered CDR files accumulated due to some condition. 2. Check network link status. 3. Check if billing server is alive. 4. Check if (s)FTP Server on the billing server is running and accepting request. 5. Check if CDRM Configuration for billing servers is correct - under Serviceability->Tools. 6. Check if CDR files maximum disk allocation is too low - under Serviceability->Tools. 7. Check CDR Repository Manager trace under /var/log/active/cm/trace/cdrrep/log4j.

Error Message

%UC_CDRREP-3-CDRFileDeliveryFailureContinues: %[BillingServerAddress=String][AppID=String][ClusterID=String][NodeID=String]: (s)FTP delivery of CDR files failed on retries..

Explanation   (s)FTP develiry of CDR files to the Billing Server outside of the cluster failed on retries after the initial failure.

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-CDRAgentSendFileFailureContinues: %[CDRRepositoryNodeAddress=String][CDRAgentNodeAddress=String][AppID=String][ClusterID=String][NodeID=String]: CDR Agent cannot send CDR files from CCM node to CDR Repository node on retries..

Explanation   CDR Agent cannot send CDR files on retries after the initial failure from CCM node to CDR Repository node within the cluster.

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.

Error Message

%UC_null-6-TestAlarmInformational: %[AppID=String][ClusterID=String][NodeID=String]: Testing INFORMATIONAL_ALARM .

Explanation   Test Alarm

Recommended Action   No action required.

Error Message

%UC_null-0-TestAlarmEmergency: %[AppID=String][ClusterID=String][NodeID=String]: Testing EMERGENCY_ALARM .

Explanation   Test Alarm

Recommended Action   No action required.

Error Message

%UC_null-1-TestAlarmAlert: %[AppID=String][ClusterID=String][NodeID=String]: Testing ALERT_ALARM .

Explanation   Test Alarm

Recommended Action   No action required.

Error Message

%UC_null-2-TestAlarmCritical: %[AppID=String][ClusterID=String][NodeID=String]: Testing CRITICAL_ALARM .

Explanation   Test Alarm

Recommended Action   No action required.

Error Message

%UC_null-7-TestAlarmDebug: %[AppID=String][ClusterID=String][NodeID=String]: Testing DEBUG_ALARM .

Explanation   Test Alarm

Recommended Action   No action required.

Error Message

%UC_null-3-TestAlarmError: %[AppID=String][ClusterID=String][NodeID=String]: Testing ERROR_ALARM .

Explanation   Test Alarm

Recommended Action   No action required.

Error Message

%UC_null-5-TestAlarmNotice: %[AppID=String][ClusterID=String][NodeID=String]: Testing NOTICE_ALARM .

Explanation   Test Alarm

Recommended Action   No action required.

Error Message

%UC_null-4-TestAlarmWarning: %[AppID=String][ClusterID=String][NodeID=String]: Testing WARNING_ALARM .

Explanation   Test Alarm

Recommended Action   No action required.

Error Message

%UC_null-6-TestAlarmAppliance: %[AppID=String][ClusterID=String][NodeID=String]: Testing INFORMATIONAL_ALARM .

Explanation   Test Alarm for Appliance OS based server Only.

Recommended Action   No action required.

Error Message

%UC_SYSACC-4-TotalProcessesAndThreadsExceededThresholdStart: %[NumberOfProcesses=String][NumberOfThreads=String][Reason=String][ProcessWithMostInstances=String][ProcessWithMostThreads=String][AppID=String][ClusterID=String][NodeID=String]: 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..

Explanation   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 RIS Data Collector, Cisco AMC Service, and Cisco RIS Perfmon Logs and contact Cisco Technical Assistance Center (TAC) for detailed assistance.

Error Message

%UC_SYSACC-5-TotalProcessesAndThreadsExceededThresholdEnd: %[NumberOfProcesses=String][NumberOfThreads=String][Reason=String][AppID=String][ClusterID=String][NodeID=String]: 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..

Explanation   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

%UC_DRF-3-DRFTruststoreMissing: %[Reason=String][AppID=String][ClusterID=String][NodeID=String]: DRF uses ipsec truststore certificate for securing communication between the MA and LA service. This certificate is missing on the node.

Explanation   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

%UC_DRF-3-DRFUnknownClient: %[Reason=String][AppID=String][ClusterID=String][NodeID=String]: 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.

Explanation   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

%UC_DRF-3-DRFSecurityViolation: %[Reason=String][AppID=String][ClusterID=String][NodeID=String]: The DRF System has detected a malicious pattern which could result in a security violation.

Explanation   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

%UC_DRF-3-DRFMasterAgentStartFailure: %[Reason=String][AppID=String][ClusterID=String][NodeID=String]: DRF Master Agent was unable to start because it was unable to open port 4040..

Explanation   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

%UC_DRF-3-DRFLocalAgentStartFailure: %[Reason=String][AppID=String][ClusterID=String][NodeID=String]: DRF Local Agent was not able to start because it was unable to connect to the Master Agent on port 4040.

Explanation   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

%UC_DRF-3-DRFLA2MAFailure: %[Reason=String][AppID=String][ClusterID=String][NodeID=String]: DRF Local Agent is not able to connect to Master Agent..

Explanation   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

%UC_DRF-3-DRFMA2LAFailure: %[Reason=String][AppID=String][ClusterID=String][NodeID=String]: Master Agent was unable to send a backup/restore request to the local agent..

Explanation   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

%UC_DRF-3-DRFBackupFailure: %[Reason=String][AppID=String][ClusterID=String][NodeID=String]: Cisco DRF Backup process failed..

Explanation   DRF Backup process encountered errors.

Recommended Action   Check DRF logs for further details.

Error Message

%UC_DRF-3-DRFRestoreFailure: %[Reason=String][AppID=String][ClusterID=String][NodeID=String]: DRF Restore process failed..

Explanation   DRF Restore process encountered errors.

Recommended Action   Check DRF logs for further details.

Error Message

%UC_DRF-3-DRFBackupDeviceError: %[Reason=String][AppID=String][ClusterID=String][NodeID=String]: DRF Backup process is failed due to backup device error..

Explanation   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

%UC_DRF-3-DRFTapeDeviceError: %[Reason=String][AppID=String][ClusterID=String][NodeID=String]: DRF is unable to access tape device..

Explanation   DRF is unable to access tape device.

Recommended Action   Check if tape drive is working properly and it contains a valid tape.

Error Message

%UC_DRF-3-DRFLocalDeviceError: %[Reason=String][AppID=String][ClusterID=String][NodeID=String]: DRF is unable to access local device..

Explanation   DRF is unable to access local device.

Recommended Action   Check if local location exists and is accessible.

Error Message

%UC_DRF-3-DRFInternalProcessFailure: %[Reason=String][AppID=String][ClusterID=String][NodeID=String]: DRF internal process has encountered an error..

Explanation   DRF internal process has encountered an error.

Recommended Action   Check DRF logs for details.

Error Message

%UC_DRF-3-DRFRestoreInternalError: %[Reason=String][AppID=String][ClusterID=String][NodeID=String]: DRF Restore operation has encountered an error. Restore cancelled internally..

Explanation   DRF Restore operation has encountered an error. Restore cancelled internally.

Recommended Action   Check DRF logs for details.

Error Message

%UC_DRF-3-DRFMABackupComponentFailure: %[Reason=String][AppID=String][ClusterID=String][NodeID=String]: DRF was unable to backup at least one component..

Explanation   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

%UC_DRF-3-DRFMARestoreComponentFailure: %[Reason=String][AppID=String][ClusterID=String][NodeID=String]: DRF was unable to restore at least one component..

Explanation   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

%UC_DRF-3-DRFMABackupNodeDisconnect: %[Reason=String][AppID=String][ClusterID=String][NodeID=String]: The node being backed up disconnected from the Master Agent prior to being fully backed up..

Explanation   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

%UC_DRF-3-DRFNoRegisteredComponent: %[Reason=String][AppID=String][ClusterID=String][NodeID=String]: No registered components available, backup failed..

Explanation   DRF backup failed since no registered components are available.

Recommended Action   Ensure at least one component is registered before attempting a backup.

Error Message

%UC_DRF-3-DRFNoRegisteredFeature: %[Reason=String][AppID=String][ClusterID=String][NodeID=String]: No feature selected for backup..

Explanation   No feature selected for backup

Recommended Action   Ensure at least one feature is configured before attempting a backup.

Error Message

%UC_DRF-3-DRFMARestoreNodeDisconnect: %[Reason=String][AppID=String][ClusterID=String][NodeID=String]: The node being restored disconnected from the Master Agent prior to being fully restored..

Explanation   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

%UC_DRF-3-DRFSftpFailure: %[Reason=String][AppID=String][ClusterID=String][NodeID=String]: DRF sftp operation has failed..

Explanation   DRF sftp operation has failed.

Recommended Action   Ensure that the destination server is available, has appropriate permissions and sftp daemon is running.

Error Message

%UC_DRF-3-DRFRegistrationFailure: %[Reason=String][AppID=String][ClusterID=String][NodeID=String]: DRF Registration operation failed..

Explanation   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

%UC_DRF-3-DRFBackupCancelInternalError: %[Reason=String][AppID=String][ClusterID=String][NodeID=String]: DRF Backup operation has encountered an error. Backup cancelled internally..

Explanation   DRF Backup operation has encountered an error. Backup cancelled internally.

Recommended Action   Check DRF logs for details.

Error Message

%UC_DRF-4-DRFLogDirAccessFailure: %[Reason=String][AppID=String][ClusterID=String][NodeID=String]: DRF couldn't access the log directory..

Explanation   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

%UC_DRF-4-DRFComponentDeRegistered: %[Reason=String][AppID=String][ClusterID=String][NodeID=String]: DRF succesfully de-registered the requested component..

Explanation   DRF succesfully de-registered the requested component.

Recommended Action   Ensure that the component deregistered is not needed for further backup/restore operation.

Error Message

%UC_DRF-4-DRFDeRegistrationFailure: %[Reason=String][AppID=String][ClusterID=String][NodeID=String]: DRF de-registration request for a component failed..

Explanation   DRF de-registration request for a component failed.

Recommended Action   Please check the DRF logs and contact support if needed.

Error Message

%UC_DRF-4-DRFDeRegisteredServer: %[Reason=String][AppID=String][ClusterID=String][NodeID=String]: DRF automatically de-registered all the components for a server..

Explanation   This server might have got disconnected from CCM cluster.

Recommended Action   Nothing.

Error Message

%UC_DRF-4-DRFSchedulerDisabled: %[Reason=String][AppID=String][ClusterID=String][NodeID=String]: DRF Scheduler is disabled because no configured features available for backup..

Explanation   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

%UC_DRF-6-DRFComponentRegistered: %[Reason=String][AppID=String][ClusterID=String][NodeID=String]: DRF Succesfully Registered the requested component..

Explanation   DRF Succesfully Registered the requested component.

Recommended Action   Ensure that the registered component is needed for backup/restore operation.

Error Message

%UC_DRF-6-DRFSchedulerUpdated: %[Reason=String][AppID=String][ClusterID=String][NodeID=String]: DRF Scheduled backup configurations is updated automatically due to feature DeRegistration..

Explanation   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

%UC_DRF-6-DRFBackupCompleted: %[Reason=String][AppID=String][ClusterID=String][NodeID=String]: DRF backup completed successfully..

Explanation   DRF backup completed successfully.

Recommended Action   Ensure that the backup operation completed successfully.

Error Message

%UC_DRF-6-DRFRestoreCompleted: %[Reason=String][AppID=String][ClusterID=String][NodeID=String]: DRF restore completed successfully..

Explanation   DRF restore completed successfully.

Recommended Action   Ensure that the restore operation completed successfully.

Error Message

%UC_DRF-3-DRFFailure: %[Reason=String][AppID=String][ClusterID=String][NodeID=String]: DRF Backup or Restore process has failed..

Explanation   DRF Backup or Restore process encountered errors.

Recommended Action   Check DRF logs for further details.

Error Message

%UC_DRF-4-DRFNoBackupTaken: %[Reason=String][AppID=String][ClusterID=String][NodeID=String]: A valid backup of the current system was not found..

Explanation   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

%UC_LOGIN-4-AuthenticationFailed: %[LoginFrom=String][TimeStamp=String][UserID=String][Interface=String][AppID=String][ClusterID=String][NodeID=String]: Login Authentication failed..

Explanation   Authentication failure for login attempt is detected.

Recommended Action   If this event happens repeatedly, investigate the source of the failed login attempts.

Error Message

%UC_LOGIN-6-AuthenticationSucceeded: %[LoginFrom=String][TimeStamp=String][UserID=String][Interface=String][AppID=String][ClusterID=String][NodeID=String]: Login Authentication succeeded..

Explanation   Authentication success for login attempt is detected.

Recommended Action   If this event is expected, no action is required; otherwise, notify the administrator.

Error Message

%UC_CERT-6-CertExpiryApproaching: %[Message=String][AppID=String][ClusterID=String][NodeID=String]: Information Alarm that Indicates a Certificate Validity Period is approaching and the expiry date is within the notification window configured .

Explanation   Certificate Expiry Date is approaching shortly and Certificate is going to be invalid.

Recommended Action   Re-generate the certificate that is about to Expire from Certificate Management UI from CUOS Administration web Page. If the Certificate is issued by a CA, Generate a CSR, Submit CSR to CSA ,obtain a fresh certificate from CA and upload it to CUCM

Error Message

%UC_CERT-0-CertExpired: %[Message=String][AppID=String][ClusterID=String][NodeID=String]: Certificate has Expired and needs to be changed at the earliest.

Explanation   The Validity Date of the Certificate indicated is over and the Certificate is expired.

Recommended Action   Re-generate the certificate that is about to Expire from Certificate Management UI from CUOS Administration web Page. If the Certificate is issued by a CA, obtain a fresh certificate from CA and upload it to CUCM.

Error Message

%UC_CERT-1-CertValidLessthanADay: %[Message=String][AppID=String][ClusterID=String][NodeID=String]: Certificate is about to Expire in less than 24 hours or has Expired .

Explanation   The Validity of the Certificate indicated in the notification message is less than 24 hours .

Recommended Action   Re-generate the certificate that is about to Expire from Certificate Management UI from CUOS Administration web Page. If the Certificate is issued by a CA, Generate a CSR, Submit CSR to CA, obtain a fresh certificate from CA and upload it to CUCM

Error Message

%UC_CERT-2-CertValidfor7days: %[Message=String][AppID=String][ClusterID=String][NodeID=String]: Alarm to indicate that Certificate has Expired or Expires in less than seven days.

Explanation   The Certifciate is invalid or Validity of the Certificate indicated in the notification less than 7 days.

Recommended Action   Re-generate the certificate that is about to Expire from Certificate Management UI from CUOS Administration web Page. If the Certificate is issued by a CA, Generate a CSR, Submit CSR to CA, obtain a fresh certificate from CA and upload it to CUCM

Error Message

%UC_CERT-5-CertValidityOver30Days: %[Message=String][AppID=String][ClusterID=String][NodeID=String]: Alarm to Indicate certificate to Expiry is approaching but expiry date is more than 30 days .

Explanation   Information Alarm that Indicates a Certificate Validity Period is approaching and validity of certificate is more than 30 days

Recommended Action   Re-generate the certificate that is about to Expire from Certificate Management UI from CUOS Administration web Page. If the Certificate is issued by a CA, Generate a CSR, Submit CSR to CA, obtain a fresh fresh certificate from CA and upload it to CUCM

Error Message

%UC_CERT-4-CertValidLessThanMonth: %[Message=String][AppID=String][ClusterID=String][NodeID=String]: Alarm that indicates Certificate Expire in 30 days or lesser .

Explanation   The Expiry date of the Certificate indicated in the notification is less than a month

Recommended Action   Re-generate the certificate that is about to Expire from Certificate Management UI from CUOS Administration web Page. If the Certificate is issued by a CA, Generate a CSR, Submit CSR to CA, obtain a fresh certificate from CA and upload it to CUCM.

Error Message

%UC_CERT-2-TomcatCertRegen: %[Message=String][AppID=String][ClusterID=String][NodeID=String]: Alarm that indicates the tomcat certificate is regenerated.

Explanation   This alarm indicates that tomcat certificate has been regenerated or CA signed Tomcat Certificate has been uploaded.

Recommended Action   Restart the tomcat service for the new tomcat certificate to be effective. If EMCC feature is enabled for the communication across the clusters, perform the bulk certificate management provisioning for tomcat unit from Cisco Unified OS Administration Webpage

Error Message

%UC_CERT-0-CertificateRevoked: %[Message=String][AppID=String][ClusterID=String][NodeID=String]: Alarm indicates that recently uploaded certificate is revoked and needs to be changed at the earliest..

Explanation   This alarm indicates that recently uploaded third party signed certificate or trust certificate is revoked.

Recommended Action   Delete revoked trust certificate and re-upload it from Cisco Unified OS Administration Webpage. In case of third party signed (own) certifiate, just re-upload new certificate.

Error Message

%UC_CERT-4-CertificateRevokationStatusByOCSP: %[Message=String][AppID=String][ClusterID=String][NodeID=String]: Alarm indicates that CUCM could not determine OCSP revocation status of recently uploaded certificate..

Explanation   This alarm indicates that CUCM failed to determine revocation status of recently uploaded third party signed certificate or trust certificate.

Recommended Action   Evaluate reason of certificate revocation failure. Delete and re-upload certificate if required.

Error Message

%UC_CERT-4-ITLRecoveryCertBackup: %[Message=String][AppID=String][ClusterID=String][NodeID=String]: This cluster has an ITLRecovery certificate that has not been backed up. Taking a manual backup of this certificate is recommended to avoid the need to manually delete the ITL file from every phone in the cluster after certain cluster reconfiguration operations..

Explanation   This alarm indicates that the newly generated ITL Recovery Certificate and key have not yet been backed up.

Recommended Action   Use the CLI command "file get tftp ITLRecovery.p12" to back up the ITL Recovery Certificate as soon as possible.

Error Message

%UC_IMS-4-authFail: %[UserID=String][Message=String][AppID=String][ClusterID=String][NodeID=String]: An attempt to authenticate this user with the given credentials failed..

Explanation   Failed to authenticate this user.

Recommended Action   Determine correct credentials and retry.

Error Message

%UC_IMS-4-SSONullTicket: %[Message=String][AppID=String][ClusterID=String][NodeID=String]: A null ticket was passed..

Explanation   Failed to authenticate this user.

Recommended Action   Get non null ticket and retry.

Error Message

%UC_IMS-4-SSOServerUnreachable: %[Message=String][AppID=String][ClusterID=String][NodeID=String]: SSO server could not be reached..

Explanation   SSO server could not be reached.

Recommended Action   Check reachability to SSO server.

Error Message

%UC_IMS-4-LDAPServerUnreachable: %[Message=String][AppID=String][ClusterID=String][NodeID=String]: Authentication server could not be reached..

Explanation   Authentication server could not be reached.

Recommended Action   Check reachability to Authentication server.

Error Message

%UC_IMS-4-SSOuserNotInDB: %[Message=String][AppID=String][ClusterID=String][NodeID=String]: User was not found in DB..

Explanation   User was not found in DB.

Recommended Action   Perform sync manually or wait till next scheduled sync.

Error Message

%UC_IMS-4-SSODisabled: %[Message=String][AppID=String][ClusterID=String][NodeID=String]: SSO disabled on CUCM..

Explanation   SSO disabled on CUCM.

Recommended Action   run CLI command to enable SSO.

Error Message

%UC_IMS-4-SSOInternal: %[Message=String][AppID=String][ClusterID=String][NodeID=String]: Failedto open a file..

Explanation   Failed to authenticate this user.

Recommended Action   Try again after some time.

Error Message

%UC_IMS-6-authSuccess: %[UserID=String][AppID=String][ClusterID=String][NodeID=String]: User successfully authenticated..

Explanation   Successfully authenticated this user.

Recommended Action   No action required.

Error Message

%UC_IMS-4-authLdapInactive: %[UserID=String][AppID=String][ClusterID=String][NodeID=String]: Authentication failed due to the user existing in the local database, but system is configured for LDAP authentication..

Explanation   A directory sync was likely done in the immediate past (1 day), This user has yet to be removed from the database. No action should be necessary. This should clear itself within 24 hours.

Recommended Action   No action should be necessary.

Error Message

%UC_IMS-4-authAdminLock: %[UserID=String][AppID=String][ClusterID=String][NodeID=String]: The Administrator has locked this credential, therfore the authentication failed..

Explanation   User is locked out by administrator.

Recommended Action   Administrator may unlock this credential.

Error Message

%UC_IMS-4-authHackLock: %[UserID=String][AppID=String][ClusterID=String][NodeID=String]: This user attempted to login unsuccessfully the number of times set by the administrator. At that time the credential is locked..

Explanation   User attempted too many incorrect authentications in the time frame set by the administrator.

Recommended Action   Wait for administrator specified time to retry, or have administrator unlock the credential.

Error Message

%UC_IMS-5-authExpired: %[UserID=String][AppID=String][ClusterID=String][NodeID=String]: The authentication failed because this credential has expired..

Explanation   This user's credentials have expired.

Recommended Action   Administrator may reset the credential.

Error Message

%UC_IMS-4-authInactiveLock: %[UserID=String][AppID=String][ClusterID=String][NodeID=String]: Authentication failed because the credential is locked due to inactivity..

Explanation   User has been inactive for the administrator specified time. The credential is locked.

Recommended Action   Administrator may reset the credential.

Error Message

%UC_IMS-5-authMustChange: %[UserID=String][AppID=String][ClusterID=String][NodeID=String]: Authentication failed because it is marked that it must be changed by the user at this time..

Explanation   User Must Change is set on this credential. The user can gain access after changing the credential.

Recommended Action   User or Administrator may reset credential.

Error Message

%UC_IMS-6-credUpdateFailure: %[UserID=String][AppID=String][ClusterID=String][NodeID=String]: There are a number of reasons an update of a credential could fail. Likely cause is that the credential doesn't pass security requirements (too short for example), has been used previously, etc..

Explanation   Some problem updating the credential.

Recommended Action   Determine issue (check length requirements, etc.) for this credential and retry.

Error Message

%UC_IMS-6-credUpdateSuccess: %[UserID=String][AppID=String][ClusterID=String][NodeID=String]: The credential has been updated..

Explanation   Credential was successfully updated.

Recommended Action   No action required.

Error Message

%UC_IMS-6-credFullUpdateSuccess: %[Message=String][AppID=String][ClusterID=String][NodeID=String]: Fields associated with this credential have been successfully updated..

Explanation   Credential was successfully updated.

Recommended Action   No action required.

Error Message

%UC_IMS-6-credFullUpdateFailure: %[Message=String][AppID=String][ClusterID=String][NodeID=String]: The update for the fields associated with this credential failed..

Explanation   An error was encountered during update of credential fields.

Recommended Action   Determine issue and retry.

Error Message

%UC_IMS-5-credReadFailure: %[UserID=String][Message=String][AppID=String][ClusterID=String][NodeID=String]: Some error was encountered when attempting to read credential from the database. This could be a network or database issue..

Explanation   Error occured attempting to read a credential.

Recommended Action   Ensure credential (user name) exists. Could be database problem.

Error Message

%UC_IMS-6-credReadSuccess: %[UserID=String][AppID=String][ClusterID=String][NodeID=String]: This credential was successfully accessed from the databse..

Explanation   Successfully read a credential.

Recommended Action   No action required.

Error Message

%UC_IMS-6-AdminPassword: %[Message=String][AppID=String][ClusterID=String][NodeID=String]: Administrative password changed successfully, or unsuccessfully based on message displayed..

Explanation   Password change succeeded or failed based on message displayed.

Recommended Action   No further recommendation.

Error Message

%UC_CAR-3-CARSchedulerJobFailed: %[JobName=String][FailureCause=String][FailureDetail=String][AppID=String][ClusterID=String][NodeID=String]: Critical CAR scheduled job failed..

Explanation   A critical CAR scheduled job failed for some reasons.

Recommended Action   1. Check the status of Cisco CAR DB service. 2. Check the status of Cisco CAR Scheduler service. 3. Check the Event Log from CAR page. 4. Check the contents in tbl_system_preferences table. 5. Check the number of records in tbl_billing_data, tbl_billing_error, and tbl_error_id_map tables. 6. Check if the scheduled job configuration is correct from CAR page. 7. Collect and check the CAR Scheduler traces for more details.

Error Message

%UC_CAR-3-CARSchedulerJobError: %[JobName=String][FailureCause=String][FailureDetail=String][AppID=String][ClusterID=String][NodeID=String]: CAR scheduled job failed..

Explanation   A normal CAR scheduled job failed for some reasons.

Recommended Action   1. Check the status of Cisco CAR Scheduler service. 2. Check the Event Log from CAR page. 3. Check the contents in tbl_system_preferences table. 4. Check the number of records in tbl_billing_data, tbl_billing_error, and tbl_error_id_map tables. 5. Check if the scheduled job configuration is correct from CAR page. 6. Collect and check the CAR Scheduler traces for more details.

Error Message

%UC_CAR-3-BadCDRFileFound: %[FileName=String][BadFileCause=String][BadFileSummary=String][AppID=String][ClusterID=String][NodeID=String]: Bad CDR or CMR flat file found during CDR Load to CAR database..

Explanation   A bad CDR or CMR flat file is found during loading to CAR database, the file could be corrupted for some reasons. However, CAR loader is able to skip the bad record(s) and load the good ones to CAR database.

Recommended Action   1. Find the bad file from the cdr_repository folders, and check its problematic record(s) based on the information given by the cause and summary. 2. Collect the associated SDI and SDL traces for the bad record(s) found in this file as soon as possible. 3. Collect and check the CAR Scheduler traces for more details.

Error Message

%UC_CAR-7-CARIDSEngineDebug: %[Specific-Msg=String][ClassMsg=String][ClassID=String][AppID=String][ClusterID=String][NodeID=String]: Indicates debug events from CAR IDS database engine..

Explanation   This alarm provides low-level debugging information from CAR IDS database engine. System administrator can disregard this alarm.

Recommended Action   This is for debug information purposes only; no action is required.

Error Message

%UC_CAR-6-CARIDSEngineInformation: %[Specific-Msg=String][ClassMsg=String][ClassID=String][AppID=String][ClusterID=String][NodeID=String]: No error has occurred but some routine event completed in CAR IDS database engine..

Explanation   This alarm is informational. No error has occurred but some routine event completed in CAR IDS database engine.

Recommended Action   This is for information purposes only; no action is required.

Error Message

%UC_CAR-2-CARIDSEngineCritical: %[Specific-Msg=String][ClassMsg=String][ClassID=String][AppID=String][ClusterID=String][NodeID=String]: Pay Attention. This alarm does not compromise data or prevent the use of the system..

Explanation   Pay Attention. This alarm does not compromise data or prevent the use of the system.

Recommended Action   This alarm needs monitoring by the CAR DB admin.

Error Message

%UC_CAR-3-CARIDSEngineFailure: %[Specific-Msg=String][ClassMsg=String][ClassID=String][AppID=String][ClusterID=String][NodeID=String]: Combined alarm for emergency and error situations. Something unexpected occurred that might compromise data or access to data or cause CAR IDS to fail..

Explanation   This alarm indicates combined alarm for emergency and error situations. Something unexpected occurred that might compromise data or access to data or cause CAR IDS to fail.

Recommended Action   Requires CAR DB admin intervention.

Error Message

%UC_CDP-2-DUPLEX_MISMATCH: %[SwitchDuplex=String][LocalInterfaceDuplex=String][AppID=String][ClusterID=String][NodeID=String]: Duplex Mismatch Alarm.

Explanation   This alarm is generated by Cisco CDP whenver there is a duplex mismatch between local inetrface and switch interface.

Recommended Action   Ensure that Duplex settings are set to auto or full on local inetrface as well as switch interface

Error Message

%UC_CAPF-0-CAPFCertificateKeyPairMismatch: %[AppID=String][ClusterID=String][NodeID=String]: CAPF certificate is not have matching public- private key pair.

Explanation   CAPF Service is not having matching certificate and key pair.

Recommended Action   1. Regenerate CAPF certificate. 2.Restart CAPF service. 3.Rerun CTLClient.4.Restart TFTP and Call Manager services.

Error Message

%UC_CTLPROVIDERALARMCATALOG-3-ChangeToClusterModeSecurityFailed: %[AppID=String][ClusterID=String][NodeID=String]: The Cisco Unified Communications Manager (Unified CM) and the Cisco Authority Proxy Function (CAPF) certificates cannot have an issuer or/and subject names longer than 255 characters..

Explanation   CTL Client fails to turn the cluster security to mixed mode if the Cisco Unified Communications Manager (Unified CM) and the Cisco Authority Proxy Function (CAPF) have a issuer or/and subject names longer than 255 characters.

Recommended Action   Regenerate the Cisco Unified Communications Manager (Unified CM) or/and the Cisco Authority Proxy Function (CAPF) certificates with issuer or/and subject names to be less than 256 characters. If you are using an external Certificate Authority (CA), its root certificate cannot have a subject name longer than 255 characters.

Error Message

%UC_CTLPROVIDERALARMCATALOG-3-ClusterModeSecurityFailedExportControlNotAllow: %[AppID=String][ClusterID=String][NodeID=String]: Setting the Cisco Unified Communications Manager to mixed-mode failed because export control functionality is not allowed.

Explanation   Action to turn the cluster security to mixed mode failed because the Unified Communications Manager cluster is not allowed for Export Control functionality.

Recommended Action   Please ensure Smart License registration is completed using the Registration Token received from the Smart/Virtual Account that has Allow export-controlled functionality checked and then enable the cluster security to mixed mode.

Error Message

%UC_EXTENSIONMOBILITY-3-EMCCFailedInLocalCluster: %[DeviceName=String][TimeStamp=String][UserID=String][Reason=String][AppID=String][ClusterID=String][NodeID=String]: EMCC Login failure in local Call Manager..

Explanation   EMCC login could fail due to 1. Using devices incompatile with EMCC feature. 2. Unable to retrieve remote cluster information. 3. EMCC is restricted by the local cluster. 4. Untrusted Certificate received from the remote end while trying to establish a connection

Recommended Action   1. Validate if the device model supports EMCC (EMCC Documentation). 2. Ensure that every remote cluster added for EMCC has valid hostname/IP address(es) for EM and PSTN Access in the RemoteCluster administration page (Logon to CUCM Administration page -> System -> EMCC -> Remote Cluster). Also, ensure that these entries are enabled. 3. Ensure that a bundle of all tomcat certificates (PKCS12) has been imported into the local tomcat-trust keystore (Logon to OS Administration page -> Security -> Certificate Management -> Check the certificates in tomcat-trust).

Error Message

%UC_EXTENSIONMOBILITY-4-EMCCFailedInRemoteCluster: %[DeviceName=String][TimeStamp=String][UserID=String][Reason=String][AppID=String][ClusterID=String][NodeID=String]: EMCC Login failure at a remote Call Manager..

Explanation   EMCC login could fail due to 1. User does not exist in any of the configured remote cluster. 2. User is not enabled for EMCC. 3. No free EMCC Base Device. 4. EMCC Access was prevented by remote cluster. 5. Untrusted Certificate received from the remote end while trying to establish a connection

Recommended Action   1. Ensure that the user is a valid EMCC user and make sure that user's home cluster is added as a EMCC remote cluster(Logon to CUCM Administration page -> System -> EMCC -> Remote Cluster -> Add New). 2. Contact remote site administrator to enable user for EMCC (Logon to CUCM Administration page -> User Management -> End User -> Select User -> Enable Extension mobility cross cluster checkbox) 3. Contact remote site administrator for adding / freeing up EMCC Base Devices (Logon to CUCM Administration page -> Bulk Administration -> EMCC -> Insert/Update EMCC). 4. Contact remote site administrator to validate the remote cluster setting for this cluster. 5. Ensure that a bundle of all tomcat certificates (PKCS12) has been imported into the local tomcat-trust keystore (Logon to OS Administration Page -> Security -> Certificate Management -> Check for all tomcat certificates in tomcat-trust).

Error Message

%UC_EXTENSIONMOBILITY-4-UserInputFailure: %[DeviceName=String][TimeStamp=String][UserID=String][Reason=String][AppID=String][ClusterID=String][NodeID=String]: EMCC Login failure due to invalid user input..

Explanation   EMCC Login failed due to error in user input. This situation can arise due to 1. Invalid User Credentials. 2. Credentials have expired.

Recommended Action   1. Try again with valid credentials or try resetting the credentils.

Error Message

%UC_EXTENSIONMOBILITY-6-EMCCUserLoggedIn: %[DeviceName=String][TimeStamp=String][UserID=String][AppID=String][ClusterID=String][NodeID=String]: EMCC login was successful..

Explanation   The user has successfully logged in to extension mobility cross-cluster (EMCC).

Recommended Action   Informational purposes only; no action is required.

Error Message

%UC_EXTENSIONMOBILITY-6-EMCCUserLoggedOut: %[DeviceName=String][TimeStamp=String][UserID=String][AppID=String][ClusterID=String][NodeID=String]: EMCC logout was successful..

Explanation   The user has successfully logged out of extension mobility cross-cluster (EMCC).

Recommended Action   Informational purposes only; no action is required.

Error Message

%UC_EXTENSIONMOBILITY-6-EMAppStarted: %[ServletName=String][AppID=String][ClusterID=String][NodeID=String]: EM Application started .

Explanation   Application started successfully.

Recommended Action   No action required.

Error Message

%UC_EXTENSIONMOBILITY-5-EMAppStopped: %[ServletName=String][AppID=String][ClusterID=String][NodeID=String]: EM Application stopped.

Explanation   Application is shutting down gracefully because of an unloaded from Tomcat.

Recommended Action   No action required on this application.

Error Message

%UC_EXTENSIONMOBILITY-3-EMAppInitializationFailed: %[ServletName=String][AppID=String][ClusterID=String][NodeID=String]: EM Application not started.

Explanation   Error occurred while starting application.

Recommended Action   See application logs for error. Default location for the logs are at /var/log/active/tomcat/logs/em/log4j/

Error Message

%UC_EXTENSIONMOBILITY-3-EMServiceConnectionError: %[ServletName=String][AppID=String][ClusterID=String][NodeID=String]: EM Service not reachable.

Explanation   EM Service might be down in one or more nodes in the cluster.

Recommended Action   Check if Cisco Extension Mobility service is running on all nodes of the cluster where the service is activated.

Error Message

%UC_EXTENSIONMOBILITY-3-NodeNotTrusted: %[TimeStamp=String][HostName=String][AppID=String][ClusterID=String][NodeID=String]: Untrusted Node was contacted.

Explanation   Application could not establish secure connection (SSL handshake failure) with another application. It could be due to 1. Certificate for tomcat service where the application is hosted is not trusted (not present in the keytore)

Recommended Action   1. Ensure that "tomcat-trust" keystore on each CCM node contains the tomcat certificates for every other node within a cluster (Logon to OS Administration Page -> Security -> Certificate Management -> Check the certificates in tomcat-trust). 2. If EMCC is enabled, then ensure that a bundle of all tomcat certificates (PKCS12) has been imported into the local tomcat-trust keystore (Logon to OS Administration Page -> Security -> Certificate Management -> Look for certificates in tomcat-trust).

Error Message

%UC_SYSAGENT-3-SyslogStringMatchFound: %[StringMatch=String][MatchedEvent=String][AppID=String][ClusterID=String][NodeID=String]: The configured Syslog Alarm/message string had matched.

Explanation   Cisco Syslog Agent had detected an alarm which matches the configured string

Recommended Action   Take the necessary action based on the received string matched event

Error Message

%UC_SYSAGENT-3-HardwareFailure: %[hwStringMatch=String][AppID=String][ClusterID=String][NodeID=String]: Hardware failure alarm is received.

Explanation   Cisco Syslog Agent had detected a hardware failure alarm

Recommended Action   Take the necessary action based on the received hardware failure event

Error Message

%UC_SYSAGENT-3-TCPRemoteSyslogDeliveryFailed: %[RemoteSyslogServerIP=String][RecommendedTCPPort=String][Source=Enum][AppID=String][ClusterID=String][NodeID=String]: Indicates a failure in delivering events to RemoteSyslogServer over TCP

Explanation   This alarm indicates a failure occurred in delivering the events to the configured remote syslog server. The reason could be that the configured syslog server is down, or TCP is not configured to port 601, or there is a network failure.

Recommended Action   Check that the configured remote syslog server is up, TCP protocol configured on the recommended port 601. If the issue persists, please contact Cisco Technical Assistance Center (TAC) for further support.

Error Message - Enum Definitions

Enum Definitions - Source

%UC_SYSAGENT-3- TLSRemoteSyslogDeliveryFailed : %[RemoteSyslogServerIP=String][ RecommendedTLSPort =Int][Source=Enum][AppID=String][ClusterID=String][NodeID=String]:  Indicates a failure in delivering events to RemoteSyslogServer over TLS

Explanation    This alarm indicates a failure occurred in delivering the events to the configured remote syslog server. The reason could be that the configured syslog server is down, or TLS is not configured to port 6514, or there is a network failure, or certificate exchange between cucm and the remote syslog server might not have done.

Recommended Action    Check that the configured remote syslog server is up, TLS protocol configured on the recommended port 6514 and proper certificate exchange is done between the cucm and remote syslog. If the issue persists, please contact Cisco Technical Assistance Center (TAC) for further support.

Error Message - Enum Definitions

Enum Definitions - Source

%UC_SYSAGENT-3-UnreachableRemoteSyslogServer: %[RemoteSyslogServerName=String][ServiceName=String][AppID=String][ClusterID=String][NodeID=String]: The configured Remote syslog server is not reachable

Explanation   This alarm indicates that the remote syslog server configured for a service is not reachable. The reason could be the IP address may be invalid, or the configured syslog server may be down, or UDP/TCP/TLS may not be configured to the ports 514/601/6514, or there is a network failure.

Recommended Action   Check whether the configured remote syslog server is up and reachable from this server. Verify the the correct protocol is configured with the CLI command "utils remotesyslog show protocol". The system will automatically try to send new messages to the remote syslog server in one hour or when an admin saves the configuration again in Alarm Configuration GUI. If this issue persists, please contact Cisco Technical Assistance Center (TAC) for further support.

Error Message

%UC_SYSAGENT-3-SyslogSeverityMatchFound: %[SeverityMatch=String][MatchedEvent=String][AppID=String][ClusterID=String][NodeID=String]: The configured Syslog Alarm/message severity had matched.

Explanation   Cisco Syslog Agent had detected an alarm which matches the configured severity

Recommended Action   Take the necessary action based on the received severity matched event

Error Message

%UC_TVS-1-SDIControlLayerFailed: %[Error=Int][Reason=String][AppID=String][ClusterID=String][NodeID=String]: Failed to update trace logging or alarm subsystem for new settings..

Explanation   This usually indicates a lack of system resources or a failure in database access by the trace logging or alarm subsystem.

Recommended Action   In Cisco Unified Serviceability, enable Detailed level traces in the Trace Configuration window for TVS and Cisco Database Layer Monitor services. Also, use RTMT to look for error messages that may have occurred around the time of the alarm. Ensure that the database server is running, and that the Cisco Database Layer Monitor service is running without problems. If this alarm persists, contact the Cisco Technical Assistance Center (TAC) with TVS service and database trace files.

Error Message

%UC_TVS-3-ConfigThreadReadConfigurationFailed: %[AppID=String][ClusterID=String][NodeID=String]: Failed to retrieve enterprise parameter values from database at TVS service startup..

Explanation   This is usually caused by database access failure.

Recommended Action   In Cisco Unified Serviceability, enable Detailed level traces in the Trace Configuration window for TVS and Cisco Database Layer Monitor services. Also, use RTMT to look for error messages that may have occurred around the time of the alarm.

Error Message

%UC_TVS-1-ConfigThreadChangeNotifyServerSingleFailed: %[AppID=String][ClusterID=String][NodeID=String]: Failed to allocate resources to handle configuration change notification from database..

Explanation   This usually indicates a lack of memory when there is a system issue such as running out of resources.

Recommended Action   Use RTMT to monitor the system memory resources and consumption and correct any system issues that might be contributing to a reduced amount of system resources.

Error Message

%UC_TVS-6-ITLFileRegenerated: %[AppID=String][ClusterID=String][NodeID=String]: New ITL File has been generated..

Explanation   This usually means that a new certificate related to ITLFile has been modified.

Recommended Action   None.

Error Message

%UC_TVS-6-TVSCertificateRegenerated: %[AppID=String][ClusterID=String][NodeID=String]: TVS Server certificate has been regenerated..

Explanation   This usually means that the TVS certificate has been regenerated. TVS server will automatically be restarted

Recommended Action   None.

Error Message

%UC_TVS-6-RollBackToPre8.0Disabled: %[AppID=String][ClusterID=String][NodeID=String]: Roll Back to Pre 8.0 has been disabled in the Enterprise Parameter page..

Explanation   This usually means that the RollBack to Pre 8.0 feature is modified in the Enterprise Parameter page

Recommended Action   None.

Error Message

%UC_TVS-6-RollBackToPre8.0Enabled: %[AppID=String][ClusterID=String][NodeID=String]: Roll Back to Pre 8.0 has been enabled in the Enterprise Parameter page..

Explanation   This usually means that the RollBack to Pre 8.0 feature is modified in the Enterprise Parameter page

Recommended Action   None.

Error Message

%UC_TVS-6-DefaultDurationInCacheModified: %[AppID=String][ClusterID=String][NodeID=String]: Default value of a Certificate duration in cache is modified in the Service Parameter page..

Explanation   This usually means that the Default Certificate duration in cache value is modified int the Service Parameter page

Recommended Action   None.

Error Message

%UC_TVS-6-ClusterSecurityModeModified: %[AppID=String][ClusterID=String][NodeID=String]: Cluster Security Mode is modified..

Explanation   This usually means that the Cluster Security mode has been modified

Recommended Action   None.

Error Message

%UC_TVS-1-TVSServerListenSetSockOptFailed: %[nError=Int][IPAddress=String][Port=Int][AppID=String][ClusterID=String][NodeID=String]: Failed to increase the size of the network buffer for receiving file requests..

Explanation   This usually indicates a lack of memory when there is a system issue such as running out of resources.

Recommended Action   Use RTMT to monitor the system memory resources and consumption and correct any system issues that might be contributing to a reduced amount of system resources.

Error Message

%UC_TVS-1-TVSServerListenBindFailed: %[nError=Int][IPAddress=String][Port=Int][AppID=String][ClusterID=String][NodeID=String]: Fail to connect to the network port through which file requests are received..

Explanation   This usually happens if the network port is being used by other applications on the system or if the port was not closed properly in the last execution of TVS server.

Recommended Action   Verify that the port is not in use by other application. After stopping the TVS server, at the command line interface (CLI) on the TVS server, execute the following command: show network status listen. If the port number specified in this alarm is shown in this CLI command output, the port is being used. Restart the Cisco Unified Communications Manager system, which may help to release the port. If the problem persists, go to Cisco Unified Serviceability and enable Detailed level traces in the Trace Configuration window for the TVS service and contact the Cisco Technical Assistance Center (TAC).

Error Message

%UC_AUDITLOG-6-AdministrativeEvent: %[UserID=String][ClientAddress=String][Severity=String][EventType=String][ResourceAccessed=String][EventStatus=String][AuditDetails=String][ComponentID=String][CompulsoryEvent=String][AuditCategory=String][AppID=String][ClusterID=String][NodeID=String]: Audit Event is generated by this application .

Explanation   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

%UC_AUDITLOG-6-SecurityEvent: %[UserID=String][ClientAddress=String][Severity=String][EventType=String][ResourceAccessed=String][EventStatus=String][AuditDetails=String][ComponentID=String][CompulsoryEvent=String][AuditCategory=String][AppID=String][ClusterID=String][NodeID=String]: Audit Event is generated by this application .

Explanation   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

%UC_AUDITLOG-6-CriticalEvent: %[UserID=String][ClientAddress=String][Severity=String][EventType=String][ResourceAccessed=String][EventStatus=String][AuditDetails=String][ComponentID=String][CompulsoryEvent=String][AuditCategory=String][AppID=String][ClusterID=String][NodeID=String]: Audit Event is generated by this application .

Explanation   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

%UC_LOGIN-4-PlatformAdminAccountLocked: %[UserID=String][UnlockTime=String][FailedLoginCount=String][AppID=String][ClusterID=String][NodeID=String]: A user attempted too many incorrect authentications and the corresponding account was locked by the platform.

Explanation   A user repeatedly attempted to login using invalid credentials and the platform locked the user account when the user exhausted the number of allowed login attempts as specified by the FailedLoginCount shown in this alarm. The account remains locked until the number of seconds specified in the UnlockTime elapses.

Recommended Action   Investigate why the user may have been attempting to login using invalid credentials to determine if the account lockout was the result of forgotten credentials or some other reason.

Error Message

%UC_FIPSMODECHANGEALARMCATALOG-5-FipsModeEnable: %[Message=String][AppID=String][ClusterID=String][NodeID=String]: FIPS mode has been successfully enabled in the Cisco Unified Communications Manager. Certifcates for CUCM, CAPF, Tomcat, Ipsec , TVS and SSH services have been regenerated. .

Explanation   This alarm is generated when the Cisco Unified Communications Manager OS administrator enables FIPS mode. Once FIPS mode has been enabled the system will reboot. After the reboot the system runs in compliance with the FIPS 140-2 Level 1 Standards.

Recommended Action   The authorized administration should check all the FIPS logs to ensure that all FIPS related operations including the power up self tests completed successfully.

Error Message

%UC_FIPSMODECHANGEALARMCATALOG-5-FipsModeDisable: %[Message=String][AppID=String][ClusterID=String][NodeID=String]: FIPS mode has been successfully disabled in the Cisco Unified Communications Manager. Certifcates for CUCM, CAPF, Tomcat, Ipsec , TVS and SSH services have been regenerated. .

Explanation   This alarm is generated when the Cisco Unified Communications Manager OS administrator disables FIPS mode. Once FIPS mode has been disabledthe system will reboot.

Recommended Action   The authorized administrator should check the FIPS logs to ensure there are no errors.

Error Message

%UC_ILS-3-ILSDBLException: %[DBLException=String][AppID=String][ClusterID=String][NodeID=String]: An error occurred while the ILS was performing database activities.

Explanation   A severe database layer interface error occurred. Some possible causes for this include the database being unreachable or down or a DNS error.

Recommended Action   Review the System Reports provided in the Cisco Unified Reporting tool, specifically the Unified CM Database Status report, for any anomalous activity. You can also go to Real-Time Reporting Tool (RTMT) and check the Replication Status in the Database Summary page. If status shows 2, then replication is working. Check network connectivity to the server that is running the database. If your system uses DNS, check the DNS configuration for any errors. If the cause is still not identified, collect SDL and SDI traces and contact the Cisco Technical Assistance Center (TAC).

Error Message

%UC_ILS-3-ILSTLSAuthenticationFailed: %[Cluster1=String][AppID=String][ClusterID=String][NodeID=String]: TLS authentication failure to cluster in this ILS network.

Explanation   A TLS connection to a cluster in the ILS network could not be established, mostly likely because of a problem with the certificate presented by the publisher Unified CM in the remote cluster. (For example, not in the Unified CM CTL, or is in the CTL but has expired).

Recommended Action   Verify that the certificate of the remote cluster Unified CM is installed and configured properly on the local Unified CM.

Error Message

%UC_ILS-3-ILSPwdAuthenticationFailed: %[IPAddress=String][AppID=String][ClusterID=String][NodeID=String]: Password authentication failure to cluster in this ILS network.

Explanation   A password authentication failure has occurred on a connection to a remote cluster.

Recommended Action   Verify that ILS at the remote server is configured to use password authentication. Reenter the ILS password if needed. The ILS password must be identical at all clusters that will participate in the same ILS network.

Error Message

%UC_ILS-3-ILSDuplicateClusterID: %[EntClusterID=String][AppID=String][ClusterID=String][NodeID=String]: Duplicate Enterprise Cluster ID found in ILS network.

Explanation   A duplicate Enterprise Cluster ID has been found in this ILS network.

Recommended Action   Check that the Enterprise Cluster ID is not set to the default value. Assign each cluster in the ILS network a unique Enterprise Cluster ID.

Error Message

%UC_ILS-3-ILSHubClusterUnreachable: %[HubCluster=String][ConnDetails=String][AppID=String][ClusterID=String][NodeID=String]: Hub cluster unreachable..

Explanation   This alarm indicates that the ILS was unable to reach the remote hub cluster. ILS will periodically re-attempt to connect to the hub cluster. If the condition is due to a temporary Internet connectivity issue, the problem will self-repair. However, if it is due to a persistent condition, action must be taken.

Recommended Action   Make sure ILS is activated and running at the remote hub cluster. The hostname and IP address that ILS attempted connection to are included in the alarm. Verify that your firewall configuration is allowing the ILS access to the remote server. Try pinging the configured IP address of the remote server, and diagnose any network issues from there.

Error Message

%UC_ILS-2-ILSTCPInUse: %[PortNumber=UInt][AppID=String][ClusterID=String][NodeID=String]: ILS failed while initializing a TCP port because the port is already in use..

Explanation   This alarm indicates that ILS was unable to bind to a TCP port because the port is already in use. It will occur during service startup if the ports that ILS tries to initialize are already in use. ILS will terminate when this error occurs.

Recommended Action   Make sure that no other services have been configured to use the same ports that ILS has been configured to use. Correct the problem and restart ILS.

Error Message

%UC_ILS-2-ILSTCPListenError: %[PortNumber=UInt][AppID=String][ClusterID=String][NodeID=String]: ILS failed while initializing a TCP port..

Explanation   This alarm indicates that ILS was unable to initialize a TCP port. It will occur during service startup when it tries to initialize TCP ports. ILS will terminate when this error occurs.

Recommended Action   Consult the diagnostics for details.

Error Message

%UC_ILS-3-ILSRemoteHostUnresponsive: %[ClusterId=String][ConnectionDetail=String][AppID=String][ClusterID=String][NodeID=String]: No response from host at remote cluster..

Explanation   ILS was able to establish a connection but the remote host was unresponsive. The connection has been dropped and ILS will periodically re-attempt to connect to remote cluster. If the condition is due to a temporary Internet connectivity issue, the problem will self-repair. However, if it is due to a persistent condition, action must be taken.

Recommended Action   Verify the ILS configuration at the remote cluster. Check the remote cluster's syslog for additional details. Diagnose any network issues between the two IP addresses provided in the connection details of this alarm.

Error Message

%UC_ILS-3-ILSUnacceptableConnectionAttempt: %[Reason=String][ConnectionDetail=String][AppID=String][ClusterID=String][NodeID=String]: A connection from a remote ILS server has been rejected..

Explanation   ILS received a connection attempt that was not acceptable. The connection has been dropped. Typically this alarm indicates a misconfiguration or incompatibility of ILS between the local and remote clusters.

Recommended Action   Use the reason message provided to further diagnose the issue. The connection details will include the IP address of the remote ILS.

Error Message

%UC_ILS-3-ILSProtocolVersion: %[ClusterId=String][ConnectionDetail=String][AppID=String][ClusterID=String][NodeID=String]: Incompatible ILS protocol used by remote cluster..

Explanation   ILS protocol used by remote system is not compatible with the local cluster. The connection has been dropped.

Recommended Action   Upgrade the lower version component so that both clusters use the same or compatible version.

Error Message

%UC_ILS-4-ILSPeerLimitApproachingWarning: %[CurrentPeerCount=UInt][AppID=String][ClusterID=String][NodeID=String]: The current peer count has reached 90% or more of the ILS network capacity(ILSP_MSG_PEER_MAX=200).

Explanation   The current peer count has reached 90% or more of the ILS network capacity.

Recommended Action   Make sure that the number of peers in the ILS network does not exceed 200.

Error Message

%UC_ILS-3-ILSPeerLimitExceeded: %[MaxPeerCount=UInt][AppID=String][ClusterID=String][NodeID=String]: Exceeded maximum number of peers in ILS network(ILSP_MSG_PEER_MAX=200).

Explanation   >The number of peers for this cluster in the ILS network is more than the limit set for ILSP_MSG_PEER_MAX. The system will be allowed to add spokes, hubs, and imported catalogs continuously; however, only max number of peers will be advertised to the ILS network.

Recommended Action   Disconnect and rejoin the clusters to the ILS network to clean up obsoleted peers.

Error Message

%UC_Location Bandwidth Manager-2-LocationBandwidthManagerFailure: %[Text=String][HostName=String][IPAddress=String][Reason=Enum][AppID=String][ClusterID=String][NodeID=String]: Indicates an internal failure in LBM.

Explanation   This alarm indicates that an internal failure occurred in the Cisco Location Bandwidth Manager Service. The service should restart in an attempt to clear the failure.

Recommended Action   Monitor for other alarms and restart Cisco Location Bandwidth Manager Service, if necessary. Collect the core file if available, SDL and CCM/SDI trace files (you can gather these from Trace and Log Central in RTMT using the Collect Files feature) and contact the Cisco Technical Assistance Center (TAC).

Reason Code - Enum Definitions

Enum Definitions - Reason

%UC_Location Bandwidth Manager-5-LBMLinkISV: %[RemoteIPAddress=String][LinkID=String][LocalNodeId=UInt][LocalApplicationId=Enum][RemoteApplicationId=Enum][AppID=String][ClusterID=String][NodeID=String]: LBM link to remote application restored.

Explanation   This alarm indicates that the LBM has gained communication with the remote LBM. Note that the remote LBM should also indicate LBMLinkISV.

Recommended Action   Informational only; no action is required

Reason Code - Enum Definitions

Enum Definitions - LocalApplicationId

Enum Definitions - RemoteApplicationId

%UC_Location Bandwidth Manager-1-LBMLinkOOS: %[RemoteIPAddress=String][LinkID=String][LocalNodeId=UInt][LocalApplicationID=Enum][RemoteNodeID=UInt][RemoteApplicationID=Enum][AppID=String][ClusterID=String][NodeID=String]: LBM link to remote application is out of service.

Explanation   This alarm indicates that the local LBM has lost communication with the remote LBM. This alarm usually indicates that a node has gone out of service (whether intentionally for maintenance or to install a new load for example; or unintentionally due to a service failure or connectivity failure).

Recommended Action   In the Cisco Unified Reporting tool, run a CM Cluster Overview report and check to see if all servers can communicate with the Publisher. Also check for any alarms that might have indicated a CallManager OR location bandwidth manager failure and take appropriate action for the indicated failure. If the node was taken out of service intentionally, bring the node back into service.

Reason Code - Enum Definitions

Enum Definitions - LocalApplicationID

Enum Definitions - RemoteApplicationID

%UC_Location Bandwidth Manager-1-LBMVersionMismatch: %[RemoteAppProtocolVersion=String][LocalAppProtocolVersion=String][RemoteNodeId=UInt][RemoteAppId=Enum][RemoteAppVersion=String][AppID=String][ClusterID=String][NodeID=String]: One or more Unified LBM nodes in a cluster are running different LBM versions.

Explanation   This alarm indicates that the local LBM is unable to establish communication with the remote LBM due to a software version mismatch. This is generally a normal occurrence when you are upgrading a LBM node.

Recommended Action   The alarm details include the versions of the local and remote LBM nodes. Compare the versions and upgrade the node if necessary.

Reason Code - Enum Definitions

Enum Definitions - RemoteAppId

%UC_Location Bandwidth Manager-4-PrimaryHubUnreachable: %[LBMHubNode=String][AppID=String][ClusterID=String][NodeID=String]: Primary LBM Hub Node Unreachable..

Explanation   This alarm indicates that the LBM spoke node was unable to connect to Primary LBM Hub Node configured in LBM Hub Group table. The LBM Node will attempt to connect to Secondary and Tertiary LBM Hub Node. If the condition is due to a temporary Network connectivity issue, the problem will self-repair. However, if it is due to a persistent condition, action must be taken.

Recommended Action   Make sure that your firewall configuration is allowing the LBM Node to access the Primary LBM Hub node. If firewall configurations are correct, try pinging the configured IP address and port of the Primary LBM Hub Node, and diagnose any network issues from there. The IP address and port of the Primary LBM Hub Node that was tried by the LBM Node is included as name/value pair in the alarm.

Error Message

%UC_Location Bandwidth Manager-4-SecondaryHubUnreachable: %[LBMHubNode=String][AppID=String][ClusterID=String][NodeID=String]: Secondary LBM Hub Node Unreachable..

Explanation   This alarm indicates that the LBM spoke node was unable to connect to Secondary LBM Hub Node configured in LBM Hub Group table. The LBM Node will attempt to connect back to Primary Hub Node.

Recommended Action   No action is required on your part.

Error Message

%UC_Location Bandwidth Manager-4-TertiaryHubUnreachable: %[LBMHubNode=String][AppID=String][ClusterID=String][NodeID=String]: Tertiary LBM Hub Node Unreachable..

Explanation   This alarm indicates that the LBM spoke node was unable to connect to Tertiary LBM Hub Node configured in LBM Hub Group table. The LBM Node will attempt to connect back to Primary Hub Node.

Recommended Action   No action is required on your part.

Error Message

%UC_Location Bandwidth Manager-2-LBMHubUnreachable: %[PrimHubNode=String][SecondaryHubNode=String][TertiaryHubNode=String][AppID=String][ClusterID=String][NodeID=String]: LBM Hub Nodes Unreachable..

Explanation   This alarm indicates that the LBM spoke node was unable to connect to any of the LBM Hub Nodes configured in LBM Hub Group table. The LBM Spoke Node will periodically re-attempt to connect to the LBM Hub Nodes. If the condition is due to a temporary Network connectivity issue, the problem will self-repair. However, if it is due to a persistent condition, action must be taken.

Recommended Action   Make sure that your firewall configuration is allowing the LBM Spoke Node to access the LBM Hub Nodes. If firewall configurations are correct, try pinging the configured IP addresses and ports of the LBM Hub Nodes, and diagnose any network issues from there. The IP addresses and ports of the LBM Hub Nodes that were tried by the LBM Spoke node are included as name/value pairs in the alarm.

Error Message

%UC_Location Bandwidth Manager-4-SuspiciousIPAddress: %[PortNumber=UInt][Address=String][AppID=String][ClusterID=String][NodeID=String]: LBM has identified suspicious connection attempts from an IP address.

Explanation   LBM has identified suspicious connection attempts from an IP address and has temporarily blocked the address. This alarm is an indication that a Denial-of-Service attack may have been attempted from this IP address.

Recommended Action   Examine network activity for repeated attempts to access the port number specified in this alarm. Using the IP address specified in this alarm, attempt to identify the device that has been sending connection attempts to the port. If the IP address belongs to a device that is configured in IME, evaluate the possible reason for such numerous connection attempts. Generally, no device that is functioning properly will trigger this alarm. Reset the device or remove the device from the network.

Error Message

%UC_Location Bandwidth Manager-2-LBMServicePortFailedToOpen: %[Protocol=String][PortNumber=UInt][ErrorNumber=Int][AppID=String][ClusterID=String][NodeID=String]: LBM service port fails to be opened.

Explanation   LBM socket port that is used to provide service fails to open.

Recommended Action   Please check the LBM configuration to make sure that this port is not used by other applications. If this alarm occurs repeatly, collect the existing trace files and contact the Cisco Technical Assistance Center (TAC).

Error Message

%UC_Location Bandwidth Manager-4-LocationOutOfResource: %[Name=String][ResourceType=Enum][AppID=String][ClusterID=String][NodeID=String]: All bandwidth allocated to the location/link is used up and no resources are available.

Explanation   The Location or Link connecting locations has run out of audio/video/immersive bandwidth and hence no further calls can originate or pass through the location/link. The out of resource condition may be temporary due to high number of calls during peak hours and may correct by itself when calls terminate and bandwidth is freed up.

Recommended Action   Consider adding additional bandwidth to the location/link.

Reason Code - Enum Definitions

Enum Definitions - ResourceType

%UC_Location Bandwidth Manager-3-NoSuchLocation: %[Location=String][FullKey=String][LocalNodeId=UInt][LocalApplicationId=Enum][AppID=String][ClusterID=String][NodeID=String]: A location name is unknown to the LBM service..

Explanation   No such location exists or is recognized by LBM service.

Recommended Action   Check whether the device supports assignment to the location (Shadow and Phantom are special). If the location is defined in a remote cluster, check the connectivity to that cluster ; check whether LBM services in the remote cluster are active; check LBM security mode mismatch between clusters; log off and log back in if this is an EMCC device.

Reason Code - Enum Definitions

Enum Definitions - LocalApplicationId

%UC_Location Bandwidth Manager-3-NoPathExists: %[Location1=String][Location2=String][FullKey=String][LocalNodeId=UInt][LocalApplicationId=Enum][AppID=String][ClusterID=String][NodeID=String]: A LBM service determined that no path exists between location 1 and location 2..

Explanation   Location 1 and Location 2 are not connected.

Recommended Action   Check whether the two locations are connected. If locations and/or links are defined in different clusters, check the connectivity to these clusters; check whether LBM services in all the affected remote clusters are active; check LBM security mode mismatch between clusters; log off and log back in if this is an EMCC device.

Reason Code - Enum Definitions

Enum Definitions - LocalApplicationId

%UC_Location Bandwidth Manager-5-LBMRemoteHubNoSecureConnectionAlarm: %[RemoteIPAddress=String][LocalNodeId=UInt][LocalApplicationID=Enum][RemoteApplicationID=Enum][AppID=String][ClusterID=String][NodeID=String]: Lost LBM secure connection to remote LBM application.

Explanation   This alarm indicates that the local LBM has lost secure communication with the remote LBM. This alarm usually indicates that a node has gone out of service (whether intentionally for maintenance or to install a new load for example; or unintentionally due to a service failure or connectivity failure); networking issues; or certificate issues.

Recommended Action   In the Cisco Unified Reporting tool, run a CM Cluster Overview report and check to see if all servers can communicate with the Publisher. Also check for any alarms that might have indicated LBM failure and take appropriate action for the indicated failure. If the node was taken out of service intentionally, bring the node back into service.

Reason Code - Enum Definitions

Enum Definitions - LocalApplicationID

Enum Definitions - RemoteApplicationID

%UC_Location Bandwidth Manager-5-LBMRemoteHubSecureConnectionRestoredAlarm: %[RemoteIPAddress=String][LocalNodeId=UInt][LocalApplicationId=Enum][RemoteApplicationId=Enum][AppID=String][ClusterID=String][NodeID=String]: Restored LBM secure connection to remote LBM application.

Explanation   This alarm indicates that the LBM has gained secure communication with the remote LBM. Note that the remote LBM should also indicate LBMRemoteHubSecureConnectionAlarm.

Recommended Action   Informational only; no action is required

Reason Code - Enum Definitions

Enum Definitions - LocalApplicationId

Enum Definitions - RemoteApplicationId

%UC_Location Bandwidth Manager-5-LBMRemoteHubNoInsecureConnectionAlarm: %[RemoteIPAddress=String][LocalNodeId=UInt][LocalApplicationID=Enum][RemoteApplicationID=Enum][AppID=String][ClusterID=String][NodeID=String]: Lost LBM insecure connection to the remote LBM application.

Explanation   This alarm indicates that the local LBM has lost insecure communication with the remote LBM. This alarm usually indicates that a node has gone out of service (whether intentionally for maintenance or to install a new load for example; or unintentionally due to a service failure or connectivity failure).

Recommended Action   In the Cisco Unified Reporting tool, run a CM Cluster Overview report and check to see if all servers can communicate with the Publisher. Also check for any alarms that might have indicated LBM failure and take appropriate action for the indicated failure. If the node was taken out of service intentionally, bring the node back into service.

Reason Code - Enum Definitions

Enum Definitions - LocalApplicationID

Enum Definitions - RemoteApplicationID

%UC_Location Bandwidth Manager-5-LBMRemoteHubInsecureConnectionRestoredAlarm: %[RemoteIPAddress=String][LocalNodeId=UInt][LocalApplicationId=Enum][RemoteApplicationId=Enum][AppID=String][ClusterID=String][NodeID=String]: Restored LBM insecure connection to remote LBM.

Explanation   This alarm indicates that the LBM has gained secure communication with the remote LBM. Note that the remote LBM should also indicate LBMRemoteHubSecureConnectionAlarm.

Recommended Action   Informational only; no action is required

Reason Code - Enum Definitions

Enum Definitions - LocalApplicationId

Enum Definitions - RemoteApplicationId

%UC_Location Bandwidth Manager-3-LBMRemoteHubNoConnectionAlarm: %[RemoteIPAddress=String][LocalNodeId=UInt][LocalApplicationID=Enum][RemoteApplicationID=Enum][AppID=String][ClusterID=String][NodeID=String]: Lost LBM all connection to the remote LBM application.

Explanation   This alarm indicates that the local LBM has lost all communications with the remote LBM. This alarm usually indicates that a node has gone out of service (whether intentionally for maintenance or to install a new load for example; or unintentionally due to a service failure or connectivity failure).

Recommended Action   In the Cisco Unified Reporting tool, run a CM Cluster Overview report and check to see if all servers can communicate with the Publisher. Also check for any alarms that might have indicated LBM failure and take appropriate action for the indicated failure. If the node was taken out of service intentionally, bring the node back into service.

Reason Code - Enum Definitions

Enum Definitions - LocalApplicationID

Enum Definitions - RemoteApplicationID

%UC_Location Bandwidth Manager-5-LBMRemoteHubConnectionRestoredAlarm: %[RemoteIPAddress=String][LocalNodeId=UInt][LocalApplicationId=Enum][RemoteApplicationId=Enum][AppID=String][ClusterID=String][NodeID=String]: Restored LBM connection to remote LBM application.

Explanation   This alarm indicates that the LBM has gained secure communication with the remote LBM. Note that the remote LBM should also indicate LBMRemoteHubSecureConnectionAlarm.

Recommended Action   Informational only; no action is required

Reason Code - Enum Definitions

Enum Definitions - LocalApplicationId

Enum Definitions - RemoteApplicationId

Explanation   This alarm indicates that the LBM has gained secure communication with the remote LBM. Note that the remote LBM should also indicate LBMRemoteHubSecureConnectionAlarm.

Recommended Action   Informational only; no action is required

Error Message

%UC_ICSA-2-InterclusterSyncAgentPeerDuplicate: %[hostname=String][existingPeer=String][AppID=String][ClusterID=String][NodeID=String]: Cisco Intercluster Sync Agent service failed to sync with remote peer.

Explanation   Cisco Intercluster Sync Agent service failed to sync user location data from a remote peer. The remote peer is from a IM and Presence Service 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 IM and Presence Service Administration GUI Inter-cluster details page. You can also run the System Troubleshooter for more details

Error Message

%UC_ICSA-2-ICSACertificateFingerPrintMisMatch: %[SubjectCN=String][IssuerCN=String][AppID=String][ClusterID=String][NodeID=String]: Cisco Intercluster Sync Agent service detected a fingerprint mismatch on the certificate being processed.

Explanation   Cisco Intercluster Sync Agent service detected a fingerprint mismatch on the certificate being processed

Recommended Action   Use the IM and Presence Service 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

%UC_ICSA-2-ICSACertificateValidationFailure: %[SubjectCN=String][IssuerCN=String][ErrorCode=String][AppID=String][ClusterID=String][NodeID=String]: Cisco Intercluster Sync Agent service detected a validation error on the certificate being processed.

Explanation   Cisco Intercluster Sync Agent service detected a validation error on the certificate being processed

Recommended Action   Use the IM and Presence Service 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

%UC_ICSA-4-ICSACertificateCAConflict: %[SubjectCN=String][IssuerCN=String][AppID=String][ClusterID=String][NodeID=String]: Cisco Intercluster Sync Agent service detected a CA certificate conflict

Explanation   Cisco Intercluster Sync Agent service detected a CA certificate conflict

Recommended Action   A conflicting CA certificate was detected on CUCM when auditing certificates. Stop the Cisco Intercluster Sync Agent on all IM and Presence nodes in the cluster. Delete the conflicting certificate on all CUCM and IM and Presence nodes and re-upload the valid certificate to each node. Start the Cisco Intercluster Sync Agent

Error Message

%UC_ICSA-2-InterClusterSyncAgentPeerSyncFailure: %[remotePeerAddress=String][AppID=String][ClusterID=String][NodeID=String]: Cisco Intercluster Sync Agent service detected periodic sync failure

Explanation   Cisco Intercluster Sync Agent is unable to read the remote peer's hostname or IP address of the IM and Presence node. The service will try resyncing every 5 minutes.

Recommended Action   Verify that the hostname or IP address of the IM and Presence node is present in System -> Server configuration page on remote cluster's Cisco Unified CM Administration.

Error Message

%UC_ICSA-2-InterClusterSyncAgentDomainConflict: %[remotePeerAddress=String][AppID=String][ClusterID=String][NodeID=String]: Cisco Intercluster Sync Agent service detected periodic sync failure

Explanation   Cisco Intercluster Sync Agent detected proxy domains mismatch. The service will try resyncing every 30 minutes

Recommended Action   Cisco Intercluster Sync Agent detected proxy domains mismatch. The service will try resyncing every 30 minutes

Error Message

%UC_ICSA-2-InterClusterSyncAgentSyncFailure: %[remotePeerAddress=String][AppID=String][ClusterID=String][NodeID=String]: Cisco Intercluster Sync Agent service detected periodic sync failure

Explanation   Cisco Intercluster Sync Agent service detected an exception.

Recommended Action   Cisco Intercluster Sync Agent service will try resyncing every 5 minutes.

Error Message

%UC_ICSA-6-InterClusterSyncAgentAxlClientTimeout: %[remotePeerAddress=String][AppID=String][ClusterID=String][NodeID=String]: Cisco Intercluster Sync Agent service detected periodic sync failure

Explanation   Cisco Intercluster Sync Agent service could not establish an AXL connection with the remote peer. The service will try resyncing every 5 minutes.

Recommended Action   Verify that the Cisco AXL Web Service on the remote peer is running.

Error Message

%UC_ICSA-2-InterClusterSyncAgentHeapSpaceError: %[AppID=String][ClusterID=String][NodeID=String]: Cisco Intercluster Sync Agent service detected a heap space error

Explanation   Cisco Intercluster Sync Agent service detected a heap space error.

Recommended Action   Restart Cisco Intercluster Sync Agent service.

Error Message

%UC_ICSA-6-InterClusterSyncAgentStatus: %[remotePeerAddress=String][AppID=String][ClusterID=String][NodeID=String]: Periodic sync completed successfully

Explanation   Periodic sync completed successfully for remote peer.

Recommended Action   Informational purposes only; no action is required.

Error Message

%UC_ICSA-6-InterClusterSyncAgentControllerStatus: %[remotePeerAddress=String][AppID=String][ClusterID=String][NodeID=String]: Peer sync controller created successfully

Explanation   Peer sync controller created successfully for remote peer.

Recommended Action   Informational purposes only; no action is required.

Error Message

%UC_ICSA-2-InterClusterSyncAgentPeerPeriodicSyncingFailure: %[remotePeerAddress=String][lastSynchronizedTime=String][AppID=String][ClusterID=String][NodeID=String]: Cisco Intercluster Sync Agent service detected periodic syncing failure with an inter-cluster peer

Explanation   Cisco Intercluster Sync Agent service detected a failure for the periodic syncing. It will try to recover the periodic syncing automatically if the Service Parameter "Enable Auto Recovery for Inter-cluster Peer Periodic Syncing Failure" of Inter-Cluster Sync Agent service is enabled.

Recommended Action   Cisco Intercluster Sync Agent service detected a failure for the periodic syncing. It will try to recover the periodic syncing automatically if the Service Parameter "Enable Auto Recovery for Inter-cluster Peer Periodic Syncing Failure" of Inter-Cluster Sync Agent service is enabled.

Error Message

%UC_ICSA-2-InterclusterSyncAgentPeerDown: %[remotePeer=String][AppID=String][ClusterID=String][NodeID=String]: Cisco Intercluster Sync Agent service has detected an Intercluster Peer is unreachable

Explanation   Cisco Intercluster Sync Agent service detected remotePeer is unreachable via ping on TCP port 8443.

Recommended Action   Verify the node remotePeer is up and the network connectivity from this node to remotePeer is reachable

Error Message

%UC_ICSA-2-MAencryptionMultiMaster: %[remotePeerAddress=String][AppID=String][ClusterID=String][NodeID=String]: Cisco Intercluster Sync Agent detected multi-master configuration

Explanation   An ICSA Peer cluster is configured for encrypted message archiving with a different master from the local cluster.

Recommended Action   Encrypted message archiving requires a single master cluster for all ICSA peers. To resolve this condition you must download the encryption key from the remote cluster and disable encrypted message archiving before adding the remote cluster(s) as ICSA Peers with this cluster.

Error Message

%UC_null-2-LocationServiceMseDown: %[hostname=String][AppID=String][ClusterID=String][NodeID=String]: Cisco Location Service MSE Down Alarm.

Explanation   MSE is down. Location services for this MSE will be unavailable.

Recommended Action   Check IM/P Service logs and MSE logs to determine problem. After resolving issue, delete and re-add the MSE.

Error Message

%UC_ReplWatcher-4-ReplicationFailure: %[HostName=String][AppID=String][ClusterID=String][NodeID=String]: Cisco IM and Presence Data Monitor detected replication failure.

Explanation   Cisco IM and Presence Data Monitor 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 IM and Presence Data Monitor logs for details. Replication status can be manually checked via the command line interface.

Error Message

%UC_ReplWatcher-6-ReplicationFailureClear: %[HostName=String][AppID=String][ClusterID=String][NodeID=String]: Cisco IM and Presence Data Monitor detected that replication has been successfully established on this node..

Explanation   Cisco IM and Presence Data Monitor has detected that replication has been successfully established on this node.

Recommended Action   No action required. See Cisco IM and Presence Data Monitor logs for details.

Error Message

%UC_ReplWatcher-4-ReplicationFailureTimeout: %[HostName=String][AppID=String][ClusterID=String][NodeID=String]: Cisco IM and Presence Data Monitor startup timeout. Cisco IM and Presence Data Monitor is allowing services to continue startup although replication has not completed setup on this publisher node..

Explanation   Cisco IM and Presence Data Monitor startup timeout. Cisco IM and Presence Data Monitor is allowing services to continue startup although replication has not completed setup on this publisher node.

Recommended Action   Please check Cisco IM and Presence Data Monitor logs for details. Replication status can be manually checked via the command line interface.

Error Message

%UC_ReplWatcher-1-ReplicationIMAddressSchemeChangeFailure: %[HostName=String][AppID=String][ClusterID=String][NodeID=String]: Cisco IM and Presence Data Monitor has detected the database job to change the IM Address Scheme has failed..

Explanation   Cisco IM and Presence Data Monitor has detected the database job to change the IM Address Scheme has failed. Cisco IM and Presence Data Monitor has stopped services.

Recommended Action   Please rerun the IM Address Scheme change procedure from the Advanced Presence Settings page.

Error Message

%UC_ReplWatcher-1-ReplicationDefaultIMDomainChangeFailure: %[HostName=String][AppID=String][ClusterID=String][NodeID=String]: Cisco IM and Presence Data Monitor has detected database job to change the local default IM domain has failed..

Explanation   Cisco IM and Presence Data Monitor has detected the database job to change the local default IM domain has failed. Cisco IM and Presence Data Monitor has stopped services.

Recommended Action   Please rerun the default IM domain change procedure from the Advanced Presence Settings page.

Error Message

%UC_ReplWatcher-1-DuplicateUserid: %[HostName=String][AppID=String][ClusterID=String][NodeID=String]: Cisco IM and Presence Data Monitor has detected that two or more users on the system share the same UserID value..

Explanation   Cisco IM and Presence Data Monitor has detected that two or more users on the system share the same UserID value. This is a misconfiguration as all users must have a unique UserID. This may result in undetermined behaviour in routing IM and Presence packets to the affected users. It is not possible for two users on the same cluster to share a common userID, so the conflicting users must reside on separate clusters.

Recommended Action   Begin by compiling a list of the duplicate UserIDs. The User Troubleshooter section on the IM and Presence System Troubleshooter will display up to 10 duplicate UserIDs. Alternatively, the following Administration CLI command will supply all affected UserIDs: utils users validate. Once the list has been compiled, check to see why each UserID is being duplicated and take the appropriate action. There are two potential reasons why an entry may be marked as Duplicate. (1) The same user has been enabled for IM and Presence on more than one cluster. In this case, disable IM and Presence for the user for all but one of the clusters to solve the issue. (2) Two or more different users, each on different clusters share a common UserID. In this case, re-configure the appropriate user's UserIDs on CUCM such that they no longer conflict with one another. If UserID values are synced from a LDAP Directory, the reconfiguration may need to take place on that Directory.

Error Message

%UC_ReplWatcher-1-DuplicateDirectoryURI: %[HostName=String][AppID=String][ClusterID=String][NodeID=String]: Cisco IM and Presence Data Monitor has detected that two or more users on the system share the same Directory URI value..

Explanation   Cisco IM and Presence Data Monitor has detected that two or more users on the system share the same Directory URI value. This is a misconfiguration as all users must have a unique Directory URI. This may result in undetermined behaviour in routing IM and Presence packets to the affected users. It is not possible for two users on the same cluster to share a common Directory URI, so the conflicting users must reside on separate clusters.

Recommended Action   Begin by compiling a list of the duplicate Directory URIs. The User Troubleshooter section on the IM and Presence System Troubleshooter will display up to 10 duplicate Directory URIs. Alternatively, the following Administration CLI command will supply all affected Directory URIs: utils users validate. Once the list has been compiled, check to see why each URI is being duplicated and take the appropriate action. There are two potential reasons why an entry may be marked as Duplicate. (1) The same user has been enabled for IM and Presence on more than one cluster. In this case, disable IM and Presence for the user for all but one of the clusters to solve the issue. (2) Two or more different users, each on different clusters share a common DirectoryURI. In this case, re-configure the appropriate user's Directory URI on CUCM such that they no longer conflict with one another. If Directory URI values are synced from a LDAP Directory, the reconfiguration may need to take place on that Directory.

Error Message

%UC_ReplWatcher-4-DuplicateDirectoryURIWarning: %[HostName=String][AppID=String][ClusterID=String][NodeID=String]: Cisco IM and Presence Data Monitor has detected that two or more users on the system share the same Directory URI value..

Explanation   Cisco IM and Presence Data Monitor has detected that two or more users on the system share the same Directory URI value. This is a misconfiguration as all users must have a unique Directory URI. This misconfiguration will not immediately impact users. However if the IM Addressing Scheme is switched to Directory URI, it will result in undetermined behaviour in routing IM and Presence packets to the affected users. It is not possible for two users on the same cluster to share a common Directory URI, so the conflicting users must reside on separate clusters.

Recommended Action   Begin by compiling a list of the duplicate Directory URIs. The User Troubleshooter section on the IM and Presence System Troubleshooter will display up to 10 affected Directory URIs. Alternatively, the following Administration CLI command will supply all affected Directory URIs: utils users validate. Once the list has been compiled, check to see why each URI is being duplicated and take the appropriate action. There are two potential reasons why an entry may be marked as Duplicate: 1) The same user has been enabled for IM and Presence on more than one cluster. In this case, disable IM and Presence for the user for all but one of the clusters to solve the issue. 2) Two or more different users, each on different clusters share a common DirectoryURI. In this case, re-configure the user's Directory URI on CUCM such that they no longer conflict with one another. If Directory URI values are synced from a LDAP Directory, the reconfiguration may need to take place on that Directory.

Error Message

%UC_ReplWatcher-1-InvalidDirectoryURI: %[HostName=String][AppID=String][ClusterID=String][NodeID=String]: Cisco IM and Presence Data Monitor has detected that one or more users have an invalid Directory URI value..

Explanation   Cisco IM and Presence Data Monitor has detected that one or more users have an invalid Directory URI value. An invalid Directory URI is deemed an entry that is either empty or does not follow the basic user@domain URI format. This misconfiguration will mean the affected users will be unable to sign into IM and Presence.

Recommended Action   Begin by compiling a list of the affected users. The User Troubleshooter section on the IM and Presence System Troubleshooter will display up to 10 affected users. Alternatively, the following Administration CLI command will supply all affected users and their home location: utils users validate. Once the list has been compiled, proceed to edit the Directory URI value for these users on CUCM. If the Directory URI field is synced from a LDAP Directory, make the required modification to that user on the Directory instead.

Error Message

%UC_ReplWatcher-4-InvalidDirectoryURIWarning: %[HostName=String][AppID=String][ClusterID=String][NodeID=String]: Cisco IM and Presence Data Monitor has detected that one or more users have an invalid Directory URI value..

Explanation   Cisco IM and Presence Data Monitor has detected that one or more users have an invalid Directory URI value. An invalid Directory URI is deemed an entry that is either empty or does not follow the basic user@domain URI format. This misconfiguration will not immediately impact users. However if the IM Addressing Scheme is switched to Directory URI, the affected users will be unable to sign into IM and Presence.

Recommended Action   Begin by compiling a list of the affected users. The User Troubleshooter section on the IM and Presence System Troubleshooter will display up to 10 affected users. Alternatively, the following Administration CLI command will supply all affected users and their home location: utils users validate. Once the list has been compiled, proceed to edit the Directory URI value for these users on CUCM. If the Directory URI field is synced from a LDAP Directory, make the required modification to that user on the Directory instead.

Error Message

%UC_ConfigAgent-3-EspConfigAgentMemAllocError: %[Location=String][AppID=String][ClusterID=String][NodeID=String]: Cisco Config Agent service was unable to allocate memory.

Explanation   Cisco 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 IM and Presence Service cluster. You can reassign users to other nodes using the Topology page on the IM and Presence Service Administration GUI

Error Message

%UC_ConfigAgent-3-EspConfigAgentFileWriteError: %[Reason=String][AppID=String][ClusterID=String][NodeID=String]: Cisco Config Agent service was unable to write to the filesystem.

Explanation   Cisco 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 IM and Presence Service cluster. You can reassign users to other nodes using the Topology page on the IM and Presence Service Administration GUI

Error Message

%UC_ConfigAgent-3-EspConfigAgentSharedMemoryStaticRouteError: %[AppID=String][ClusterID=String][NodeID=String]: Cisco Config Agent service could not access static route shared memory.

Explanation   Cisco 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 IM and Presence Service cluster. You can reassign users to other nodes using the Topology page on the IM and Presence Service Administration GUI

Error Message

%UC_ConfigAgent-5-EspConfigAgentServiceStartFailed: %[AppID=String][ClusterID=String][NodeID=String]: Cisco Config Agent failed to start a feature service.

Explanation   Cisco 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

%UC_ConfigAgent-5-EspConfigAgentServiceStopFailed: %[AppID=String][ClusterID=String][NodeID=String]: Cisco Config Agent failed to stop a feature service.

Explanation   Cisco 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

%UC_ConfigAgent-4-EspConfigAgentNetworkOutage: %[AppID=String][ClusterID=String][NodeID=String]: Cisco Config Agent network outage.

Explanation   Cisco Config Agent noticed a network outage

Recommended Action   Using RTMT, verify system health and network connectivity.

Error Message

%UC_ConfigAgent-4-EspConfigAgentNetworkRestored: %[AppID=String][ClusterID=String][NodeID=String]: Cisco Config Agent network restored.

Explanation   Cisco Config Agent noticed network was restored

Recommended Action   Using RTMT, verify system health and network connectivity.

Error Message

%UC_ConfigAgent-4-EspConfigAgentHighMemoryUtilization: %[AppID=String][ClusterID=String][NodeID=String]: Virtual memory utilization has exceeded the configured threshold.

Explanation   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 IM and Presence Service Administration GUI Service Parameters for the Cisco Config Agent

Error Message

%UC_ConfigAgent-5-EspConfigAgentHighMemoryUtilizationClear: %[AppID=String][ClusterID=String][NodeID=String]: Virtual memory utilization is below the configured low watermark.

Explanation   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

%UC_ConfigAgent-4-EspConfigAgentHighCPUUtilization: %[AppID=String][ClusterID=String][NodeID=String]: CPU utilization has exceeded the configured threshold.

Explanation   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 IM and Presence Service Administration GUI Service Parameters for the Cisco Config Agent

Error Message

%UC_ConfigAgent-5-EspConfigAgentHighCPUUtilizationClear: %[AppID=String][ClusterID=String][NodeID=String]: CPU utilization is below the configured low watermark.

Explanation   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

%UC_ConfigAgent-3-EspConfigAgentLocalDBAccessError: %[AppID=String][ClusterID=String][NodeID=String]: Cisco Config Agent service was unable to access the local IM and Presence Service database.

Explanation   Cisco Config Agent service failed to read or write to the local IM and Presence Service 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

%UC_ConfigAgent-4-EspConfigAgentRemoteDBAccessError: %[AppID=String][ClusterID=String][NodeID=String]: Cisco Config Agent service was unable to access a remote IM and Presence Service database.

Explanation   Cisco Config Agent service failed to read or write to a remote IM and Presence Service 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

%UC_ConfigAgent-4-EspConfigAgentProxyDomainNotConfigured: %[AppID=String][ClusterID=String][NodeID=String]: Cisco Config Agent service requires that the Default IM Domain is configured..

Explanation   Cisco Config Agent service uses the Default IM Domain to properly generate ACLs. If not configured this could lead to routing failures.

Recommended Action   Go to the Presence -> Settings -> Advanced Configuration Page on your IM and Presence Server to set this value and save.

Error Message

%UC_PE-2-PEDatabaseError: %[PEDatabaseErrorAlarmMessage=String][AppID=String][ClusterID=String][NodeID=String]: Information lookup failed.

Explanation   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 Presence service logs for errors

Error Message

%UC_PE-2-PEPeerNodeFailure: %[PEPeerNodeFailureAlarmMessage=String][AppID=String][ClusterID=String][NodeID=String]: The Cisco Presence Engine service on the peer node of a subcluster has failed.

Explanation   The Cisco Presence Engine service in the peer node is not responding

Recommended Action   Use Cisco Unified Serviceability to verify the Cisco Presence Engine service is activated and running

Error Message

%UC_PE-3-PEAutoRecoveryFailed: %[PEAutorecoveryFailedAlarmMessage=String][AppID=String][ClusterID=String][NodeID=String]: Cisco Presence Engine service auto-recovery failure.

Explanation   An error occurred during the startup sequence of the Cisco Presence Engine service

Recommended Action   This error may indicate a possible configuration issue. Please correct the problem identified in the failure message

Error Message

%UC_PE-5-PEPeerNodeFailureCleared: %[PEPeerNodeFailureClearedAlarmMessage=String][AppID=String][ClusterID=String][NodeID=String]: Cisco Presence Engine service on the clusters peer node has returned to normal operation.

Explanation   The Cisco 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

%UC_PE-4-PELoadHighWaterMark: %[PELoadHighWaterMarkAlarmMessage=String][AppID=String][ClusterID=String][NodeID=String]: Indicates the Cisco Presence Engine service has exceeded a CPU utilization threshold.

Explanation   The Cisco Presence Engine service has detected that the CPU utilization has exceeded the configured threshold. During this time the Cisco 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 IM and Presence Service node in the cluster

Error Message

%UC_PE-5-PELoadHighWaterMarkCleared: %[PELoadHighWaterMarkClearedAlarmMessage=String][AppID=String][ClusterID=String][NodeID=String]: Cisco Presence Engine service high water threshold has cleared.

Explanation   The Cisco 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

%UC_PE-2-PEIDStoIMDBDatabaseSyncError: %[PEIDStoIMDBDatabaseSyncErrorAlarmMessage=String][AppID=String][ClusterID=String][NodeID=String]: Synchronization between the IM and Presence Service Database and the Cisco Presence Engine database has failed.

Explanation   An error has occurred synchronizing the IM and Presence Service data with the Cisco Presence Engine database

Recommended Action   See associated error message and log files. Please restart the Cisco Presence Engine service when convenient

Error Message

%UC_PE-5-PEIDStoIMDBDatabaseSyncErrorCleared: %[PEIDStoIMDBDatabaseSyncErrorClearedAlarmMessage=String][AppID=String][ClusterID=String][NodeID=String]: Synchronization between the IM and Presence Service database and the Cisco Presence Engine database established.

Explanation   The Cisco Presence Engine service has established synchronization between IM and Presence Service database and the Cisco Presence Engine database

Recommended Action   Notification purposes only; no action is required

Error Message

%UC_PE-2-PEIDSSubscribeError: %[PEIDSSubscribeErrorAlarmMessage=String][AppID=String][ClusterID=String][NodeID=String]: The Cisco Presence Engine service was unable to subscribe for IM and Presence Service database change notifications.

Explanation   An error has occurred subscribing to IM and Presence Service database change notifications

Recommended Action   See associated error message and log files. Please restart the Cisco Presence Engine service when convenient

Error Message

%UC_PE-2-PEIDSQueryError: %[PEIDSQueryErrorAlarmMessage=String][AppID=String][ClusterID=String][NodeID=String]: The Cisco Presence Engine service has detected an error while querying the IM and Presence Service database.

Explanation   An error has occurred whilst querying the IM and Presence Service database

Recommended Action   See associated error message and log files. Please restart the Cisco Presence Engine service when convenient

Error Message

%UC_PE-4-PEMemoryHigh: %[PEMemoryHighAlarmMessage=String][AppID=String][ClusterID=String][NodeID=String]: Indicates the Cisco Presence Engine service has hit a high memory threshold.

Explanation   The Cisco Presence Engine service has encountered a high memory condition. The Cisco 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 IM and Presence node in the cluster

Error Message

%UC_PE-5-PEMemoryHighCleared: %[PEMemoryHighClearedAlarmMessage=String][AppID=String][ClusterID=String][NodeID=String]: Indicates that the Cisco Presence Engine service has cleared the high memory condition.

Explanation   The Cisco 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

%UC_PE-6-PESipMessageTimeout: %[SipMessageCallID=String][AppID=String][ClusterID=String][NodeID=String]: Timeout occurred on SIP message transmission.

Explanation   The transmission of an Cisco Presence Engine service SIP message timed out

Recommended Action   Look for possible network latency problems

Error Message

%UC_PE-2-PESipSocketBindFailure: %[SipSocketInterface=String][AppID=String][ClusterID=String][NodeID=String]: Cisco Presence Engine service was unable to connect to the SIP listener interface.

Explanation   Cisco 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 Presence Engine service listen interface is configured correctly on the IM and Presence Service Administration GUI Application Listener page. Verify that no other process is listening on the same port using netstat

Error Message

%UC_PE-6-PEStateStopped: %[AppID=String][ClusterID=String][NodeID=String]: Cisco Presence Engine service is terminating.

Explanation   Cisco Presence Engine service is terminating

Recommended Action   Notification purposes only; no action is required

Error Message

%UC_PE-4-PEStateLocked: %[AppID=String][ClusterID=String][NodeID=String]: Cisco Presence Engine service is administratively prohibited from processing traffic.

Explanation   Cisco Presence Engine service is administratively prohibited from processing traffic

Recommended Action   Notification purposes only; no action is required

Error Message

%UC_PE-6-PEStateShuttingdown: %[AppID=String][ClusterID=String][NodeID=String]: Cisco Presence Engine service is shutting down.

Explanation   Cisco 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

%UC_PE-6-PEStateUnlocked: %[AppID=String][ClusterID=String][NodeID=String]: Cisco Presence Engine service is administratively permitted to process traffic.

Explanation   Cisco Presence Engine service is administratively permitted to process traffic

Recommended Action   Notification purposes only; no action is required

Error Message

%UC_PE-4-PEStateDisabled: %[PEStateDisabledAlarmMessage=String][AppID=String][ClusterID=String][NodeID=String]: Cisco Presence Engine service is inoperable and unable to process traffic.

Explanation   Cisco Presence Engine service is inoperable and unable to process traffic

Recommended Action   Check the log files and monitor the Cisco Presence Engine service with RTMT

Error Message

%UC_PE-5-PEStateEnabled: %[PEStateEnabledAlarmMessage=String][AppID=String][ClusterID=String][NodeID=String]: Cisco Presence Engine service is now able to process traffic.

Explanation   Cisco Presence Engine service is now able to process traffic

Recommended Action   Notification purposes only; no action is required

Error Message

%UC_PE-3-PECalendarConnectionLoss: %[PECalendarConnectionLossAlarmMessage=String][AppID=String][ClusterID=String][NodeID=String]: Indicates that the Cisco Presence Engine service cannot connect to the Calendar Server.

Explanation   The Cisco 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 IM and Presence Service Administration GUI Presence Gateways page

Error Message

%UC_PE-5-PECalendarConnectionLossCleared: %[PECalendarConnectionLossClearedAlarmMessage=String][AppID=String][ClusterID=String][NodeID=String]: Cisco Presence Engine service has regained connection to the Calendar Server.

Explanation   The Cisco 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

%UC_PE-3-PEWebDAVInitializationFailure: %[PEWebDAVInitializationFailureAlarmMessage=String][AppID=String][ClusterID=String][NodeID=String]: Cisco Presence Engine service attempt to init the WebDAV library failed.

Explanation   The Cisco Presence Engine service has failed to initialize the WebDAV library. The Calendaring feature will not work without WebDAV

Recommended Action   Restart the Cisco Presence Engine service

Error Message

%UC_PE-3-PEWebDAVInitializationFailure: %[AppID=String][ClusterID=String][NodeID=String]: Cisco Presence Engine service attempt to init the WebDAV library failed.

Explanation   The Cisco Presence Engine service has failed to initialize the WebDAV library. The Calendaring feature will not work without WebDAV

Recommended Action   Restart the Cisco Presence Engine service

Error Message

%UC_Proxy-2-ESPStopped: %[Version=String][AppID=String][ClusterID=String][NodeID=String]: Cisco SIP Proxy service child process has been stopped.

Explanation   Cisco 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

%UC_Proxy-2-ESPSharedMemCreateFailed: %[AppID=String][ClusterID=String][NodeID=String]: Failed to create shared memory.

Explanation   Failed to create shared memory segments while trying to initialize tables

Recommended Action   Use RTMT to check system shared memory and check the Cisco SIP Proxy service trace log file for any detailed error messages

Error Message

%UC_Proxy-2-ESPSharedMemSetPermFailed: %[AppID=String][ClusterID=String][NodeID=String]: Failed to set permissions on shared memory.

Explanation   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 SIP Proxy service trace log file for any detailed error messages

Error Message

%UC_Proxy-2-ESPSharedMemAllocFailed: %[MySQL=String][AppID=String][ClusterID=String][NodeID=String]: Failed to allocate shared memory.

Explanation   Failed to allocate shared memory segments while trying to initialize tables

Recommended Action   Use RTMT to check system shared memory and check the Cisco SIP Proxy service trace log file for any detailed error messages

Error Message

%UC_Proxy-3-ESPConfigError: %[SharedMemorySize=String][NumberOfVsa=String][ENUM=String][NumberExpansion=String][NumberServices=String][Registry=String][Routing=String][Radius=String][RAS=String][RPMS=String][MethodRouting=String][AppID=String][ClusterID=String][NodeID=String]: Cisco SIP Proxy service configuration file error.

Explanation   This may indicate a formatting error, invalid value, etc with the Cisco SIP Proxy service configuration file

Recommended Action   Verify that the Cisco Config Agent service is running. This service is responsible for writing the Proxy configuration file

Error Message

%UC_Proxy-3-ESPConfigNotFound: %[SipModule=String][SipAuthenModule=String][SipEnum=String][SipNumExpand=String][SipNumServices=String][SipRegistry=String][SipRouting=String][SipAcct=String][SipRpms=String][SipPrivacy=String][SipMethodRoute=String][AppID=String][ClusterID=String][NodeID=String]: Cisco SIP Proxy service configuration file not found.

Explanation   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 IM and Presence server

Error Message

%UC_Proxy-3-ESPCreateLockFailed: %[AppID=String][ClusterID=String][NodeID=String]: Failed to create a lock file.

Explanation   Failed to create a lock file

Recommended Action   Use RTMT to check the Cisco SIP Proxy service trace log file for any detailed error messages

Error Message

%UC_Proxy-3-ESPSocketError: %[Radius=String][RAS=String][AppID=String][ClusterID=String][NodeID=String]: Network socket errors encountered.

Explanation   Network socket errors could be caused by binding errors, get socket address failures, etc

Recommended Action   Use RTMT to check the Cisco SIP Proxy service trace log file for any detailed error messages

Error Message

%UC_Proxy-3-ESPStatsLogFileOpenFailed: %[AppID=String][ClusterID=String][NodeID=String]: Failed to open stats log file.

Explanation   Failed to open the Cisco SIP Proxy service stats log file

Recommended Action   Use RTMT to check the Cisco SIP Proxy service trace log file for any detailed error messages

Error Message

%UC_Proxy-3-ESPStatsInitFailed: %[AppID=String][ClusterID=String][NodeID=String]: Failed to initialize the performance interface.

Explanation   Failed to initialize the performance Interface

Recommended Action   Use RTMT to check the Cisco SIP Proxy service trace log file for any detailed error messages

Error Message

%UC_Proxy-3-ESPMallocFailure: %[SIPProtocol=String][NumberExpansion=String][SipRegistry=String][SipRouting=String][RAS=String][RPMS=String][AppID=String][ClusterID=String][NodeID=String]: Failed to allocate memory.

Explanation   Failed to allocate memory. This may indicate a low/no memory issue with the server

Recommended Action   Use RTMT to check the Cisco SIP Proxy service trace log file for any detailed error messages

Error Message

%UC_Proxy-3-ESPWrongIPAddress: %[ProxyIPAddrTab=String][IPAddrNotMine=String][DNSReturnedBadIP=String][ProxyLoopbackIPA=String][InvalidRASIPAddr=String][InvalidRPMSIPAddr=String][AppID=String][ClusterID=String][NodeID=String]: Wrong IP address provided.

Explanation   Wrong/invalid IP address was provided

Recommended Action   Use RTMT to check the Cisco SIP Proxy service trace log file for any detailed error messages

Error Message

%UC_Proxy-3-ESPWrongHostName: %[AppID=String][ClusterID=String][NodeID=String]: Wrong host name.

Explanation   This problem could be due to an invalid IP address, or an unresolvable hostname

Recommended Action   Use RTMT to check the Cisco SIP Proxy service trace log file for any detailed error messages

Error Message

%UC_Proxy-3-ESPPassedParamInvalid: %[MySQL=String][ENUM=String][NumberExpansion=String][RAS=String][AppID=String][ClusterID=String][NodeID=String]: Invalid parameter specified.

Explanation   Invalid parameters were specified. This could be because the parameters were NULL

Recommended Action   Use RTMT to check the Cisco SIP Proxy service trace log file for any detailed error messages

Error Message

%UC_Proxy-3-ESPNAPTRInvalidRecord: %[ENUM=String][AppID=String][ClusterID=String][NodeID=String]: NAPTR record format error.

Explanation   This error may indicate invalid flag fields, missing delimiter, etc

Recommended Action   Use RTMT to check the Cisco SIP Proxy service trace log file for any detailed error messages

Error Message

%UC_Proxy-3-ESPVirtualProxyError: %[AppID=String][ClusterID=String][NodeID=String]: Virtual_Proxy_Domain related error..

Explanation   Virtual_Proxy_Domain related error.

Recommended Action   Use RTMT to check the Cisco SIP Proxy service trace log file for any detailed error messages

Error Message

%UC_Proxy-3-ESPRegistryError: %[InvalidContact=String][ExceedMax=String][RegistryDatabaseError=String][AppID=String][ClusterID=String][NodeID=String]: SIP Registry failure.

Explanation   Unable to add registration to the SIP Registry because a resource limit was exceeded

Recommended Action   Use RTMT to check the Cisco SIP Proxy service trace log file for any detailed error messages

Error Message

%UC_Proxy-3-ESPRoutingError: %[ExceedMax=String][RoutingDatabaseError=String][AppID=String][ClusterID=String][NodeID=String]: SIP route interface error.

Explanation   SIP Route Interface resource limit exceeded error

Recommended Action   Use RTMT to check the Cisco SIP Proxy service trace log file for any detailed error messages

Error Message

%UC_Proxy-3-ESPLoginError: %[LoginDatabaseError=String][AppID=String][ClusterID=String][NodeID=String]: Login datastore error.

Explanation   Failed to connect or an error occurred while communicating with login datastore.

Recommended Action   Use RTMT to check the Cisco SIP Proxy service trace log file for any detailed error messages

Error Message

%UC_Proxy-3-UASCBFindFailed: %[SCBFindFailure=String][AppID=String][ClusterID=String][NodeID=String]: SCB find failure.

Explanation   A call to find_scb() returned NULL which indicates the SCB lookup failed

Recommended Action   Use RTMT to check the Cisco SIP Proxy service trace log file for any detailed error messages

Error Message

%UC_Proxy-3-UASCBGetFailed: %[SCBGetFailure=String][AppID=String][ClusterID=String][NodeID=String]: SCB get or create failure.

Explanation   A call to tcbtable_acquire_tcb() returned NULL which indicates a SCB get/create failure

Recommended Action   Use RTMT to check the Cisco SIP Proxy service trace log file for any detailed error messages

Error Message

%UC_Proxy-6-CTIGWStarted: %[AppID=String][ClusterID=String][NodeID=String]: Cisco CTI Gateway application started.

Explanation   Cisco CTI Gateway application started

Recommended Action   Notification purposes only; no action is required

Error Message

%UC_Proxy-6-CTIGWStopped: %[AppID=String][ClusterID=String][NodeID=String]: Cisco CTI Gateway application stopped.

Explanation   Cisco CTI Gateway application stopped

Recommended Action   Notification purposes only; no action is required

Error Message

%UC_Proxy-4-CTIGWModuleNotEnabled: %[AppID=String][ClusterID=String][NodeID=String]: Cisco CTI Gateway application module is either not configured or enabled.

Explanation   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 CM IM and Presence CTI Gateway Settings page

Error Message

%UC_Proxy-6-CTIGWConnectionRestarted: %[AppID=String][ClusterID=String][NodeID=String]: CTI connection was restarted.

Explanation   The CTI/QBE connection was restarted

Recommended Action   Notification purposes only; no action is required

Error Message

%UC_Proxy-2-CTIGWProviderDown: %[AppID=String][ClusterID=String][NodeID=String]: CTI provider is down.

Explanation   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 CM IM and Presence Service CTI Settings page

Error Message

%UC_Proxy-4-CTIGWUserNotLicenced: %[AppID=String][ClusterID=String][NodeID=String]: User has no license.

Explanation   User failed to authorize due to no license available

Recommended Action   Check the Cisco CTI Gateway application license and user configuration

Error Message

%UC_Proxy-4-CTIGWUserNotAuthorized: %[AppID=String][ClusterID=String][NodeID=String]: User not authorized by CTI Gateway.

Explanation   User failed to authorized due to wrong device or line DN

Recommended Action   Verify user device configuration and MOC settings

Error Message

%UC_Proxy-2-CTIGWProviderFailedToOpen: %[AppID=String][ClusterID=String][NodeID=String]: CTI Provider failed to open.

Explanation   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 CM IM and Settings Service CTI Settings page

Error Message

%UC_Proxy-3-CTIGWQBEFailedRequest: %[AppID=String][ClusterID=String][NodeID=String]: QBE Request failure.

Explanation   The Cisco CTI Gateway application received a failed response to a request

Recommended Action   Use RTMT to check the Cisco SIP Proxy service trace log file for any detailed error messages

Error Message

%UC_Proxy-3-CTIGWSystemError: %[CSTAError=String][InternalError=String][GeneralError=String][AppID=String][ClusterID=String][NodeID=String]: Cisco CTI Gateway application system errors.

Explanation   Cisco CTI Gateway application system errors

Recommended Action   Use RTMT to check the Cisco SIP Proxy service trace log file for any detailed error messages

Error Message

%UC_Proxy-3-PWSSCBFindFailed: %[SCBFindFailure=String][AppID=String][ClusterID=String][NodeID=String]: SCB find failure.

Explanation   A call to find_scb() returned NULL which indicates the SCB lookup failed

Recommended Action   Use RTMT to check the Cisco SIP Proxy service trace log file for any detailed error messages

Error Message

%UC_Proxy-3-PWSSCBInitFailed: %[SCBInitFailure=String][AppID=String][ClusterID=String][NodeID=String]: SCB init failure.

Explanation   SCB init failed

Recommended Action   Restart the Cisco SIP Proxy service

Error Message

%UC_Proxy-5-PWSBelowCPULimit: %[BelowCPULimit=String][AppID=String][ClusterID=String][NodeID=String]: CPU utilization has fallen below the max CPU limit.

Explanation   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

%UC_Proxy-4-PWSAboveCPULimit: %[AboveCPULimit=String][AppID=String][ClusterID=String][NodeID=String]: Indicates the Presence Web Service has exceeded a CPU utilization threshold.

Explanation   The Presence Web Service module running in the Cisco 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 SIP Proxy service logs for more details

Error Message

%UC_Proxy-4-PWSRequestLimitReached: %[RequestLimitReached=String][AppID=String][ClusterID=String][NodeID=String]: Proxy service request per second limit reached.

Explanation   The Cisco SIP Proxy service request per second limit has been reached

Recommended Action   You may need to throttle back the incoming request rate

Error Message

%UC_Proxy-4-PWSAboveSipSubscriptionLimit: %[AboveSipSubscriptionLimit=String][AppID=String][ClusterID=String][NodeID=String]: Indicates the Presence Web Service subscription count has exceeded the maximum limit.

Explanation   The Presence Web Service running in the Cisco 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 SIP Proxy service logs for more details

Error Message

%UC_Proxy-5-PWSBelowSipSubscriptionLimit: %[BelowSipSubscriptionLimit=String][AppID=String][ClusterID=String][NodeID=String]: Subscriptions have fallen below the max limit.

Explanation   The Presence Web Service running in the Cisco 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

%UC_SoapAPI-4-LegacyCUPCLogin: %[userid=String][version=String][AppID=String][ClusterID=String][NodeID=String]: A legacy Cisco Unified Personal Communicator client attempted to login to the Cisco Client Profile Agent service.

Explanation   A legacy Cisco Unified Personal Communicator client attempted to login to the Cisco 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

%UC_SA-2-SyncAgentAXLConnectionFailed: %[AppID=String][ClusterID=String][NodeID=String]: Cisco Sync Agent service failed authentication.

Explanation   Cisco 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

%UC_SA-2-NotInCucmServerListError: %[AppID=String][ClusterID=String][NodeID=String]: Cisco Sync Agent failed to start up because the IM and Presence node is not in the server list, or has been deleted and then readded to the server list on the Cisco Unified Communications Manager publisher..

Explanation   The IM and Presence Server node is not in the server list, or has been deleted and then readded to the server list on the Cisco Unified Communications Manager publisher.

Recommended Action   Please add the IM and Presence node in the server list on the Cisco Unified Communications Manager server and reinstall the IM and Presence node.

Error Message

%UC_SRM-2-SRMFailover: %[FromNode=String][ToNode=String][Reason=String][AppID=String][ClusterID=String][NodeID=String]: Cisco SRM is performing an automatic failover.

Explanation   Cisco SRM is performing an automatic failover

Recommended Action   Please verify that the failed node is up and that critical services are running.

Error Message

%UC_SRM-2-SRMFailed: %[AppID=String][ClusterID=String][NodeID=String]: Cisco Server Recovery Manager is in the failed state.

Explanation   Cisco SRM is in the failed state

Recommended Action   Please restart the Cisco Server Recovery Manager.

Error Message

%UC_Xcp-3-XcpDBConnectError: %[AppID=String][ClusterID=String][NodeID=String]: Cisco XCP data acces layer was unable to connect to the DB..

Explanation   Cisco 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

%UC_Xcp-6-XcpDBConnectRestore: %[AppID=String][ClusterID=String][NodeID=String]: Cisco XCP data access layer was able to restore connection to the DB..

Explanation   Cisco 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

%UC_Xcp-3-XcpComponentConnectError: %[AppID=String][ClusterID=String][NodeID=String]: The XCP component failed to connect to the XCP Router. The component is shutting down. .

Explanation   The concerned XCP component failed to connect to the XCP Router. The component is shutting down after reaching the configured number of reconnect attempts.

Recommended Action   Please check the component log file for more details.

Error Message

%UC_Xcp-3-XcpComponentConfigError: %[AppID=String][ClusterID=String][NodeID=String]: The XCP component detected a bad configuration. .

Explanation   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

%UC_Xcp-3-XcpMdnsStartError: %[AppID=String][ClusterID=String][NodeID=String]: The XCP Router failed to startup the MDNS. .

Explanation   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

%UC_Xcp-3-XcpCmPauseSockets: %[AppID=String][ClusterID=String][NodeID=String]: The XCP Router has directed the XCP Connection Manager (CM) to pause listening on its socket due to load on the system..

Explanation   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

%UC_Xcp-6-XcpCmResumeSockets: %[AppID=String][ClusterID=String][NodeID=String]: Outstanding internal packet or database requests have dropped back below configured threshold..

Explanation   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

%UC_Xcp-3-XcpCmStartupError: %[AppID=String][ClusterID=String][NodeID=String]: The XCP Connection Manager service failed to startup. .

Explanation   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

%UC_Xcp-3-XcpCmHttpdError: %[AppID=String][ClusterID=String][NodeID=String]: The XCP Connection Manager service has errors in the HTTP interface. .

Explanation   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

%UC_Xcp-3-XcpCmXmppdError: %[AppID=String][ClusterID=String][NodeID=String]: The XCP Connection Manager service has errors in the XMPP interface. .

Explanation   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

%UC_Xcp-3-XcpTxtConfGearError: %[AppID=String][ClusterID=String][NodeID=String]: The XCP Text Conference Manager Service failed to load a configured gear. .

Explanation   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

%UC_Xcp-6-XcpTxtConfRoomLimitError: %[AppID=String][ClusterID=String][NodeID=String]: This server has a limit on the maximum number of supported text conference rooms. .

Explanation   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

%UC_Xcp-3-XcpTxtConfDbQueueSizeLimitError: %[AppID=String][ClusterID=String][NodeID=String]: The number of DB requests has reached the maximum limit specified by the configuration..

Explanation   The TC service queues database requests to the external database. If the database server is overloaded or is not accessible, database requests will be queued by the TC service. Once the queue size exceeds the configurable threshold, database requests will be discarded. This may result in persistent room data or messages not being saved to the database.

Recommended Action   Check the state of the external database server and check that it is accessible over the network. Then restart the Cisco XCP Text Conference Manager on CUP.

Error Message

%UC_Xcp-2-XcpSIPGWStackResourceError: %[AppID=String][ClusterID=String][NodeID=String]: The number of concurrent S2S SIP Federation subscriptions or call-legs has reached the maximum limit specified by the configuration..

Explanation   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 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

%UC_Xcp-3-XcpThirdPartyComplianceConnectError: %[complianceserver=String][AppID=String][ClusterID=String][NodeID=String]: Cisco XCP Router is unable to connect to Third Party Compliance Server.

Explanation   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 the IM and Presence Service. 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

%UC_Xcp-6-XcpThirdPartyComplianceConnectRestore: %[complianceserver=String][AppID=String][ClusterID=String][NodeID=String]: Cisco XCP Router is reconnected to Third Party Compliance Server.

Explanation   Cisco XCP Router is reconnected to Third Party Compliance Server. This indicates an initial connection or reconnection

Recommended Action   None.

Error Message

%UC_Xcp-3-XcpMFTExtFsMountErrorStart: %[AppID=String][ClusterID=String][NodeID=String]: Cisco XCP File Transfer Manager has lost its connection to the external file server.

Explanation   Cisco XCP File Transfer Manager has lost its connection to the external file server.

Recommended Action   Please check the External File Server Troubleshooter for more information. Also check that the external file server is running correctly or if there is any problem with the network connectivity to the external file server.

Error Message

%UC_Xcp-5-XcpMFTExtFsMountErrorEnd: %[AppID=String][ClusterID=String][NodeID=String]: Cisco XCP File Transfer Manager was able to re-establish its connection to the external file server.

Explanation   Cisco XCP File Transfer Manager was able to re-establish its connection to the external file server.

Recommended Action   This alarm is for information purposes only; no action is required.

Error Message

%UC_Xcp-3-XcpMFTExtFsFreeSpaceWarnStart: %[AppID=String][ClusterID=String][NodeID=String]: Cisco XCP File Transfer Manager has detected that the available disk space on the external file server is low.

Explanation   Cisco XCP File Transfer Manager has detected that the available disk space on the external file server is low.

Recommended Action   Please free up space on the external file server by deleting unwanted files from the partition used for file transfer.

Error Message

%UC_Xcp-5-XcpMFTExtFsFreeSpaceWarnEnd: %[AppID=String][ClusterID=String][NodeID=String]: CCisco XCP File Transfer Manager has detected that there is sufficient disk space on the external file server.

Explanation   Cisco XCP File Transfer Manager has detected that there is sufficient disk space on the external file server.

Recommended Action   This alarm is for information purposes only; no action is required.

Error Message

%UC_Xcp-3-XcpComponentWriteAlarmYellow: %[component=String][AppID=String][ClusterID=String][NodeID=String]: Cisco XCP Router - Component's MIO Write buffer's nominal capacity exceeded

Explanation   Component's MIO Write buffer's exceeded 50K write buffer

Recommended Action   None

Error Message

%UC_Xcp-3-XcpComponentWriteAlarmOrange: %[component=String][AppID=String][ClusterID=String][NodeID=String]: Cisco XCP Router - Component's MIO Write buffer's warning capacity exceeded

Explanation   Component's MIO Write buffer's exceeded 80K write buffer

Recommended Action   None

Error Message

%UC_Xcp-3-XcpComponentWriteAlarmRed: %[component=String][AppID=String][ClusterID=String][NodeID=String]: Cisco XCP Router - Component's MIO Write buffer's critical capacity exceeded

Explanation   Component's MIO Write buffer's exceeded 100K write buffer

Recommended Action   None

Error Message

%UC_XcpCM-2-XCPConfigMgrJabberRestartRequired: %[AppID=String][ClusterID=String][NodeID=String]: Cisco XCP Config Manager has regenerated XCP XML files after system halt due to buffer size. The XCP Router must now be restarted to pick up changes..

Explanation   Cisco XCP Config Manager has regenerated XCP XML files after system halt due to buffer size. The XCP Router must now be restarted to pick up changes .

Recommended Action   Restart the XCP Router.

Error Message

%UC_XcpCM-2-XCPConfigMgrConfigurationFailure: %[realm=String][component=String][AppID=String][ClusterID=String][NodeID=String]: Cisco XCP Config Manager was unable to send configuration to a component. Please check logs..

Explanation   Cisco XCP Config Manager failed to successfully update XCP Configuration.

Recommended Action   See Cisco XCP Config Manager logs for further root cause.

Error Message

%UC_XcpCM-2-XCPConfigMgrHostNameResolutionFailed: %[hostname=String][AppID=String][ClusterID=String][NodeID=String]: XCP Config manager hostname resolution failed.

Explanation   Cisco 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

%UC_XcpCM-2-XCPConfigMgrR2RPasswordEncryptionFailed: %[hostname=String][AppID=String][ClusterID=String][NodeID=String]: XCP Config Manager Password Encryption Failed.

Explanation   Cisco XCP Config Manager was unable to encrypt the password associated with an Inter-cluster Router-to-Router configuration.

Recommended Action   Restart XCP Config Manager and then restart the XCP Router

Error Message

%UC_XcpCM-2-XCPConfigMgrR2RRequestTimedOut: %[hostname=String][AppID=String][ClusterID=String][NodeID=String]: XCP Config Manager R2R Configuration Request Timed Out.

Explanation   Cisco XCP Config Manager sent an R2R configuration request to the XCP Router, but the XCP Router did not acknowledge the request in the time allowed.

Recommended Action   Restart XCP Config Manager and then restart the XCP Router

Error Message

%UC_XcpCM-2-XCPExternalDatabaseCertificateNotFound: %[AppID=String][ClusterID=String][NodeID=String]: Cisco XCP Config Manager was unable to find one or more external Database certificates from cup-xmpp-trust store

Explanation   An attempt to establish an SSL connection between the Cisco Unified IM and Presence Service node and the configured External Database has failed because the required certificate is missing.This may have occurred as a result of the Cisco Inter Cluster Sync Agent (ICSA) service not having propagated the certificate to all nodes yet or the required certificate has been deleted.

Recommended Action   Please ensure that the required certificate is uploaded to the cup-xmpp-trust store. If the certificate is already present, please ensure that the Cisco ICSA service is running on all the IM and Presence service nodes. Restart the Cisco ICSA service on all the nodes or wait for 15 minutes to ensure that the Cisco ICSA service propagates the certificate to all the IM and Presence service nodes. As an additional step, please navigate to the External Database configuration page for the particular database and take corrective measures if there are any error messages displayed on the page. Finally, restart the Cisco XCP Config Manager Service.

Error Message

%UC_XcpCM-2-PushNotificationFailed: %[Type=String][TrackingID=String][SourceUserJID=String][DestinationUserJID=String][ErrorCode=String][ErrorDescription=String][component=String][AppID=String][ClusterID=String][NodeID=String]: Cisco XCP Config Manager was not able to send Push Notification.

Explanation   An attempt to send a message packet to PushUri failed, Push Notification not sent

Recommended Action   Take action as appropriate based on the Error Code and Error Description. If further assistance is required, please contact Cisco Technical Support.

Error Message

%UC_XcpCM-2-PushNotificationFailedInvalidDeviceToken: %[Type=String][TrackingID=String][SourceUserJID=String][DestinationUserJID=String][ErrorCode=String][ErrorDescription=String][component=String][AppID=String][ClusterID=String][NodeID=String]: Cisco XCP Config Manager was not able to send Push Notification.

Explanation   An attempt to send a Push Notification to Cisco Cloud(Push Microservice) failed due to an invalid device token.

Recommended Action   Have the impacted user attempt to logout and log back in to Jabber. If this does not resolve the issue, please contact Cisco Technical Support.

Error Message

%UC_XcpCM-2-PushNotificationFailedInvalidAccessToken: %[Type=String][TrackingID=String][SourceUserJID=String][DestinationUserJID=String][ErrorCode=String][ErrorDescription=String][component=String][AppID=String][ClusterID=String][NodeID=String]: Cisco XCP Config Manager was not able to send Push Notification.

Explanation   An attempt to send a Push Notification to Cisco Cloud(Push Microservice) failed due to an invalid access token.

Recommended Action   Inspect the IMnPresence XCP Config Manager service logs to ensure the AccessToken was fetched and refreshed in a timely manner. If this was done in a timely manner, then the issue may be on the Cisco Cloud side. In that case, please contact Cisco Technical Support for further debugging.

Error Message

%UC_XcpCM-2-AccessTokenFetchFailed: %[Type=String][ErrorCode=String][ErrorDescription=String][component=String][AppID=String][ClusterID=String][NodeID=String]: Cisco XCP Config Manager was unable to fetch the Access Token

Explanation   Cisco XCP Config Manager was unable to fetch the access token

Recommended Action   Take action as appropriate based on the Error Code and Error Description. If further assistance is required, please contact Cisco Technical Support.

Error Message

%UC_XcpCM-2-InvalidPushPacket: %[Type=String][ErrorDescription=String][component=String][AppID=String][ClusterID=String][NodeID=String]: Cisco XCP Config Manager was not able to send Push Notification.

Explanation   An attempt to send a Push Notification to Cisco Cloud(Push Microservice) failed due to an Invalid Push Packet.

Recommended Action   Take action as appropriate based on the Error Description. Further analysis may require investigation including the Client and server-side XCP Router service. If further assistance is required, please contact Cisco Technical Support.

Error Message

%UC_XcpCM-2-PushXMPPClientPoolError: %[Type=String][ErrorDescription=String][component=String][AppID=String][ClusterID=String][NodeID=String]: Cisco XCP Config Manager was not able to send Push Notification.

Explanation   Encountered an issue while establishing HTTP client pool connection from Config Manager to Cisco Cloud.

Recommended Action   [Note: the following recovery techniques will impact multiple clients; please plan accordingly as to when these activities are performed] Within the Unified CM configuration, set Push to 'Disable', then back to 'Enable.' If this is unsuccessful, restart the Cisco XCP Config Manager service. For further assistance please contact Cisco Technical Support.

Error Message

%UC_XcpCA-3-XCAPollingThreadExited: %[Reason=String][AppID=String][ClusterID=String][NodeID=String]: Cisco XCP Counter Aggregator service has its polling thread exited..

Explanation   Cisco XCP Counter Aggregator service has its polling thread exited.

Recommended Action   Check log file for any errors. Try restarting the Cisco XCP Counter Aggregator service.

Error Message

%UC_SAMLSSO-6-SAMLSSOEnableSuccess: %[AppID=String][ClusterID=String][NodeID=String]: SAML SSO enable operation successful.

Explanation   This alarm indicates that operation to enable SAML SSO was successful.

Recommended Action   Informational alarm. No action required.

Error Message

%UC_SAMLSSO-3-SAMLSSOEnableFailure: %[ErrorDetails=String][AppID=String][ClusterID=String][NodeID=String]: SAML SSO enable operation failed.

Explanation   This alarm indicates that operation to enable SAML SSO has failed.

Recommended Action   In the Cisco Unified Reporting tool, run a CM Cluster Overview report and check the SAML SSO status on other nodes in the cluster to determine if operation has failed on other nodes as well. Verify that there is connectivity between the node from where the enable operation is initiated and the node(s) where the operation failed. Use RTMT to collect traces for Cisco SSO and contact Cisco TAC for assistance. Alternately, use CLI to collect traces by running the commands 'file get activelog tomcat/logs/ssosp/log4j/*.log' and 'file get activelog platform/log/ssoApp*.log'.

Error Message

%UC_SAMLSSO-6-SAMLSSODisableSuccess: %[AppID=String][ClusterID=String][NodeID=String]: SAML SSO disable operation successful.

Explanation   This alarm indicates that operation to disable SAML SSO was successful.

Recommended Action   Informational alarm. No action required.

Error Message

%UC_SAMLSSO-3-SAMLSSODisableFailure: %[ErrorDetails=String][AppID=String][ClusterID=String][NodeID=String]: SAML SSO disable operation failed.

Explanation   This alarm indicates that operation to disable SAML SSO has failed.

Recommended Action   In the Cisco Unified Reporting tool, run a CM Cluster Overview report and check the SAML SSO status on other nodes in the cluster to determine if operation has failed on other nodes as well. Verify that there is no connectivity issues between the node from where the disable operation is initiated and the node(s) where the operation failed. If the disable operation was performed from the web pages, the same can be tried from the CLI (of the node where the disable failed) using command "utils sso disable". If the disable still fails, use RTMT to collect traces for Cisco SSO and contact Cisco TAC for assistance. Alternately, use CLI to collect traces by running the commands 'file get activelog tomcat/logs/ssosp/log4j/*.log' and 'file get activelog platform/log/ssoApp*.log'.

Error Message

%UC_LPMTCT-4-LogPartitionLowWaterMarkExceeded: %[UsedDiskSpace=String][{Optional}MessageString=String][AppID=String][ClusterID=String][NodeID=String]: The percentage of used disk space in the log partition has exceeded the configured low water mark..

Explanation   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

%UC_LPMTCT-2-LogPartitionHighWaterMarkExceeded: %[UsedDiskSpace=String][{Optional}MessageString=String][AppID=String][ClusterID=String][NodeID=String]: The percentage of used disk space in the log partition has exceeded the configured high water mark..

Explanation   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

%UC_LPMTCT-6-LogFileSearchStringFound: %[SearchString=String][AppID=String][ClusterID=String][NodeID=String]: The search string has been found in the log file..

Explanation   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

%UC_LPMTCT-4-LogCollectionJobLimitExceeded: %[JobType=String][AppID=String][ClusterID=String][NodeID=String]: The number of Log Collection Jobs have excceded the allowed limit.

Explanation   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

%UC_LPMTCT-3-ScheduledCollectionError: %[JobID=String][Reason=String][AppID=String][ClusterID=String][NodeID=String]: An error occurred while executing scheduled collection..

Explanation   Scheduled collection encountered an error during execution.

Recommended Action   Review configuration for scheduled collection job under Job Status window.

Error Message

%UC_LPMTCT-2-CoreDumpFileFound: %[TotalCoresFound=String][CoreDetails=String][Core1=String][Core2=String][Core3=String][Core4=String][Core5=String][Core6=String][AppID=String][ClusterID=String][NodeID=String]: The new core dump file(s) have been found in the system..

Explanation   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

%UC_LPMTCT-3-SparePartitionLowWaterMarkExceeded: %[UsedDiskSpace=String][{Optional}MessageString=String][AppID=String][ClusterID=String][NodeID=String]: The percentage of used disk space in the spare partition has exceeded the configured low water mark..

Explanation   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

%UC_LPMTCT-4-SparePartitionHighWaterMarkExceeded: %[UsedDiskSpace=String][{Optional}MessageString=String][AppID=String][ClusterID=String][NodeID=String]: The percentage of used disk space in the spare partition has exceeded the configured high water mark..

Explanation   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

%UC_LPMTCT-4-AuditLogOverflowDueToLPMPurge: %[AppID=String][ClusterID=String][NodeID=String]: Indicates that application audit log files have been deleted by Log Partition Monitor(LPM).

Explanation   This alarm indicates an overflow occurred due to purge by LPM clean up logic. When the total disk space usage of log partition crosses the high water mark configured, the LPM tool's clean up logic deletes the oldest files from the log partition so that the new logs can be written.

Recommended Action    Login to " Cisco Unified Serviceability - > Tools - > Audit Log Configuration " page and check if the purging is enabled. You can choose not to delete the audit log files by LPM by disabling the " Enable Purging " option.

Error Message

%UC_CALLMANAGER-2-CallManagerFailure: %[{Optional}Text=String][HostName=String][IPAddress=String][Reason=Enum][AppID=String][ClusterID=String][NodeID=String]: Indicates an internal failure in Unified CM.

Explanation   This alarm indicates that an internal failure occurred in the Cisco CallManager service. The service should restart in an attempt to clear the failure.

Recommended Action   Monitor for other alarms and restart Cisco CallManager service, if necessary. Collect the core file if available, SDL and CCM/SDI trace files (you can gather these from Trace and Log Central in RTMT using the Collect Files feature) and contact the Cisco Technical Assistance Center (TAC).

Reason Code - Enum Definitions

Enum Definitions - Reason

%UC_CALLMANAGER-5-SDLLinkISV: %[RemoteIPAddress=String][LinkID=String][LocalNodeId=UInt][LocalApplicationId=Enum][RemoteNodeID=UInt][RemoteApplicationId=Enum][AppID=String][ClusterID=String][NodeID=String]: SDL link to remote application restored.

Explanation   This alarm indicates that the local Unified CM has gained communication with the remote Unified CM. Note that the remote Unified CM should also indicate SDLLinkISV with a different LinkID.

Recommended Action   Informational only; no action is required

Reason Code - Enum Definitions

Enum Definitions - LocalApplicationId

Enum Definitions - RemoteApplicationId

%UC_CALLMANAGER-1-SDLLinkOOS: %[RemoteIPAddress=String][LinkID=String][LocalNodeId=UInt][LocalApplicationID=Enum][RemoteNodeID=UInt][RemoteApplicationID=Enum][AppID=String][ClusterID=String][NodeID=String]: SDL link to remote application is out of service.

Explanation   This alarm indicates that the local Unified CM has lost communication with the remote Unified CM. This alarm usually indicates that a node has gone out of service (whether intentionally for maintenance or to install a new load for example; or unintentionally due to a service failure or connectivity failure).

Recommended Action   In the Cisco Unified Reporting tool, run a CM Cluster Overview report and check to see if all servers can communicate with the Publisher. Also check for any alarms that might have indicated a CallManager failure and take appropriate action for the indicated failure. If the node was taken out of service intentionally, bring the node back into service.

Reason Code - Enum Definitions

Enum Definitions - LocalApplicationID

Enum Definitions - RemoteApplicationID

%UC_CALLMANAGER-1-CMVersionMismatch: %[RemoteAppProtocolVersion=String][LocalAppProtocolVersion=String][RemoteNodeId=UInt][RemoteAppId=Enum][RemoteAppVersion=String][AppID=String][ClusterID=String][NodeID=String]: One or more Unified CM nodes in a cluster are running different Unified CM versions.

Explanation   This alarm indicates that the local Unified CM is unable to establish communication with the remote Unified CM due to a software version mismatch. This is generally a normal occurrence when you are upgrading a Unified CM node.

Recommended Action   The alarm details include the versions of the local and remote Unified CM nodes. Compare the versions and upgrade a node if necessary.

Reason Code - Enum Definitions

Enum Definitions - RemoteAppId

%UC_CALLMANAGER-2-BChannelOOS: %[ChannelKey=String][DeviceName=String][Reason=Enum][ChannelId=UInt][AppID=String][ClusterID=String][NodeID=String]: The B-channel is out of service.

Explanation   The B-channel indicated by this alarm has gone out of service. Some of the more common reasons for a B-channel to go out of service include: Taking the channel out of service intentionally to perform maintenance on either the near-end or far-end; Losing T1/E1/BRI cable connectivity; When the MGCP gateway returns an error code 501 or 510 for a MGCP command sent from Unified CM; When the MGCP gateway doesn't respond to an MGCP command sent by Unified CM three times; When a speed and duplex mismatch exists on the Ethernet port between Unified CM and the MGCP gateway.

Recommended Action   Check the Cisco CallManager advanced service parameter, Change B-channel Maintenance Status to determine if the B-channel has been taken out of service intentionally; Check the Q.931 trace for PRI SERVICE message to determine whether a PSTN provider has taken the B-channel out of service; Check the connection of the T1/E1/BRI cable; Reset the MGCP gateway; Check the speed and duplex settings on the Ethernet port.

Reason Code - Enum Definitions

Enum Definitions - Reason

%UC_CALLMANAGER-5-BChannelISV: %[ChannelId=UInt][ChannelKey=String][DeviceName=String][AppID=String][ClusterID=String][NodeID=String]: B-channel is in service.

Explanation   The B-channel indicated by this alarm has gone in service

Recommended Action   Informational purposes only; no action is required

Error Message

%UC_CALLMANAGER-2-DChannelOOS: %[ChannelId=UInt][ChannelKey=String][DeviceName=String][IPAddress=String][Reason=Enum][AppID=String][ClusterID=String][NodeID=String]: The D-channel is out of service.

Explanation   The D-channel indicated by this alarm has gone out of service. Common reasons for a D-channel to go out of service include losing T1/E1/BRI cable connectivity; losing the gateway data link (Layer 2) due to an internal or external problem; or a gateway reset.

Recommended Action   Check the connection of the T1/E1/BRI cable; reset the gateway to restore Layer 2 connectivity; investigate whether the gateway reset was intentional. If the reset was not intentional, take steps to restrict access to the Gateway Configuration window in Cisco Unified CM Administration and the gateway terminal.

Reason Code - Enum Definitions

Enum Definitions - Reason

%UC_CALLMANAGER-5-DChannelISV: %[ChannelId=UInt][ChannelKey=String][DeviceName=String][IPAddress=String][AppID=String][ClusterID=String][NodeID=String]: D-channel is in service.

Explanation   The indicated D-channel has gone in service

Recommended Action   Notification purposes only; no action is required

Error Message

%UC_CALLMANAGER-4-DeviceTransientConnection: %[{Optional}IPAddress=String][{Optional}DeviceName=String][{Optional}MACAddress=String][Protocol=String][{Optional}DeviceType=Enum][{Optional}Reason=Enum][ConnectingPort=UInt][{Optional}SIPUser=String][{Optional}IPV6Address=String][{Optional}IPAddrAttributes=Enum][{Optional}IPV6AddrAttributes=Enum][AppID=String][ClusterID=String][NodeID=String]: A device attempted to register but did not complete registration.

Explanation   A connection was established and immediately dropped before completing registration. Incomplete registration may indicate that a device is rehoming in the middle of registration. The alarm could also indicate a device misconfiguration, database error, or an illegal/unknown device trying to attempt a connection. Network connectivity problems can affect device registration, or the restoration of a primary Unified CM may interrupt registration.

Recommended Action   In the Cisco Unified Reporting tool, check the Active Services section of the Unified CM Cluster Overview report to confirm that any failover/fallback scenarios have completed. Confirm that auto-registration is enabled if the phone attempting to connect is set to auto-register, or locate the phone that is attempting to auto-register if auto-registration has been intentionally disabled. Check the device indicated in this alarm and confirm that the device registration details in Cisco Unified CM Administration are accurate. Also, refer to the reason code definitions in the alarm for recommended actions. No action is required if this event was issued as a result of a normal device rehome.

Reason Code - Enum Definitions

Enum Definitions - DeviceType

Enum Definitions - Reason

Enum Definitions - IPAddrAttributes

Enum Definitions - IPV6AddrAttributes

%UC_CALLMANAGER-3-EndPointTransientConnection: %[IPAddress=String][DeviceName=String][MACAddress=String][Protocol=String][DeviceType=Enum][Reason=Enum][ConnectingPort=UInt][SIPUser=String][IPV6Address=String][IPAddrAttributes=Enum][IPV6AddrAttributes=Enum][LastSignalReceived=String][StationState=String][AppID=String][ClusterID=String][NodeID=String]: An endpoint attempted to register but did not complete registration.

Explanation   A connection was established and immediately dropped before completing registration. Incomplete registration may indicate that a device is rehoming in the middle of registration. The alarm could also indicate a device misconfiguration, database error, or an illegal/unknown device trying to attempt a connection. Network connectivity problems can affect device registration, or the restoration of a primary Unified CM may interrupt registration.

Recommended Action   Investigate any network connectivity problems in the system. It's possible that you have reached the maximum number of devices; the Cisco CallManager service parameter, Maximum Number of Registered Devices, controls the number of devices allowed in the system. After taking licensing, system hardware and other related concerns into consideration, you could increase the value of the service parameter. Also, refer to the reason code definitions in the alarm for additional recommended actions. No action is required if this event was issued as a result of a normal device rehome.

Reason Code - Enum Definitions

Enum Definitions - DeviceType

Enum Definitions - Reason

Enum Definitions - IPAddrAttributes

Enum Definitions - IPV6AddrAttributes