The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
Unified RTMT displays both preconfigured alerts and custom alerts in Alert Central. Unified RTMT organizes the alerts under the applicable tabs: System, Voice/Video, IM and Presence Service, Cisco Unity Connection, and Custom.
You can enable or disable preconfigured and custom alerts in Alert Central; however, you cannot delete preconfigured alerts.
The following list comprises the preconfigured system alerts:
AuthenticationFailed
CiscoDRFFailure
CoreDumpFileFound
CpuPegging
CriticalServiceDown
DBChangeNotifyFailure
DBReplicationFailure
DBReplicationTableOutofSync
HardwareFailure
LogFileSearchStringFound
LogPartitionHighWaterMarkExceeded
LogPartitionLowWaterMarkExceeded
LowActivePartitionAvailableDiskSpace
LowAvailableVirtualMemory
LowInactivePartitionAvailableDiskSpace
LowSwapPartitionAvailableDiskSpace
ServerDown (Applies to Unified Communications Manager clusters)
SparePartitionHighWaterMarkExceeded
SparePartitionLowWaterMarkExceeded
SyslogSeverityMatchFound
SyslogStringMatchFound
SystemVersionMismatched
TotalProcessesAndThreadsExceededThreshold
Some preconfigured alerts allow you to initiate a trace download based on the occurrence of an event. You can automatically capture traces when a particular event occurs by checking the Enable Trace Download check box in Set Alert/Properties for the following alerts:
CriticalServiceDown: CriticalServiceDown alert is generated when any service is down. CriticalServiceDown alert monitors only those services that are listed in RTMT Critical Services.
Note | The Unified RTMT backend service checks status (by default) every 30 seconds. If service goes down and comes back up within that period, CriticalServiceDown alert may not be generated. |
CodeYellow: This alarm indicates that Cisco Unified Communications Manager initiated call throttling due to unacceptably high delay in handling calls.
CoreDumpFileFound: CoreDumpFileFound alert is generated when the Unified RTMT backend service detects a new Core Dump file.
Note | You can configure both CriticalServiceDown and CoreDumpFileFound alerts to download corresponding trace files for troubleshooting purposes. This setup helps preserve trace files at the time of crash. |
Caution | Trace Download may affect services on the node. A high number of downloads adversely impacts the quality of services on the node. |
The following list comprises the preconfigured Voice and Video alerts:
BeginThrottlingCallListBLFSubscriptions
CallAttemptBlockedByPolicy
CallProcessingNodeCpuPegging
CARIDSEngineCritical
CARIDSEngineFailure
CARSchedulerJobFailed
CDRAgentSendFileFailed
CDRFileDeliveryFailed
CDRHighWaterMarkExceeded
CDRMaximumDiskSpaceExceeded
CiscoElmNotConnected
CiscoGraceTimeLeft
CiscoNoProvisionTimeout
CiscoSystemInDemo
CiscoSystemInOverage
CiscoSystemSecurityMismatch
CodeYellow
DDRBlockPrevention
DDRDown
EMCCFailedInLocalCluster
EMCCFailedInRemoteCluster
ExcessiveVoiceQualityReports
ILSHubClusterUnreachable
ILSPwdAuthenticationFailed
ILSTLSAuthenticationFailed
IMEDistributedCacheInactive
IMEOverQuota
IMEQualityAlert
IMEServiceStatus
InsufficientFallbackIdentifiers
InvalidCredentials
LocationOutOfResource
MaliciousCallTrace
MediaListExhausted
MgcpDChannelOutOfService
NumberOfRegisteredDevicesExceeded
NumberOfRegisteredGatewaysDecreased
NumberOfRegisteredGatewaysIncreased
NumberOfRegisteredMediaDevicesDecreased
NumberOfRegisteredMediaDevicesIncreased
NumberOfRegisteredPhonesDropped
RecordingCallSetupFail
RecordingGatewayRegistrationRejected
RecordingGatewayRegistrationTimeout
RecordingGatewaySessionFailed
RecordingResourcesNotAvailable
RecordingSessionTerminatedUnexpectedly
RouteListExhausted
RTMTSessionExceedsThreshold
SDLLinkOutOfService
TCPSetupToIMEFailed
TLSConnectionToIMEFailed
UserInputFailure
The following list comprises the preconfigured IM and Presence Service alerts:
CTIGWModuleNotEnabled
CTIGWProviderDown
CTIGWUserNotLicenced
CTIGWUserNotAuthorized
CTIGWProviderFailedToOpen
CTIGWQBEFailedRequest
CTIGWSystemError
EspConfigAgentMemAllocError
EspConfigAgentFileWriteError
EspConfigAgentNetworkOutage
EspConfigAgentNetworkRestored
EspConfigAgentHighMemoryUtilization
EspConfigAgentHighCPUUtilization
EspConfigAgentLocalDBAccessError
EspConfigAgentProxyDomainNotConfigured
EspConfigAgentRemoteDBAccessError
EspConfigAgentSharedMemoryStaticRouteError
ESPConfigError
ESPConfigNotFound
ESPCreateLockFailed
ESPLoginError
ESPMallocFailure
ESPNAPTRInvalidRecord
ESPPassedParamInvalid
ESPRegistryError
ESPRoutingError
ESPSharedMemCreateFailed
ESPSharedMemSetPermFailed
ESPSharedMemAllocFailed
ESPSocketError
ESPStopped
ESPStatsLogFileOpenFailed
ESPVirtualProxyError
ESPWrongIPAddress
ESPWrongHostName
ICSACertificateCASignedTrustCertFound
ICSACertificateFingerPrintMisMatch
ICSACertificateValidationFailure
InterclusterSyncAgentPeerDuplicate
LegacyCUPCLogin
NotInCucmServerListError
PEAutoRecoveryFailed
PEDatabaseError
PEIDSQueryError
PEIDSSubscribeError
PEIDStoIMDBDatabaseSyncError
PELoadHighWaterMark
PEMemoryHighCondition
PEPeerNodeFailure
PESipSocketBindFailure
PEStateDisabled
PEStateLocked
PEWebDAVInitializationFailure
PWSSCBFindFailed
PWSSCBInitFailed
PWSAboveCPULimit
PWSAboveSipSubscriptionLimit
PWSRequestLimitReached
SRMFailed
SRMFailover
SyncAgentAXLConnectionFailed
UASCBFindFailed
UASCBGetFailed
XcpCmComponentConnectError
XcpCmPauseSockets
XcpCmStartupError
XcpCmXmppdError
XcpConfigMgrConfigurationFailure
XcpConfigMgrHostNameResolutionFailed
XcpConfigMgrJabberRestartRequired
XcpConfigMgrR2RPasswordEncryptionFailed
XcpConfigMgrR2RRequestTimedOut
XcpDBConnectError
XcpMdnsStartError
XcpSIPFedCmComponentConnectError
XcpSIPFedCmStartupError
XcpSIPGWStackResourceError
XcpThirdPartyComplianceConnectError
XcpTxtConfComponentConfigError
XcpTxtConfDBConnectError
XcpTxtConfDBQueueSizeLimitError
XcpTxtConfGearError
XcpWebCmComponentConnectError
XcpWebCmHttpdError
XcpWebCmStartupError
XcpXMPPFedCmComponentConnectError
XcpXMPPFedCmStartupError
The following list comprises the preconfigured Cisco Unity Connection alerts.
NoConnectionToPeer
AutoFailoverSucceeded
AutoFailoverFailed
AutoFailbackSucceeded
AutoFailbackFailed
SbrFailed (Split Brain Resolution Failed)
DiskConsumptionCloseToCapacityThreshold
DiskConsumptionExceedsCapacityThreshold
LicenseExpirationWarning
LicenseExpired
Note | The first six alerts apply only to Cisco Unity Connection cluster configurations. |
In RTMT, you can configure alert actions for every alert that is generated and have the alert action sent to e-mail recipients that you specify in the alert action list.
The following table provides a list of fields that you will use to configure alert actions. Users can configure all fields, unless otherwise marked.
List of e-mail addresses. You can selectively enable or disable an individual e-mail in the list. |
By using the following procedure, you can perform tasks, such as access Alert Central, sort alert information, enable, disable, or remove an alert, clear an alert, or view alert details.
Using the alert notification feature, the application notifies you of system problems. The following configuration setup is required to activate alert notifications for a system performance counter.
From the RTMT Perfmon Monitoring pane, you select the system perfmon counter and perform the following actions:
Tip | To remove the alert for the counter, right-click the counter and choose Remove Alert. The option appears dim after you remove the alert. |
You may want to temporarily suspend some or all alerts; you can suspend alerts on a particular node or on an entire cluster. For example, if you are upgrading your system to a newer release, suspend alerts until the upgrade completes, so that you do not receive e-mails and e-pages during the upgrade.
Follow this procedure to suspend alerts in Alert Central.
Step 1 | Choose .
| ||
Step 2 | Perform one of the following actions: | ||
Step 3 | Click OK.
|
Core dumps can be difficult to reproduce so it is particularly important to collect the log files associated with them when they occur and before they are over written.
Set up an e-mail alert for core dumps, so that you are immediately notified when one occurs to assist in troubleshooting its cause.
Follow this procedure to collect logs after you receive an e-mail alert.
Step 1 | Note which services initiated the alert, which are indicated by "Core" in the e-mail message. |
Step 2 | Select
and select the relevant logs for all impacted services.
For example, if the service is Cisco Presence Engine, collect the Cisco Presence Engine, Cisco XCP router and Cisco XCP Connection Manager logs. Or, if the service is Cisco XCP Router, collect the Cisco XCP Router, and Cisco XCP Connection Manager and Cisco Presence Engine logs. |
Step 3 | Generate the stack trace by running the following commands from
the CLI:
utils core active list utils core active analyze core filename |
Step 4 | Select RIS Data Collector PerfMon Log. and select the |
Step 5 | Select to collect the system logs. |
Step 6 | Attach the collected files to your Cisco technical support case. |