Cisco Unified Communications Manager
Managed Services Guide, Release 8.0(1)
Americas Headquarters
Cisco Systems, Inc.
170 West Tasman Drive
San Jose, CA 95134-1706
USA
http://www.cisco.com
Tel: 408 526-4000
800 553-NETS (6387)
Fax: 408 527-0883
Text Part Number: OL-20105-01
THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL
STATEMENTS, INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT
WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS.
THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE INFORMATION PACKET THAT
SHIPPED WITH THE PRODUCT AND ARE INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE
OR LIMITED WARRANTY, CONTACT YOUR CISCO REPRESENTATIVE FOR A COPY.
The Cisco implementation of TCP header compression is an adaptation of a program developed by the University of California, Berkeley (UCB) as part of UCB’s public
domain version of the UNIX operating system. All rights reserved. Copyright © 1981, Regents of the University of California.
NOTWITHSTANDING ANY OTHER WARRANTY HEREIN, ALL DOCUMENT FILES AND SOFTWARE OF THESE SUPPLIERS ARE PROVIDED “AS IS” WITH
ALL FAULTS. CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT
LIMITATION, THOSE OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OR ARISING FROM A COURSE OF
DEALING, USAGE, OR TRADE PRACTICE.
IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING,
WITHOUT LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO
OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
CCDE, CCENT, CCSI, Cisco Eos, Cisco Explorer, Cisco HealthPresence, Cisco IronPort, the Cisco logo, Cisco Nurse Connect, Cisco Pulse, Cisco SensorBase,
Cisco StackPower, Cisco StadiumVision, Cisco TelePresence, Cisco TrustSec, Cisco Unified Computing System, Cisco WebEx, DCE, Flip Channels, Flip for Good, Flip
Mino, Flipshare (Design), Flip Ultra, Flip Video, Flip Video (Design), Instant Broadband, and Welcome to the Human Network are trademarks; Changing the Way We Work,
Live, Play, and Learn, Cisco Capital, Cisco Capital (Design), Cisco:Financed (Stylized), Cisco Store, Flip Gift Card, and One Million Acts of Green are service marks; and
Access Registrar, Aironet, AllTouch, AsyncOS, Bringing the Meeting To You, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, CCSP, CCVP, Cisco, the
Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Lumin, Cisco Nexus, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity,
Collaboration Without Limitation, Continuum, EtherFast, EtherSwitch, Event Center, Explorer, Follow Me Browsing, GainMaker, iLYNX, IOS, iPhone, IronPort, the
IronPort logo, Laser Link, LightStream, Linksys, MeetingPlace, MeetingPlace Chime Sound, MGX, Networkers, Networking Academy, PCNow, PIX, PowerKEY,
PowerPanels, PowerTV, PowerTV (Design), PowerVu, Prisma, ProConnect, ROSA, SenderBase, SMARTnet, Spectrum Expert, StackWise, WebEx, and the WebEx logo are
registered trademarks of Cisco and/or its affiliates in the United States and certain other countries.
All other trademarks mentioned in this document or website are the property of their respective owners. The use of the word partner does not imply a partnership relationship
between Cisco and any other company. (1002R)
Any Internet Protocol (IP) addresses used in this document are not intended to be actual addresses. Any examples, command display output, and figures included in the
document are shown for illustrative purposes only. Any use of actual IP addresses in illustrative content is unintentional and coincidental.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
© 2010 Cisco Systems, Inc. All rights reserved.
CONTENTS
Preface
xxv
Purpose
xxv
Audience
xxv
Organization
xxvi
Related Documentation
Conventions
xxvi
xxvii
Obtaining Documentation and Submitting a Service Request
Cisco Product Security Overview
CHAPTER
1
Overview
xxviii
xxviii
1-1
Cisco Unified Communications Manager
Supported Deployment Models
Managed Services
1-1
1-2
1-3
Cisco Unified Serviceability 1-4
Trace Tools 1-4
Troubleshooting Trace 1-5
Trace Collection 1-5
Cisco Unified Reporting
1-5
Cisco Unified Real-Time Monitoring Tool
1-6
Call Detail Records and Call Management Records
Call Detail Record Analysis and Reporting
Management Information Base
CHAPTER
2
New and Changed Information
1-7
1-7
1-8
2-1
Cisco Unified Communications Manager, Release 8.0(1)
Cisco Unified Serviceability 2-1
Alarm Additions and Changes 2-2
Obsolete Alarms 2-17
Cisco Unified Real-Time Monitoring Tool 2-22
Cisco Unified CDR Analysis and Reporting 2-25
New Cisco CAR DB Alarms 2-25
New CAR Object and Counters 2-26
Hunt/CTI Integration for CAR Reporting 2-26
2-1
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
i
Contents
CAR and CDRM Alarm Interface 2-27
System-Wide Call Tracking End-to-End Call Trace 2-27
Cisco Unified Call Detail Records 2-27
End-to-End Call Trace 2-27
Remote Destination to Number Mapping and CDRs 2-28
New CDR Fields to Support Call Control Discovery 2-28
New CDR Fields to Support External Call Control 2-28
New CDR Support for iSAC Codec 2-29
New CDR Fields for Hunt List Support 2-30
Cisco Unified Reporting 2-30
MIB Updates
CHAPTER
3
2-30
Managing and Monitoring the Health of Cisco Unified Communications Manager Systems
Overview of Supported Interfaces
Critical Processes to Monitor
Available Supported MIBs
3-1
3-1
3-2
3-11
RTMT Monitoring of Cisco Unified CM System Health 3-12
RTMT Summary View 3-12
CPU Usage 3-13
% IOwait Monitoring 3-15
Virtual Memory 3-15
Disk Usage 3-17
Disk Name Mapping 3-18
Database Replication and Cisco Unified Communication Manager Nodes
ccm Process and CPU Usage 3-20
CodeYellow 3-21
RIS Data Collector PerfMonLog 3-23
Critical Service Status 3-24
Syslog Messages 3-25
RTMT Alerts as Syslog Messages and Traps 3-26
Recovery, Hardware Migration, and Backup/Restore
Backup/Restore 3-26
3-20
3-26
Platform Monitoring 3-27
Using SNMP MIBs 3-27
MIBs and MCS Types 3-28
Using Command Line Interface 3-28
Hardware Migration 3-32
Platform Security 3-32
Locked-down System 3-32
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
ii
OL-20105-01
Contents
Cisco Security Agent Support 3-33
Security Patching and Updating 3-33
Role-Based Access Control 3-33
Software Configuration Management 3-33
General Install/Upgrade Procedures 3-33
Detecting Installed Release and Packages 3-34
Available Reports 3-34
RTMT Reports 3-34
Serviceability Reports 3-34
Cisco Unified Reporting 3-35
General Health and Troubleshooting Tips 3-36
Using of Onboard Agents 3-36
Call Detail Records and Call Maintenance Records 3-36
Perfmon Counters 3-37
Integration with Uninterruptible Power Supplies (UPS) 3-37
Native Hardware Out of Band Management (OOB) 3-37
Phone Registration Status 3-38
Historical Information Download 3-38
Cisco CallManager Service Stops Responding 3-38
Database Replication Fails Between the Publisher and the Subscriber
Database Replication Does Not Occur on Lost Node 3-42
Database Tables Out of Sync Do Not Trigger Alert 3-42
Reset Database Replication When Reverting to Prior Release 3-43
Useful Commands and Utilities 3-43
Related Documentation
CHAPTER
4
3-44
Simple Network Management Protocol
Overview
4-1
4-1
SNMP Versioning
4-2
SNMP and Cisco Unified CM Basics
SNMP Basic Commands
SNMP and Cisco MIBs
4-3
4-3
SNMP Community Strings and Users
4-4
4-4
SNMP Traps and Informs
4-5
SNMP Trace Configuration
SNMP Tips
3-39
4-5
4-5
SNMP Troubleshooting
SNMP/R MIBs
4-6
4-8
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
iii
Contents
CHAPTER
5
Cisco Unified Real-Time Monitoring Tool Tracing, PerfMon Counters, and Alerts
Cisco Unified Real-Time Monitoring
5-1
5-1
Performance Monitoring in RTMT 5-2
PerfMon Alert Notifications 5-2
PerfMon Objects and Counters for Cisco Unified Communications Manager
Cisco Analog Access 5-5
Cisco Annunciator Device 5-5
Cisco CallManager 5-5
Cisco CallManager External Call Control 5-13
Cisco CallManager SAF 5-14
Cisco CallManager System Performance 5-15
Cisco CTIManager 5-17
Cisco Dual-Mode Mobility 5-17
Cisco Extension Mobility 5-19
Cisco Feature Control Policy 5-20
Cisco Gatekeeper 5-20
Cisco H.323 5-20
Cisco Hunt Lists 5-21
Cisco HW Conference Bridge Device 5-22
Cisco IME Server 5-22
Cisco IP Manager Assistant 5-23
Cisco Lines 5-24
Cisco Locations 5-24
Cisco Media Streaming Application 5-25
Cisco Messaging Interface 5-28
Cisco MGCP BRI Device 5-29
Cisco MGCP FXO Device 5-30
Cisco MGCP FXS Device 5-30
Cisco MGCP Gateways 5-31
Cisco MGCP PRI Device 5-31
Cisco MGCP T1 CAS Device 5-32
Cisco Mobility Manager 5-33
Cisco Music On Hold (MOH) Device 5-34
Cisco MTP Device 5-35
Cisco Phones 5-35
Cisco Presence Feature 5-35
Cisco QSIG Feature 5-36
Cisco Signaling Performance 5-36
Cisco SIP 5-37
5-5
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
iv
OL-20105-01
Contents
Cisco SIP Stack 5-37
Cisco SIP Station 5-45
Cisco SW Conf Bridge Device 5-46
Cisco TFTP Server 5-47
Cisco Transcode Device 5-50
Cisco Video Conference Bridge 5-51
Cisco Web Dialer 5-52
Cisco WSM Connector 5-52
PerfMon Objects and Counters for System 5-53
Cisco Tomcat Connector 5-53
Cisco Tomcat JVM 5-55
Cisco Tomcat Web Application 5-55
Database Change Notification Client 5-56
Database Change Notification Server 5-57
Database Change Notification Subscription 5-58
Database Local DSN 5-58
DB User Host Information Counters 5-58
Enterprise Replication DBSpace Monitors 5-58
Enterprise Replication Perfmon Counters 5-59
IP 5-59
Memory 5-60
Network Interface 5-61
Number of Replicates Created and State of Replication
Partition 5-63
Process 5-64
Processor 5-65
System 5-66
TCP 5-67
Thread 5-67
CHAPTER
6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Cisco Unified Serviceability Alarms and CiscoLog Messages
CiscoLog Format 6-2
Log File and Syslog Outputs 6-3
Standard Syslog Server Implementations 6-4
Clock Synchronization 6-4
Multipart Messages 6-4
CiscoLog Message Format 6-5
Message Length Limit 6-6
SEQNUM Field 6-6
5-62
6-1
6-2
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
v
Contents
HOST Field 6-6
TIMESTAMP Field 6-8
HEADER Field 6-10
TAGS Field 6-14
MESSAGE Field 6-17
Internationalization 6-18
Versioning 6-18
Preconfigured System Alarm Notifications 6-19
AuthenticationFailed 6-19
CiscoDRFFailure 6-20
CoreDumpFileFound 6-20
CpuPegging 6-21
CriticalServiceDown 6-22
HardwareFailure 6-22
LogFileSearchStringFound 6-23
LogPartitionHighWaterMarkExceeded 6-23
LogPartitionLowWaterMarkExceeded 6-24
LowActivePartitionAvailableDiskSpace 6-25
LowAvailableVirtualMemory 6-25
LowInactivePartitionAvailableDiskSpace 6-26
LowSwapPartitionAvailableDiskSpace 6-26
ServerDown 6-27
SparePartitionHighWaterMarkExceeded 6-27
SparePartitionLowWaterMarkExceeded 6-28
SyslogSeverityMatchFound 6-29
SyslogStringMatchFound 6-30
SystemVersionMismatched 6-30
TotalProcessesAndThreadsExceededThreshold 6-31
Preconfigured CallManager Alarm Notifications 6-31
BeginThrottlingCallListBLFSubscriptions 6-32
CallProcessingNodeCpuPegging 6-32
CDRAgentSendFileFailed 6-33
CDRFileDeliveryFailed 6-34
CDRHighWaterMarkExceeded 6-34
CDRMaximumDiskSpaceExceeded 6-35
CodeYellow 6-35
DBChangeNotifyFailure 6-36
DBReplicationFailure 6-36
DDRBlockPrevention 6-37
DDRDown 6-38
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
vi
OL-20105-01
Contents
ExcessiveVoiceQualityReports 6-38
LowCallManagerHeartbeatRate 6-39
LowTFTPServerHeartbeatRate 6-39
MaliciousCallTrace 6-40
MediaListExhausted 6-40
MgcpDChannelOutOfService 6-41
NumberOfRegisteredDevicesExceeded 6-41
NumberOfRegisteredGatewaysDecreased 6-42
NumberOfRegisteredGatewaysIncreased 6-42
NumberOfRegisteredMediaDevicesDecreased 6-42
NumberOfRegisteredMediaDevicesIncreased 6-43
NumberOfRegisteredPhonesDropped 6-43
RouteListExhausted 6-44
SDLLinkOutOfService 6-44
Emergency-Level Alarms 6-45
IPAddressResolveError 6-45
NoCMEntriesInDB 6-46
NoFeatureLicense 6-46
LineStateSrvEngCreationError 6-47
GlobalSPUtilsCreationError 6-47
TapiLinesTableCreationError 6-48
HuntGroupControllerCreationError 6-48
HuntGroupCreationError 6-48
CallDirectorCreationError 6-49
SysControllerCreationError 6-49
TimerServicesCreationError 6-50
ExcceptionInInitSDIConfiguration 6-50
SyncDBCreationError 6-50
LostConnectionToCM 6-51
IPMANotStarted 6-51
BDINotStarted 6-52
WDNotStarted 6-52
CiscoDirSyncStartFailure 6-52
TestAlarmEmergency 6-53
OutOfMemory 6-53
ServiceNotInstalled 6-53
FileWriteError 6-54
Alert-Level Alarms 6-54
CertValidLessthanADay
CMIException 6-55
6-55
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
vii
Contents
CMOverallInitTimeExceeded 6-56
ConfigThreadChangeNotifyServerInstanceFailed 6-56
ConfigThreadChangeNotifyServerSingleFailed 6-57
ConfigThreadChangeNotifyServerStartFailed 6-58
CreateThreadFailed 6-58
CMVersionMismatch 6-59
DBLException 6-60
InvalidCredentials 6-60
MemAllocFailed 6-61
NoDbConnectionAvailable 6-62
ParityConfigurationError 6-62
SerialPortOpeningError 6-63
StopBitConfigurationError 6-63
UnknownException 6-64
VMDNConfigurationError 6-64
CiscoLicenseOverDraft 6-65
CiscoLicenseApproachingLimit 6-66
SDIControlLayerFailed 6-66
SocketError 6-67
SDLLinkOOS 6-67
TFTPServerListenSetSockOptFailed 6-68
TFTPServerListenBindFailed 6-69
TestAlarmAlert 6-70
TLSConnectionToIMEFailed 6-70
TVSServerListenBindFailed 6-71
TVSServerListenSetSockOptFailed 6-71
Critical-Level Alarms 6-72
BChannelOOS 6-72
CallManagerFailure 6-73
CertValidfor7days 6-74
CodeRedEntry 6-75
CodeYellowEntry 6-76
DChannelOOS 6-76
LogPartitionHighWaterMarkExceeded 6-77
MGCPGatewayLostComm 6-78
CDRMaximumDiskSpaceExceeded 6-78
ErrorChangeNotifyClientBlock 6-79
MaxCallsReached 6-80
StationTCPInitError 6-81
TCPSetupToIMEFailed 6-81
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
viii
OL-20105-01
Contents
TimerThreadSlowed 6-82
CiscoDirSyncProcessFailToStart
CoreDumpFileFound 6-83
TestAlarmCritical 6-83
DUPLEX_MISMATCH 6-84
CertExpiryCritical 6-84
6-82
Error-Level Alarms 6-85
AwaitingResponseFromPDPTimeout 6-85
CCDIPReachableTimeOut 6-86
CCDPSTNFailOverDurationTimeOut 6-87
CNFFBuffWriteToFilefopenfailed 6-87
CNFFBuffWriteToFilefwritefailed 6-88
ConfigItAllBuildFilesFailed 6-89
ConfigItAllReadConfigurationFailed 6-89
ConfigThreadBuildFileFailed 6-90
ConfigThreadCNCMGrpBuildFileFailed 6-90
ConfigThreadCNGrpBuildFileFailed 6-91
ConfigThreadReadConfigurationFailed 6-91
ConflictingDataIE 6-92
ConnectionFailureToPDP 6-93
CtiProviderOpenFailure 6-93
DeviceTypeMismatch 6-95
DbInfoCorrupt 6-99
DbInfoError 6-99
DbInfoTimeout 6-100
DRFLocalDeviceError 6-100
EMAppInitializationFailed 6-101
EMCCFailedInLocalCluster 6-101
EMServiceConnectionError 6-102
EndPointTransientConnection 6-103
EndPointUnregistered 6-107
FirewallMappingFailure 6-112
InsufficientFallbackIdentifiers 6-113
InvalidPortHandle 6-114
kANNDeviceRecordNotFound 6-114
kCFBDeviceRecordNotFound 6-115
LostConnectionToSAFForwarder 6-115
MultipleSIPTrunksToSamePeerAndLocalPort 6-116
NodeNotTrusted 6-117
PublishFailedOverQuota 6-117
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
ix
Contents
ReadingFileFailure 6-118
Make sure that the cable connecting the USB0 port and voice messaging system is firmly
connected. 6-119
SAFForwarderError 6-119
SerialPortGetStatusError 6-122
SerialPortSetStatusError 6-122
UnableToRegisterwithCallManagerService 6-123
WritingFileFailure 6-124
ConnectionFailure 6-124
RTMT_ALERT 6-126
DeviceInitTimeout 6-127
NumDevRegExceeded 6-127
RsvpNoMoreResourcesAvailable 6-128
ICTCallThrottlingStart 6-130
DeviceCloseMaxEventsExceeded 6-131
InvalidIPNetPattern 6-131
CDRFileDeliveryFailed 6-132
CDRAgentSendFileFailed 6-133
CDRFileDeliveryFailureContinues 6-134
CDRAgentSendFileFailureContinues 6-134
CARSchedulerJobFailed 6-135
CARSchedulerJobError 6-136
BadCDRFileFound 6-137
kReadCfgUserLocaleEnterpriseSvcParm 6-138
kPWavMgrThreadxFailed 6-138
ANNDeviceRecoveryCreateFailed 6-139
kRequestedANNStreamsFailed 6-140
CFBDeviceRecoveryCreateFailed 6-140
kCreateAudioSourcesFailed 6-141
kCreateControlFailed 6-142
kIPVMSDeviceDriverNotFound 6-142
kIpVmsMgrNoLocalHostName 6-143
kIpVmsMgrNoLocalNetworkIPAddr 6-144
kIPVMSMgrWrongDriverVersion 6-144
kMOHTFTPGoRequestFailed 6-145
DBLGetVersionInfoError 6-146
UserLoginFailed 6-146
kDbConnectionFailed 6-146
ErrorReadingInstalledRPMS 6-147
ErrorChangeNotifyClientTimeout 6-147
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
x
OL-20105-01
Contents
IDSEngineFailure 6-148
IDSReplicationFailure 6-148
IPMAApplicationError 6-149
IPMAOverloaded 6-149
IPMAFilteringDown 6-150
BDIApplicationError 6-150
BDIOverloaded 6-151
WDApplicationError 6-151
WDOverloaded 6-151
CiscoDirSyncProcessFailedRetry 6-152
CiscoDirSyncProcessFailedNoRetry 6-152
CiscoDirSyncProcessConnectionFailed 6-153
CiscoDirSyncDBAccessFailure 6-153
DirSyncScheduledTaskFailed 6-153
DirSyncSchedulerFailedToGetDBSchedules 6-154
DirSyncSchedulerInvalidEventReceived 6-154
DirSyncInvalidScheduleFound 6-155
DirSyncSchedulerFailedToRegisterDBEvents 6-155
DirSyncSchedulerEngineFailedToStart 6-155
DirSyncScheduleDeletionFailed 6-156
DirSyncScheduleUpdateFailed 6-156
DRFMasterAgentStartFailure 6-157
DRFLocalAgentStartFailure 6-157
DRFRestoreFailure 6-158
DRFInternalProcessFailure 6-159
DRFTruststoreMissing 6-160
DRFUnknownClient 6-160
DRFSecurityViolation 6-161
DRFBackupDeviceError 6-162
DRFTapeDeviceError 6-162
DRFRestoreInternalError 6-163
DRFMABackupComponentFailure 6-164
DRFMARestoreComponentFailure 6-164
DRFMABackupNodeDisconnect 6-165
DRFNoRegisteredComponent 6-166
DRFNoRegisteredFeature 6-166
DRFMARestoreNodeDisconnect 6-167
DRFSftpFailure 6-168
DRFRegistrationFailure 6-168
DRFBackupCancelInternalError 6-169
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
xi
Contents
DRFLogDirAccessFailure 6-169
DRFFailure 6-170
CiscoDhcpdFailure 6-171
CiscoLicenseManagerDown 6-171
CiscoLicenseRequestFailed 6-172
CiscoLicenseDataStoreError 6-172
CiscoLicenseInternalError 6-173
CiscoLicenseFileError 6-173
DirSyncSchedulerFailedToUpdateNextExecTime
DuplicateLearnedPattern 6-174
ScheduledCollectionError 6-175
SparePartitionLowWaterMarkExceeded 6-175
RTMT-ERROR-ALERT 6-176
ConfigThreadUnknownExceptionCaught 6-176
ErrorParsingDirectiveFromPDP 6-177
FailureResponseFromPDP 6-177
ReadConfigurationUnknownException 6-178
SAFResponderError 6-179
ThreadPoolProxyUnknownException 6-180
IPv6InterfaceNotInstalled 6-180
TestAlarmError 6-181
ServiceActivationFailed 6-181
ServiceDeactivationFailed 6-182
ServiceFailed 6-182
ServiceStartFailed 6-183
ServiceStopFailed 6-183
ServiceExceededMaxRestarts 6-183
FailedToReadConfig 6-184
SystemResourceError 6-184
CLM_MsgIntChkError 6-185
CLM_UnrecognizedHost 6-185
IDSEngineCritical 6-186
6-173
Warning-Level Alarms 6-186
AnnunciatorNoMoreResourcesAvailable 6-187
ApplicationConnectionDropped 6-188
ApplicationConnectionError 6-188
AuthenticationFailed 6-189
CallAttemptBlockedByPolicy 6-189
CCDLearnedPatternLimitReached 6-190
CertValidLessThanMonth 6-191
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
xii
OL-20105-01
Contents
ConferenceNoMoreResourcesAvailable 6-192
CtiDeviceOpenFailure 6-192
CtiLineOpenFailure 6-194
CtiIncompatibleProtocolVersion 6-195
CtiMaxConnectionReached 6-196
CtiProviderCloseHeartbeatTimeout 6-196
CtiQbeFailureResponse 6-197
DaTimeOut 6-198
DevicePartiallyRegistered 6-198
DeviceTransientConnection 6-202
DeviceUnregistered 6-207
DigitAnalysisTimeoutAwaitingResponse 6-212
DRFNoBackupTaken 6-212
EMCCFailedInRemoteCluster 6-213
ErrorParsingResponseFromPDP 6-214
FailedToFulfillDirectiveFromPDP 6-215
H323Stopped 6-216
InvalidSubscription 6-217
InvalidQBEMessage 6-217
kANNAudioFileMissing 6-218
kANNAudioUndefinedAnnID 6-218
kANNAudioUndefinedLocale 6-219
kANNDeviceStartingDefaults 6-219
kCFBDeviceStartingDefaults 6-220
kChangeNotifyServiceCreationFailed 6-221
kChangeNotifyServiceGetEventFailed 6-222
kChangeNotifyServiceRestartFailed 6-222
kDeviceDriverError 6-223
kDeviceMgrCreateFailed 6-224
kDeviceMgrOpenReceiveFailedOutOfStreams 6-225
kDeviceMgrRegisterKeepAliveResponseError 6-225
kDeviceMgrRegisterWithCallManagerError 6-226
kDeviceMgrSocketNotifyEventCreateFailed 6-227
kDeviceMgrStartTransmissionOutOfStreams 6-227
kDeviceMgrThreadxFailed 6-228
kFixedInputCodecStreamFailed 6-229
kFixedInputCreateControlFailed 6-229
kFixedInputCreateSoundCardFailed 6-230
kFixedInputInitSoundCardFailed 6-231
kFixedInputTranscoderFailed 6-231
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
xiii
Contents
kGetFileNameFailed 6-232
kIPVMSMgrEventCreationFailed 6-233
kIPVMSMgrThreadxFailed 6-233
kIpVmsMgrThreadWaitFailed 6-234
kMOHMgrCreateFailed 6-235
kMOHMgrExitEventCreationFailed 6-235
kMOHMgrThreadxFailed 6-236
kMTPDeviceRecordNotFound 6-237
kRequestedCFBStreamsFailed 6-237
kRequestedMOHStreamsFailed 6-238
kRequestedMTPStreamsFailed 6-238
LogCollectionJobLimitExceeded 6-239
LogPartitionLowWaterMarkExceeded 6-239
MaliciousCall 6-240
MaxDevicesPerNodeExceeded 6-240
MaxDevicesPerProviderExceeded 6-241
MemAllocFailed 6-242
MohNoMoreResourcesAvailable 6-242
MtpNoMoreResourcesAvailable 6-244
MTPDeviceRecoveryCreateFailed 6-246
NotEnoughChans 6-247
NoCallManagerFound 6-247
PublishFailed 6-248
RejectedRoutes 6-249
SparePartitionHighWaterMarkExceeded 6-249
SIPStopped 6-250
SIPLineRegistrationError 6-251
StationEventAlert 6-254
SoftwareLicenseNotValid 6-255
ThreadKillingError 6-256
UserInputFailure 6-256
UserUserPrecedenceAlarm 6-257
UnableToSetorResetMWI 6-258
MediaResourceListExhausted 6-259
RouteListExhausted 6-261
CDRHWMExceeded 6-262
QRTRequest 6-262
DeviceImageDownloadFailure 6-263
EMAppStopped 6-265
IPMAStopped 6-265
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
xiv
OL-20105-01
Contents
IPMAManagerLogout 6-266
BDIStopped 6-266
DirSyncNoSchedulesFound 6-266
DirSyncScheduledTaskTimeoutOccurred 6-267
DRFComponentDeRegistered 6-267
DRFDeRegistrationFailure 6-268
DRFDeRegisteredServer 6-269
DRFSchedulerDisabled 6-269
TotalProcessesAndThreadsExceededThresholdStart 6-270
ServingFileWarning 6-271
TestAlarmWarning 6-271
authLdapInactive 6-272
authAdminLock 6-272
authHackLock 6-273
authInactiveLock 6-273
BeginThrottlingCallListBLFSubscriptions 6-274
ServiceStartupFailed 6-274
authFail 6-275
kANNAudioCreateDirFailed 6-275
MOHDeviceRecoveryCreateFailed 6-276
kMOHDeviceRecordNotFound 6-276
kDeviceMgrExitEventCreationFailed 6-277
kMOHBadMulticastIP 6-278
kDeviceMgrSocketDrvNotifyEvtCreateFailed 6-279
WDStopped 6-280
Notice-Level Alarms 6-280
BChannelISV 6-280
CallManagerOnline 6-281
CertValidityOver30Days 6-281
CodeYellowExit 6-282
DbInsertValidatedDIDFailure 6-283
DChannelISV 6-283
EndPointRegistered 6-284
H323Started 6-287
ICTCallThrottlingEnd 6-288
kDeviceMgrMoreThan50SocketEvents
MGCPGatewayGainedComm 6-289
MaxCallDurationTimeout 6-290
SDLLinkISV 6-291
SIPStarted 6-292
6-289
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
xv
Contents
SMDICmdError 6-293
SMDIMessageError 6-294
TestAlarmNotice 6-294
TotalProcessesAndThreadsExceededThresholdEnd
authExpired 6-295
authMustChange 6-296
credReadFailure 6-296
6-295
Informational-Level Alarms 6-297
AdministrativeEvent 6-297
CiscoHardwareLicenseInvalid 6-298
CiscoLicenseFileInvalid 6-298
CMIServiceStatus 6-298
ConnectionToPDPInService 6-299
CriticalEvent 6-300
CtiDeviceClosed 6-300
CtiDeviceInService 6-301
CtiDeviceOpened 6-302
CtiLineOpened 6-303
CtiLineOutOfService 6-303
CtiProviderClosed 6-304
CtiProviderOpened 6-306
DatabaseDefaultsRead 6-307
CtiDeviceOutofService 6-308
CtiLineClosed 6-308
CtiLineInService 6-310
DefaultDurationInCacheModified 6-311
DeviceApplyConfigInitiated 6-311
DRFBackupCompleted 6-312
DRFRestoreCompleted 6-312
EndPointResetInitiated 6-312
EndPointRestartInitiated 6-315
EndThrottlingCallListBLFSubscriptions 6-317
DeviceRegistered 6-317
DeviceDnInformation 6-321
EMCCUserLoggedIn 6-324
EMCCUserLoggedOut 6-324
ITLFileRegenerated 6-325
kDeviceMgrLockoutWithCallManager 6-325
kDeviceMgrThreadWaitFailed 6-326
kMOHMgrThreadWaitFailed 6-327
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
xvi
OL-20105-01
Contents
kMOHRewindStreamControlNull 6-327
kMOHRewindStreamMediaPositionObjectNull 6-328
PublicationRunCompleted 6-329
RedirectCallRequestFailed 6-329
RollBackToPre8.0Disabled 6-330
RollBackToPre8.0Enabled 6-330
RouteRemoved 6-331
SAFPublishRevoke 6-331
SAFUnknownService 6-332
SecurityEvent 6-333
SoftwareLicenseValid 6-333
StationConnectionError 6-334
StationAlarm 6-335
TVSCertificateRegenerated 6-335
DeviceResetInitiated 6-336
DeviceRestartInitiated 6-338
MaxHoldDurationTimeout 6-340
PktCapServiceStarted 6-341
PktCapServiceStopped 6-341
PktCapOnDeviceStarted 6-341
PktCapOnDeviceStopped 6-342
CMInitializationStateTime 6-342
CMTotalInitializationStateTime 6-343
kANNICMPErrorNotification 6-343
kCFBICMPErrorNotification 6-344
kReadCfgIpTosMediaResourceToCmNotFound 6-344
kDeviceMgrRegisterWithCallManager 6-345
kDeviceMgrUnregisterWithCallManager 6-345
kIPVMSStarting 6-346
kIPVMSStopping 6-347
kMOHICMPErrorNotification 6-347
kMOHMgrIsAudioSourceInUseThisIsNULL 6-348
kMTPDeviceStartingDefaults 6-349
kReadCfgMOHEnabledCodecsNotFound 6-349
LoadShareDeActivateTimeout 6-350
UserLoginSuccess 6-350
UserAlreadyLoggedIn 6-350
UserLoggedOut 6-351
AgentOnline 6-351
AgentOffline 6-352
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
xvii
Contents
DeviceImageDownloadStart 6-352
DeviceImageDownloadSuccess 6-352
DeviceApplyConfigResult 6-353
IDSEngineInformation 6-354
IDSReplicationInformation 6-354
ServiceStarted 6-355
EMAppStarted 6-355
IPMAStarted 6-356
IPMAInformation 6-356
BDIStarted 6-357
WDStarted 6-357
WDInformation 6-357
CiscoDirSyncStarted 6-358
CiscoDirSyncProcessStarted 6-358
CiscoDirSyncProcessCompleted 6-359
CiscoDirSyncProcessStoppedManually 6-359
CiscoDirSyncProcessStoppedAuto 6-359
DirSyncScheduledTaskOver 6-360
DirSyncSchedulerEngineStopped 6-360
DirSyncNewScheduleInserted 6-361
DRFLA2MAFailure 6-361
DRFMA2LAFailure 6-361
CiscoDRFComponentRegistered 6-362
DRFSchedulerUpdated 6-363
CiscoDhcpdRestarted 6-363
DirSyncScheduleInsertFailed 6-363
DirSyncSchedulerEngineStarted 6-364
AuthenticationSucceeded 6-364
LogFileSearchStringFound 6-365
BuildStat 6-365
TestAlarmInformational 6-366
TestAlarmAppliance 6-366
ServiceActivated 6-366
ServiceDeactivated 6-367
authSuccess 6-367
credUpdateFailure 6-368
credUpdateSuccess 6-368
credFullUpdateSuccess 6-369
credFullUpdateFailure 6-369
credReadSuccess 6-370
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
xviii
OL-20105-01
Contents
AdminPassword 6-370
AuditEventGenerated 6-371
PermissionDenied 6-371
ServiceStopped 6-371
CLM_IPSecCertUpdated 6-372
CLM_IPAddressChange 6-372
CLM_PeerState 6-373
CLM_ConnectivityTest 6-373
IDSEngineDebug 6-374
Debug-Level Alarms 6-374
TestAlarmDebug 6-375
Obsolete Alarms in Cisco Unified Communications Manager Release 8.0(1)
Obsolete Alarms in CallManager Catalog 6-376
Obsolete Alarms in CertMonitor Alarm Catalog 6-377
Obsolete Alarms in CMI Alarm Catalog 6-377
Obsolete Alarms in CTI Manager Alarm Catalog 6-377
Obsolete Alarms in DB Alarm Catalog 6-379
Obsolete Alarms in IpVms Alarm Catalog 6-379
Obsolete Alarms in Test Alarm Catalog 6-382
CHAPTER
7
Cisco Management Information Base
6-375
7-1
CISCO-CCM-MIB 7-1
Revisions 7-2
Definitions 7-13
Textual Conventions 7-13
Objects 7-19
Tables 7-19
Cisco Unified CM Group Table 7-19
Cisco Unified CM Table 7-21
Cisco Unified CM Group Mapping Table 7-23
Cisco Unified CM Region Table 7-24
Cisco Unified CM Region Pair Table 7-25
Cisco Unified CM Time Zone Table 7-27
Device Pool Table 7-28
Cisco Unified CM Product Type Table 7-30
Phone Table 7-32
Phone Extension Table 7-38
Phone Failed Table 7-40
Phone Status Update Table 7-42
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
xix
Contents
Enhanced Phone Extension Table with Combination Index
Gateway Table 7-46
Gateway Trunk Table 7-53
All Scalar Objects 7-55
Media Device Table 7-62
Gatekeeper Table 7-66
CTI Device Table 7-69
CTI Device Directory Number Table 7-73
Alarms 7-74
Cisco Unified CM Alarm Enable 7-74
Phone Failed Config Objects 7-75
Phone Status Update Config Objects 7-75
Gateway Alarm Enable 7-76
Malicious Call Alarm Enable 7-76
Notification and Alarms 7-77
H323 Device Table 7-84
Voice Mail Device Table 7-92
Voice Mail Directory Number Table 7-95
Quality Report Alarm Configuration Information 7-96
Sip Device Table 7-97
Notifications Types 7-100
MIB Conformance Statements 7-103
Compliance Statements 7-103
Cisco Unified CM Managed Services and SNMP Traps 7-128
Cisco Unified CM Alarms to Enable 7-128
Traps to Monitor 7-129
Dynamic Table Objects 7-131
Static Table Objects 7-132
Troubleshooting 7-133
General Tips 7-133
For Linux and Cisco Unified CM Releases 5.x, 6.x, 7.x 7-136
Windows and Cisco Unified CM version 4.x 7-137
Limitations 7-137
Frequently Asked Questions 7-138
7-44
CISCO-CCM-CAPABILITY 7-143
Revisions 7-144
Definitions 7-144
Agent Capabilities 7-144
CISCO-CDP-MIB 7-149
Revisions 7-150
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
xx
OL-20105-01
Contents
Definitions 7-151
CDP Interface Group 7-151
CDP Address Cache Group 7-154
CDP Global Group 7-161
Conformance Information 7-162
Compliance Statements 7-163
Units Of Conformance 7-163
Troubleshooting 7-165
Frequently Asked Questions 7-165
CISCO-SYSLOG-MIB 7-166
Revisions 7-167
Definitions 7-167
Object Identifiers 7-167
Textual Conventions 7-167
Basic Syslog Objects 7-168
Syslog Message History Table 7-169
Notifications 7-171
Conformance Information 7-172
Compliance Statements 7-172
Units of Conformance 7-172
Troubleshooting 7-172
Trap Configuration 7-172
Frequently Asked Questions 7-173
CISCO-SYSLOG-EXT-MIB 7-174
Revisions 7-175
Definitions 7-175
Textual Conventions 7-175
Syslog Configuration Group 7-177
cseSyslogServerTable 7-178
cseSyslogMessageControlTable 7-180
Conformance 7-182
Units of Conformance 7-183
CHAPTER
8
Industry-Standard Management Information Base
8-1
SYSAPPL-MIB 8-1
Revisions 8-2
Definitions 8-2
System Application MIB 8-2
Textual Conventions 8-3
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
xxi
Contents
Installed Application Groups 8-3
sysApplInstallPkgTable 8-4
sysApplInstallElmtTable 8-6
sysApplRun Group 8-10
sysApplRunTable 8-10
sysApplPastRunTable 8-12
sysApplElmtRunTable 8-14
sysApplElmtPastRunTable 8-17
Additional Scalar Objects that Control Table Sizes 8-21
sysApplMap Group 8-23
Conformance Macros 8-25
Troubleshooting 8-26
Linux and Cisco Unified CM Releases 5.x, 6.x, 7.x 8-26
Windows and Cisco Unified CM Release 4.x 8-26
Using Servlets in Cisco Unified CM 7.x 8-27
Frequently Asked Questions 8-28
RFC1213-MIB (MIB-II) 8-28
Revisions 8-29
Definitions 8-29
Object Identifiers 8-29
Textual Conventions 8-29
Groups in MIB-II 8-29
Historical 8-30
System Group 8-30
Interfaces Group 8-32
Interfaces Table 8-32
Address Translation Group 8-37
IP Group 8-39
IP Address Table 8-43
IP Routing Table 8-45
IP Address Translation Table 8-49
Additional IP Objects 8-50
ICMP Group 8-50
TCP Group 8-55
TCP Connection Table 8-58
Additional TCP Objects 8-60
UDP Group 8-60
UDP Listener Table 8-61
EGP Group 8-62
EGP Neighbor Table 8-63
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
xxii
OL-20105-01
Contents
Additional EGP Objects
Transmission Group 8-67
SNMP Group 8-67
8-67
HOST-RESOURCES-MIB 8-73
Revisions 8-75
Definitions 8-76
Object Identifiers 8-76
Textual Conventions 8-76
Host Resources System Group 8-77
Host Resources Storage Group 8-79
Host Resources Device Group 8-81
File System Table 8-90
Host Resources Running Software Group 8-92
Host Resources Running Software Performance Group 8-95
Host Resources Installed Software Group 8-96
Conformance Information 8-98
Compliance Statements 8-98
Cisco Unified CM Release 6.x Feature Services 8-100
Cisco Unified CM Release 6.x Network Services 8-102
Troubleshooting 8-103
Frequent Asked Questions 8-104
IF-MIB 8-106
Revisions 8-107
Definitions 8-107
Objects 8-107
Textual Conventions 8-107
Interface Index 8-108
Interfaces Table 8-109
Extension to the Interface Table 8-115
High Capacity Counter Objects 8-117
Interface Stack Group 8-121
Generic Receive Address Table 8-123
Definition of Interface-Related Traps 8-125
Conformance Information 8-125
Compliance Statements 8-125
Units of Conformance 8-127
Deprecated Definitions - Objects 8-129
The Interface Test Table 8-129
Deprecated Definitions - Groups 8-133
Deprecated Definitions - Compliance 8-134
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
xxiii
Contents
CHAPTER
9
Vendor-Specific Management Information Base
Vendor-Specific Management Information Base
9-1
9-1
Supported Servers in Cisco Unified CM Releases 9-1
Cisco Unified CM Release 8.0(1) 9-2
Inapplicable MIBs in Cisco Unified CM Release 8.0(1)
Cisco Unified CM Release 7.1(2) 9-4
Inapplicable MIBs in Cisco Unified CM Release 7.1(2)
Cisco Unified CM 7.1(1) Release 9-5
Inapplicable MIBs 9-6
Cisco Unified CM Release 7.0(1) 9-7
Unsupported Servers by MIB 9-7
Cisco Unified CM Release 6.1(3) 9-8
Unsupported Servers by MIB 9-9
Cisco Unified CM Release 6.1 9-10
Unsupported Servers by MIB 9-10
Cisco Unified CM Release 6.0 9-11
Unsupported Servers by MIB 9-12
IBM MIBs 9-13
IBM Status Messages
9-2
9-5
9-14
Hewlett Packard MIBs 9-16
HP Status Messages 9-16
Intel MIBs 9-22
Intel Status Messages
9-22
INDEX
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
xxiv
OL-20105-01
Preface
This chapter describes the purpose, audience, organization, and conventions of this document. It
contains the following sections:
•
Purpose, page xxv
•
Audience, page xxv
•
Organization, page xxvi
•
Related Documentation, page xxvi
•
Conventions, page xxvii
•
Obtaining Documentation and Submitting a Service Request, page xxviii
•
Cisco Product Security Overview, page xxviii
Purpose
This document gives an overview of Cisco Unified Communications Manager (formerly Cisco Unified
CallManager), deployment models, and related Management Information Bases (MIBs). It also explains
syslogs, alerts, and alarms for the managed services that Service Providers implement in their networks.
This document outlines basic concepts including Simple Network Management Protocol (SNMP) and
the features of Cisco Unified Serviceability including Real-Time Monitoring Tool (RTMT).
Audience
This document provides information for administrators who install, upgrade, and maintain a service
provider network. You need to have an understanding of Cisco Unified Communications Manager and
Cisco Unified Communications Manager Business Edition. See the “Related Documentation” section on
page xxvi for Cisco Unified Communications Manager documents and other related technologies.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
xxv
Preface
Organization
The following table provides an outline of the chapters in this document.
Chapter
Description
Chapter 1, “Overview”
Describes concepts with which you need to be familiar
to implement SNMP, MIBs, and serviceability
features.
Chapter 2, “New and Changed Information”
Describes the new and changed information in Cisco
Unified Communications Manager releases.
Chapter 3, “Managing and Monitoring the
Health of Cisco Unified Communications
Manager Systems”
Describes methods for managing and monitoring the
Cisco Unified Communications Manager servers.
Chapter 4, “Simple Network Management
Protocol”
Describes the versions of SNMP and provides some
troubleshooting tips.
Chapter 5, “Cisco Unified Real-Time
Describes the Cisco Unified Real-Time Monitoring
Monitoring Tool Tracing, PerfMon Counters, Tool, default alarms, PerfMon counters, trace
collection and other tools for troubleshooting.
and Alerts”
Chapter 6, “Cisco Unified Serviceability
Alarms and CiscoLog Messages”
Describes error messages in Cisco Unified
Serviceability and CiscoLog message formats.
Chapter 7, “Cisco Management Information
Base”
Describes Cisco MIBs and the functionality of each
with troubleshooting tips.
Chapter 8, “Industry-Standard Management
Information Base”
Describes industry-standard MIBs including the
functionality of each with troubleshooting tips.
Chapter 9, “Vendor-Specific Management
Information Base”
Describes vendor-specific MIBs including the
functionality of each with troubleshooting tips.
Related Documentation
This section lists documents that provide information on Cisco Unified Communications Manager,
Cisco Unified IP Phones, and Cisco Unified Serviceability. Find the index to the documents at
http://www.cisco.com/en/US/products/sw/voicesw/ps556/prod_maintenance_guides_list.html
•
Cisco Unified Communications Manager Release 8.0(1)—A suite of documents that relate to the
installation and configuration of Cisco Unified Communications Manager. Refer to the Cisco
Unified Communications Manager Documentation Guide for a list of documents on installing and
configuring Cisco Unified Communications Manager including:
– Cisco Unified Communications Manager Administration Guide
– Cisco Unified Communications Manager System Guide
– Cisco Unified Communications Manager Features and Services Guide
•
Cisco Unified IP Phones and Services—A suite of documents that relate to the installation and
configuration of Cisco Unified IP Phones.
•
Cisco Unified Serviceability—A suite of documents that relate to the maintenance of managed
services within Cisco Unified Serviceability. Refer to the Cisco Unified Communications Manager
Documentation Guide for a complete list of documents including:
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
xxvi
OL-20105-01
Preface
– Cisco Unified Serviceability Administration Guide
– Cisco Unified Communications Manager Call Detail Records Administration Guide
– Cisco Unified Communications Manager CDR Analysis and Reporting Administration Guide
– Cisco Unified Real-Time Monitoring Tool Administration Guide
– Cisco Unified Reporting Administration Guide
– Command Line Interface Reference Guide for Cisco Unified Communications Solutions
– Disaster Recovery System Administration Guide for Cisco Unified Communications Manager
Conventions
This document uses the following conventions:
Convention
Description
boldface font
Commands and keywords are in boldface.
italic font
Arguments for which you supply values are in italics.
[ ]
Elements in square brackets are optional.
{x|y|z}
Alternative keywords are grouped in braces and separated by
vertical bars.
[x|y|z]
Optional alternative keywords are grouped in brackets and
separated by vertical bars.
string
A nonquoted set of characters. Do not use quotation marks
around the string or the string will include the quotation marks.
screen
font
boldface
screen
Terminal sessions and information the system displays are in
screen font.
Information you must enter is in boldface screen font.
font
italic screen
font
→
Arguments for which you supply values are in italic screen
font.
This pointer highlights an important line of text in an example.
^
The symbol ^ represents the key labeled Control—for example,
the key combination ^D in a screen display means hold down
the Control key while you press the D key.
< >
Nonprinting characters, such as passwords are in angle
brackets.
Notes use the following conventions:
Note
Means reader take note. Notes contain helpful suggestions or references to material not covered in the
publication.
Timesavers use the following conventions:
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
xxvii
Preface
Timesaver
Means the described action saves time. You can save time by performing the action described in the
paragraph.
Tips use the following conventions:
Tip
Means the following are useful tips.
Obtaining Documentation and Submitting a Service Request
For information on obtaining documentation, submitting a service request, and gathering additional
information, see the monthly What’s New in Cisco Product Documentation, which also lists all new and
revised Cisco technical documentation, at:
http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html
Subscribe to the What’s New in Cisco Product Documentation as a Really Simple Syndication (RSS) feed
and set content to be delivered directly to your desktop using a reader application. The RSS feeds are a free
service and Cisco currently supports RSS Version 2.0.
Cisco Product Security Overview
This product contains cryptographic features and is subject to United States and local country laws
governing import, export, transfer and use. Delivery of Cisco cryptographic products does not imply
third-party authority to import, export, distribute or use encryption. Importers, exporters, distributors
and users are responsible for compliance with U.S. and local country laws. By using this product you
agree to comply with applicable laws and regulations. If you are unable to comply with U.S. and local
laws, return this product immediately.
A summary of U.S. laws governing Cisco cryptographic products may be found
at—http://www.cisco.com/wwl/export/crypto/tool/stqrg.html.
If you require further assistance please contact us by sending e-mail to export@cisco.com.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
xxviii
OL-20105-01
CH A P T E R
1
Overview
This chapter gives a conceptual overview of Cisco Unified Communications Manager (Cisco Unified
CM) and Cisco Unified CM Business Edition, possible deployment models, Simple Network
Management Protocol (SNMP) including traps, Management Information Bases (MIBs), syslogs, and
alerts/alarms. It contains the following sections:
•
Cisco Unified Communications Manager, page 1-1
•
Supported Deployment Models, page 1-2
•
Managed Services, page 1-3
•
Cisco Unified Serviceability, page 1-4
•
Cisco Unified Real-Time Monitoring Tool, page 1-6
•
Call Detail Records and Call Management Records, page 1-7
•
Call Detail Record Analysis and Reporting, page 1-7
•
Management Information Base, page 1-8
Cisco Unified Communications Manager
The Cisco Unified CM serves as the software-based call-processing component of the Cisco Unified
Communications family of products. A wide range of Cisco Media Convergence Servers provides
high-availability server platforms for Cisco Unified Communications Manager call processing, services,
and applications.
The Cisco Unified CM system extends enterprise telephony features and functions to packet telephony
network devices such as IP phones, media processing devices, voice-over-IP (VoIP) gateways, and
multimedia applications. Additional data, voice, and video services, such as unified messaging,
multimedia conferencing, collaborative contact centers, and interactive multimedia response systems,
interact through Cisco Unified CM open telephony application programming interface (API).
Cisco Unified CM provides signaling and call control services to Cisco integrated telephony
applications as well as third-party applications. Cisco Unified CM performs the following primary
functions—
•
Call processing
•
Signaling and device control
•
Dial plan administration
•
Phone feature administration
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
1-1
Chapter 1
Overview
Supported Deployment Models
•
Directory services
•
Operations, administration, maintenance, and provisioning (OAM&P)
•
Programming interface to external voice-processing applications such as Cisco IP Communicator,
Cisco Unified IP Interactive Voice Response (IP IVR), and Cisco Unified Communications
Manager Attendant Console
Supported Deployment Models
Three types of Cisco Unified CM supported deployments exist—Single site, multisite WAN with
centralized call processing, and multisite WAN with distributed call processing. The following
paragraphs describe each of these:
•
Single Site—Consists of a call processing agent cluster that is located at a single site, or campus,
with no telephony services that are provided over an IP WAN. An enterprise would typically deploy
the single-site model over a LAN or metropolitan area network (MAN), which carries the voice
traffic within the site. In this model, calls beyond the LAN or MAN use the public switched
telephone network (PSTN).
•
Multisite WAN with Centralized Call Processing—Consists of a single call processing agent cluster
that provides services for many remote sites and uses the IP WAN to transport Cisco Unified
Communications traffic between the sites. The IP WAN also carries call control signaling between
the central site and the remote sites.
•
Multisite WAN with Distributed Call Processing—Consists of multiple independent sites, each with
its own call processing agent cluster that is connected to an IP WAN that carries voice traffic
between the distributed sites.
Cisco Unified CMBE supports three main types of deployment models—Single-site, multisite WAN
with centralized call processing, and multisite WAN deployment with distributed call processing. Cisco
Unified CMBE is a single-platform deployment, running both Cisco Unified CM and Cisco Unity
Connection on the same server. Each type is described in the following paragraphs:
•
Single-Site—Consists of Cisco Unified CM and Cisco Unity Connection running on the same
hardware platform located at a single site or campus, with no telephony services provided over an
IP WAN.
•
Multisite WAN with Centralized Call Processing—Consists of a single call processing appliance
that provides services for up to 20 sites (one central site and 19 remote sites), and this model uses
the IP WAN to transport IP telephony traffic between the sites. The IP WAN also carries call control
signaling between the central site and the remote sites.
•
Multisite WAN with Distributed Call Processing—Consists of independent sites, each with its own
call processing agent connected to an IP WAN that carries voice traffic between the distributed sites.
The multisite WAN deployment with distributed call processing enables Cisco Unified CMBE to
operate with Cisco Unified CM or other Cisco Unified CMBE deployments. With this model, Cisco
Unified CMBE supports the use of H.323 intercluster trunks as well as SIP trunks to interconnect
with Cisco Unified CM deployments or other Cisco Unified CMBE deployments. Each site can be
a single site with its own call processing agent, a centralized call processing site and all of its
associated remote sites, or a legacy PBX with Voice over IP (VoIP) gateway.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
1-2
OL-20105-01
Chapter 1
Overview
Managed Services
Managed Services
Two general types of managed services exist:
•
Basic services that provide connectivity to the network—Routing, Domain Name System (DNS),
and quality of service (QoS).
•
High-valued services that the Service Provider offers to its customers—Videoconferencing, mobile
IP, VPNs, VoIP, and Wireless. The high-valued services use the basic services as a backbone.
The service provider may require these server types and services:
•
Web server with the ability to display web pages, even during high usage hours, to meet the demands
of customers. The web pages get used to pay bills, check minutes of usage in the case of a cell phone,
and buy new products. The web server and application server work together to display information
that the service provider customer requires.
•
Dedicated application server with the ability to advise customers when a product is out of stock,
when bill is past due, or when need arises to buy more minutes.
•
Mail server with the ability to notify customers to confirm an order or send a receipt for purchases.
•
Secure gateway with VPN with the ability to have secure communications between the service
provider and its customers and suppliers.
Be aware that any one of these services is critical to the operations of a service provider. Managing these
services to ensure continuous operation requires a system that monitors fault, configuration,
performance and security across all of the network elements. The introduction of element-to-element
synchronization and the issues of using different vendor products complicates the task.
Cisco Unified Serviceability and SNMP attempt to address some of these network management issues:
•
Are infrastructure elements functioning? If not, which are failing?
•
What cause the failure? For example, recent configuration changes.
•
What is the impact of the failure on the network as a whole and the impact on the elements within
the network?
•
What is the impact of the failure on services and customers?
•
How long to correct the failure?
•
Are there backup facilities?
•
Are there any pending failures?
•
How many packets were sent and received on a particular device? How many web pages were
accessed.
•
How were other devices used—how often and how long?
Cisco Unified CM supports SNMP v1, v2, and v3. SNMP remotely monitors, configures, and controls
networks. SNMP sends fault messages to assigned managers as SNMP trap or inform request Protocol
Data Units (PDUs). For more information, see Chapter 4, “Simple Network Management Protocol.”
Cisco Unified Serviceability, a component of Cisco Unified CM Administration includes its own set of
error messages and alarms. Both applications use Management Information Base (MIB) text files to
manage alarms and alerts, notifications, and error messages. For more information, see Chapter 6,
“Cisco Unified Serviceability Alarms and CiscoLog Messages.”
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
1-3
Chapter 1
Overview
Cisco Unified Serviceability
Cisco Unified Serviceability
Cisco Unified Serviceability, a web-based troubleshooting tool, enables the following functions:
•
Saves alarms and events for troubleshooting and provides alarm definitions.
•
Saves trace information to various log files for troubleshooting.
•
Monitors real-time behavior of components by using the Cisco Unified Real-Time Monitoring Tool
(RTMT).
•
Provides feature services that you can activate, deactivate, and view through the Service Activation
window.
•
Provides an interface for starting and stopping feature and network services.
•
Generates and archives daily reports; for example, alert summary or server statistic reports.
•
Allows Cisco Unified Communications Manager to work as a managed device for SNMP remote
management and troubleshooting.
•
Monitors the disk usage of the log partition on a server.
•
Monitors the number of threads and processes in the system; uses cache to enhance the performance.
For information about configuring service parameters, refer to the Cisco Unified Communications
Manager Administration Guide. For information about configuring Serviceability features, refer to the
Cisco Unified Serviceability Administration Guide.
This section contains the following topics:
•
Trace Tools, page 1-4
•
Troubleshooting Trace, page 1-5
•
Trace Collection, page 1-5
•
Cisco Unified Reporting, page 1-5
Trace Tools
Trace tools assist you in troubleshooting issues with your voice application. Cisco Unified Serviceability
supports SDI (System Diagnostic Interface) trace, SDL (Signaling Distribution Layer) trace for Cisco
CallManager and Cisco CTIManager services, and Log4J trace for Java applications.
You use the Trace Configuration window to specify the level of information that you want traced as well
the type of information that you want to be included in each trace file. If the service is a call-processing
application such as Cisco CallManager or Cisco CTIManager, you can configure a trace on devices such
as phones and gateway.
In the Alarm Configuration window, you can direct alarms to various locations, including SDI trace log
files or SDL trace log files. If you want to do so, you can configure trace for alerts in the RTMT. After
you have configured information that you want to include in the trace files for the various services, you
can collect and view trace files by using the trace and log central option in the RTMT.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
1-4
OL-20105-01
Chapter 1
Overview
Cisco Unified Reporting
Troubleshooting Trace
The Troubleshooting Trace Settings window allows you to choose the services in Cisco Unified
Serviceability for which you want to set predetermined troubleshooting trace settings. In this window,
you can choose a single service or multiple services and change the trace settings for those services to
the predetermined trace settings.
If you have clusters (Cisco Unified Communications Manager only), you can choose the services on
different Cisco Unified Communications Manager servers in the cluster, so the trace settings of the
chosen services get changed to the predetermined trace settings. You can choose specific activated
services for a single server, all activated services for the server, specific activated services for all servers
in the cluster, or all activated services for all servers in the cluster. In the window, N/A displays next to
inactive services.
When you open the Troubleshooting Trace Settings window after you apply troubleshooting trace
settings to a service, the service that you set for troubleshooting displays as checked. In the
Troubleshooting Trace Settings window, you can reset the trace settings to the original settings.
After you apply Troubleshooting Trace Setting to a service, the Trace Configuration window displays a
message that troubleshooting trace is set for the given service(s). From the Related Links drop-down list
box, you can choose the Troubleshooting Trace Settings option if you want to reset the settings for the
service. For the given service, the Trace Configuration window displays all the settings as read-only,
except for some parameters of trace output settings; for example, Maximum No. of Files. You can
modify these parameters even after you apply troubleshooting trace settings.
Trace Collection
Use Trace and Log Central, an option in the RTMT, to collect, view, and zip various service traces and/or
other log files. With the Trace and Log Central option, you can collect SDL/SDI traces, Application
Logs, System Logs (such as Event View Application, Security, and System logs), and crash dump files.
For more information on trace collection, refer to the Cisco Unified Real-Time Monitoring Tool
Administration Guide.
Cisco Unified Reporting
Cisco Unified Reporting web application, which is accessed at the Cisco Unified Communications
Manager console, generates reports for troubleshooting or inspecting cluster data. This tool provides a
snapshot of cluster data without requiring multiple steps to find the data. The tool design facilitates
gathering data from existing sources, comparing the data, and reporting irregularities.
A report combines data from one or more sources on one or more servers into one output view. For
example, you can view a report that shows the hosts file for all servers in the cluster. The application
gathers information from the publisher server and each subscriber server. A report provides data for all
active cluster nodes that are accessible at the time that the report is generated.
Some reports run checks to identify conditions that could impact cluster operations. Status messages
indicate the outcome of every data check that is run.
Only authorized users can access the Cisco Unified Reporting application. By default, this includes
administrator users in the Standard Cisco Unified CM Super Users group. As an authorized user, you
can view reports, generate new reports, or download reports at the graphical user interface (GUI).
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
1-5
Chapter 1
Overview
Cisco Unified Real-Time Monitoring Tool
Administrator users in the Standard Cisco Unified CM Super Users group can access all administrative
applications in the Cisco Unified Communications Manager Administration navigation menu, including
Cisco Unified Reporting, with a single sign onto one of the applications.
Cisco Unified Reporting includes the following capabilities:
•
A user interface for generating, archiving, and downloading reports
•
Notification message if a report will take excessive time to generate or consume excessive CPU
Generated reports in Cisco Unified Reporting may use any of the following data sources:
•
RTMT counters
•
CDR CAR
•
Cisco Unified CM DB
•
Disk files
•
Operating System API calls
•
Network API calls
•
Prefs (Windows registry)
•
CLI
•
RIS
Cisco Unified Real-Time Monitoring Tool
RTMT is a client-side application that uses HTTPS and TCP to monitor system performance, device
status, device discovery, CTI applications, and voice messaging ports. RTMT can connect directly to
devices by using HTTPS to troubleshoot system issues. RTMT performs the following tasks:
•
Monitor a set of predefined management objects that monitor the health of the system.
•
Generate various alerts, in the form of e-mails, for objects when values go over/below
user-configured thresholds.
•
Collect and view traces in various default viewers that exist in RTMT.
•
Translate Q931 messages.
•
View syslog messages in SysLog Viewer.
•
Work with performance-monitoring counters.
In addition to SNMP traps, RTMT can monitor and parse syslog messages that are provided by the
hardware vendors, and then send these alerts to RTMT Alert Central. You can configure RTMT to notify
the Cisco Unified CM system administrator if and when the alerts occur. You can configure the
notifications for e-mail or Epage or both.
For more information, refer to Cisco Unified Real-Time Monitoring Tool Administration Guide.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
1-6
OL-20105-01
Chapter 1
Overview
Call Detail Records and Call Management Records
Call Detail Records and Call Management Records
Call Detail Records (CDRs) and Call Management Records (CMRs) get used for post-processing
activities such as generating billing records and network analysis. When you install your system, the
system enables CDRs by default. CMRs remain disabled by default. You can enable or disable CDRs or
CMRs at any time that the system is in operation.
The CDR Management (CDRM) feature, a background application, supports the following capabilities:
•
Collects the CDR/CMR files from the Cisco Unified Communications Manager server or node to
the CDR Repository server or node.
•
Collects and maintains the CDR/CMR files on the server where you configure CAR.
•
Maintains the CDR/CMR files on the CDR Repository node or CDR server.
•
Allows third-party applications to retrieve CDR/CMR files on demand through a SOAP interface.
•
Accepts on-demand requests for searching file names.
•
Pushes CDR/CMR files from individual nodes within a cluster to the CDR Repository server or
node.
•
Sends CDR/CMR files to up to three customer billing servers via FTP/SFTP.
•
Monitors disk usage of CDR/CMR files on the server where you configure CAR or on the CDR
Repository server or node.
•
Periodically deletes CDR/CMR files that were successfully delivered. You can configure the
amount of storage that is used to store flat files. Predefined storage limits exist. If the storage limits
are exceeded, the CDR Repository Manager deletes old files to reduce the disk usage to the
preconfigured low water mark. The post-processing applications can later retrieve the buffered
historical data to re-get any lost, corrupted, or missing data. The CDRM feature, which is not aware
of the flat file format, does not manipulate the file contents.
CDRM includes two default services, the CDR Agent and the CDR Repository Manager, and one
activate service, CDR onDemand Service.
For more information, refer to the Cisco Unified Communications Manager Call Detail Records
Administration Guide.
Call Detail Record Analysis and Reporting
Cisco Unified Serviceability supports Call Detail Record (CDR) Analysis and Reporting (CAR) and is
is available in the Tools menu. CAR generates reports for Quality of Service (QoS), traffic, and billing
information. For its primary function, CAR generates reports about the users of Cisco Unified
Communications Manager and reports on system status with respect to call processing. CAR also
performs CAR database management activities. You can perform these tasks in one of the following
ways:
•
Automatically configure the required tasks to take place.
•
Manually perform the tasks by using the web interface.
CAR processes the CDRs from flat files that the CDR repository service places in the repository folder
structure. CAR processes CDRs at a scheduled time and frequency. By default, CDR data loads
continuously 24 hours per day and 7 days per week; however, you can set the loading time, interval, and
duration as needed. In addition, the default setting loads only CDR records. CMR records do not get
loaded by default.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
1-7
Chapter 1
Overview
Management Information Base
CAR provides e-mail alerts for various events, including the following events:
•
Charge Limit Notification indicates when the daily charge limit for a user exceeds the specified
maximum.
•
QoS Notification indicates when the percentage of good calls drops below a specified range or the
percentage of poor calls exceeds a specified limit.
For more information, refer to the Cisco Unified Communications Manager CDR Analysis and
Reporting Administration Guide.
Management Information Base
The Management Information Base (MIB) converts object identifiers (OIDs) that are numerical strings
into an ASCII text file. The OIDs identify data objects. The OID represents specific characteristics of a
device or application and can have one or more object instances (variables). Managed objects, alarms,
notifications, and other valuable information get identified by the OID and get listed in the MIB.
The OID gets logically represented in a tree hierarchy. The root of the tree stays unnamed and splits into
three main branches—Consultative Committee for International Telegraph and Telephone (CCITT),
International Organization for Standardization (ISO), and joint ISO/CCITT.
These branches and those that fall below each category have short text strings and integers to identify
them. Text strings describe object names, while integers allow computer software to create compact,
encoded representations of the names. For example, the Cisco MIB variable authAddr represents an
object name and gets denoted by the number 5, which is listed at the end of OID 1.3.6.1.4.1.9.2.1.5.
The OID in the Internet MIB hierarchy represents the sequence of numeric labels on the nodes along a
path from the root to the object. The OID 1.3.6.1.2.1 represents the Internet standard MIB. It also can
get expressed as iso.org.dod.internet.mgmt.mib.
The Cisco MIB set comprises a collection of variables that are private extensions to the Internet standard
MIB II and many other Internet standard MIBs. RFC 1213, Management Information Base for Network
Management of TCP/IP-based Internets—MIB-II documents MIB II.
Cisco Unified CM and Cisco Unified CMBE support the following MIBs:
•
CISCO-CCM-MIB
•
CISCO-CCM-CAPABILITY
•
CISCO-CDP-MIB
•
CISCO-SYSLOG-MIB
•
HOST-RESOURCES-MIB
•
MIB-II
•
SYSAPPL-MIB
•
Vendor-specific MIBs
For descriptions of the supported MIBs, see the following chapters:
•
Chapter 7, “Cisco Management Information Base”
•
Chapter 8, “Industry-Standard Management Information Base”
•
Chapter 9, “Vendor-Specific Management Information Base”
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
1-8
OL-20105-01
CH A P T E R
2
New and Changed Information
This chapter describes new and changed information in Cisco Unified Communications Manager (Cisco
Unified CM) for Release 8.0(1). It contains the following sections:
•
Cisco Unified Communications Manager, Release 8.0(1), page 2-1
•
MIB Updates, page 2-30
For more information, refer to the latest release notes at
http://www.cisco.com/en/US/products/sw/voicesw/ps556/prod_release_notes_list.html.
Cisco Unified Communications Manager, Release 8.0(1)
This section describes the new and changed information in Cisco Unified Communications Manager,
Release 8.0. It contains the following subsections:
•
Cisco Unified Serviceability, page 2-1
•
Cisco Unified Real-Time Monitoring Tool, page 2-22
•
Cisco Unified CDR Analysis and Reporting, page 2-25
•
Cisco Unified Call Detail Records, page 2-27
•
Cisco Unified Reporting, page 2-30
Cisco Unified Serviceability
This section contains the following subsections:
•
Alarm Additions and Changes, page 2-2
•
Obsolete Alarms, page 2-17
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
2-1
Chapter 2
New and Changed Information
Cisco Unified Communications Manager, Release 8.0(1)
Alarm Additions and Changes
•
Audit Log Catalog—The following new Audit Log alarms are added:
Alarm Name
Description
AdministrativeEvent
Failed to write into the primary file path. Audit Event is
generated by this application. Severity level is Informational.
CriticalEvent
Failed to write into the primary file path. Audit Event is
generated by this application. Severity level is Informational.
SecurityEvent
Failed to write into the primary file path. Audit Event is
generated by this application. Severity level is Informational.
•
EM Alarm Catalog—The following new EM alarms are added:
Alarm Name
Description
EMAppInitializationFailed
EM Application not started. Error occurred while starting
application. Severity level is Error.
EMAppStarted
EM Application started successfully. Severity level is
Informational.
EMAppStopped
EM Application started. Application is shutting down
gracefully because of an unloaded from Tomcat. Severity level
is Notice.
EMCCFailedInLocalCluster
EMCC login failure occurred due to one of the following
conditions:
EMCCFailedInRemoteCluster
•
Devices are incompatible with EMCC.
•
Unable to retrieve remote cluster information.
•
EMCC is restricted by the local cluster.
•
EMCC is restricted by the local cluster.
There was an EMCC login failure at a remote Unified CM.
EMCC login could fail due to the following reasons:
•
User does not exist in any of the configured remote cluster.
•
User is not enabled for EMCC.
•
No free EMCC base device.
•
EMCC access was prevented by remote cluster.
•
Untrusted certificate received from the remote end while
trying to establish a connection.
EMCCUserLoggedIn
EMCC login was successful. Severity level is
Informational(6).
EMCCUserLoggedOut
EMCC logout was successful. Severity level is
Informational(6).
EMServiceConnectionError
EM Service not reachable. EM Service might be down in one
or more nodes in the cluster. Severity level is Error.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
2-2
OL-20105-01
Chapter 2
New and Changed Information
Cisco Unified Communications Manager, Release 8.0(1)
Alarm Name
Description
NodeNotTrusted
Untrusted Node was contacted. Severity level is Error.
UserInputFailure
EMCC login failure due to invalid user input due to invalid
user credentials or the credentials have expired. Severity level
is Warning(4).
•
TVS Alarm Catalog—The following new TVS alarms are added:
Alarm Name
Description
ConfigThreadChangeNotifyServerSingleFailed
Failed to allocate resources to handle
configuration change notification from database.
ConfigThreadReadConfigurationFailed
Failed to retrieve enterprise parameter values
from database at TVS service startup.
DefaultDurationInCacheModified
Default value of a Certificate duration in cache is
modified in the Service Parameter page.
ITLFileRegenerated
New ITL File has been generated.
RollBackToPre8.0Disabled
Roll Back to Pre 8.0 has been disabled in the
Enterprise Parameter page.
SDIControlLayerFailed
Failed to update trace logging or alarm subsystem
for new settings.
TVSCertificateRegenerated
TVS Server certificate has been regenerated.
TVSServerListenBindFailed
Fail to connect to the network port through which
file requests are received.
TVSServerListenSetSockOptFailed
Failed to increase the size of the network buffer
for receiving file requests.
•
Call Manager Catalog—The following new Call Manager alarms are added:
Alarm Name
Description
CMVersionMismatch
One or more Unified CM nodes in a cluster are running different
Cisco CallManager versions.
ConflictingDataIE
A call has been rejected because the incoming PRI/BRI Setup
message had an invalid IE.
DbInfoCorrupt
Database information returned is corrupt. Database configuration
error was encountered.
DbInfoError
Error in the database information retrieved. Database
configuration error was encountered.
DbInfoTimeout
Database Information request timed out. Timeout was
encountered while trying to read database configuration.
DbInsertValidatedDIDFailure
The Insertion of an IME provided E.164 DID has failed. A failure
occurred attempting to insert a Cisco Unified Active Link
learned DID.
EndPointRegistered
This alarm occurs when a device is successfully registered with
Cisco Unified Communications Manager.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
2-3
Chapter 2
New and Changed Information
Cisco Unified Communications Manager, Release 8.0(1)
Alarm Name
Description
EndPointResetInitiated
This alarm occurs when a device is reset via the Reset button in
Cisco Unified CM Administration.
EndPointRestartInitiated
Device restart initiated or Apply Config initiated on the specified
device.
EndPointTransientConnection
End point transient connection attempt.
EndPointUnregistered
An endpoint that has previously registered with Cisco Unified
Communications Manager has unregistered.
FirewallMappingFailure
Firewall unreachable.
IMEQualityAlertEntry
IME call quality problem.
IMEQualityAlertExit
IME call quality problem cleared.
IMEDistributedCacheInactive
Inactive IME distributed cache.
IMEOverQuota
Each IME server has a fixed quota on the total number of DIDs
it can write into the IME distributed cache.
InsufficientFallbackIdentifiers
Cannot allocate fallback identifier.
InvalidSubscription
A message has been received from an IME server that contains a
subscription identifier that is not handled by this node.
RouteRemoved
Route is removed automatically.
InvalidCredentials
Credential Failure to IME server.
PublicationRunCompleted
Completion of publication of published DID patterns.
PublishFailed
Unified CM attempted to store a number into the IME distributed
cache, but the attempt failed. This is typically due to a transient
problem in the IME distributed cache.
PublishFailedOverQuota
Each IME server has a fixed quota on the total number of DIDs
it can write into the IME distributed cache.
RejectedRoutes
Rejected route due to Untrusted status.
TCPSetupToIMEFailed
Connection Failure to IME server.
TLSConnectionToIMEFailed
TLS Failure to IME service.
New SAF and CCD Alarms
LostConnectionToSAFForwarder
Connection to the SAF Forwarder has been lost.
SAFForwarderError
SAF Forwarder error response sent to Unified CM.
SAFUnknownService
Unified CM does not recognize the service ID in a publish revoke
or withdraw message.
SAFPublishRevoke
A CLI command revoked the publish action for the specified
service or subservice ID.
SAFResponderError
This is raised when SAF forwarder doesn't know the transaction
ID within SAF response from this Cisco Unified CM.
DuplicateLearnedPattern
This alarm occurs when CCD requesting service received a
duplicate Hosted DN.
CCDIPReachableTimeOut
CCD Requesting Service IP Reachable Duration times out.
CCDPSTNFailOverDurationTime
Out
The internal limit on PSTN failover has expired.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
2-4
OL-20105-01
Chapter 2
New and Changed Information
Cisco Unified Communications Manager, Release 8.0(1)
Alarm Name
Description
CCDPSTNFailOverDurationTime
Out
CCD has reached the maximum number of learned patterns
allowed.
New Alarms in External Call Control
ConnectionFailureToPDP
A connection request from Unified CM to the policy decision
point (PDP) failed.
ConnectionToPDPInService
A connection was successfully established between Cisco
Unified Communications Manager (Unified CM) and the policy
decision point (PDP).
AwaitingResponseFromPDPTimeo Cisco Unified Communication Manager timed out waiting for the
ut
routing response from the policy decision point.
ErrorParsingResponseFromPDP
Cisco Unified Communications Manager failed to parse one or
multiple optional elements or attributes in the call routing
response from the policy decision point.
ErrorParsingDirectiveFromPDP
Cisco Unified Communications Manager (Unified CM) failed to
parse the call routing directive or the diversion destination in the
call routing response from the policy decision point (PDP).
FailureResponseFromPDP
The policy decision point (PDP) returned a 4xx (client) or 5xx
(server) status code in the HTTP response.
CallAttemptBlockedByPolicy
A call was attempted but blocked or rejected by the policy
decision point (PDP).
FailedToFulfillDirectiveFromPDP
Cisco Unified Communications Manager cannot fulfill the call
routing directive returned by the PDP.
DigitAnalysisTimeoutAwaitingRe
sponse
Cisco Unified Communications Manager sent a routing request
to the policy decision point but the request timed out without a
response.
Changed Alarms in Call Manager Catalog
The following existing CallManager alarms are updated:
Alarm Names
Alarm Changes
AnnunciatorNoMoreResourcesAvailable
Severity changed from Error to Warning
BChannelISV
Severity changed from Informational to Notice.
BChannelOOS
Severity changed from Error to Critical.
BeginThrottlingCallListBLFSubscriptions
Severity level is Warning.
CMInitializationStateTime
Severity level is Informational.
CMOverallInitTimeExceeded
Severity changed from Error to Alert.
CMTotalInitializationStateTime
Severity level is Informational.
CallManagerFailure
Severity changed from Error to Critical;
Enum Definitions are updated.
CallManagerOnline
Severity level is Notice.
CodeRedEntry
Severity changed from Error to Critical.
CodeYellowEntry
Severity changed from Error to Critical.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
2-5
Chapter 2
New and Changed Information
Cisco Unified Communications Manager, Release 8.0(1)
Alarm Names
Alarm Changes
CodeYellowExit
Severity changed from Error to Notice.
ConferenceNoMoreResourcesAvailable
Changed severity level from Error to Warning.
ConnectionFailure
Severity level is Error (3).
DBLException
Severity changed from Error to Alert.
DChannelISV
Severity changed from Informational to Notice
DChannelOOS
Severity changed from Error to Critical.
DaTimeOut
Severity changed from Error to Warning.
DatabaseDefaultsRead
Severity changed from Notice to Informational.
DeviceApplyConfigInitiated
Severity level is Informational.
DeviceCloseMaxEventsExceeded
Severity level is Error (3).
DeviceDnInformation
Severity level is Informational (6).
DeviceInitTimeout
Severity level is Error (3)
DevicePartiallyRegistered
Following information is updated:
DeviceRegistered
DeviceResetInitiated
DeviceRestartInitiated
DeviceTransientConnection
•
Enum Definitions for performance monitor
object type
•
Enum Definitions for DeviceType
Following information is updated:
•
Enum Definitions for Performance Monitor
ObjType
•
Enum Definitions for Device type
•
Enum Definitions for IPAddrAttributes
•
Enum Definitions for IPV6AddrAttributes
•
Enum Definitions for DeviceType are updated.
•
Parameters added: Product type [String]
•
Enum Definitions for DeviceType are updated.
•
Parameters added: Product type [String]
•
Severity changed from Error to Warning.
•
Following information is updated:
– Enum Definitions for DeviceType
– Enum Definitions
– Enum Definitions for IPAddrAttributes
– Enum Definitions for IPV6AddrAttributes
DeviceTypeMismatch
Following information is updated:
•
Enum Definitions for DBDeviceType
•
Enum Definitions for DeviceType
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
2-6
OL-20105-01
Chapter 2
New and Changed Information
Cisco Unified Communications Manager, Release 8.0(1)
Alarm Names
Alarm Changes
DeviceUnregistered
•
Severity changed from Error to Warning.
•
Following information is updated:
– Enum Definitions for DeviceType
– Enum Definition
– Enum Definitions for IPAddrAttributes
– Enum Definitions for IPV6AddrAttributes
EndThrottlingCallListBLFSubscriptions
H323Started
Severity changed from Warning to Informational.
•
Severity changed from Informational to Notice.
•
Following information is updated:
– Parameters
– Enum Definitions for DeviceType
H323Stopped
Following information is updated:
•
Parameters
•
Enum Definitions for DeviceType
ICTCallThrottlingEnd
Severity changed from Error to Notice.
ICTCallThrottlingStart
Severity level is Error (3).
MGCPGatewayGainedComm
Severity changed from Informational to Notice.
MaliciousCall
Severity changed from Informational to Warning.
MaxCallDurationTimeout
•
Severity changed from Informational to Notice.
•
Following parameters added:
– Originating Device name(String)
– Destination Device name(String)
– Call start time(UInt)
– Call stop time(UInt)
– Calling Party Number(String)
– Called Party Number(String)
MaxCallsReached
Severity changed from Error to Critical.
MaxHoldDurationTimeout
Following parameters added:
•
Originating Device Name(String)
•
Destination Device Name(String)
•
Hold start time(UInt)
•
Hold stop time(UInt)
•
Calling Party Number(String)
•
Called Party Number(String)
MediaResourceListExhausted
Enum Definitions for MediaResourceType is
updated.
MohNoMoreResourcesAvailable
Severity changed from Error to Warning.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
2-7
Chapter 2
New and Changed Information
Cisco Unified Communications Manager, Release 8.0(1)
Alarm Names
MtpNoMoreResourcesAvailable
Alarm Changes
•
Severity changed from Error to Warning.
•
Media Resource List Name parameter added.
MultipleSIPTrunksToSamePeerAndLocalPort Severity level is Error.
NoFeatureLicense
NotEnoughChans
Severity changed from Error to Emergency.
•
Severity changed from Error to Warning.
•
Device Name(String) is the only parameter.
NumDevRegExceeded
Severity level is Error (3).
PktCapOnDeviceStarted
Severity level is Informational (6).
PktCapOnDeviceStopped
Severity level is Informational (6).
PktCapServiceStarted
Severity level is Informational (6).
PktCapServiceStopped
Severity level is Informational (6).
RouteListExhausted
Severity level is Warning.
RsvpNoMoreResourcesAvailable
Media Resource List Name(String) parameter is
added.
SDLLinkISV
Severity changed from Informational to Notice.
SDLLinkOOS
Severity changed from Error to Alert.
SIPLineRegistrationError
SIPStarted
•
Severity changed from Error to Warning.
•
Enum Definitions for DeviceType are updated.
•
Enum Reasons table is updated
•
Severity changed from Informational to Notice.
•
Enum Definitions for InTransportType and
OutTransportType are updated
SIPStopped
Enum Definitions for InTransportType and
OutTransportType are updated.
StationAlarm
Severity level is Informational (6).
StationConnectionError
StationEventAlert
StationTCPInitError
•
Reason Code[Enum] parameter added.
•
Enum Definitions for Reason Code table added.
Severity changed from Error to Warning.
•
Severity changed from Error to Critical.
•
Following parameters are removed:
– Error Number [String]
– ErrorCode [Int]
TimerThreadSlowed
UserUserPrecedenceAlarm
Severity changed from Warning to Critical.
•
Severity changed from Error to Warning.
•
Enum definitions updated.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
2-8
OL-20105-01
Chapter 2
New and Changed Information
Cisco Unified Communications Manager, Release 8.0(1)
•
CDRRep Alarm Catalog—The following existing CDRRep alarms are updated:
Alarm Name
Alarm Changes
CDRAgentSendFileFailed
Changed Data Collector Routing List element to Alert
Manager.
CDRAgentSendFileFailureContinues
Severity level is Error (3).
CDRFileDeliveryFailed
Changed Data Collector Routing List element to Alert
Manager.
CDRFileDeliveryFailureContinues
Severity level is Error (3).
CDRHWMExceeded
Changed Data Collector Routing List element to Alert
Manager.
CDRMaximumDiskSpaceExceeded
Facility and sub-facility changed. Added Routing List and
changed Data Collector to Alert Manager.
•
Certificate Monitor Alarm Catalog—The following new Certificate Monitor alarms are added:
Alarm Name
Description
CertValidLessthanADay
Certificate is about to expire in less than 24 hours or has expired.
CertValidfor7days
Alarm indicates that the certificate has expired or expires in less
than seven days.
CertValidityOver30Days
Alarm indicates that the certificate expiry is approaching but the
expiry date is more than 30 days.
CertValidLessThanMonth
Alarm indicates that the certificate will expire in 30 days or less.
•
CMI Alarm Catalog—The following new CMI alarms are added:
Alarm Name
Description
CMIException
Error while reading the database.
CMIServiceStatus
CMI service is running and working properly.
DBLException
Unable to connect to the database.
InvalidPortHandle
The handle for the opened serial port is invalid.
MemAllocFailed
CMI tried to allocate memory and failed.
ParityConfigurationError
The CMI service parameter, Parity, has an invalid configuration.
ReadingFileFailure
CMI failed to read SMDI messages from the serial port.
SMDICmdError
CMI receives an invalid incoming SMDI message.
SMDIMessageError
SMDI message contains invalid DN.
SerialPortGetStatusError
When CMI tries to get the status of serial port, the operating
system returns an error.
SerialPortOpeningError
When CMI tries to open the serial port, the operating system
returns an error.
SerialPortSetStatusError
When CMI tries to set the status of serial port, the operating
system returns an error.
StopBitConfigurationError
The Cisco Messaging Interface service parameter, Stop Bits, has
an invalid configuration.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
2-9
Chapter 2
New and Changed Information
Cisco Unified Communications Manager, Release 8.0(1)
Alarm Name
Description
ThreadKillingError
An error occurred when CMI tried to stop the CMI service.
UnknownException
Unknown error while connecting to database.
VMDNConfigurationError
The Voice Mail DN for CMI is invalid.
WritingFileFailure
CMI failed to write SMDI messages to the serial port.
•
CTI Manager Alarm Catalog—The following new CTI Manager alarms are added:
Alarm Name
Description
ApplicationConnectionDropped
Application has dropped the connection to
CTIManager.
ApplicationConnectionError
CTIManager is unable to allow connections from
Applications.
CtiDeviceClosed
Application closed a device.
CtiDeviceInService
Device is back in service.
CtiDeviceOpenFailure
Application is unable to open the device.
CtiDeviceOpened
Application opened a device.
CtiDeviceOutofService
Device is out of service.
CtiIncompatibleProtocolVersion
Incompatible protocol version.
CtiLineClosed
Application closed the line.
CtiLineInService
Line is back in service.
CtiLineOpenFailure
Application is unable to open the line.
CtiLineOpened
Application opened the line.
CtiLineOpened
Line is out of service.
CtiMaxConnectionReached
Maximum number of CTI connections has been
reached, no new connection will be accepted unless an
existing connection is closed.
CtiProviderCloseHeartbeatTimeout
CTI heartbeat timeout occurred causing CTIManager to
close the application connection.
CtiProviderClosed
CTI application closed the provider. The IP address is
shown in either IPv4 or IPv6 format depending on the
IP addressing mode of the application.
CtiProviderOpenFailure
CTI application is unable to open the provider. The IP
address is shown in either IPv4 or IPv6 format
depending on the IP addressing mode of the
application.
CtiProviderOpened
CTI Application opened the provider successfully. The
IP address is shown in either IPv4 or IPv6 format
depending on the IP addressing mode of the
Application.
CtiQbeFailureResponse
The requested operation from the application could not
be performed because of a normal or abnormal
condition.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
2-10
OL-20105-01
Chapter 2
New and Changed Information
Cisco Unified Communications Manager, Release 8.0(1)
Alarm Name
Description
InvalidQBEMessage
QBE PDU from application is invalid.
MaxDevicesPerNodeExceeded
An application has opened more devices than the limit
set in the CTIManager service parameter, Maximum
Devices Per Node.
MaxDevicesPerProviderExceeded
An application has opened more devices than the limit
set in the CTIManager service parameter, Maximum
Devices Per Provider.
RedirectCallRequestFailed
CTIManager is unable to redirect a call.
UnableToRegisterwithCallManagerService
CTI cannot communicate with Cisco CallManager
service to register supplementary service features.
UnableToSetorResetMWI
An error occurred when setting the message waiting
indication (MWI) lamp.
•
DB Alarm Catalog—The following existing DB alarms are updated:
Alarm Name
Alarm Changes
ErrorChangeNotifyClientBlock
Changed severity level to Critical from Error.
ErrorReadingInstalledRPMS
Severity level is Error (3).
IDSEngineCritical
Changed severity level to Error from Critical.
IDSEngineDebug
Changed severity level to Informational from Debug.
IDSReplicationInformation
Severity level is Informational.
•
DRF Alarm Catalog—The following new DRF alarms are added:
–DRFBackupCompleted—DRF backup completed successfully.
–DRFLocalDeviceError—DRF unable to access local device.
–DRFNoBackupTaken—A valid backup of the current system was not found after an Upgrade,
Migration, or Fresh Install.
–DRFRestoreCompleted—DRF restore completed successfully.
•
IMS Alarm Catalog—The following existing IMS alarms are updated:
Alarm Name
Alarm Changes
AdminPassword
Severity level is Informational.
authAdminLock
Severity level is Warning (4).
authExpired
Added Routing List element and updated the parameter list.
authFail
Changed severity level from Notice to Warning.
authHackLock
Updated the parameter list.
authInactiveLock
Updated the parameter list.
authLdapInactive
Severity level is Warning (4).
authMustChange
authSuccess
•
Parameter list is updated.
•
Routing List element is added.
Severity level is Informational (6).
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
2-11
Chapter 2
New and Changed Information
Cisco Unified Communications Manager, Release 8.0(1)
Alarm Name
Alarm Changes
credFullUpdateFailure
Severity level is Informational (6).
credFullUpdateSuccess
Severity level is Informational (6).
credReadFailure
Changed severity level to Notice from Informational. Updated
parameter list and added Routing List element.
credReadSuccess
Severity level is Informational (6).
credUpdateFailure
Severity level is Informational (6).
credUpdateSuccess
Severity level is Informational (6).
•
IpVms Alarm Catalog—The following new IpVms alarm is added:
–kANNAudioFileMissing—Announcement file not found. 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.
Changed Alarms in IpVms Alarm Catalog
The following existing IpVms alarms are updated:
Alarm Name
Alarm Changes
ANNDeviceRecoveryCreateFailed
Added Routing List elements and Parameters.
CFBDeviceRecoveryCreateFailed
Added Routing List elements and Parameters.
MOHDeviceRecoveryCreateFailed
Severity changed from Error to Warning.
MTPDeviceRecoveryCreateFailed
Changed severity level from Error to Warning and
added existing Routing List elements and
Parameters.
SoftwareLicenseNotValid
Severity changed from Error to Warning.
SoftwareLicenseValid
Severity—Informational.
kANNAudioCreateDirFailed
kANNAudioUndefinedAnnID
kANNAudioUndefinedLocale
kANNDeviceRecordNotFound
kANNDeviceStartingDefaults
•
Severity changed from Error to Warning.
•
Parameter list updated.
•
Severity changed from Error to Warning.
•
Parameter list removed.
•
Severity changed from Error to Warning.
•
Parameter list is updated.
Severity changed from Warning to Error.
•
Severity changed from Informational to
Warning.
•
Parameter list added.
kANNICMPErrorNotification
Parameter list updated.
kCFBDeviceRecordNotFound
Severity changed from Informational to Error.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
2-12
OL-20105-01
Chapter 2
New and Changed Information
Cisco Unified Communications Manager, Release 8.0(1)
Alarm Name
Alarm Changes
kCFBDeviceStartingDefaults
•
Severity changed from Informational to
Warning.
•
New parameters added:
– Parameter Name(String)
– Value Used(String)
kCFBICMPErrorNotification
Following parameters are removed:
Call ID [ULong] Party ID [ULong] IP Port
[ULong]
kChangeNotifyServiceCreationFailed
•
Severity changed from Error to Warning.
•
Following parameters added:
– OS Error Code(Int)
– OS Error Description(String)
kChangeNotifyServiceGetEventFailed
•
Severity changed from Error to Warning.
•
Following parameters added:
– OS Error Code(Int
– OS Error Description(String)
kChangeNotifyServiceRestartFailed
•
Severity changed from Error to Warning.
•
Following parameters added:
– OS Error Code(Int)
– OS Error Description(String)
kCreateAudioSourcesFailed
Following parameters added:
– OS Error Code(Int)
– OS Error Description(String)
kCreateControlFailed
Following parameters added:
– OS Error Code(Int)
– OS Error Description(String)
kDeviceDriverError
Severity changed from Error to Warning.
kDeviceMgrCreateFailed
Severity changed from Error to Warning.
kDeviceMgrExitEventCreationFailed
Severity changed from Error to Warning.
kDeviceMgrLockoutWithCallManager
Severity changed from Error to Informational.
kDeviceMgrMoreThan50SocketEvents
Severity changed from Informational to Notice.
kDeviceMgrOpenReceiveFailedOutOfStreams
Severity changed from Error to warning.
kDeviceMgrRegisterKeepAliveResponseError
Severity changed from Error to Warning.
kDeviceMgrRegisterWithCallManager
Severity level is Informational (6).
kDeviceMgrRegisterWithCallManagerError
Severity changed from Error to Warning.
kDeviceMgrSocketDrvNotifyEvtCreateFailed
Severity changed from Error to Warning.
kDeviceMgrSocketDrvNotifyEvtCreateFailed
Severity changed to Warning from Error.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
2-13
Chapter 2
New and Changed Information
Cisco Unified Communications Manager, Release 8.0(1)
Alarm Name
Alarm Changes
kDeviceMgrStartTransmissionOutOfStreams
Severity changed from Error to Warning.
kDeviceMgrThreadWaitFailed
•
Severity changed from Error to Informational.
•
Following parameters added:
– OS Error Code [Int]
– OS Error Description [String]
kDeviceMgrThreadxFailed
•
Severity changed from Error to Warning.
•
Following parameters added:
– OS Error Code[Int]
– OS Error Description [String]
kDeviceMgrUnregisterWithCallManager
kFixedInputCodecStreamFailed
Severity level is Informational (6).
•
Severity changed from Error to Warning.
•
Following parameters removed:
– Audio Source ID [ULong]
– System error code [ULong]
kFixedInputCreateControlFailed
kFixedInputCreateSoundCardFailed
kFixedInputInitSoundCardFailed
•
Severity changed from Error to Warning.
•
Audio Source ID [ULong] parameter is
removed.
•
Severity changed from Error to Warning.
•
Audio Source ID [ULong] parameter is
removed
•
Severity changed from Error to Warning.
•
Following parameters are removed:
– Audio Source ID [ULong]
– System error code [ULong]
kFixedInputTranscoderFailed
•
Severity changed from Error to Warning.
•
Following parameters are removed:
– Audio Source ID [ULong
– System error code [ULong]
kGetFileNameFailed
•
Severity changed from Error to Warning.
•
Audio Source ID [ULong] parameter is
removed.
kIPVMSDeviceDriverNotFound
This alarm is available in 8.0(1).
kIPVMSMgrEventCreationFailed
Severity changed from Error to Warning.
kIPVMSMgrThreadxFailed
Severity changed from Error to Warning.
kIPVMSMgrWrongDriverVersion
Following parameters are removed:
•
Found [ULong]
•
Need [ULong]
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
2-14
OL-20105-01
Chapter 2
New and Changed Information
Cisco Unified Communications Manager, Release 8.0(1)
Alarm Name
Alarm Changes
kIPVMSStarting
ProcessID [ULong] parameter is removed.
kIPVMSStopping
ProcessID [ULong] parameter is removed.
kIpVmsMgrNoLocalHostName
Severity level is Error (3).
kIpVmsMgrNoLocalNetworkIPAddr
Severity level is Error (3).
kIpVmsMgrThreadWaitFailed
Severity changed from Error to Warning.
kMOHBadMulticastIP
Severity changed to Warning from Error.
Following parameters are removed:
•
Audio Source ID [ULong]
•
Call/Conference ID [ULong]
•
Multicast IP Port [ULong]
kMOHDeviceRecordNotFound
Severity changed from Informational to Warning.
kMOHICMPErrorNotification
Following parameters are removed:
kMOHMgrCreateFailed
•
Call ID [ULong] Party ID [ULong] IP Port
[ULong]
•
Severity changed from Error to Warning.
•
OS Error Description(String) parameter is
added.
kMOHMgrExitEventCreationFailed
Severity changed from Error to Warning.
kMOHMgrIsAudioSourceInUseThisIsNULL
Severity level is Informational (6).
kMOHMgrThreadWaitFailed
kMOHMgrThreadxFailed
kMOHRewindStreamControlNull
kMOHRewindStreamMediaPositionObjectNull
kMOHTFTPGoRequestFailed
•
Severity changed from Error to Informational.
•
OS Error Description(String) parameter is
added.
•
Severity changed from Error to Warning.
•
OS Error Description(String) parameter is
added
•
Severity changed from Error to Informational.
•
Audio Source ID [ULong] parameter is
removed.
•
Severity changed from Error to Informational.
•
Audio Source ID [ULong] parameter is
removed.
Following parameters added:
Error Description [String] Source Path [String]
Destination Path [String] OS Error Code [Int]
OS Error Description [String]
kMTPDeviceRecordNotFound
Severity changed from Informational to Warning.
kMTPDeviceStartingDefaults
MTP Run Flag(String) parameter is added.
kPWavMgrThreadxFailed
Severity level is Error (3).
kReadCfgIpTosMediaResourceToCmNotFound Severity level is Informational (6).
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
2-15
Chapter 2
New and Changed Information
Cisco Unified Communications Manager, Release 8.0(1)
Alarm Name
Alarm Changes
kReadCfgMOHEnabledCodecsNotFound
Severity level is Informational (6).
kReadCfgUserLocaleEnterpriseSvcParm
Severity level is Error (3).
kRequestedANNStreamsFailed
Following parameters are removed:
Requested streams [ULong] Allocated
streams [ULong]
kRequestedCFBStreamsFailed
Severity changed from Error to Warning.
kRequestedMOHStreamsFailed
Severity changed from Error to Warning.
kRequestedMTPStreamsFailed
Severity changed from Error to Warning.
•
JavaApplications Alarm Catalog—The following new JavaApplications alarms are added:
–CiscoHardwareLicenseInvalid—Installation on invalid or obsolete hardware. Cannot upload
license files.
–CiscoLicenseFileInvalid—License File is invalid.
Changed Alarms in JavaApplications Alarm Catalog
The following existing JavaApplications Alarms are updated:
–IPMAFilteringDown—Severity level is Error (3).
–WDStopped—Severity changed from Alert to Warning.
•
Login Alarm Catalog—The following existing Login Alarm is updated:
–AuthenticationFailed—Severity Changed from Error to Warning.
•
LpmTct Alarm catalog—The following existing Login Alarms are updated:
Alarm Name
Description
CoreDumpFileFound
Severity level is Critical.
LogCollectionJobLimitExceeded Severity changed from Informational to Warning.
LogFileSearchStringFound
Severity level is Informational.
LogPartitionHighWaterMarkExc Severity changed from Error to Critical.
eeded
LogPartitionLowWaterMarkExc
eeded
Severity changed from Error to Warning.
SparePartitionHighWaterMarkE
xceeded
Severity changed from Error to Warning.
Note
Spare Partition is not used for Intercompany Media
Engine server. So this alert will not be triggered for
Intercompany Media Engine
SparePartitionLowWaterMarkEx Severity level is Error (3).
ceeded
Note
Spare Partition is not used for Intercompany Media
Engine server. So this alert will not be triggered for
Intercompany Media Engine
•
RTMT Alarm Catalog—The following new RTMT alarms are added:
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
2-16
OL-20105-01
Chapter 2
New and Changed Information
Cisco Unified Communications Manager, Release 8.0(1)
–RTMT_ALERT—A Real-Time Monitoring Tool (RTMT) process in the AMC service uses the
alarm mechanism to facilitate delivery of RTMT alerts in the RTMT AlertCentral or through email.
•
SystemAccess Alarm catalog—The following existing System Access Alarms are updated:
–TotalProcessesAndThreadsExceededThresholdEnd—Severity changed from Informational to
Notice.
•
TFTP Alarm catalog—The following existing TFTP Alarms are updated:
Alarm Name
Description
CNFFBuffWriteToFilefopenfailed
Severity changed from Informational to Error.
CNFFBuffWriteToFilefwritefailed
Severity changed from Informational to Error.
ConfigItAllBuildFilesFailed
Severity changed from Informational to Error.
ConfigItAllReadConfigurationFailed
Severity changed from Informational to Error.
ConfigThreadBuildFileFailed
Severity changed from Informational to Error.
ConfigThreadCNCMGrpBuildFileFailed
Severity changed from Informational to Error.
ConfigThreadCNGrpBuildFileFailed
Severity changed from Informational to Error.
ConfigThreadChangeNotifyServerInstanceFailed Severity changed from Error to Alert.
ConfigThreadChangeNotifyServerSingleFailed
Severity changed from Error to Alert.
ConfigThreadChangeNotifyServerStartFailed
Severity changed from Error to Alert.
ConfigThreadReadConfigurationFailed
Severity changed from Informational to Error.
CreateThreadFailed
Severity changed from Error to Alert.
NoCallManagerFound
Severity changed from Error to Warning.
SDIControlLayerFailed
Severity changed from Critical to Alert.
For more information on alarms, see Cisco Unified Serviceability Alarms and CiscoLog Messages,
page 6-1.
Obsolete Alarms
The following alarms are obsoleted in this release:
Call Manager Catalog
•
ConferenceCreated
•
ConferenceDeleted
•
CtiCallAcceptTimeout
•
CtiStaleCallHandle
•
DatabaseAuditInfo_074
•
DatabaseDeviceNoDirNum
•
DatabaseInternalDataError_06e
•
DatabaseInternalDataError_06f
•
DatabaseInternalDataError_070
•
DatabaseInternalDataError_071
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
2-17
Chapter 2
New and Changed Information
Cisco Unified Communications Manager, Release 8.0(1)
•
DatabaseInternalDataError_072
•
DatabaseInternalDataError_073
•
DatabaseInternalDataError_075
•
DnTimeout
•
GatewayAlarm
•
H323AddressResolutionError
•
H323CallFailureAlarm
•
MWIParamMisMatch
•
NoConnection
•
OutOfDnForAutoRegistration
•
PktCapDownloadFailed
•
PktCapDownloadOK
•
PktCapLoginFailed
•
PktCapLoginOK
•
Redirection
•
SIP IPPortConflict
•
ThrottlingSampleActivity
•
TotalCodeYellowEntry
CertMonitor Alarm Catalog
•
CertExpired
•
CertExpiryApproaching
•
CertExpiryDebug
•
CertExpiryError
CMI Alarm Catalog
•
CCMConnectionError
•
CMIDebugAlarm
•
CMIServiceStarted
•
CMIServiceStopped
•
COMException
•
ConfigParaNotFound
•
DisconnectionToCCM
•
WSAStartupFailed
CTI Manager Alarm Catalog
•
kCtiDeviceOpenFailAccessDenied
•
kCtiDirectoryLoginFailure
•
kCtiEnvProcDevListRegTimeout
•
kCtiExistingCallNotifyArrayOverflow
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
2-18
OL-20105-01
Chapter 2
New and Changed Information
Cisco Unified Communications Manager, Release 8.0(1)
•
kCtiIllegalEnumHandle
•
kCtiIllegalFilterSize
•
kCtiIllegalQbeHeader
•
kCtiInvalidQbeSizeAndOffsets
•
kCtiLineCallInfoResArrayOverflow
•
kCtiLineOpenFailAccessDenied
•
kCtiMYTCPSendError
•
kCtiMytcpErrSocketBroken
•
kCtiNewCallNotifyArrayOverflow
•
kCtiNullTcpHandle
•
kCtiProviderOpenInvalidUserNameSize
•
kCtiQbeLengthMisMatch
•
kCtiQbeMessageTooLong
•
kCtiSdlErrorvException
•
kCtiSsRegisterManagerErr
•
kCtiTcpInitError
•
kCtiUnknownConnectionHandle
DB Alarm Catalog
•
ErrorChangeNotifyReconcile
IpVms Alarm Catalog
•
kANNAudioComException
•
kANNAudioOpenFailed
•
kANNAudioTftpFileMissing
•
kANNAudioTftpMgrCreate
•
kANNAudioTftpMgrStartFailed
•
kANNAudioThreadException
•
kANNAudioThreadWaitFailed
•
kANNAudioThreadxFailed
•
kANNAudioXmlLoadFailed
•
kANNAudioXmlSyntax
•
kAddIpVmsRenderFailed
•
kCfgListComException
•
kCfgListDblException
•
kCfgListUnknownException
•
kCreateGraphManagerFailed
•
kDeviceMgrThreadException
•
kDownloadMOHFileFailed
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
2-19
Chapter 2
New and Changed Information
Cisco Unified Communications Manager, Release 8.0(1)
•
kFixedInputAddAudioCaptureDeviceFailed
•
kFixedInputAddG711AlawIpVmsRenderFailed
•
kFixedInputAddG711UlawIpVmsRenderFailed
•
kFixedInputAddG729IpVmsRenderFailed
•
kFixedInputAddMOHEncoderFailed
•
kFixedInputAddWideBandIpVmsRenderFailed
•
kFixedInputAudioCapMOHEncoderConnFailed
•
kFixedInputAudioCaptureCreateFailed
•
kFixedInputClassEnumeratorCreateFailed
•
kFixedInputCreateGraphManagerFailed
•
kFixedInputFindAudioCaptureDeviceFailed
•
kFixedInputGetEventNotificationFailed
•
kFixedInputGetFileNameFailed
•
kFixedInputGetG711AlawIpVmsRendInfFailed
•
kFixedInputGetG711AlawIpVmsRenderFailed
•
kFixedInputGetG711UlawIpVmsRendInfFailed
•
kFixedInputGetG711UlawIpVmsRenderFailed
•
kFixedInputGetG729IpVmsRendInfFailed
•
kFixedInputGetG729IpVmsRenderFailed
•
kFixedInputGetMOHEncoderFailed
•
kFixedInputGetMediaControlFailed
•
kFixedInputGetMediaPositionFailed
•
kFixedInputGetWideBandIpVmsRendInfFailed
•
kFixedInputGetWideBandIpVmsRenderFailed
•
kFixedInputMOHEncG711AlawRenderConnFail
•
kFixedInputMOHEncG711UlawRenderConnFail
•
kFixedInputMOHEncG729RenderConnFailed
•
kFixedInputMOHEncWidebandRenderConnFail
•
kFixedInputSetNotifyWindowFailed
•
kGetEventNotificationFailed
•
kGetIpVmsRenderFailed
•
kGetIpVmsRenderInterfaceFailed
•
kGetMediaControlFailed
•
kGetMediaPositionFailed
•
kMOHFilterNotifyError
•
kMOHMgrThreadCreateWindowExFailed
•
kMOHPlayStreamControlNull
•
kMOHPlayStreamMediaControlObjectNull
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
2-20
OL-20105-01
Chapter 2
New and Changed Information
Cisco Unified Communications Manager, Release 8.0(1)
•
kMOHThreadException
•
kMTPICMPErrorNotification
•
kPWavMgrExitEventCreateFailed
•
kPWavMgrThreadException
•
kReadCfgANNComException
•
kReadCfgANNDblException
•
kReadCfgANNListComException
•
kReadCfgANNListDblException
•
kReadCfgANNListUnknownException
•
kReadCfgANNUnknownException
•
kReadCfgCFBComException
•
kReadCfgCFBDblException
•
kReadCfgCFBListComException
•
kReadCfgCFBListDblException
•
kReadCfgCFBListUnknownException
•
kReadCfgCFBUnknownException
•
kReadCfgDblGetChgNotifyFailed
•
kReadCfgDblGetNodeNameFailed
•
kReadCfgEnterpriseComException
•
kReadCfgEnterpriseDblException
•
kReadCfgEnterpriseException
•
kReadCfgEnterpriseUnknownException
•
kReadCfgMOHAudioSourceComException
•
kReadCfgMOHAudioSourceDblException
•
kReadCfgMOHAudioSourceUnknownException
•
kReadCfgMOHComException
•
kReadCfgMOHDblException
•
kReadCfgMOHListComException
•
kReadCfgMOHListDblException
•
kReadCfgMOHListUnknownException
•
kReadCfgMOHServerComException
•
kReadCfgMOHServerDblException
•
kReadCfgMOHServerUnknownException
•
kReadCfgMOHTFTIPAddressNotFound
•
kReadCfgMOHUnknownException
•
kReadCfgMTPComException
•
kReadCfgMTPDblException
•
kReadCfgMTPListComException
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
2-21
Chapter 2
New and Changed Information
Cisco Unified Communications Manager, Release 8.0(1)
•
kReadCfgMTPListDblException
•
kReadCfgMTPListUnknownException
•
kReadCfgMTPUnknownException
•
kRenderFileFailed
•
kSetNotifyWindowFailed
Test Alarm Catalog
•
TestAlarmWindows
Cisco Unified Real-Time Monitoring Tool
This section contains the following subsections:
•
New Perfmon Counters, page 2-22
New Perfmon Counters
New perfmon counters are added for the following objects:
•
Cisco CallManager External Call Control—This feature provides information about the counters
that are added to support the External Call Control feature. Table 2-1 contains information about the
External Call Control counters.
Table 2-1
Cisco CallManager External Call Control
Counters
Counter Description
Cisco CallManager Object
ExternalCallControlEnabledCallsAttempted
This counter specifies the total number of calls to devices that
have the External Call Control feature enabled. This is a cumulative count of all calls to intercept-enabled patterns or DNs
since the last restart of the Cisco CallManager service.
ExternalCallControlEnabledCallsCompleted
This counter specifies the total number of calls that were
connected to a device that had the External Call Control feature
enabled. This is a cumulative count of all calls to intercept-enabled patterns or DNs since the last restart of the Cisco CallManager service.
ExternalCallControlEnabledFailureTreatmentApplied
This counter specifies the total number of calls that were cleared
or routed based on failure treatments (such as Allow or Deny)
that are defined in the External Call Control profile.
External Call Control Objects
PDPServersTotal
This counter defines the total number of PDP servers in all
External Call Control Profiles configured in Cisco Unified CM
Administration. This counter increments when a new PDP
server is added and decrements when a PDP server is removed.
PDPServersInService
This counter defines the total number of in-service (active) PDP
servers.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
2-22
OL-20105-01
Chapter 2
New and Changed Information
Cisco Unified Communications Manager, Release 8.0(1)
Table 2-1
Cisco CallManager External Call Control
Counters
Counter Description
PDPServersOutOfService
This counter defines the total number of times that PDP servers
have transitioned from in-service to out-of-service. This is a cumulative count of out-of-service PDP servers since the last
restart of the Cisco CallManager service.
ConnectionsActiveToPDPServer
This counter specifies the total number of connections that
Cisco Unified Communications Manager has established (currently active) with PDP servers.
ConnectionsLostToPDPServer
This counter specifies the total number of times that active connections between Cisco Unified Communications Manager and
the PDP servers were disconnected. This is a cumulative count
since the last restart of the Cisco CallManager service.
•
Cisco CallManager SAF—The Cisco SAF Client object provides information about SAF counters
that are specific to each node. Table 2-2 contains information about Cisco SAF Client object
counters.
Table 2-2
Note
Cisco CallManager SAF Client Object
Counters
Counter Description
SAFConnectionsSucceeded
(range from 0 to 2)
Total number of SAF client connections currently active on this
Unified CM node.
SAFFConnectionsFailed
(range from 0 to 2)
Total number of SAF client connections that failed on the Unified CM
node. A failed connection is a connection that did not register with the
SAF Forwarder.
A Cisco Unified CM node restart causes a counter reset.
•
Cisco Extension Mobility—The Cisco Extension Mobility object provides information about the
extension mobility application. Table 2-3 contains information about the newly added
Cisco Extension Mobility counters.
Table 2-3
Cisco Extension Mobility Application
Counters
Counter Description
Total Number of EMCC Messages
This represents the total number of messages related to EMCC
Requests that came from remote clusters.
Number of Remote Devices
This represents the total number of devices from other clusters
that are currently using a EMCC Base Device (EMCC Logged
in).
Number of Unknown Remote Users
This represents the total number of users who were not found
in any of the remote cluster during inter-cluster extension
mobility login.
Active Inter-cluster Sessions
This represents the total number of inter cluster Extension
Mobility requests that are currently in progress.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
2-23
Chapter 2
New and Changed Information
Cisco Unified Communications Manager, Release 8.0(1)
Table 2-3
Cisco Extension Mobility Application (continued)
Counters
Counter Description
Total Number of Remote Users
This represents the total number of users from other cluster
who use a local device of this cluster and have logged into a
remote cluster.
EMCC Check User Requests
Handled
This represents the total number of EMCC check user requests
that came from remote clusters.
•
Cisco Feature Control Policy—The Cisco Feature Control feature provides information about the
two new counters for TFTP. Table 2-4 contains information about the newly added Cisco Feature
Control Policy feature counters.
Table 2-4
Cisco Feature Control Policy
Counters
Counter Description
BuildFeaturePolicyCount
Indicates the number of built FCP files
FeaturePolicyChangeNotifications
Indicates the number of sent FCP change notifications
•
Cisco IME Server—The Cisco IME Server provides information about the Performance Object and
Counters for IME.
The following contains the Performance Object for Cisco IME Server:
VAPStatus (range from 0 to 2)—This flag indicates the overall health of the connection to the IME
servers for a particular IME service. If 1, it means that Unified CM has successfully established a
connection to its primary and, if configured, backup servers for the IME service. 2 = Unhealthy.
0 = Unknown.
•
The following contains the Performance Counters for Cisco IME Server. Table 2-5 contains
information about the Performance Counters for Cisco IME Server.
Table 2-5
Cisco IME Server
Counters
Counter Description
PublishedRoutes
Total number of DIDs published successfully into the DHT across all
IME services. It is a dynamic measurement, and as such, gives you an
indication of your own provisioned usage in addition to a sense of how
successful the system has been in storing them into the network.
RejectedRoutes
Number of learned routes which were rejected because the number or
domain were blacklisted by the administrator. This provides an indication of the number of 'missed opportunities' - cases where a VoIP call
could happen in the future, but will not due to the blocked validation.
LearnedRoutes
Total number of distinct phone numbers which have been learned by
IME and are present as routes in Unified CM's routing tables. If this
number grows too large, it may exceed the per-cluster limit, and require
additional clusters for scale.
UniqueDomains
Number of unique domain names of peer enterprises discovered by
IME. It is an indicator of overall usage of the system.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
2-24
OL-20105-01
Chapter 2
New and Changed Information
Cisco Unified Communications Manager, Release 8.0(1)
Table 2-5
Cisco IME Server
Counters
Counter Description
FailedB2BLinkSetups
Total number of call attempts for which a IME route was available, but
which were set up through the PSTN due to a failure to connect to the
target over the IP network.
B2BLinkCallsAttempted
Number of calls initiated by UCM through IME. This includes calls
that are accepted, as well as busy, no-answer and failed calls. The
metric is strictly on initiation.
B2BLinkCallsSetup
Number of IME calls successfully placed by Unified CM and answered
by the remote party, resulting in an IP call.
FailedFallbackCalls
Total number of failed fallback attempts.
e164 DIDs Learned
Number of DIDs learned from the IME server.
B2BLinkCallsAccepted
Number of IME calls successfully received by UCM and answered by
the called party, resulting in an IP call.
B2BLinkCallsReceived
Number of calls received by Unified CM through IME. This includes
calls that are accepted, as well as busy, no-answer and failed calls. The
metric is strictly on initiation.
For more information, see the Cisco Unified Real-Time Monitoring Tool Administration Guide.
Cisco Unified CDR Analysis and Reporting
The functionality of Call Detail Records (CDR) Analysis and Reporting (CAR) is primarily to generate
reports on Unified CM users and system status with respect to call processing records that are loaded to
CAR database. CAR also does some CAR database management activities. CAR automatically
schedules required tasks to take place or you can manually perform the tasks by using the web interface.
This section contains the following subsections:
•
New Cisco CAR DB Alarms, page 2-25
•
New CAR Object and Counters, page 2-26
•
Hunt/CTI Integration for CAR Reporting, page 2-26
•
CAR and CDRM Alarm Interface, page 2-27
•
System-Wide Call Tracking End-to-End Call Trace, page 2-27
New Cisco CAR DB Alarms
New alarms for the CAR DB instance separation get added in this release. A new thread of
[CARIDSAlarm] gets created in the existing CAR Scheduler Service to receive the IDS alarms. There
are four new categories and alarms with information specific to the IDS based on the class IDs.
The following new alarms support the CAR database instance:
•
CARIDSEngineDebug—Indicates debug events from CAR IDS database engine. This alarm
provides low-level debugging information from CAR IDS database engine. System administrator
can disregard this alarm. Severity level is Debug(7).
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
2-25
Chapter 2
New and Changed Information
Cisco Unified Communications Manager, Release 8.0(1)
Note
•
CARIDSEngineInformation—No error has occurred but some routine event completed in CAR IDS
database engine. Severity level is Informational(6).
•
CARIDSEngineCritical—This alarm does not compromise data or prevent the use of the system but
does required attention. Severity level is Critical(2).
•
CARIDSEngineFailure—Combined alarm for emergency and error situations. Something
unexpected occurred that might compromise data or access to data or cause CAR IDS to fail.
Severity level is Error(3).
For any alarms with severity levels at or higher than Critical, an alert gets automatically generated.
For more information, see Cisco Unified CDR Analysis and Reporting Guide.
New CAR Object and Counters
The new CAR counters monitor the CAR database space and shared memory usage. The following CAR
counters for the Cisco CAR DB object get supported:
•
RootDBSpaceUsed—Percentage of Root DB space consumed. The root DB space gets used by the
IDS system tables in the CAR IDS instance.
•
CARDBSpaceUsed—Percentage of CAR DB space consumed. The CAR DB space gets used by the
CAR database.
•
CARTempDBSpaceUsed—Percentage of CAR temporary DB space consumed. The CAR
temporary DB space gets used by temporary tables in the CAR IDS instance and used by CAR
applications.
•
FreeSharedMemory—Total free and shared memory expressed in kilobytes (KB). Shared memory
gets used by the database system and all database applications in the CAR IDS instance.
•
UsedSharedMemory—Total used and shared memory expressed in kilobytes (KB). Shared memory
gets used by the database system and all database applications in the CAR IDS instance.
There are no performance counters that monitor the CAR IDS processes individually because the
counters get automatically added for each new process. The counters get implemented with a new
thread/job of the CAR IDS performance in the existing CAR Scheduler service by using Java API (JNI
based statsUpdate()).
Hunt/CTI Integration for CAR Reporting
CAR supports hunt groups and contains the following new reports:
•
Hunt Pilot Summary
•
Hunt Pilot Detailed Report
Hunt Pilot Summary
Only CAR administrators generate the Hunt Pilot Summary Report.The CDR Hunt Pilot Call Summary
report displays the call details for the specified hunt pilot. This report displays an only an overview of
the calls for the hunt pilots and hunt member information is not included. The CAR administrator can
generate report for a maximum of five hunt pilot DNs.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
2-26
OL-20105-01
Chapter 2
New and Changed Information
Cisco Unified Communications Manager, Release 8.0(1)
Hunt Pilot Detailed Report
Only CAR administrators generate the Hunt Pilot Detailed Call Report. This report displays call details
for a hunt pilot number or a hunt member DN.
CAR and CDRM Alarm Interface
CAR and CDRM allow the alarm interface to raise alerts. The alarm interface can generate Syslog
events, SNMP traps, and e-mail notifications by using RIS/Collector/Alert Manager. CAR allows the
performance interface to poll serviceability counters and to be monitored in Cisco Unified Real Time
Monitoring Tool.
System-Wide Call Tracking End-to-End Call Trace
The End-to-End Call Trace feature facilitates tracing calls that traverse multiple Cisco voice products,
such as Unified CM, Cisco IOS Gateways, and other products.
There are four new CDR fields added: CAR Loader, schema, CDR export, CDR search reports and
migration.
For more information about System-Wide Call Tracking (SCT), see End-to-End Call Trace, page 2-27.
Cisco Unified Call Detail Records
This feature traces calls that traverse multiple Cisco voice products by using the call records collected
from each platform generated for the same call.
This section contains information on the following topics:
•
End-to-End Call Trace, page 2-27
•
Remote Destination to Number Mapping and CDRs, page 2-28
•
New CDR Fields to Support Call Control Discovery, page 2-28
•
New CDR Fields to Support External Call Control, page 2-28
•
New CDR Support for iSAC Codec, page 2-29
•
New CDR Fields for Hunt List Support, page 2-30
End-to-End Call Trace
To support the End-to-End call trace, following new fields have been added in the CDR search reports:
•
IncomingProtocolID
•
IncomingProtocolCallRef
•
OutgoingProtocolID
•
OutgoingProtocolCallRef
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
2-27
Chapter 2
New and Changed Information
Cisco Unified Communications Manager, Release 8.0(1)
Remote Destination to Number Mapping and CDRs
For an outgoing call to mobile users, the called party information in the CDR gets recorded based on the
“Log Mobile Number in CDR” service parameter. The default equals False. If the service parameter is
False, the enterprise number of the mobile user gets recorded in the CDR as the called party number. If
the service parameter equals True, the mobile number gets recorded in CDR as the called party number.
New CDR Fields to Support Call Control Discovery
New codes display for the call control discovery feature, as described in Table 2-6. (For more
information on call control discovery, see Cisco Unified CDR Guide.)
Table 2-6
Codes for Call Control Discovery
Value
Type
Description
464
Redirect Reason Code
Indicates that the call is redirected to a PSTN failover
number
131
Call Termination Code
Call Control Discovery PSTN Failover (Cisco specific)
29
OnBehalfof Code
CCDRequestingService
New CDR Fields to Support External Call Control
Table 2-7 describes the new CDR fields for the external call control feature. Use Table 2-7 in
conjunction with the Table 2-8, which describes the routing reason values that are specific to external
call control. (For more information on external call control, see Cisco Unified CDR Guide.)
Table 2-7
CDR Fields for External Call Control
Field Name
Range of Values
Description
currentRoutingReason
Positive Integer
This field, which is used with the external
call control feature, displays the reason why
the call was intercepted for the current call.
For a list of reasons, see Table 2-8.
Default value is 0.
origRoutingReason
Positive Integer
This field, which is used with the external
call control feature, displays the reason why
the call was intercepted for the first time. For
a list of reasons, see Table 2-8.
Default value is 0.
lastRedirectingRoutingRe
ason
Positive Integer
This field, which is used with the external
call control feature, displays why the call
was intercepted for the last time. For a list of
reasons, see Table 2-8.
Default - Empty string.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
2-28
OL-20105-01
Chapter 2
New and Changed Information
Cisco Unified Communications Manager, Release 8.0(1)
Table 2-8 includes the reasons that can display for the currentRoutingReason, origRoutingReason, or
lastRedirectingRoutingReason fields.
Table 2-8
Routing Reason Values for External Call Control
Value that Displays
in the Field
Reason
Description
0
PDPDecision_NONE
This value indicates that the route
server did not return a routing directive
to the Cisco Unified Communications
Manager.
1
PDPDecision_Allow_Fulfilled
This value indicates that Cisco Unified
Communications Manager allowed a
call.
2
PDPDecision_Allow_Unfulfilled
This value indicates that Cisco Unified
Communications Manager disallowed
a call.
3
PDPDecision_Divert_Fulfilled
This value indicates that Cisco Unified
Communications Manager diverted the
call.
4
PDPDecision_Divert_Unfulfilled
This value indicates that Cisco Unified
Communications Manager was not
able to divert the call.
5
PDPDecision_Forward_Fulfilled
This value indicates that Cisco Unified
Communications Manager forwarded
the call.
6
PDPDecision_Forward_Unfulfilled
This value indicates that Cisco Unified
Communications Manager was unable
to forward the call.
7
PDPDecision_Reject_Fulfilled
This value indicates that Cisco Unified
Communications Manager rejected the
call.
8
PDPDecision_Reject_Unfulfilled
This value indicates that Cisco Unified
Communications Manager was not
able to reject the call.
CAR supports the new fields from the loader, CDR export, and CDR search reports on display and
migration.
New CDR Support for iSAC Codec
The codec fields can now support the iSAC (Media_Payload_ISAC) with the value of 89.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
2-29
Chapter 2
New and Changed Information
MIB Updates
New CDR Fields for Hunt List Support
Table 2-9 describes the new CDRs for the hunt list support (see Cisco Unified CDR Guide for more
information).
Table 2-9
CDR Fields for Hunt Lists
Field Name
Range of Values
Description
huntPilotDN
Text String
This field indicates the hunt pilot DN
through which the call is routed.
Default - Empty string.
huntPilotPartition
Text String
This field indicates the partition for the hunt
pilot DN.
Default - Empty string.
huntPilotDN
Text String
This field indicates the hunt pilot DN
through which the call is routed.
Default - Empty string.
Cisco Unified Reporting
There are no updates for Cisco Unified Reporting Guide in the Release 8.0(1).
MIB Updates
Table 2-10 lists the deprecated and replaced MIBs.
Table 2-10
Updated MIBs
Action
Description
Deprecated
CcmDevFailCauseCode;
Added CcmDevRegFailCauseCode and
CcmDevUnregCauseCode
Deprecated
ccmPhoneStatusReason;
Added ccmPhoneUnregReason and
ccmPhoneRegFailReason in ccmPhoneTable
Deprecated
ccmPhoneFailCauseCode;
Added ccmPhoneFailedRegFailReason in ccmPhoneFailedTable
Deprecated
ccmPhoneStatusUpdateReason;
Added ccmPhoneStatusUnregReason and
ccmPhoneStatusRegFailReason in ccmPhoneStatusUpdateTable
Deprecated
ccmGatewayStatusReason;
Added ccmGatewayUnregReason and
ccmGatewayRegFailReason in ccmGatewayTable.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
2-30
OL-20105-01
Chapter 2
New and Changed Information
MIB Updates
Table 2-10
Updated MIBs (continued)
Action
Description
Deprecated
ccmMediaDeviceStatusReason;
Added ccmMediaDeviceUnregReason and
ccmMediaDeviceRegFailReason in ccmMediaDeviceTable.
Deprecated
ccmCTIDeviceStatusReason;
Added ccmCTIDeviceUnregReason and
ccmCTIDeviceRegFailReason in ccmCTIDeviceTable
Deprecated
ccmH323DevStatusReason;
Added ccmH323DevUnregReason and ccmH323DevRegFailReason
in ccmH323DeviceTable.
Deprecated
ccmVMailDevStatusReason;
Added ccmVMailDevUnregReason and
ccmVMailDevRegFailReason in ccmVoiceMailDeviceTable.
Deprecated
ccmGatewayFailCauseCode;
Added ccmGatewayRegFailCauseCode in ccmNotificationsInfo.
Deprecated the following
Notification Type
ccmGatewayFailed and added ccmGatewayFailedReason.
Deprecated following
OBJECT_GROUPS
ccmPhoneInfoGroupRev5,
ccmNotificationsInfoGroupRev4, ccmGatewayInfoGroupRev3,
ccmMediaDeviceInfoGroupRev3, ccmCTIDeviceInfoGroupRev3,
ccmH323DeviceInfoGroupRev2,
ccmVoiceMailDeviceInfoGroupRev1 and
ccmNotificationsGroupRev2;
Added following OBJECT_GROUPS:
ccmPhoneInfoGroupRev6,
ccmNotificationsInfoGroupRev5,
ccmGatewayInfoGroupRev4,
ccmMediaDeviceInfoGroupRev4,
ccmCTIDeviceInfoGroupRev4,
ccmH323DeviceInfoGroupRev3,
ccmVoiceMailDeviceInfoGroupRev2,
ccmNotificationsGroupRev3.
Deprecated following
MODULE-COMPLIANCE
ciscoCcmMIBComplianceRev6;
Obsoleted following
OBJECT_GROUPS
ccmInfoGroupRev3,
Added ciscoCcmMIBComplianceRev7.
ccmH323DeviceInfoGroupRev1
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
2-31
Chapter 2
New and Changed Information
MIB Updates
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
2-32
OL-20105-01
CH A P T E R
3
Managing and Monitoring the Health of Cisco
Unified Communications Manager Systems
This chapter describes how to manage and monitor the health of Cisco Unified Communications
Manager (Cisco Unified CM) systems. It contains the following sections:
Note
•
Overview of Supported Interfaces, page 3-1
•
Critical Processes to Monitor, page 3-2
•
Available Supported MIBs, page 3-11
•
RTMT Monitoring of Cisco Unified CM System Health, page 3-12
•
Recovery, Hardware Migration, and Backup/Restore, page 3-26
•
Platform Monitoring, page 3-27
•
Software Configuration Management, page 3-33
•
Available Reports, page 3-34
•
General Health and Troubleshooting Tips, page 3-36
•
Related Documentation, page 3-44
Serviceability APIs (AXL/SOAP) that are used for serviceability queries and Administrative XML
(AXL) that are used as a provisioning read and write APIs are not covered in this document.
Overview of Supported Interfaces
The following interfaces are supported on Cisco Unified CM servers:
•
SNMP MIB/Trap—Supports polling and traps by using select MIBs from Cisco and the native
platforms.
•
SSH Secure Shell Client— Replaces telnet and ftp clients by using a more secure protocol. This
application encrypts the entire network session and can use public-key authentication.
•
Local and Remote Syslog—Contains types of platform and Cisco Unified CM application events,
alerts, and alarms are written to syslog servers.
•
HTTPS—Displays the following web pages by using HTTPS—Cisco Unified CM Administration,
Cisco Unified Serviceability, Disaster Recovery System, and Unified OS Administration.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
3-1
Chapter 3
Managing and Monitoring the Health of Cisco Unified Communications Manager Systems
Critical Processes to Monitor
•
Command Line Interface (CLI)—Used for a subset of functions available by using the web browser
interfaces and primarily used to re-establish these interfaces if inoperable. The CLI is accessible by
using SSH or a serial console port on the appliance. The complete set of CLI commands is described
in the Cisco Unified Communications Operating System Administration Guide.
•
Native Hardware Out of Band Management (OOB)—Supports select features of HP iLO and IBM
RSA II.
•
Secure FTP (SFTP)—Used for secure file push from or pull to the appliance, including CDR/CMR
push, trace file push, push of backups or pull or restores, and pull of upgrade files.
•
Third-party Network Management Systems (NMS)—Monitors appliances by leveraging the exact
same interfaces exposed to Cisco network management applications. Certain functions of these
applications may not be supported on the appliance if native platform access is required, such as
account management, software configuration management, or other forms of native platform
manipulation. For example, the system management portal web page on HP servers is not supported,
but polling and alerting by using the HP System Insight Manager and the appliance MIB is
supported.
•
Cisco Unified Communications Real-Time Management Tool—Used for perfmon and TCT
functions.
Figure 3-1 shows the supported interfaces in Cisco Unified CM Release 5.0 and later releases.
Figure 3-1
Supported Management Interfaces in Cisco Unified CM Release 5.0 and Later
Releases
Management
Console
Unified Communications
Manager Cluster Nodes
Serviceability API (AXL/SOAP)
Provisioning API (AXL)
CUCMS
M
M
M
SNMP MIB/Trap
Other NMS
Local
Syslog
HTTPS
Admin Web
Pages
Pager/email
RTMT
•Perlmon
•TCT
M
M
SSH
CLI
Alerts
Trace
Files
CDR
274326
(S)FTP (push CDR/CMR, trace, backups)
(Remote Syslog (Unified
Communications Manager services)
Critical Processes to Monitor
Table 3-1 describes the critical processes that require monitoring. Be aware of following items while
monitoring the processes:
•
Any of the services, process names, or process sets could change at any time with newer Cisco
Unified CM releases without notice.
•
HOST-RESOURCES-MIB could be deprecated in any future Cisco Unified CM release.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
3-2
OL-20105-01
Chapter 3
Managing and Monitoring the Health of Cisco Unified Communications Manager Systems
Critical Processes to Monitor
Table 3-1
•
Whether a process is auto-restarted or the maximum number of restarts could change for any newer
Cisco Unified CM releases without notice.
•
Process names represent value shown in HOST-RESOURCES-MIB::hrSWRUNName.
•
Any processes not included in this list are transient or not critical for system operation. Those
processes should be ignored and they can change without notice.
•
Services Cisco CallManager through Cisco CDR Agent can be monitored by using SYSAPPL-MIB.
Critical Services to Monitor
Stop | Start|
Restart Instruction
Process
Name
Auto
Restart
Cisco CallManager
Serviceability/Tools >
Control Center - Feature
Services *****
ccm
3
The Cisco CallManager service provides
software-only call processing as well as signaling
and call control functionality for Cisco Unified
Communications Manager.
Cisco TFTP
Serviceability/Tools >
Control Center - Feature
Services *****
ctftp
3
The Cisco Trivial File Transfer Protocol (TFTP)
builds and serves files that are consistent with the
trivial file transfer protocol, a simplified version of
FTP. Cisco TFTP serves embedded component
executable, ringer files, and device configuration
files.
Cisco IP Voice
Media Streaming
App
Serviceability/Tools >
Control Center - Feature
Services *****
ipvmsd
3
The Cisco IP Voice Media Streaming Application
service provides voice media streaming
functionality for the Cisco Unified CallManager
for use with MTP, conferencing, music on hold
(MOH), and annunciator. The Cisco IP Voice
Media Streaming Application relays messages
from the Cisco Unified CallManager to the IP
voice media streaming driver, which handles RTP
streaming.
Cisco CTIManager
Serviceability/Tools >
Control Center - Feature
Services *****
CTI
Manager
3
The CTI Manager contains the CTI components
that interface with applications. With CTI
Manager, applications can access resources and
functionality of all Cisco Unified CallManagers in
the cluster and have improved failover capability.
Although one or more CTI Managers can be active
in a cluster, only one CTI Manager can exist on an
individual server. An application (JTAPI/TAPI)
can have simultaneous connections to multiple CTI
Managers; however, an application can only use
one connection at a time to open a device with
media termination.
Service
Description
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
3-3
Chapter 3
Managing and Monitoring the Health of Cisco Unified Communications Manager Systems
Critical Processes to Monitor
Table 3-1
Critical Services to Monitor
Stop | Start|
Restart Instruction
Process
Name
Auto
Restart
Cisco DHCP
Monitor Service
Serviceability/Tools >
Control Center - Feature
Services *****
DHCP
Monitor
3
Cisco DHCP Monitor Service monitors IP address
changes for IP phones in the database tables. When
a change is detected, it modifies the
/etc./dhcpd.conf file and restarts the DHCPD
daemon.
Cisco CallManager
SNMP Service
Serviceability/Tools >
Control Center - Feature
Services *****
ccmAgt
3
This service provides SNMP access to
provisioning and statistics information that is
available for Cisco Unified CallManager
Cisco CTL
Provider Service
Status
Serviceability/Tools >
Control Center - Feature
Services *****
CTL
Provider
3
The Cisco CTL Provider service, which runs with
local system account privileges, works with the
Cisco CTL Provider Utility, a client-side plug-in,
to change the security mode for the cluster from
nonsecure to mixed mode. When you install the
plug-in, the Cisco CTL Provider service retrieves a
list of all Cisco Unified CallManager and Cisco
TFTP servers in the cluster for the CTL file, which
contains a list of security tokens and servers in the
cluster.
Cisco Certificate
Authority Proxy
Function
Serviceability/Tools >
Control Center - Feature
Services *****
capf
3
Working in conjunction with the CAPF
application, the Cisco Certificate Authority Proxy
Function (CAPF) service can perform the
following tasks, depending on your
configuration—(1)Issue locally significant
certificates to supported Cisco Unified IP Phone
models. (2)Using SCEP, request certificates from
third-party certificate authorities on behalf of
supported Cisco Unified IP Phone models.
(3)Upgrade existing certificates on the phones.
(4)Retrieve phone certificates for troubleshooting.
(5)Delete locally significant certificates on the
phone.
Cisco DirSync
Serviceability/Tools >
Control Center - Feature
Services *****
CCM
DirSync
3
Unlike Windows versions of Cisco Unified
CallManager, Cisco Unified CallManager does not
contain an embedded directory. Because of this
change, the Cisco Unified CallManager database
stores all user information. If you use an integrated
corporate directory, for example, Microsoft Active
Directory or Netscape/iPlanet Directory, with
Cisco Unified CallManager, the Cisco DirSync
service migrates the user data to the Cisco Unified
CallManager database. The Cisco DirSync service
does not synchronize the passwords from the
corporate directory.
Service
Description
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
3-4
OL-20105-01
Chapter 3
Managing and Monitoring the Health of Cisco Unified Communications Manager Systems
Critical Processes to Monitor
Table 3-1
Critical Services to Monitor
Stop | Start|
Restart Instruction
Process
Name
Auto
Restart
Cisco Messaging
Interface
Serviceability/Tools >
Control Center - Feature
Services *****
cmi
3
The Cisco Messaging Interface allows you to
connect a simplified message desk interface
(SMDI)-compliant external voice-messaging
system with the Cisco Unified CallManager. The
CMI service provides the communication between
the voice-messaging system and Cisco Unified
CallManager. The SMDI defines a way for a phone
system to provide a voice-messaging system with
the information that is needed to intelligently
process incoming calls.
Cisco CallManager
Attendant Console
Server
Serviceability/Tools >
Control Center - Feature
Services *****
acserver
3
The Cisco CallManager Attendant Console Server
service provides centralized services for Cisco
Unified CallManager Attendant Console clients
and pilot points. For Attendant Console clients,
this service provides call-control functionality,
line state information for any accessible line within
the Cisco Unified CallManager domain, and
caching of directory information. For pilot points,
this service provides automatic redirection to
directory numbers that are listed in hunt groups
and failover during a Cisco Unified CallManager
failure.
Cisco Extended
Functions
Serviceability/Tools >
Control Center - Feature
Services *****
cef
3
The Cisco Extended Functions service provides
support for some Cisco Unified CallManager
features, including Quality Report Tool (QRT).
Cisco Bulk
Provisioning
Service
Serviceability/Tools >
Control Center - Feature
Services *****
BPS
3
You can activate the Cisco Bulk Provisioning
Service only on the first node. If you use the Cisco
Unified Bulk Administration Tool (BAT) to
administer phones and users, you must activate this
service.
Cisco TAPS
Service
Serviceability/Tools >
Control Center - Feature
Services *****
TAPS
3
The Cisco TAPS Service supports the Cisco
Unified CallManager Auto-Registered Phone
Tool, which allows a user to upload a customized
configuration on an autoregistered phone after a
user responds to Interactive Voice Response (IVR)
prompts.
Cisco
Serviceability
Reporter
Serviceability/Tools >
Control Center - Feature
Services *****
rtmt
reporter
3
The Cisco Serviceability Reporter service
generates the following daily reports—Device
Statistics, Server Statistics, Service Statistics, Call
Activities, Alert, Performance Protection Report.
Service
Description
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
3-5
Chapter 3
Managing and Monitoring the Health of Cisco Unified Communications Manager Systems
Critical Processes to Monitor
Table 3-1
Critical Services to Monitor
Stop | Start|
Restart Instruction
Process
Name
Cisco CAR
Scheduler
Serviceability/Tools >
Control Center Network Services
carschlr
Cisco AMC
Service
Serviceability/Tools >
Control Center Network Services
amc
3
Used for the real-time monitoring tool (RTMT),
this service, Alert Manager and Collector service,
existed as a component of the Cisco RIS Data
Collector service in previous Windows releases of
Cisco Unified CallManager. This service allows
RTMT to retrieve real-time information that exists
on nodes in the cluster.
Cisco Trace
Collection Service
Serviceability/Tools >
Control Center Network Services
tracecoll
ection
3
The Cisco Trace Collection Service, along with the
Cisco Trace Collection Servlet, supports trace
collection and allows users to view traces by using
the RTMT client. After Cisco Unified
CallManager installation, this service starts
automatically. If you stop this service on a server,
you cannot collect or view traces on that server.
A Cisco DB
CLI utils service start |
stop A Cisco DB
cmoninit
3
A Cisco DB acts as the Progress database engine.
A Cisco DB
Replicator
Serviceability/Tools >
Control Center Network Services
dblrpc
3
The A Cisco DB Replicator service ensures
database configuration and data synchronization
between the first and subsequent nodes in the
cluster.
Cisco Tomcat
CLI utils service restart
Cisco Tomcat
tomcat
3
The Cisco Tomcat service supports the web server.
SNMP Master
Agent
Serviceability/Tools >
Control Center Network Services *
snmpdm
3
This service, which acts as the agent protocol
engine, provides authentication, authorization,
access control, and privacy functions that relate to
SNMP requests.
MIB2 Agent
Serviceability/Tools >
Control Center Network Services *
mib2agt
3
This service provides SNMP access to variables
that are defined in RFC 1213, which read and write
variables; for example, system, interfaces, IP, and
so on.
Host Resources
Agent
Serviceability/Tools >
Control Center Network Services *
hostagt
3
This service provides SNMP access to host
information, such as storage resources, process
tables, device information, and installed software
base.
Service
Auto
Restart
Description
The Cisco CAR Scheduler service allows you to
schedule CAR-related tasks; for example, you can
schedule report generation or CDR file loading
into the CAR database. This service starts
automatically.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
3-6
OL-20105-01
Chapter 3
Managing and Monitoring the Health of Cisco Unified Communications Manager Systems
Critical Processes to Monitor
Table 3-1
Critical Services to Monitor
Stop | Start|
Restart Instruction
Process
Name
Auto
Restart
Native Agent
Adapter
Serviceability/Tools >
Control Center Network Services *
naaagt
3
This service allows you to forward SNMP requests
to another SNMP agent that runs on the system.
System
Application Agent
Serviceability/Tools >
Control Center Network Services
sappagt
3
This service provides SNMP access to the
applications that are installed and executing on the
system. This implements the SYSAPPL-MIB.
Cisco CDP Agent
Serviceability/Tools >
Control Center Network Services
cdpAgt
3
This service uses the Cisco Discovery Protocol to
provide SNMP access to network connectivity
information on the Cisco Unified CallManager
node.
Cisco Syslog
Agent
Serviceability/Tools>
Control Center Network Services
Cisco
Syslog
SubA
3
This service supports gathering of syslog messages
that various Cisco Unified CallManager
components generate.
Cisco License
Manager
Serviceability/Tools >
Control Center Network Services
Cisco
License
Mgr
3
Cisco License Manager keeps track of the licenses
that a customer purchases and uses. It controls
licenses checkins and checkouts, and it takes
responsibility for issuing and reclaiming licenses.
Cisco License Manager manages the Cisco Unified
CallManager application and the number of IP
phone unit licenses. When the number of phones
exceeds the number of licenses, it issues alarms to
notify the administrator. This service runs on all
the nodes, but the service on the first node has the
responsibility for issuing and reclaiming licenses.
Cisco Certificate
Expiry Monitor
Serviceability/Tools >
Control Center Network Services
certM
3
This service periodically checks the expiration
status of certificates that Cisco Unified
CallManager generates and sends notification
when a certificate gets close to its expiration date.
Cisco Database
Layer Monitor
CLI utils service restart
Cisco Database Layer
Monitor
dbmon
3
The Cisco Database Layer Monitor service
monitors aspects of the database layer. This server
takes responsibility for change notification and
monitoring.
Cisco Log
Partition
Monitoring Tool
Serviceability/Tools >
Control Center Network Services
Lpm
Tool
3
The Cisco Log Partition Monitoring Tool service
supports the Log Partition Monitoring feature,
which monitors the disk usage of the log partition
on a server (or all servers in the cluster) by using
configured thresholds and a polling interval.
Service
Description
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
3-7
Chapter 3
Managing and Monitoring the Health of Cisco Unified Communications Manager Systems
Critical Processes to Monitor
Table 3-1
Critical Services to Monitor
Stop | Start|
Restart Instruction
Process
Name
Auto
Restart
Cisco CDP
Serviceability/Tools >
Control Center Network Services
cdpd
6
Cisco CDP advertises Cisco Unified CallManager
to other applications, so the application, for
example, SNMP or CiscoWorks2000, can perform
network management tasks for Cisco Unified
CallManager.
Cisco RIS Data
Collector
Serviceability/Tools >
Control Center Network Services
RisDC
3
The Real-time Information Server (RIS) maintains
real-time Cisco Unified CallManager information
such as device registration status, performance
counter statistics, critical alarms generated, and so
on. The Cisco RIS Data Collector service provides
an interface for applications, such as Real-Time
Monitoring Tool (RTMT), SOAP applications,
Cisco Unified CallManager Administration and
AlertMgrCollector (AMC) to retrieve the
information that is stored in all RIS nodes in the
cluster.
Cisco DRF Master
Serviceability/Tools >
Control Center Network Services
CiscoDR
FMaster
3
The Cisco DRF Master Agent service supports the
DRF Master Agent, which works with the
graphical user interface (GUI) or command line
interface (CLI) to schedule backups, perform
restorations, view dependencies, check status of
jobs, and cancel jobs, if necessary. The Cisco DRF
Master Agent also provides the storage medium for
the backup and restoration process .
Cisco DRF Local
Serviceability/Tools >
Control Center Network Services
CiscoDR
FLocal
3
The Cisco DRF Local service supports the Cisco
DRF Local Agent, which acts as the workhorse for
the DRF Master Agent. Components on a node
register with the Cisco DRF Local Agent to use the
disaster recovery framework. The Cisco DRF
Local Agent executes commands that it receives
from the Cisco DRF Master Agent. Cisco DRF
Local Agent sends the status, logs, and command
results to the Cisco DRF Master Agent.
Cisco CDR
Repository
Manager
Serviceability/Tools >
Control Center Network Services
cdrrep
3
You can start and stop the Cisco CDR Repository
Manager service only on the first node, which
contains the Cisco Unified CallManager database.
This service starts automatically.
Service
Description
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
3-8
OL-20105-01
Chapter 3
Managing and Monitoring the Health of Cisco Unified Communications Manager Systems
Critical Processes to Monitor
Table 3-1
Critical Services to Monitor
Stop | Start|
Restart Instruction
Process
Name
Auto
Restart
Cisco CDR Agent
Serviceability/Tools >
Control Center Network Services
cdragent
3
The Cisco CDR Agent service transfers CDR and
CMR files that are generated by Cisco Unified
CallManager from the local host to the CDR
repository node, where the CDR Repository
Manager service runs over a SFTP connection. For
this service to work, activate the Cisco
CallManager service on the first node and ensure
that it is running.
SSH Service Status
CLI utils service restart
System SSH
sshd
3
—
Syslog Service
Status
Auto-restart being
addressed by Cisco.
syslogd
—
—
SNMP Service
Status
CLI utils snmp
hardware-agent restart
**
—
—
IBM—snmpd, slp_srvreg cimlistener, cimserver,
dirsnmpd, ““java...
com.tivoli.twg.agent.TWGAgent””
****
Service
Description
HP
DRF Restoral
Condition
—
—
—
No API to monitor status of DRF Restoral
Condition.
IBM Director
Agent SNMP
IBM process covered by
SNMP Service
cim
listenerd
—
—
IBM Director
Agent SNMP
IBM process covered by
SNMP Service
cim
serverd
—
—
dirsnmpd
IBM process covered by
SNMP Service
dir
snmpd
—
—
Cmaeventd
HP process covered by
SNMP Service
—
—
—
Cmafcad
HP process covered by
SNMP Service
—
—
—
Cmahealthd
HP process covered by
SNMP Service
—
—
—
Cmahostd
HP process covered by
SNMP Service
—
—
—
Cmaidad
HP process covered by
SNMP Service
—
—
—
Cmaided
HP process covered by
SNMP Service
—
—
—
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
3-9
Chapter 3
Managing and Monitoring the Health of Cisco Unified Communications Manager Systems
Critical Processes to Monitor
Table 3-1
Critical Services to Monitor
Stop | Start|
Restart Instruction
Process
Name
Auto
Restart
Description
Cmanicd
HP process covered by
SNMP Service
—
—
—
Cmapeerd
HP process covered by
SNMP Service
—
—
—
Cmaperfd
HP process covered by
SNMP Service
—
—
—
Cmasm2d
HP process covered by
SNMP Service
—
—
—
Cmastdeqd
HP process covered by
SNMP Service
—
—
—
Cmathreshd
HP process covered by
SNMP Service
—
—
—
hpasm
HP process covered by
SNMP Service
hpasm
—
—
hpasmxld
HP process covered by
SNMP Service
hpas
mxld
—
—
snmpsa-ah
INTEL process covered
by SNMP Service
snmp
sa-ah
—
—
Cisco Security
Agent Service
Status
Auto-restart being
addressed by Cisco.
—
—
—
ciscosec
Indefinite
—
—
—
Cisco Electronic
Notification
Serviceability/Tools >
Control Center Network Services
enStart
3
—
Time
Synchronization
Service
—
ntpd
—
Auto-restarts according to ‘init’ rules (10 if
instantaneous failure, otherwise higher).”
Service Manager
CLI utils service restart
Service Manager
servM
—
Auto-restarts according to ‘init’ rules (10 if
instantaneous failure, otherwise higher).
Racoon DB
N/A
racoon
—
Internet Key Exchange (IKE) daemon for
automatically keying IPsec connections.
Service
Auto-restarts according to ‘init’ rules (10 if
instantaneous failure, otherwise higher).
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
3-10
OL-20105-01
Chapter 3
Managing and Monitoring the Health of Cisco Unified Communications Manager Systems
Available Supported MIBs
Table 3-1
Critical Services to Monitor
Service
Stop | Start|
Restart Instruction
Process
Name
Auto
Restart
IP Sec Manager
—
ipsec
_mgr
—
Description
Auto-restarts according to ‘init’ rules (10 if
instantaneous failure, otherwise higher).
SysLog Test Cases For Cisco Unified CM
MGCPGateway
LostComm
Natively supported alarm—GUI Serviceability/Alarm/Catalog, CallManager,
MGCPGatewayLostComm/Find
SDLLinkOOS
Natively supported alarm—GUI Serviceability/Alarm/Catalog, CallManager, SDLLinkOOS/Find”
SNMP Trap Test Cases
ccmGatewayFailed
Event
CCM-MIB::ccmGatewayFailed
iBMPSG
PowerSupplyEvent
IBM-SYSTEM-POWER-MIB; pull cord on IBM MCS-7835 & MCS-7845 servers with redundant
power supply to invoke.
* HOST-RESOURCES-MIB and possibly other MIBS fail to function or respond
when this service is stopped.
** Only in Cisco Unified CM Release 5.1(3) and Release 6.1(1) and later releases.
***All of the listed processes may not be running as it is a function of the particular
server model or what the service deems appropriate.
****There is more than one process by this name; second argument is relevant for
distinction.
*****Feature Services are not activated by default.
Available Supported MIBs
The following MIBs can be reviewed and used for monitoring system health:
•
Cisco MIBs (Chapter 7, “Cisco Management Information Base”)
– CISCO-CCM-MIB, page 7-1
– CISCO-CCM-CAPABILITY, page 7-143
– CISCO-CDP-MIB, page 7-149
– CISCO-SYSLOG-MIB, page 7-166
– CISCO-SYSLOG-EXT-MIB, page 7-174
•
Industry-Standard MIBs (Chapter 8, “Industry-Standard Management Information Base”)
– SYSAPPL-MIB, page 8-1
– HOST-RESOURCES-MIB, page 8-73
– RFC1213-MIB (MIB-II), page 8-28
– IF-MIB, page 8-106
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
3-11
Chapter 3
RTMT Monitoring of Cisco Unified CM System Health
Managing and Monitoring the Health of Cisco Unified Communications Manager Systems
RTMT Monitoring of Cisco Unified CM System Health
The following topics are described in this section:
•
RTMT Summary View, page 3-12
•
CPU Usage, page 3-13
•
% IOwait Monitoring, page 3-15
•
Virtual Memory, page 3-15
•
Disk Usage, page 3-17
•
Database Replication and Cisco Unified Communication Manager Nodes, page 3-20
•
ccm Process and CPU Usage, page 3-20
•
CodeYellow, page 3-21
•
RIS Data Collector PerfMonLog, page 3-23
•
Critical Service Status, page 3-24
•
Syslog Messages, page 3-25
•
RTMT Alerts as Syslog Messages and Traps, page 3-26
RTMT Summary View
The RTMT summary view displays the overall health of the system, which should be monitored daily,
including:
•
CPU utilization level
•
Memory utilization level
•
Phone registration status
•
Call in progress
•
Gateway status
If CPU and memory utilization levels exceeds the 70 percent mark, then the Cisco Unified CM publisher
and subscribers that are participating in call processing could be overloaded . Key indicators of system
health and performance issues are:
•
System Time, User Time, IOWait, soft irq, irq
•
CPU Pegging Alerts
•
Process using most CPU
•
High % iowait
•
High % iowait due to common partition
•
Process responsible for Disk IO
•
CodeYellow
If you do not want the RTMT client running on your workstation or PC all the time, you can configure
a threshold for each alert that is of interest to you and how you want to be notified. Then you can close
the RTMT client on your workstation or PC.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
3-12
OL-20105-01
Chapter 3
Managing and Monitoring the Health of Cisco Unified Communications Manager Systems
RTMT Monitoring of Cisco Unified CM System Health
The RTMT backend, AMC service, which is up and running as soon as the Cisco Unified CM server is
up and running, collects and processes all the information needed, and notifies you according to how you
configured the notification.
RTMT CPU and memory page reports CPU usage in terms of the following:
•
%System—CPU utilization percentage that occurred while executing at the system level (kernel)
•
%User—CPU utilization percentage that occurred while executing at the user level (application).
•
%IOWait—CPU percentage of time of idle waiting for outstanding disk I/O request.
•
%SoftIrq—Percentage of time that the processor is executing deferred IRQ processing (for example,
processing of network packets).
•
%Irq—Percentage of time that the processor is executing the interrupt request which is assigned to
devices for interrupt or sending a signal to the computer when it is finished processing.
CPU Usage
High CPU utilization can impact the call processing by creating delays or interruptions in the service. It
could affect the end user service. Sometimes high CPU utilization is indicative of a memory leak. RIS
DataCollector PerfMonLog when enabled tracks CPU usage.
Note
Cisco recommends that RIS DataCollector PerfMonLog be enabled.
Table 3-2 shows CPU usage guidelines.
Table 3-2
CPU Usage Guidelines
Usage
MCS-7835
Total CPU usage—Processor (_Total) \ % < 68% is good
CPU Time
68–70% triggers a warning
MCS-7845
< 68% is good
68–70% triggers a warning
> 80% is bad
> 80% is bad
Process ccm CPU
< 44%
< 22%
IOWAIT—Processor (_Total) \IOwait
Percentage
< 10% is good
< 10% is good
CallManager Service Virtual Memory size < 2.1 GB
< 2.1 GB
You can also monitor CPU usage by using APIs. Using the SOAP API, you can monitor the following
perfmon counters:
•
Under Processor object—% CPU Time, System Percentage, User Percentage, IOwait Percentage,
Softirq Percentage, Irq Percentage
•
Under Process object—% CPU Time
Using the SNMP interface, you can monitor the following perfmon counters:
•
Host Resource MIB—hrProcessorLoad, hrSWRunPerfCPU
•
CPQHOST-MIB—cpqHoCpuUtilMin, cpqHoCpuUtilFiveMin
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
3-13
Chapter 3
RTMT Monitoring of Cisco Unified CM System Health
Managing and Monitoring the Health of Cisco Unified Communications Manager Systems
If you see high CPU usage, identify which process is causing it. If %system and/or %user is high enough
to generate CPUPegging alert, check the alert message to see the processes that are using the most CPU.
You can go to the RTMT Process page, sort by %CPU to identify high CPU processes.
Figure 3-2 shows the CPU usage.
Figure 3-2
Cisco Unified Serviceability CPU Usage
For analysis, RIS Data Collector PerfMonLog tracks processes %CPU usage at system level.
RTMT monitors CPU usage and when CPU usage is above a threshold, RTMT generates
CallProcessingNodeCPUPegging alert. Figure 3-3 shows the alert status.
Figure 3-3
RTMT Alert Central with Alert Status
Monitor the “In Safe Range” column often. If it is marked “No,” then the condition is not corrected. For
example, if In Safe Range column displays No for CallProcessingNodeCPUPegging, then it means the
CPU usage on that node is above the threshold and requires attention.
In addition to CallProcessingNodeCPUPegging, high CPU usage potentially causes the following alerts
to trigger:
•
CodeYellow
•
CodeRed
•
CoreDumpFileFound
•
CriticalServiceDown
•
LowCallManagerHeartbeatRate
•
LowTFTPServerHeartbeatRate
•
LowAttendantConsoleHeartRate
When a service crashes, the corresponding trace files may have been overwritten. Cisco TAC needs the
trace files to troubleshoot the crash. In the case of CoreDumpFileFound, CodeYellow, and
CriticalServiceDown, the Enable Trace Download option should be enabled to assist Cisco TAC.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
3-14
OL-20105-01
Chapter 3
Managing and Monitoring the Health of Cisco Unified Communications Manager Systems
RTMT Monitoring of Cisco Unified CM System Health
% IOwait Monitoring
High %IOwait indicates high disk input/output (I/O) activities. Consider the following high IOwait
conditions:
•
Heavy memory swapping—Check %CPU Time for Swap Partition to see if there is high level of
memory swapping activity. One potential cause of high memory swapping is memory leak.
•
DB activity—Database accesses Active Partition. If %CPU Time for Active Partition is high, then
most likely there are a lot of DB activities.
•
Common (or Log) Partition in the trace and log files storage location—Check the following:
– Trace Log Center to see if there is any trace collection activity going on. If call processing is
impacted (ie, CodeYellow), then consider adjusting trace collection schedule. If zip option is
used, please turning it off.
– Trace setting at the detailed level because Cisco Unified CM generates a lot of trace. If high
%iowait and/or Cisco Unified CM is in CodeYellow state, and Cisco Unified CM service trace
setting is at Detailed, please chance trace setting to “Error” to reduce the trace writing.
You can use RTMT to identify processes that are responsible for high %IOwait:
•
If %IOwait is high enough to cause CPUPegging alert, check the alert message to check processes
waiting for disk IO.
•
Go to RTMT Process page, sort by Status. Check for processes in Uninterruptible Disk Sleep state
•
Download RIS Data Collector PerfMonLog file to examine the process status for longer period of
time.
Figure 3-4 shows an example of RTMT Process window sorted by Status. Check for processes in
Uninterruptible Disk Sleep state. The FTP process is in the Uninterruptible Disk Sleep state.
Figure 3-4
FTP Process in Uninterruptible Disk Sleep State
Virtual Memory
Virtual memory consists of physical memory (RAM) and swap memory (Disk). The RTMT CPU and
Memory window has system level memory usage information as the following:
•
Total—total amount of physical memory
•
Free—amount of free memory
•
Shared—amount of shared memory used
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
3-15
Chapter 3
RTMT Monitoring of Cisco Unified CM System Health
Note
Managing and Monitoring the Health of Cisco Unified Communications Manager Systems
•
Buffers—amount of memory used for buffering purpose
•
Cached—amount of cached memory
•
Used—calculated as Total – Free – Buffers – Cached + Shared
•
Total Swap—total amount of swap space
•
Used Swap—the amount of swap space in use on the system.
•
Free Swap—the amount of free swap space available on the system
Using SOAP APIs, you can query memory information for the following perfmon counters:
•
Under Memory object—% Mem Used, % VM Used, Total Kbytes, Total Swap Kbytes, Total VM
Kbytes, Used Kbytes, Used Swap Kbytes, Used VM Kbytes
•
Under Process object—VmSize, VmData, VmRSS, % Memory Usage
Using SNMP, you can query the following perfmon counters:
•
Host Resource MIB—hrStorageSize, hrStorageUsed, hrStorageAllocationUnits, hrStorageDescr,
hrStorageType, hrMemorySize
Note
You can download some historical information by using RTMT Trace Log Central. The Cisco AMC
Service PerfMonLog is enabled by default. Deprecated in Cisco Unified CM Release 6.0 because Cisco
RIS Data Collector PerfMonLog was introduced. The Cisco RIS Data Collector PerfMonLog disabled
by default in Cisco Unified CM Release 5.x and enabled by default in Cisco Unified CM Release 6.0.
Note
Perfmon Virtual Memory refers to Total (Physical + Swap) memory whereas Host Resource MIB
Virtual Memory refers to Swap memory only.
The RTMT Process window displays process level memory usage information as follows:
•
VmSize—Total virtual memory used by the process
•
VmRSS—Resident Set currently in physical memory used by the process including Code, Data and
Stack
•
VmData—Virtual memory usage of heap by the process
•
Page Fault Count—Represents the number of major page faults that a process encountered that
required the data to be loaded into physical memory
Figure 3-5 shows RTMT Process window. You can sort VmSize by clicking on VmSize tab. Then you
can identify which process consumes more memory.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
3-16
OL-20105-01
Chapter 3
Managing and Monitoring the Health of Cisco Unified Communications Manager Systems
RTMT Monitoring of Cisco Unified CM System Health
Figure 3-5
VmSize listed by RTMT Process
Possible memory leak causes can be from the VmSize continuously increasing.
When a process leaks memory, the system administrator should report it to Cisco and include trace files.
Ris Data Collector PerfMonLog collects the data and it contains historical information on memory
usage.
Disk Usage
There are four disks or partitions in the Cisco Unified CM hard drive:
•
Common partition (log partition)—Contains the trace/log files
•
Active partition—Contains files (binaries, libraries and config files) of active OS and the Cisco
Unified CM release
•
Inactive partition—Contains files for alternative Cisco Unified CM release (for example, an older
version that was upgraded from or newer version recently upgraded to but the server has not been
toggled to this release).
•
Swap partition—Used for swap space.
Using SOAP APIs, you can get partition information for the following perfmon counters:
•
Under Partition object—Total Mbytes, Used Mbytes, Queue Length, Write Bytes Per Sec, Read
Bytes Per Sec
Using the SNMP MIB, you can query the following information:
•
Host Resource MIB—hrStorageSize, hrStorageUsed hrStorageAllocationUnits, hrStorageDescr,
hrStorageType
You can download the following historical information by using RTMT Trace and Log Central:
•
Cisco AMC Service PerfMonLog // enabled by default. Deprecated in Cisco Unified CM 6.0,
because Cisco RIS Data Collector PerfMonLog is introduced.
•
Cisco RIS Data Collector PerfMonLog // disabled by default in Cisco Unified CM 5.x; enabled by
default in Cisco Unified CM 6.0
Figure 3-6 shows disk usage in RTMT.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
3-17
Chapter 3
RTMT Monitoring of Cisco Unified CM System Health
Figure 3-6
Managing and Monitoring the Health of Cisco Unified Communications Manager Systems
Disk Usage by Partition
Disk Name Mapping
Perfmon instance names as shown in RTMT and SOAP are:
•
Active
•
Inactive
•
Common
•
Boot
•
Swap
•
SharedMemory
Names shown in Host Resource MIB hrStorage description are:
•
/partB
•
/common
•
/grub
•
Virtual Memory
•
/dev/shm
The partition alerts are as follows:
•
LogPartitionLowWaterMarkExceeded—Occurs when the percentage of used disk space in the log
partition has exceeded the configured low water mark. This alert should be considered as early
warning for an administrator to clean up disk space. You can use RMT Trace/Log Central to collect
trace/log files and then delete these trace/log files from the server. In addition to manually clean up
the traces/log files, the system administrator should also adjust the number of trace files to be kept
to avoid hitting low water mark again.
•
LogPartitionHighWaterMarkExceeded—Occurs when the percentage of used disk space in the log
partition has exceeded the configured high water mark. When this alert is generated, Log Partition
Monitoring (LPM) utility starts to delete files in Log Partition until the Log Partition is down to the
low water mark to avoid running out of disk space. Since LPM may delete some files that you want
to keep, you need to act upon receiving LogPartitionLowWaterMarkExceed alert.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
3-18
OL-20105-01
Chapter 3
Managing and Monitoring the Health of Cisco Unified Communications Manager Systems
RTMT Monitoring of Cisco Unified CM System Health
•
LowActivePartitionAvailableDiskSpace—Occurs when the percentage of available disk space of
the Active Partition is lower than the configured value. Please use the default threshold that Cisco
recommends. At default threshold, this alert should never be generated. If this alert occurs, a system
administrator can adjust the threshold as temporary workaround but Cisco TAC should look into
this. One place to look is /tmp using remote access. We have seen cases where large files are left
there by 3rd party software.
•
LowInactivePartitionAvailableDiskSpace—Occurs when the percentage of available disk space of
the InActive Partition is lower than the configured value. Please use the default threshold that Cisco
recommends. At default threshold, this alert should never be generated. If this alert occurs, a system
administrator can adjust the threshold as temporary workaround but Cisco TAC should look into
this.
Table 3-3 shows a comparison of disk-related perfmon counters between Cisco Unified CM Release 4.x
and Cisco Unified CM Release 5.x.
Table 3-3
Disk-Related Perfmon Counters
Cisco Unified CM Release 4.x Perfmon Counters
Cisco Unified CM Release 5.x Perfmon Counters
Logical Disk
Partition
% Disk Time
% CPU Time
Disk Read Bytes/sec
Read Kbytes Per Sec
Disk Write Bytes/sec
Write Kbytes Per Sec
Current Disk Queue Length
Queue Length
Free Megabytes
Used Mbytes
Total Mbytes
% Free Space
% Used
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
3-19
Chapter 3
RTMT Monitoring of Cisco Unified CM System Health
Managing and Monitoring the Health of Cisco Unified Communications Manager Systems
Database Replication and Cisco Unified Communication Manager Nodes
You can use RTMT Database Summary to monitor your database activities as shown in Figure 3-7. For
example, click CallManager > Service > Database Summary.
Figure 3-7
Database Summary in RTMT
ccm Process and CPU Usage
The Cisco Unified CM process is labeled “ccm.” Table 3-4 contains general guidelines for the ccm
service CPU usage.
Table 3-4
Cisco Unified CM ccm Process and CPU Usage
CPU usage Process (ccm)\% CPU Time
MCS-7835 Server
MCS-7845 Server
< 44% is good
< 22% is good
44-52% triggers a warning
22-36% triggers a warning
> 60% is bad
> 30% is bad
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
3-20
OL-20105-01
Chapter 3
Managing and Monitoring the Health of Cisco Unified Communications Manager Systems
RTMT Monitoring of Cisco Unified CM System Health
The MCS-7845 server has more processors and a lower threshold for CPU usage because the ccm
process is a multithreaded application. But the main router thread does the bulk of call processing. A
single thread can run only on one processor at any given time even when there are multiple processors
available. That means ccm main router thread can run out of CPU resource even when there are idle
processors.
With hyper-threading, the MCS-7845 server has 4 virtual processors. So on the server where the main
router thread is running at full blast to do call processing, it is possible three other processors are near
idle. In this situation UC Manager can get into Code Yellow state even when total CPU usage is 25 to
30 percent. (Similarly MCS-7835 server with two virtual processors, UC Manager could get into Code
Yellow state at around 50 to 60 percent of CPU usage.
Use the following to query perfmon counters:
•
SOAP APIs:
– Perfmon counters
– Device information
– DB access
– CDR access
•
SNMP:
– CISCO-CCM-MIB—ccmPhoneTable, ccmGatewayTable, etc.
– Download historical information by using RTMT Trace/Log Central
– Cisco AMC Service PerfMonLog is enabled by default. This was deprecated in Cisco Unified
CM Release 6.0 because Cisco RIS Data Collector PerfMonLog was introduced.
– Cisco RIS Data Collector PerfMonLog was disabled by default in Cisco Unified CM Release
5.x and enabled by default in Cisco Unified CM Release 6.0.
CodeYellow
CodeYellow state occurs when the ccm process is so overloaded that it cannot process incoming calls
anymore. In this case, ccm initiates call throttling.This does not mean that one processor CPU usage is
at 100 percent and the remaining processors are operating at 0 percent in RTMT.
Since the main thread can run on processor A for 1/10th of a second and processor B on the next 2/10th
of a second, etc., the CPU usage shown in RTMT would be more balanced. By default RTMT shows
average CPU usage for a 30-second duration.
You can configure the CodeYellow alert so that once it occurs, the trace files can be downloaded for
troubleshooting purposes.
The AverageExpectedDelay counter represents the current average expected delay for handling any
incoming message. If the value is above the value specified in “Code Yellow Entry Latency” service
parameter, CodeYellow alarm is generated. This counter is one of key indicator of call processing
performance issue.
If you see CodeYellow, but the total CPU usage is only 25 percent, it is because Cisco Unified CM needs
one processor for call processing. When no processor resource is available, CodeYellow may occur even
when the total CPU usage is only around 25 to 30 percent in a 4-virtual processor server. Similarly on a
2 processor server, CodeYellow is possible around 50 percent of total CPU usage.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
3-21
Chapter 3
RTMT Monitoring of Cisco Unified CM System Health
Managing and Monitoring the Health of Cisco Unified Communications Manager Systems
Other perfmon counters should be monitored are:
•
Cisco CallManager\CallsActive, CallsAttempted, EncryptedCallsActive,
AuthenticatedCallsActive, VideoCallsActive
•
Cisco CallManager\RegisteredHardwarePhones, RegisteredMGCPGateway
•
Cisco CallManager\T1ChannelsActive, FXOPortsActive, MTPResourceActive,
MOHMulticastResourceActive
•
Cisco Locations\BandwidthAvailable
•
Cisco CallManager System Performance\AverageExpectedDelay
•
CodeYellow
•
DBReplicationFailure
•
LowCallManagerHeartbeat
•
ExcessiveVoiceQualityReports
•
MaliciousCallTrace
•
CDRFileDeliveryFailure/CDRAgentSendFileFailed
•
Critical Service Down
•
CoreDumpFileFound
Figure 3-8 displays the RTMT performance window.
Figure 3-8
Note
RTMT Performance of Stand Alone Clusters
In general, Cisco Unified CM Release 4.x perfmon counters have been preserved by using the same
names and representing the same values.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
3-22
OL-20105-01
Chapter 3
Managing and Monitoring the Health of Cisco Unified Communications Manager Systems
RTMT Monitoring of Cisco Unified CM System Health
RIS Data Collector PerfMonLog
In Cisco Unified CM Release 5.x, the RIS Data Collector PerfMonLog file is not enabled by default. It
is recommended that RIS Data Collector PerfMonLog is enabled to assist in troubleshooting. It tracks
CPU, memory, disk, and the network. If you enable RIS Data Collector PerfMonLog, then you can
disable AMC PerfMonLog. In Cisco Unified CM Release 6.x, RIS Data Collector PerfMonLog replaced
AMC PerfMonLog.
Note
With RIS Data Collector PerfMonLog enabled, the impact on the CPU is small, around 1%.
Use RTMT Trace and Log Center to download Cisco RIS Data Collector PerfMonLog files for the time
period that you are interested in. Open the log file using Windows Perfmon Viewer (or RTMT Perfmon
viewer), then add Performance counters of interest such as:
•
CPU usage > Processor or Process % CPU
•
Memory usage > Memory %VM Used
•
Disk usage > Partition % Used
•
Call Processing > Cisco CallManager CallsActive
Figure 3-9 shows the output of the Windows Perfmon Viewer.
Figure 3-9
Windows Perfmon Viewer
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
3-23
Chapter 3
RTMT Monitoring of Cisco Unified CM System Health
Managing and Monitoring the Health of Cisco Unified Communications Manager Systems
Critical Service Status
The RTMT Critical Service window provides current status of all critical services as shown in
Figure 3-10.
Figure 3-10
Critical Service Window in RTMT
CriticalServiceDown alert is generated when any of service is down. By default, RTMT back-end
service checks for the status every 30 seconds. It is possible if the service goes down and comes back up
within that period, the CriticalServiceDown alert may not be generated.
CriticalServiceDown alert monitors only those services listed in RTMT Critical Services page. If you
suspect if service got restarted without generating Core files, check the RTMT Critical Service page has
elapsed time and Check RIS Troubleshooting perfmon log files and see if PID for service (process) is
changed.
The following CLI can be used to check the logs of Service Manager:
•
file get activelog platform/servm_startup.log
•
file get activelog platform/log/servm*.log
The following CLI can be used to duplicate certain RTMT functions:
•
admin:utils service
•
show perf
•
show risdb
CoreDumpFileFound alert is generated when RTMT backend service detects new Core Dump file. Both
CriticalServiceDown and CoreDumpFileFound alert can be configured to download corresponding trace
files for troubleshooting purpose. This helps to preserve trace files at the time of a crash.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
3-24
OL-20105-01
Chapter 3
Managing and Monitoring the Health of Cisco Unified Communications Manager Systems
RTMT Monitoring of Cisco Unified CM System Health
Syslog Messages
Syslog messages can be viewed using RTMT syslog viewer as shown in Figure 3-11.
Figure 3-11
Syslog Viewer
To send syslog traps to a remote server for the CISCO-SYSLOG-MIB follow these steps:
Step 1
Setup Trap (Notification) destination in Cisco Unified Serviceability SNMP window.
Step 2
Enable trap generation in CISCO-SYSLOG-MIB.
Step 3
Set the appropriate SysLog level in CISCO-SYSLOG-MIB.
If syslog traps are not being generated for some Cisco Unified CM service alarms, check the RTMT
syslog viewer to see if the alarms are shown there. If not, adjust alarm configuration setting to send
alarms to local syslog.
Syslogs generated due to hardware failures have an event severity of 4 or higher and contain one of the
following patterns:
•
*cma*[???]:*
•
*cma*[????]:*
•
*cma*[?????]:*
•
*hp*[???]:*
•
*hp*[????]:*
•
*hp*[?????]:*
You can search for the above patterns to find hardware failure events in syslog.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
3-25
Chapter 3
Recovery, Hardware Migration, and Backup/Restore
Managing and Monitoring the Health of Cisco Unified Communications Manager Systems
For information on alarm configuration, refer to the Alarm Configuration section of the Cisco Unified
Serviceability Administration Guide at
http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/service/5_1_3/ccmsrva/saalarm.html
RTMT Alerts as Syslog Messages and Traps
RTMT alerts can be sent to a remote syslog server. To send to a local and remote syslog server, configure
the AMC alarm in Cisco Unified Serviceability. Figure 3-12 shows the window.
Figure 3-12
Local and Remote Syslog Configuration
Recovery, Hardware Migration, and Backup/Restore
The following topics are described in this section:
•
Backup/Restore, page 3-26
•
Platform Monitoring, page 3-27
Backup/Restore
Cisco provides the following backup/restore utilities:
•
Cisco Unified CM Release 4.x uses the Backup and Restore System (BARS) application
•
Cisco Unified CM Release 5.x uses the Disaster Recovery Framework (DRF)
•
Cisco Unified CM Release 6.x uses the Disaster Recovery System (DRS), essentially a renaming of
DRF above
These tools support writing backup files to (or reading restore files from) a local tape drive, or a file on
a network location. BARS uses Windows shares and DRF/DRS use SFTP to access the network
location. If a third-party backup solution is desired, BARS/DRF/DRS can write to a network location
for the third-party backup solution to pick up.
DRF/DRS perform a cluster-wide backup, meaning data from all nodes is backed up, but restores are
only to the node (s) that need it.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
3-26
OL-20105-01
Chapter 3
Managing and Monitoring the Health of Cisco Unified Communications Manager Systems
Platform Monitoring
For more details, including what is configured to be included in the backup or what files are created,
refer to the following documents depending on release:
•
Disaster Recovery Administration Guide
•
Cisco IP Telephony Disaster Recovery Administration Guide
•
Cisco IP Telephony Backup and Restore System (BARS) Administration Guide
It is recommended to take a fresh backup every time an install, upgrade or options install is done to the
appliance, whether or not configuration data changes were made.
If a catastrophic hardware failure occurs and the hardware must be replaced, reinstall Cisco Unified CM
on the new hardware, then perform a restore from your backup.
Note
Drive pull/swap is not supported as a fast recovery solution for the appliance.
Refer to the Replacing a Single Server or Cluster for Cisco Unified Communications Manager chapter
of your release of Cisco Unified Communications Manager Install and Upgrade Guide at this index:
http://www.cisco.com/en/US/products/sw/voicesw/ps556/prod_installation_guides_list.html.
Platform Monitoring
This section describes hardware-layer monitoring for system component temperature, fan status, power
supply status, RAID and disk status, network status, and operational status. CPU status/utilization and
Memory status/utilization are covered in another section. It contains the following subsections:
•
Using SNMP MIBs, page 3-27
•
Using Command Line Interface, page 3-28
•
Hardware Migration, page 3-32
•
Platform Security, page 3-32
Using SNMP MIBs
Cisco Unified CM hardware servers are monitored by using SNMP MIBs. The following MIBs are
supported:
•
Vendor-Specific MIBs (Chapter 9, “Vendor-Specific Management Information Base”)
– IBM-SYSTEM-LMSENSOR
– IBM-SYSTEM-POWER
– IBM-SYSTEM-RAID
– IBM-SYSTEM-xxx-MIB
– CPQ-xxx-MIB (HP)
– CPQHEALTH (HP)
– INTEL-SERVER-BASEBOARD6 (Introduced in Cisco Unified CM Release 7.1[2])
You configure SNMP in the network management applications to receive SNMP traps, notifications, and
informs listed in the MIBs. Specific MIB support varies by Cisco Unified CM release and hardware
vendor.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
3-27
Chapter 3
Managing and Monitoring the Health of Cisco Unified Communications Manager Systems
Platform Monitoring
MIBs and MCS Types
There are no specific OIDs available to directly give the MCS type. In the case of Linux appliances, the
value of sysObjectID can be mapped to the server types. For instance sysobjectID returns
1.3.6.1.4.1.9.1.583 for a HP-7825 server.
In the case of Windows, there are no such specific values returned for server types except for OID does
identify the server as a Windows server. Refer to
http://www.oidview.com/mibs/9/CISCO-PRODUCTS-MIB.html for list of sysObjectIDs assigned to
different hardware.
For Media Convergence Server (MCS) MIBs supported by Cisco Unified CM releases, go to this
URL—http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/compat/cmmibcmp.xls.
Using Command Line Interface
System BIOS is viewable during the server boot sequence. The following commands are useful to view
details about hardware, BIOS, RAID, and firmware. These items are included as part of the Cisco
Unified CM image and do not need to be managed separately as in Cisco Unified CM Release 4.x, but
may need to be inspected during diagnostic activity.
show hardware
show environment [fans | power-supply | temperature]
show tech all
utils create report hardware
You can also use the admin:utils fior status CLI to isolate which process causes high IOwait. Other
available options to use with the admin:utils fior command are—enable, disable, start, stop, list, top. For
example, at the command prompt type admin:utils fior list. This displays:
2007-05-31
Counters Reset
Time
Process
PID
State
Bytes Read
Bytes Written
17:02:45
rpmq
31206
Done
14173728
0
17:04:51
java
31147
Done
310724
3582
17:04:56
snmpget
31365
Done
989543
0
17:10:22
top
12516
Done
7983360
0
17:21:17
java
31485
Done
313202
2209
17:44:34
java
1194
Done
92483
0
17:44:51
java
1231
Done
192291
0
17:45:09
cdpd
6145
Done
0
2430100
17:45:25
java
1319
Done
192291
0
17:45:31
java
1330
Done
192291
0
17:45:38
java
1346
Done
192291
0
17:45:41
rpmq
1381
Done
14172704
0
17:45:44
java
1478
Done
192291
0
17:46:05
rpmq
1540
Done
14172704
0
17:46:55
cat
1612
Done
2560
165400
17:46:56
troff
1615
Done
244103
0
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
3-28
OL-20105-01
Chapter 3
Managing and Monitoring the Health of Cisco Unified Communications Manager Systems
Platform Monitoring
18:41:52
rpmq
4541
Done
14172704
0
18:42:09
rpmq
4688
Done
14172704
0
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
3-29
Chapter 3
Managing and Monitoring the Health of Cisco Unified Communications Manager Systems
Platform Monitoring
Use admin:utils fior top CLI fior output sorted by top disk users. This displays:
Top processes for interval starting 2007-05-31 15:27:23
Sort by Bytes Written
Process
PID
Bytes Read
Read Rate
Bytes Written
Write Rate
Linuxzip
19556
61019083
15254771
12325229
3081307
Linuxzip
19553
58343109
11668622
9860680
1972136
Linuxzip
19544
55679597
11135919
7390382
1478076
installdb
28786
3764719
83660
6847693
152171
Linuxzip
20150
18963498
6321166
6672927
2224309
Linuxzip
20148
53597311
17865770
5943560
1981187
Linuxzip
19968
9643296
4821648
5438963
2719482
Linuxzip
19965
53107868
10621574
5222659
1044532
Linuxzip
19542
53014605
13253651
4922147
1230537
mv
5048
3458525
3458525
3454941
3454941
Other commands that are available are as follows:
•
admin:utils diagnose list
•
admin:utils diagnose test
•
admin:utils diagnose module <moduleName>
•
admin:utilsdiagnose fix
•
admin:utils create report hardware
•
admin:utils iostat
admin:utils diagnose list CLI
Displays all available diagnostic tests as follows:
Available diagnostics modules
disk_space
- Check available disk space as well as any unusual disk usage
service_manager
- Check if service manager is running
tomcat
- Check if Tomcat is deadlocked or not running
admin:utils diagnose test CLI
Executes each diagnostic test. It will not attempt to repair anything. This displays:
Starting diagnostic test(s)
===========================
test - disk_space
—Passed
test - service_manager
—Passed
test - tomcat
—Passed
Diagnostics Completed
admin:utils diagnose module <moduleName> CLI
Executes a single diagnostic test and attempt to fix the problem. You can also use admin:utils diagnose
fix CLI to run all of the diagnostic tests at once. For example, admin:utils diagnose module tomcat
displays:
Starting diagnostic test(s)
===========================
test - tomcat
—Passed
Diagnostics Completed
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
3-30
OL-20105-01
Chapter 3
Managing and Monitoring the Health of Cisco Unified Communications Manager Systems
Platform Monitoring
admin:utils diagnose fix CLI
Execute all diagnostic tests, and if possible, attempt to repair the system. This displays:
Starting diagnostic test(s)
===========================
test - disk_space
—Passed
test - service_manager
—Passed
test - tomcat
—Passed
Diagnostics Completed
admin:utils create report hardware CLI
Creates a system report containing disk array, remote console, diagnostic, and environmental data. No
parameters are required. This displays:
***
W A R N I N G
***
This process can take several minutes as the disk array, remote console,
system diagnostics and environmental systems are probed for their current
values.
Continue? Press y or Y to continue, any other key to cancel request.
Continuing with System Report request...
Collecting Disk Array Data...SmartArray Equipped server detected...Done
Collecting Remote Console Data...Done
Collecting Model Specific System Diagnostic Information...Done
Collecting Environmental Data...Done
Collecting Remote Console System Log Data...Done
Creating single compressed system report...Done
System report written to SystemReport-20070730020505.tgz
To retrieve diagnostics use CLI command:
file get activelog platform/log/SystemReport-20070730020505.tgz
admin:utils iostat CLI
Provides the iostat output for the given number of iterations and interval. Displays the interval in
seconds between two iostat readings and the number of iostat iterations to be performed. This displays:
Executing command... Please be patient
Tue Oct 9 12:47:09 IST 2007
Linux 2.4.21-47.ELsmp (csevdir60)
10/09/2007 Time—12:47:09 PM
avg-cpu
%user
%nice
%sys
%iowait
%idle
3.61
0.02
3.40
0.51
92.47
Device
rrqm/s
wrqm/s
r/s
w/s
rsec/s
wsec/s
rkB/s
wkB/s
avgrq-sz
avgqu-sz
await
svctm
sda
3.10
19.78
0.34
7.49
27.52
218.37
13.76
109.19
31.39
0.05
5.78
0.73
sda1
0.38
4.91
0.14
0.64
4.21
44.40
2.10
22.20
62.10
0.02
26.63
1.62
sda2
0.00
0.00
0.00
0.00
0.00
0.00
0.00
0.00
10.88
0.00
2.20
2.20
sda3
0.00
0.00
0.00
0.00
0.00
0.000.00
0.00
5.28
0.00
1.88
1.88
0.00
sda4
0.00
0.00
0.00
0.00
0.00
0.00
0.00
0.00
1.83
0.00
1.67
1.67
sda5
0.00
0.08
0.01
0.01
0.04
0.73
0.02
0.37
64.43
0.00
283.91
69.81
sda6
2.71
14.79
0.20
6.84
23.26
173.24
11.63
86.62
27.92
0.02
2.98
0.61
The following CLI can be used to monitor and manage intracluster connections:
•
admin:utils dbreplication status
•
admin:utils dbreplication repair all/nodename
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
3-31
Chapter 3
Managing and Monitoring the Health of Cisco Unified Communications Manager Systems
Platform Monitoring
•
admin:utils dbreplication reset all/nodename
•
admin:utils dbreplication stop
•
admin:utils dbreplication dropadmindb
•
admin:utils dbreplication setrepltimeout
•
show tech dbstateinfo
•
show tech dbinuse
•
show tech notify
•
run sql <query>
Hardware Migration
Customers may wish to migrate their Cisco Unified CM to more powerful hardware, either to prepare
for upgrading to a later Cisco Unified CM release that does not support the older hardware, or just to
leverage capabilities only available in the more powerful hardware, such as increases in
capacity/performance or RAID. The procedure is to backup from the old hardware, install the same
Cisco Unified CM release to the new hardware, then restore on the new hardware.
Migrating to more powerful hardware may require a migration SKU to cover royalties Cisco owes to
third-parties. If you are considering this, have your account team check the Guide to Cisco Unified CM
Upgrades and Server Migrations, which is a supplement to the Cisco Unified CM Ordering Guide.
Platform Security
The following topics are covered in this section:
•
Locked-down System, page 3-32
•
Cisco Security Agent Support, page 3-33
•
Security Patching and Updating, page 3-33
•
Role-Based Access Control, page 3-33
Locked-down System
For security, Cisco Security Agent is included along with a built-in firewall controlling connectivity
among all cluster nodes, via IP tables and sensitive ports defined by the application. No AntiVirus
application is installed on the appliance. The native OS used by the appliance is also hardened to
minimize attack surface and vulnerabilities; fewer than 200 of the thousands of available packages are
used to eliminate unused software and the corresponding vulnerabilities.
No “on-box” e-mail clients or Web browsers are supported, all unnecessary logins have been removed
or disabled, and all software is provided by Cisco and digitally signed to ensure it is authorized by Cisco.
The GUI, CLI, and API interfaces that Cisco provides are the only methods to administer the system,
and authentication is required for users to interact with them. It also useful to note that appliances of this
sort are less frequently targets of malware than Microsoft Windows or other systems with open-system
access to the native OS, so significantly fewer patches need to be applied to the base OS.
Cisco Unified CM regulates its TCP/UDP port usage. See the “Cisco Unified Communications Manager
TCP and UDP Port Usage” document for each Cisco Unified CM release for the specific list.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
3-32
OL-20105-01
Chapter 3
Managing and Monitoring the Health of Cisco Unified Communications Manager Systems
Software Configuration Management
Cisco Security Agent Support
The Appliance supports the “headless” or unmanaged Cisco Security Agent. A future release will add
support for the event monitoring features of Cisco Security Agent Management Center, but not for
policy edits and distribution.
Security Patching and Updating
The Appliance’s software image contains all security updates and patches made to firmware, drivers,
native OS, database and Cisco Unified CM application components. Customers who keep current with
Cisco maintenance releases are automatically covered for security updates. For more details, refer to the
Application Note “Appliance Security Update Process for Cisco Unified Communications Manager”
(C27-412838-00), available on request from your Cisco account team.
Role-Based Access Control
Cisco Unified CM uses Multi-Layer Admin (MLA) for RBAC control over authorization to Cisco
Unified CM configuration.
Software Configuration Management
The Cisco Unified CM server uses a bundled image including all components needed for the system in
a single set of DVDs or software downloads. Unlike Cisco Unified CM Release 4.x in which there were
up to 6 different components to manage for a total of 18 updates per year on average to stay current, the
server has 2 components with an average of 5 updates per year to stay current.
It is recommended that you keep your system current with the latest maintenance release for a
major/minor feature release. Major and minor release install files are available on DVD media kits or on
Product Upgrade Tool at http://www.cisco.com/go/upgrade.
Rebuilds, upgrade files for minor and maintenance releases, and Cisco option files and tools are
available as software downloads from Software Center at
http://www.cisco.com/kobayashi/sw-center/sw-voice.shtml.
Customers wishing to receive automatic e-mail notification of availability of new files on Software
Center should subscribe to the e-mail notification tool on that site. Engineering “special” releases are
only available to customers by using Cisco Technical Assistance Center.
The following topics are described in this section:
•
General Install/Upgrade Procedures, page 3-33
•
Detecting Installed Release and Packages, page 3-34
General Install/Upgrade Procedures
Unattended first-time installs can be performed by using the Cisco Unified Communications Answer
File Generator at http://www.cisco.com/web/cuc_afg/index.html . For other details, see the online help
and the document Installing Cisco Unified Communications Manager.
For upgrades and from the list, find the appropriate release for your upgrade in the following index:
http://www.cisco.com/en/US/products/sw/voicesw/ps556/prod_installation_guides_list.html
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
3-33
Chapter 3
Managing and Monitoring the Health of Cisco Unified Communications Manager Systems
Available Reports
Detecting Installed Release and Packages
You have several methods to display the installed release and packages that are:
•
show version [active | inactive] and show packages active commands
•
Cisco Unified Operations Manager
•
Unified OS Administration
•
Cisco Unified Communications Manager
•
SNMP
A third-party NMS can query the Cisco Unified CM release by using the following SNMP OID:
•
.iso.org.dod.internet.private.enterprises.cisco.ciscoMgmt.ciscoCcmMIB.ciscoCcmMIBObjects.ccm
GeneralInfo.ccm Table.ccmEntry.ccmVersion
The Cisco Unified CM licensing web page displays the uploaded license file release, which may or may
not be an exact match for what is installed on the system.
Available Reports
This section contains the following subsections:
•
RTMT Reports, page 3-34
•
Serviceability Reports, page 3-34
•
Cisco Unified Reporting, page 3-35
RTMT Reports
RTMT has a number of pre-can screens for information such as Summary, Call Activity, Device Status,
Server Status, Service Status, and Alert Status. RTMT “Summary” pre-can screen shows a summary
view of Cisco Unified C M system health. It shows CPU, Memory, Registered Phones, CallsInProgress,
and ActiveGateway ports & channels. This should be one of the first thing you want to check each day
to make sure CPU & memory usage are within normal range for your cluster and all phones are registered
properly.
Phone Summary and Device Summary pre-can screens provide more detailed information about phone
and gateway status. If there are a number of devices that fail to register, then you can use the Admin
Find/List page or RTMT device search to get further information regarding the problem devices. Critical
Services pre-can screen displays the current running/activation status of key services. You can access
all the pre-can screens by simply clicking the corresponding icons on the left.
Serviceability Reports
The Cisco Serviceability Reporter service generates daily reports in Cisco Unified CallManager
Serviceability Web Page. Each report provides a summary that comprises different charts that display
the statistics for that particular report. Reporter generates reports once a day on the basis of logged
information, such as—
•
Device Statistics Report
•
Server Statistics Report
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
3-34
OL-20105-01
Chapter 3
Managing and Monitoring the Health of Cisco Unified Communications Manager Systems
Available Reports
•
Service Statistics Report
•
Call Activities Report
•
Alert Summary Report
•
Performance Protection Report
For detailed information about each report, go to
http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/service/5_0_2/ccmsrvs/sssrvrep.html#wp103
3420
Cisco Unified Reporting
Cisco Unified Reporting is accessed at the Cisco Unified CM Administration console and generates
reports for troubleshooting or inspecting cluster data. It provides cluster data without requiring multiple
steps to find the data. The tool design facilitates gathering data from existing sources, comparing the
data, and reporting irregularities. Figure 3-13 displays the available reports. Refer to the Cisco Unified
CM Administration Guide for further detailed information.
Figure 3-13
System Reports
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
3-35
Chapter 3
Managing and Monitoring the Health of Cisco Unified Communications Manager Systems
General Health and Troubleshooting Tips
General Health and Troubleshooting Tips
This section contains the following subsections:
•
Using of Onboard Agents, page 3-36
•
Call Detail Records and Call Maintenance Records, page 3-36
•
Perfmon Counters, page 3-37
•
Integration with Uninterruptible Power Supplies (UPS), page 3-37
•
Native Hardware Out of Band Management (OOB), page 3-37
•
Phone Registration Status, page 3-38
•
Historical Information Download, page 3-38
•
Cisco CallManager Service Stops Responding, page 3-38
•
Database Replication Fails Between the Publisher and the Subscriber, page 3-39
•
Database Replication Does Not Occur on Lost Node, page 3-42
•
Database Tables Out of Sync Do Not Trigger Alert, page 3-42
•
Reset Database Replication When Reverting to Prior Release, page 3-43
•
Useful Commands and Utilities, page 3-43
For more information on troubleshooting, refer to the Troubleshooting Guide for Cisco Unified
Communications Manager at the following index:
http://www.cisco.com/en/US/products/sw/voicesw/ps556/prod_troubleshooting_guides_list.html.
Using of Onboard Agents
Onboard agents are third-party software clients, agents or daemons installed on-box, including but not
limited to:
•
Anti-virus clients
•
Uninterruptible Power Supply monitoring agents
•
Management agents
Certain types of onboard agents are supported in Cisco Unified CM Release 4.x. The appliance used by
Cisco Unified CM Release 5.0 and later releases does not support installation of onboard agents, rather
it exposes APIs for third-party integration.
For more details, see the November 2007 bulletin on Third-Party Platform Agents at
http://www.cisco.com/en/US/products/sw/voicesw/ps556/prod_bulletins_list.html.
Call Detail Records and Call Maintenance Records
CDR and CMRs are used for a variety of uses including billing, chargeback, administrative oversight
and diagnostics. In addition to a canned application for managing CDR/CMR, Cisco Unified CM
Release 4.x supported various means of direct database access for external systems to access the
CDR/CMR data. Cisco Unified CM Release 5.0 and later releases use SFTP to push formatted files off
Cisco Unified CM to the requesting application.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
3-36
OL-20105-01
Chapter 3
Managing and Monitoring the Health of Cisco Unified Communications Manager Systems
General Health and Troubleshooting Tips
When CDR is activated, a CPU utilization increase of 2% is typical, 4% if both CDR and CMR are
activated.
Perfmon Counters
Table 3-5 lists some equivalent perfmon counters between Cisco Unified CM Release 4.x and Release
5.x and later.
Table 3-5
Equivalent Perfmon Counters
Cisco Unified CM Release 4.x Perfmon
Counters
Cisco Unified CM Release 5.x Perfmon
Counters
Process
Process
% Privileged Time
% Processor Time
Processor
% UserTime
STime
% CPU Time
Processor
User Percentage
% Privileged Time
System Percentage
% Idle Time
Nice Percentage
% Processor Time
% CPU Time
Integration with Uninterruptible Power Supplies (UPS)
As of Cisco Unified CM Release 6.0(1a) and later, the server supports integration with certain models
of APC UPS for certain MCS 7800 models. Previous server releases rely on an external script monitoring
the UPS and issuing the Cisco CLI for graceful shutdown. See the release notes for Cisco Unified CM
6.0(1b) for more details at
http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/rel_notes/6_0_1/cucm-rel_note-601b.html.
Note
Native hardware out-of-band management such as HP iLO or IBM RSA II cannot be used for graceful
shutdown of Cisco Unified CM.
Native Hardware Out of Band Management (OOB)
The supported features of HP iLO and IBM RSA II are enabled for the following areas:
•
CPU status/utilization
•
Memory status/utilization
•
System components temperatures
•
Fan status
•
Power Supply status
•
RAID & disk status
•
Network status including NIC
•
Operational status, including instrumentation of system/kernel status and data dumps following
major system issues, indicating nature/type of the operational problem and degree of severity.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
3-37
Chapter 3
Managing and Monitoring the Health of Cisco Unified Communications Manager Systems
General Health and Troubleshooting Tips
Support of these interfaces on the server includes the following capabilities (specific feature names vary
by hardware vendor):
•
Remote console (to access boot screens and the Cisco CLI)
•
Remote power management
Phone Registration Status
Phone registration status needs to be monitored for sudden changes. If the registration status changes
slightly and readjusts quickly over a short time frame, then it could be indicative of phone move, add,
or change. A sudden smaller drop in phone registration counter can be indicative of a localized outage,
for instance an access switch or a WAN circuit outage or malfunction. A significant drop in registered
phone level needs immediate attention by the administrator. This counter especially needs to be
monitored before and after the upgrades to ensure the system is restored completely.
Historical Information Download
You can also download some historical information using RTMT Trace Log Center or SOAP APIs, such
as:
•
Cisco AMC Service PerfMonLog is enabled by default but deprecated in Cisco Unified CM Release
6.0 because Cisco RIS Data Collector PerfMonLog is introduced.
•
Cisco RIS Data Collector PerfMonLog is disabled by default in Cisco Unified CM Release 5.x and
enabled by default in Cisco Unified CM Release 6.0.
Cisco CallManager Service Stops Responding
When the Cisco CallManager service stops responding, the following message displays in the System
Event log:
The Cisco CallManager service terminated unexpectedly.
It has done this 1 time. The following corrective action
will be taken in 60000 ms. Restart the service.
Other messages you may see in this situation:
Timeout 3000 milliseconds waiting for
Cisco CallManager service to connect.
The Cisco Communications Manager failed to start due to the following error:
The service did not respond to the start or control request in a timely fashion.
At this time when devices such as the Cisco Unified IP Phones and gateways, unregister from the Cisco
Unified Communications Manager, users receive delayed dial tone, and/or the Cisco Unified
Communications Manager server freezes due to high CPU usage. For event log messages that are not
included here, view the Cisco Unified Communications Manager Event Logs.
Possible Cause
The Cisco CallManager service can stop responding because the service does not have enough resources
such as CPU or memory to function. Generally, the CPU utilization in the server is 100 percent at that
time.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
3-38
OL-20105-01
Chapter 3
Managing and Monitoring the Health of Cisco Unified Communications Manager Systems
General Health and Troubleshooting Tips
Recommended Action
Depending on what type of interruption you experience, you will need to gather different data that will
help determine the root cause of the interruption.
Use the following procedure if a lack of resources interruption occurs.
Procedure
Step 1
Collect Cisco CallManager traces 15 minutes before and after the interruption.
Step 2
Collect SDL traces 15 minutes before and after the interruption.
Step 3
Collect perfmon traces if available.
Step 4
If the traces are not available, start collecting the perfmon traces and track memory and CPU usage for
each process that is running on the server. These will help in the event of another lack of resources
interruption.
Database Replication Fails Between the Publisher and the Subscriber
Replicating the database represents a core function of Cisco Unified Communications Manager clusters.
The server with the master copy of the database acts as the publisher (first node), while the servers that
replicate the database comprise subscribers (subsequent nodes).
Tip
Before you install Cisco Unified Communications Manager on the subscriber server, you must add the
subscriber to the Server Configuration window in Cisco Unified Communications Manager
Administration to ensure that the subscriber replicates the database that exists on the publisher database
server. After you add the subscriber server to the Server Configuration window and then install Cisco
Unified Communications Manager on the subscriber, the subscriber receives a copy of the database that
exists on the publisher server.
Changes that are made on the publisher server are not reflected on phones that are registered with the
subscriber server.
Possible Cause
Replication fails between the publisher and subscriber servers.
Recommended Action
Verify and, if necessary, repair database replication, as described in the following procedure:
Procedure
Step 1
Verify database replication. You can use the CLI, Cisco Unified Reporting, or RTMT to verify database
replication.
•
To verify using the CLI, see Step 2.
•
To verify using Cisco Unified Reporting, see Step 3.
•
To verify using RTMT, see Step 4.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
3-39
Chapter 3
Managing and Monitoring the Health of Cisco Unified Communications Manager Systems
General Health and Troubleshooting Tips
Step 2
To verify database replication using the CLI, access the CLI and issue the following command to check
replication on each node. You will need to run this CLI command on each node to check its replication
status. Also, after a subscriber is installed, depending on the number of subscribers, it may take a
considerable amount of time to achieve a status of 2.:
admin: show perf query class “Number of Replicates Created and State of Replication”
==>query class :
- Perf class (Number of Replicates Created and State of Replication)
has instances and values:
ReplicateCount -> Number of Replicates Created
= 344
ReplicateCount -> Replicate_State
= 2
Be aware that the Replicate_State object shows a value of 2 in this case. The following list shows the
possible values for Replicate_State:
Step 3
•
0—This value indicates that replication did not start. Either no subsequent nodes (subscribers) exist,
or the Cisco Database Layer Monitor service is not running and has not been running since the
subscriber was installed.
•
1—This value indicates that replicates have been created, but their count is incorrect.
•
2—This value indicates that replication is good.
•
3—This value indicates that replication is bad in the cluster.
•
4—This value indicates that replication setup did not succeed.
To verify database replication using Cisco Unified Reporting, perform the following tasks.
a.
From the Navigation drop-down list box in the upper, right corner in Cisco Unified Communications
Manager Administration, choose Cisco Unified Reporting.
b.
After Cisco Unified Reporting displays, click System Reports.
c.
Generate and view the Cisco Unified CM Database Status report, which provides debugging
information for database replication.
Once you have generated the report, open it and look at the Cisco Unified CM Database Status. It
gives the RTMT replication counters for all servers in the cluster. All servers should have a replicate
state of 2, and all servers should have the same number of replicates created.
If you see any servers whose replicate states are not equal to 2 in the above status check, inspect the
“Replication Server List” on this report. It shows which servers are connected and communicating
with each node. Each server should show itself as local (in its list) and the other servers as active
connected. If you see any servers as dropped, it usually means there is a communication problem
between the nodes.
d.
Step 4
If you want to do so, generate and view the Cisco Unified CM Database Status report, which
provides a snapshot of the health of the Cisco Unified Communications Manager database.
To verify database replication using RTMT, perform the following tasks:
a.
Open the Cisco Unified Real-Time Monitoring Tool (RTMT).
b.
Click the CallManager tab.
c.
Click Database Summary. The Replication Status pane displays.
The following list shows the possible values for the Replication Status pane:
•
0—This value indicates that replication has not started. Either no subsequent nodes (subscribers)
exist, or the Cisco Database Layer Monitor service is not running and has not been running since
the subscriber was installed.
•
1—This value indicates that replicates have been created, but their count is incorrect.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
3-40
OL-20105-01
Chapter 3
Managing and Monitoring the Health of Cisco Unified Communications Manager Systems
General Health and Troubleshooting Tips
•
2—This value indicates that replication is good.
•
3—This value indicates that replication is bad in the cluster.
•
4—This value indicates that replication setup did not succeed.
d.
To view the Replicate_State performance monitoring counter, choose System > Performance >
Open Performance Monitoring. Double-click the publisher database server (first node) to expand
the performance monitors. Click Number of Replicates Created and State of Replication.
Double-click Replicate_State. Click ReplicateCount from the Object Instances window and click
Add.
Tip
Step 5
To view the definition of the counter, right click the counter name and choose Counter
Description.
If all the servers have a good RTMT status, but you suspect the databases are not in sync, you can run
the CLI command utils dbreplication status (If any of the servers showed an RTMT status of 4, proceed
to Step 6).
This status command can be run on all servers by using utils dbreplication status all or on one
subscriber by using utils dbreplication status <hostname>.
The status report will tell you if any tables are suspect. If there are suspect tables, you will want to do a
replication repair CLI command to sync the data from the publisher server to the subscriber servers.
The replication repair can be done on all subscriber servers (using the all parameter) or on just one
subscriber server by using the following: utils dbreplication repair usage:utils dbreplication
repair [nodename]|all.
After running the replication repair, which can take several minutes, you can run another status
command to verify that all tables are now in sync. If tables are in sync after running the repair, you are
successful in fixing replication.
Note
Only do Step 6 if one of the servers showed an RTMT status of 4, or had a status of 0 for more than four
hours.
Step 6
Generate and view the Cisco Unified CM Database Status report, which provides debugging
information for database replication. For each subscriber server that has a bad RTMT status, check that
the hosts, rhosts, sqlhosts, and services files have the appropriate information.
Generate and view the Cisco Unified CM Cluster Overview report. Verify that the subscriber servers
have the same version, verify that connectivity is good, and verify that time delay is within tolerances.
If the preceding conditions are acceptable, do the following to reset replication on that subscriber server:
a.
At the subscriber server, perform the CLI command utils dbreplication stop
Do this for all subscriber servers that have an RTMT value of 4
b.
At the publisher server, perform the CLI command utils dbreplication stop
c.
At the publisher server, perform the CLI command utils dbreplication reset <hostname> where
<hostname> is the hostname of the subscriber server that needs to be reset. If all subscriber servers
need to be reset, use command utils dbreplication reset all
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
3-41
Chapter 3
Managing and Monitoring the Health of Cisco Unified Communications Manager Systems
General Health and Troubleshooting Tips
Database Replication Does Not Occur on Lost Node
Database replication does not occur when connectivity is restored on lost node recovery. You can verify
the state of replication by using the methods given in the topic Database Replication Fails Between the
Publisher and the Subscriber, page 3-39. Only use the following procedure if you have already tried to
reset replication on the node, and have been unsuccessful.
Possible Cause
The CDR check remains stuck in a loop, due to a delete on device table.
Recommended Action
Step 1
Run utils dbreplication stop on the affected subscribers. You can run them all at once.
Step 2
Wait until Step 1 completes, then, run utils dbreplication stop on the affected publisher server.
Step 3
Run utils dbreplication clusterreset from the affected publisher server. When you run the command,
the log name gets listed in the log file. Watch this file to monitor the process status. The path to the
follows:
/var/log/active/cm/trace/dbl/sdi
Step 4
From the affected publisher, run utils dbreplication reset all.
Step 5
Stop and restart all the services on all the subscriber servers [or restart/reboot all the systems (subscriber
servers)] in the cluster to get the service changes. Do this only after utils dbreplication status shows
Status 2.
Database Tables Out of Sync Do Not Trigger Alert
Out of sync means that two servers in the cluster do not contain the same information in a specific
database table.
On Cisco Unified Communications Manager Version 6.x or later, the symptoms include unexpected call
processing behaviors. Calls do get not routed or handled as expected. The symptoms may occur on either
the publisher or on the subscriber servers.
On Cisco Unified Communications Manager Version 5.x, the symptoms include unexpected call
processing behaviors. Calls do not get routed or handled as expected but only when the publisher server
is offline. If you see these symptoms, you can run the utils dbreplication status command “Out of sync”
displays. If “Out of sync” does not display, this is not the problem.
Possible Cause
Database tables remain out of sync between nodes. Replication alerts only indicate failure in the
replication process and do not indicate when database tables are out of sync. Normally, if replication is
working, tables should remain in sync. Instances can occur in which replication appears to be working,
but database tables are “Out of sync”.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
3-42
OL-20105-01
Chapter 3
Managing and Monitoring the Health of Cisco Unified Communications Manager Systems
General Health and Troubleshooting Tips
Recommended Action
Step 1
Reset cluster replication by using CLI commands. Ensure servers in the cluster are online with full IP
connectivity for this to work. Confirm that all servers in the cluster are online by using platform CLI and
Cisco Unified Reporting.
Step 2
If the servers are in Replication State 2, use the utils dbreplication repair server name command on
the publisher server.
If the servers are not in Replication State 2, use the utils dbreplication stop command on all subscriber
servers.
Then, use the utils dbreplication stop and then utils dbreplication reset all commands on the publisher
server.
Reset Database Replication When Reverting to Prior Release
If you revert the servers in a cluster to run an older product release, you must manually reset database
replication within the cluster. To reset database replication after you revert all the cluster servers to the
older product release, use the utils dbreplication reset command all on the publisher server.
When you switch versions by using Cisco Unified Communications Operating System Administration
or the CLI, you get a message reminding you about the requirement to reset database replication if you
are reverting to an older product release.
Useful Commands and Utilities
This section provides a quick reference for commands and utilities to help you troubleshoot a Cisco
Unified Communications Manager server with root access disabled.
Table 3-6 provides a summary of the CLI commands and GUI selections that you can use to gather
information troubleshoot various system problems.
Table 3-6
Summary of CLI Commands and GUI Selections
Information
Linux
Command
Serviceability GUI Tool
CLI commands
CPU usage
top
RTMT
Processor CPU usage:
Go to View tab and select
Server > CPU and Memory
show perf query class Processor
Process CPU Usage for all processes:
show perf query counter Process “% CPU Time”
Individual process counter details (including CPU
usage)
show perf query instance <Process task_name>
Process state
ps
RTMT
show perf query counter Process “Process Status”
Go to View tab and select
Server > Process
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
3-43
Chapter 3
Managing and Monitoring the Health of Cisco Unified Communications Manager Systems
Related Documentation
Table 3-6
Summary of CLI Commands and GUI Selections (continued)
Information
Linux
Command
Serviceability GUI Tool
CLI commands
Disk usage
df/du
RTMT
show perf query counter Partition
“% Used”
Go to View tab and select
Server > Disk Usage
Memory
free
RTMT
or show perf query class Partition
show perf query class Memory
Go to View tab and select
Server > CPU and Memory
Network status
netstats
Reboot server
reboot
show network status
Log in to Platform Web page on utils system restart
the server
Go to Restart > Current Version
Collect
Traces/logs
Sftp, ftp
RTMT
List file: file list
Go to Tools tab and select Trace Download files: file get
> Trace & Log Central
View a file: file view
Related Documentation
It supplements but does not replace the existing documentation including the following:
•
Maintain and operate guides index at
http://www.cisco.com/en/US/products/sw/voicesw/ps556/prod_maintenance_guides_list.html
– Cisco Unified Communications Manager Serviceability Administration Guide
– Cisco Unified Communications Manager Serviceability System Guide
– Changing the IP Address and Hostname for Cisco Unified Communications Manager 5.x, 6.x,
and 7.x Servers
– Cisco Unified Communications Real-Time Monitoring Tool Administration Guide
– Cisco Unified Communications Operating System Administration Guide
– Disaster Recovery System Administration Guide
•
Install and upgrade guides index at
http://www.cisco.com/en/US/products/sw/voicesw/ps556/prod_installation_guides_list.html
– Replacing a Single Server or Cluster for Cisco Unified Communications Manager
– Upgrading to Cisco Unified Communications Manager
– Installing Cisco Security Agent for Cisco Unified Communications Manager
For documentation for CDR/CMR, see the following documents:
•
For Cisco Unified CM Release 8.0(1)
http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/service/8_0_1/cdrdef/cdradmin.html
•
For Cisco Unified CM Release 6.1(1)
http://www.cisco.com/en/US/docs/voice_ip_comm/service/6_1_1/car_cm/pdf - chapter 10
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
3-44
OL-20105-01
Chapter 3
Managing and Monitoring the Health of Cisco Unified Communications Manager Systems
Related Documentation
•
For Cisco Unified CM Release 6.0(1)
http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/service/6_0_1/car/cmcarbk.html chapter 10
•
Cisco Unified CM Release 5.1(3)
http://www.cisco.com/en/US/products/sw/voicesw/ps556/prod_maintenance_guides_list.html
•
Cisco Unified CM Release 5.0(4)
http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/cdr_defs/5_x/cdr504.html
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
3-45
Chapter 3
Managing and Monitoring the Health of Cisco Unified Communications Manager Systems
Related Documentation
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
3-46
OL-20105-01
CH A P T E R
4
Simple Network Management Protocol
This chapter gives an overview of Simple Network Management Protocol (SNMP). It contains the
following sections:
•
Overview, page 4-1
•
SNMP Versioning, page 4-2
•
SNMP and Cisco Unified CM Basics, page 4-3
•
SNMP Basic Commands, page 4-3
•
SNMP Community Strings and Users, page 4-4
•
SNMP and Cisco MIBs, page 4-4
•
SNMP Traps and Informs, page 4-5
•
SNMP Trace Configuration, page 4-5
•
SNMP Tips, page 4-5
•
SNMP Troubleshooting, page 4-6
Overview
Simple Network Management Protocol (SNMP), an application layer protocol, facilitates the exchange
of management information among network devices, such as nodes and routers. It comprises part of the
TCP/IP suite. System administrators can remotely manage network performance, find and solve network
problems, and plan for network growth by using SNMP.
Instead of defining a large set of commands, SNMP places all operations in a get-request,
get-next-request, get-bulk-request, and set-request format. For example, an SNMP manager can get a
value from an SNMP agent or store a value in that SNMP agent. The SNMP manager can comprise part
of a network management system (NMS), and the SNMP agent can reside on a networking device such
as a router.
SNMP comprises of three parts—SNMP manager, SNMP agent, and MIBs. You can compile the Cisco
MIB with your network management software.
The NMS uses the Cisco MIB variables to set device variables and to poll devices on the internetwork
for specific information. The results of a poll can get graphed and analyzed to help you troubleshoot
internetwork problems, increase network performance, verify the configuration of devices, and monitor
traffic loads.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
4-1
Chapter 4
Simple Network Management Protocol
SNMP Versioning
The SNMP agent gathers data from the MIB, which is the repository for information about device
parameters and network data. The SNMP agent also can send traps (notifications) of certain events, to
the SNMP manager. The Cisco host //ftp.cisco.com makes available the Cisco trap file, “mib.traps,”
which documents the format of Cisco traps.
The SNMP manager uses information in the MIB to perform the operations as described:
Operation
Description
get-request
Retrieve a value from a specific variable.
get-next-request
Retrieve the value following the named variable. Often used to retrieve
variables from within a table. With this operation, an SNMP manager does not
need to know the exact variable name. A sequential search gets performed to
find the needed variable from within the MIB.
get-response
Reply to a get-request, get-next-request, get-bulk-request, and set-request that
an NMS sent.
get-bulk-request
Fills the get-response with up to max-repetition number of get-next
interactions, similar to get-next-request.
set-request
Store a value in a specific variable.
traps
Sent by an SNMP agent to an SNMP manager to indicate that some event
occurred.
SNMP Versioning
Three versions of SNMP exist: version 1 (SNMPv1), version 2 (SNMPv2), and version 3 (SNMPv3).
SNMPv1 represents the initial implementation of SNMP that functions within the specifications of the
Structure of Management Information (SMI) and operates over protocols, such as User Datagram
Protocol (UDP) and IP.
The SNMPv1 SMI defines highly structured MIB tables that are used to group objects that contain
multiple variables. Tables contain zero or more rows, which are indexed, so SNMP can retrieve or alter
an entire row with a supported command.
With SNMPv1, the NMS issues a request, and managed devices return responses. Agents use the Trap
operation to asynchronously inform the NMS of a significant event.
As with SNMPv1, SNMPv2c functions within the specifications of SMI. MIB modules contain
definitions of interrelated managed objects. Be aware that the operations that are used in SNMPv1 are
similar to those that are used in SNMPv2. The SNMPv2 trap operation, for example, serves the same
function as that used in SNMPv1, but it uses a different message format and replaces the SNMPv1 trap.
The Inform operation in SNMPv2c enables one NMS to send trap information to another NMS and to
receive a response from the NMS.
SNMPv3 provides the following security features:
•
Authentication—Verifying that the request comes from a genuine source.
•
Privacy—Encrypting data.
•
Authorization—Verifying that the user allows the requested operation.
•
Access control—Verifying that the user has access to the objects that are requested.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
4-2
OL-20105-01
Chapter 4
Simple Network Management Protocol
SNMP and Cisco Unified CM Basics
SNMPv3 prevents packets from being exposed on the network. Instead of using community strings like
SNMP v1 and v2, SNMP v3 uses SNMP users, as described in the “SNMP Community Strings and
Users” section on page 4-4.
SNMP and Cisco Unified CM Basics
A network that uses SNMP requires three key components—managed devices, agents, and network
management software (NMS).
•
Managed devices—Devices that contain SNMP agents and reside on a network. Managed devices
collect and store information and make it available by using SNMP.
– The first node in the Cisco Unified CM cluster acts as the managed device. In Cisco Unified
CMBE, the server on which Cisco Unified CM is installed acts as the managed device.
•
Agents—Software modules that contain local knowledge of management information and translates
it into a form that is compatible with SNMP.
– Cisco Unified CM uses a master agent and subagent components to support SNMP. The master
agent acts as the agent protocol engine and performs the authentication, authorization, access
control, and privacy functions that relate to SNMP requests. It contains a few Management
Information Base (MIB) variables. The master agent also connects and disconnects subagents
after the subagent completes necessary tasks.
– Cisco Unified CM uses a subagent to interact with the local Cisco Unified CM only. The Cisco
Unified CM subagents send trap and information messages to the SNMP Master Agent, and the
SNMP Master Agent communicates with the SNMP trap receiver (notification destination).
•
NMS—SNMP management application that runs on a PC and provides the bulk of the processing
and memory resources that are required for network management. It executes applications that
monitor and control managed devices. Cisco Unified Communications Manager works with the
following NMS:
– CiscoWorks2000
– HP OpenView
– Third-party applications that support SNMP and Cisco Unified Communications Manager
SNMP interfaces
SNMP Basic Commands
Managed devices get monitored and controlled by using four basic SNMP commands: read, write, trap,
and traversal operations.
•
NMS uses the read command to monitor managed devices. The NMS examines different variables
that are maintained by managed devices.
•
NMS uses the write command to control managed devices. The NMS changes the values of variables
stored within managed devices.
•
Managed devices use the trap command to asynchronously report events to the NMS. When certain
types of events occur, a managed device sends a trap to the NMS.
•
NMS uses traversal operations to determine which variables a managed device supports and to
sequentially gather information in variable tables, such as a routing table.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
4-3
Chapter 4
Simple Network Management Protocol
SNMP Community Strings and Users
SNMP Community Strings and Users
Although SNMP community strings provide no security, the strings authenticate access to MIB objects
and function as embedded passwords. You configure SNMP community strings for SNMP v1 and v2c
only.
SNMP v3 does not use community strings. It uses SNMP users that serve the same purpose as
community strings but provide security because encryption or authentication is configured.
No default community string or user exists.
SNMP and Cisco MIBs
You can access the Cisco MIB variables by using SNMP which facilitates the exchange of management
information between network devices. The SNMP system comprises three parts: SNMP manager, SNMP
agent, and MIB.
Instead of defining a large set of commands, SNMP places all operations in a get-request,
get-next-request, get-bulk-request, and set-request format. For example, an SNMP manager can get a
value from an SNMP agent or store a value in that SNMP agent. The SNMP manager can comprise part
of a network management system (NMS), and the SNMP agent can reside on a networking device such
as a router. You can compile the Cisco MIB with your network management software. If SNMP is
configured on a router, the SNMP agent can respond to MIB-related queries that are being sent by the
NMS.
The NMS uses the Cisco MIB variables to set device variables and to poll devices on the internetwork
for specific information. The results of a poll can get graphed and analyzed to help you troubleshoot
internetwork problems, increase network performance, verify the configuration of devices, monitor
traffic loads, and more.
The SNMP agent gathers data from the MIB, which provides the repository for information about device
parameters and network data. The SNMP agent also can send traps (notifications) of certain events, to
the SNMP manager. The Cisco host //ftp.cisco.com makes available the Cisco trap file, “mib.traps,”
which documents the format of Cisco traps.
The SNMP manager uses information in the MIB to perform the operations as described:
Operation
Description
get-request
Retrieve a value from a specific variable.
get-next-request
Retrieve the value following the named variable. Often used to retrieve
variables from within a table. With this operation, an SNMP manager does not
need to know the exact variable name. A sequential search is performed to
find the needed variable from within the MIB.
get-response
The reply to a get-request, get-next-request, get-bulk-request, and set-request
sent by an NMS.
get-bulk-request
Similar to get-next-request, but fills the get-response with up to
max-repetition number of get-next interactions.
set-request
Store a value in a specific variable.
traps
An unsolicited message sent by an SNMP agent to an SNMP manager
indicating that some event has occurred.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
4-4
OL-20105-01
Chapter 4
Simple Network Management Protocol
SNMP Traps and Informs
SNMP Traps and Informs
An SNMP agent sends notifications in the form of traps or informs to identify important system events.
Traps do not receive acknowledgments from the destination whereas informs do receive
acknowledgments.
Note
Cisco Unity Connection does not support SNMP traps.
For all notifications, the system sends traps immediately if the corresponding trap flags are enabled. In
the case of the syslog agent, the Cisco Unified CM alarms and system-level log messages get sent to
syslog daemon for logging. Also, some standard third-party applications send the log messages to syslog
daemon for logging. These log messages get logged locally in the syslog files and also get converted into
SNMP traps/notifications.
The following list contains Cisco Unified CM SNMP trap and inform messages that are sent to a
configured trap destination:
•
Cisco Unified CM failed
•
Phone failed
•
Phones status update
•
Gateway failed
•
Media resource list exhausted
•
Route list exhausted
•
Gateway layer 2 change
•
Quality report
•
Malicious call
•
Syslog message generated
SNMP Trace Configuration
For Cisco Unified CM, you can configure traces for the SNMP agent in the Trace Configuration window
in Cisco Unified Serviceability by choosing the Cisco Unified CM SNMP Service in the Performance
and Monitoring Services service group. A default setting exists for all the agents. For Cisco CDP Agent
and Cisco Syslog Agent, you use the command line interface (CLI) to change trace settings, as described
in the Command Line Interface Reference Guide for Cisco Unified Solutions.
SNMP Tips
Refer to the CISCO-CCM-CAPABILITY-MIB at
http://tools.cisco.com/Support/SNMP/do/BrowseMIB.do?local=en&step=2&mibName=CISCO-CCMCAPABILITY or “CISCO-CCM-CAPABILITY” section on page 7-143. As stated in the
CISCO-CCM-CAPABILITY-MIB, ccmPhoneDevicePoolIndex does not get supported, so it returns a 0.
The Callmanager device registration alarm currently does not contain the device pool information.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
4-5
Chapter 4
Simple Network Management Protocol
SNMP Troubleshooting
If Cisco CallManager SNMP service is not running, only the following tables in the MIB respond:
•
ccmGroupTable
•
ccmRegionTable
•
ccmRegionPairTable
•
ccmDevicePoolTable
•
ccmProductTypeTable
•
ccmQualityReportAlarmConfigInfo
•
ccmGlobalInfo
To get Cisco CallManager SNMP service running, activate and start the service in Cisco Unified
Serviceability. Query the following tables in the SYSAPPL-MIB:
Note
•
SysApplInstallPkgTable to get an inventory of Cisco Unified Communications Manager
applications that are installed on the system.
•
SysApplRunTable to get an inventory of Cisco Unified Communications Manager applications that
are running on the system.
Cisco Unified Communications Manager uses the following Web application services and servlets:
Cisco CallManager Admin, Cisco CallManager Cisco IP Phone Services, Cisco CallManager Personal
Directory, Cisco CallManager Serviceability, Cisco CallManager Serviceability RTMT, Cisco
Extension Mobility, Cisco Extension Mobility Application, Cisco RTMT Reporter Servlet, Cisco
Tomcat Stats Servlet, Cisco Trace Collection Servlet, Cisco AXL Web Service, Cisco Unified Mobile
Voice Access Service, Cisco Extension Mobility, Cisco IP Manager Assistant, Cisco Web Dialer
Service, Cisco CAR Web Service, and Cisco Dialed Number Analyzer.
SNMP Troubleshooting
In general ensure that all the feature and network services are running and verify that the community
string or SNMP user is properly configured on the Cisco Unified CM system. You configure the SNMP
community string or user by choosing SNMP > V1/V2 > Community String or SNMP > V3> User in
Cisco Unified Serviceability.
Other tips are as follows:
•
Cannot poll any MIBs from the system—This condition means that the community string or the
SNMP user is not configured on the system or they do not match with what is configured on the
system. Check the configuration and reconfigure if necessary.
Note
By default, no community string or user is configured on the system.
•
Cannot receive any notifications from the system—This condition means that the notification
destination is not configured correctly on the system. Verify that you configured the notification
destination properly in the Notification Destination (V1/V2c or V3) Configuration window.
•
Cannot receive SNMP traps from Cisco Unified Communications Manager node—Verify that you
configured the following MIB Object IDentifiers (OIDs) that relate to phone
registration/deregistration/failure to the following values (the default for both values equals 0):
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
4-6
OL-20105-01
Chapter 4
Simple Network Management Protocol
SNMP Troubleshooting
– ccmPhoneFailedAlarmInterval (1.3.6.1.4.1. 9.9.156.1.9.2) set to 30-3600. You can use this CLI
command: snmpset -c <community string> -v2c <transmitter ipaddress>
1.3.6.1.4.1.9.9.156.1.9.2 .0 i <value>
– ccmPhoneStatusUpdateAlarmInterval (1.3.6.1.4.1.9.9.156.1.9.4) set to 30-3600. You can use
this CLI command: snmpset -c <community string> -v2c <transmitter ipaddress>
1.3.6.1.4.1.9.9.156.1.9.4.0 i <value>
Verify that you configured the notification destination properly in the Notification Destination
(V1/V2c or V3) Configuration window.
Verify that you configured the community string/user privileges correctly, including Notify
permissions, in the Community String (V1/V2c) or User (V3) Configuration window.
Because System Application Agent cannot show services that are activated and deactivated or monitor
Web App services or servlets, use this approach to monitor system health and service status for Cisco
Unified Communications Manager applications:
•
Use the Serviceability API getservicestatus to provide complete status information, including
activation status, for both Web applications and non-Web applications. See the AXL Serviceability
API Guide for more details.
•
Check service status with this CLI command: utils service list
•
Monitor the servM-generated messages with Syslog (see the following example):
Mar 18 16:40:52 ciscart26 local7 6 : 92: Mar 18 11:10:52.630 UTC :
%CCM_SERVICEMANAGER-SERVICEMANAGER-6-ServiceActivated: Service Activated. Service
Name:Cisco CallManager SNMP Service App ID:Cisco Service Manager Cluster ID: Node
ID:ciscart26
If an SNMP request specifies multiple OIDs and the variables are pointing to empty tables, you may get
a NO_SUCH_NAME (for SNMP V1) or GENERIC ERROR (for SNMP V2c or V3) due to a timeout
problem. A timeout can occur as a result of throttling enhancements to protect the Cisco Unified
Communications Manager processing engine.
You can retrieve the count of entries in CCMH323DeviceTable and ccmSIPDeviceTable by using scalar
objects, so the SNMP Manager (the client) can avoid unnecessary get/getnext operations on these tables
when no entries exist. As an SNMP developer, you can use the following workaround for this problem:
•
Use the available scalar variables (1.3.6.1.4.1.9.9.156.1.5) to determine table size before accessing
the table or perform the get operation on the desired table; then, query the non-empty tables.
•
Reduce the number of variables that are queried in a single request; for example, for empty tables,
if the management application has the timeout set to 3 seconds, specify only 1 OID. (For non-empty
tables, it takes 1 second to retrieve one row of data.)
•
Increase the response timeout.
•
Reduce the number of retries.
•
Avoid using getbulk SNMP API. The getbulk API retrieves the number of records that is specified
by MaxRepetitions, so even if the next object goes outside the table or MIB, it gets those objects.
Empty tables cause even more delay. Use getbulk API for non-empty tables with a known number
of records. In these circumstances, set MaxRepetitions to 5 seconds to require a response within 5
seconds.
•
Structure SNMP queries to adapt to existing limits.
•
Avoid performing multiple getbulks to walk the PhoneTable periodically in case a large number of
phones are registered to Cisco CallManager. You can use the ccmPhoneStatusUpdateTable, which
updates whenever there is a Phone update, to decide whether to walk the PhoneTable.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
4-7
Chapter 4
Simple Network Management Protocol
SNMP/R MIBs
For more information about MIBs and troubleshooting, refer to the following chapters:
•
Chapter 7, “Cisco Management Information Base”
•
Chapter 8, “Industry-Standard Management Information Base”
•
Chapter 9, “Vendor-Specific Management Information Base”
SNMP/R MIBs
When SNMP/R binaries spike the CPU, collect the following logs and information for analysis:
•
Note the processes that are experiencing high CPU usage.
•
Check to see if any SNMP polling is occurring and get the polling interval of the application.
•
Note the SNMP versions by using the show packages active snmp command.
•
Execute the show process using-most cpu command and collect the output.
•
Collect the Perfmon logs by executing the file get activelog /cm/log/ris/csv/ command.
•
Collect the traces for SNMP Master Agent, and other binaries experiencing high CPU.
•
Send the above information to Support for further troubleshooting.
When the SNMP Master Agent does not start, check to see if port 161 is open. If the port is open, collect
the SNMP Master Agent traces for further analysis.
When migrating from Windows to Linux Cisco Unified CM, the ccmH323DevRmtCM1InetAddress has
been defined as OctetString in Cisco Unified CM Release 5.x and later. So, the IP Address displays as
Hexadecimal instead of the dotted decimal format as displayed in Cisco Unified CM Release 4.x.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
4-8
OL-20105-01
CH A P T E R
5
Cisco Unified Real-Time Monitoring Tool
Tracing, PerfMon Counters, and Alerts
This chapter briefly describes the Cisco Unified Communications Real-Time Monitoring Tool (RTMT)
tracing capabilities, perfmon objects and counters, and alerts. It contains the following sections:
•
Cisco Unified Real-Time Monitoring, page 5-1
•
Performance Monitoring in RTMT, page 5-2
Cisco Unified Real-Time Monitoring
The RTMT runs as a client-side application and uses HTTPS and TCP to monitor system performance,
device status, device discovery, CTI applications, and voice messaging ports. RTMT can connect
directly to devices by using HTTPS to troubleshoot system issues. Cisco Unified RTMT performs the
following tasks:
•
Monitor a set of predefined management objects that monitor the health of the system.
•
Generate various alerts, in the form of e-mails, for objects when values go over/below
user-configured thresholds.
•
Collect and view traces in various default viewers that exist in RTMT.
•
Translate Q931 messages.
•
View syslog messages in SysLog Viewer.
•
Work with performance-monitoring counters.
In addition to SNMP traps, Cisco Unified RTMT can monitor and parse syslog messages that are
provided by the hardware vendors, and then send these alerts to RTMT Alert Central. You can configure
RTMT to notify the Cisco Unified CM system administrator when the alerts occur. The notifications can
occur by using e-mail or Epage or both.
Note
Be aware the RTMT is best used for a single cluster. For large and enterprise networks that have multiple
clusters deployed, Cisco recommends using Cisco Unified Operations Manager. For details about Cisco
Unified Operations Manager, go to http://www.cisco.com/en/US/products/ps6535/index.htm.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
5-1
Chapter 5
Cisco Unified Real-Time Monitoring Tool Tracing, PerfMon Counters, and Alerts
Performance Monitoring in RTMT
Performance Monitoring in RTMT
Cisco Unified Communications Manager updates performance counters (called PerfMon counters). The
counters contain simple, useful information about the system and devices on the system, such as number
of registered phones, number of active calls, number of available conference bridge resources, and voice
messaging port usage.
You can monitor the performance of the components of the system and the components for the
application on the system by choosing the counters for any object. The counters for each object display
when the folder expands.
For Cisco Unified Communications Manager, the Cisco CallManager object contains most of the Cisco
Unified Communications Manager performance counters, and these counters have only one instance.
The instance-based counters that belong to the other objects can have zero or more instances. For
example, if two phones are registered to Cisco Unified Communications Manager, two instances of each
counter that belong to the Cisco phones object exist.
You can log perfmon counters locally on the computer and use the performance log viewer in RTMT to
display the perfmon CSV log files that you collected or the Real-time Information Server Data
Collection (RISDC) perfmon logs.
RTMT provides alert notifications for troubleshooting performance. It also periodically polls
performance counters to display data for that counter. Performance monitoring allows you to perform
the following tasks:
•
Monitor performance counters including all the Cisco Unified Communications Manager servers in
a cluster (if applicable), TFTP servers, and database servers.
•
Continuously monitor a set of preconfigured objects and receive notification in the form of an e-mail
message.
•
Associate counter threshold settings to alert notification. An e-mail or popup message provides
notification to the administrator.
•
Save and restore settings, such as counters that get monitored, threshold settings, and alert
notifications, for customized troubleshooting tasks.
•
Display up to six perfmon counters in one chart for performance comparisons.
This section contains the following subsections:
•
PerfMon Alert Notifications, page 5-2
•
PerfMon Objects and Counters for Cisco Unified Communications Manager, page 5-5
•
PerfMon Objects and Counters for System, page 5-53
PerfMon Alert Notifications
The alert notifications keep you updated on system and Cisco Unified Communications Manager issues.
You can use the parameters that are already contained in RTMT or configure your own. Table 5-1 lists
the available settings and describes each. The Threshold, Value Calculated As, Duration, Frequency, and
Schedule panes of RTMT contain the settings.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
5-2
OL-20105-01
Chapter 5
Cisco Unified Real-Time Monitoring Tool Tracing, PerfMon Counters, and Alerts
Performance Monitoring in RTMT
Table 5-1
Counter Alert Configuration Parameters
Setting
Description
Threshold Pane
Trigger alert when Over and
Under conditions get met
Check the box and enter the value that applies.
•
Over—Check this box to configure a maximum threshold that
must be met before an alert notification is activated. In the
Over value field, enter a value. For example, enter a value that
equals the number of calls in progress.
•
Under—Check this box to configure a minimum threshold that
must be met before an alert notification is activated. In the
Under value field, enter a value. For example, enter a value that
equals the number of calls in progress.
Tip
Use these boxes in conjunction with the Frequency and
Schedule configuration parameters.
Value Calculated As Pane
Absolute, Delta, Delta
Percentage
Click the radio button that applies.
•
Absolute—Choose Absolute to display the data at its current
status. These counter values are cumulative.
•
Delta—Choose Delta to display the difference between the
current counter value and the previous counter value.
•
Delta Percentage—Choose Delta Percentage to display the
counter performance changes in percentage.
•
Trigger alert only when value constantly...—If you want the
alert notification only when the value is constantly below or
over threshold for a desired number of seconds, click this radio
button and enter seconds after which you want the alert to be
sent.
•
Trigger alert immediately—If you want the alert notification to
be sent immediately, click this radio button.
Duration Pane
Trigger alert only when value
constantly...; Trigger alert
immediately
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
5-3
Chapter 5
Cisco Unified Real-Time Monitoring Tool Tracing, PerfMon Counters, and Alerts
Performance Monitoring in RTMT
Table 5-1
Counter Alert Configuration Parameters (continued)
Setting
Description
Frequency Pane
Trigger alert on every poll;
trigger up to...
Click the radio button that applies.
•
Trigger alert on every poll—If you want the alert notification
to activate on every poll when the threshold is met, click this
radio button.
For example, if the calls in progress continue to go over or
under the threshold, the system does not send another alert
notification. When the threshold is normal (between 50 and
100 calls in progress), the system deactivates the alert
notification; however, if the threshold goes over or under the
threshold value again, the system reactivates alert notification.
•
Trigger up to...—If you want the alert notification to activate
at certain intervals, click this radio button and enter the number
of alerts that you want sent and the number of minutes within
which you want them sent.
Schedule Pane
24-hours daily; start/stop
Note
Click the radio button that applies:
•
24-hours daily—If you want the alert to be triggered 24 hours
a day, click this radio button.
•
Start/Stop—If you want the alert notification activated within
a specific time frame, click the radio button and enter a start
time and a stop time. If the check box is checked, enter the start
and stop times of the daily task. For example, you can
configure the counter to be checked every day from 9:00 am to
5:00 pm or from 9:00 pm to 9:00 am.
If you require an e-mail notifications, check the Enable E-mail box.
You can also use data sampling in RTMT. The perfmon counters that display in the RTMT Perfmon
Monitoring pane have green dots that represent samples of data over time. You can configure the number
of samples to collect and the number of data points to show in the chart. Table 5-2 lists and describes
the parameters.
Table 5-2
Data Sample Parameters
Parameter
Description
Absolute
Because some counter values are accumulative, choose Absolute to
display the data at its current status.
Delta
Choose Delta to display the difference between the current counter
value and the previous counter value.
Delta Percentage
Choose Delta Percentage to display the counter performance
changes in percentage.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
5-4
OL-20105-01
Chapter 5
Cisco Unified Real-Time Monitoring Tool Tracing, PerfMon Counters, and Alerts
Performance Monitoring in RTMT
PerfMon Objects and Counters for Cisco Unified Communications Manager
This section provides information on Cisco Unified Communications Manager PerfMon objects and
counters.
Cisco Analog Access
The Cisco Analog Access object provides information about registered Cisco Analog Access gateways.
Table 5-3 contains information about Cisco Analog Access counters.
Table 5-3
Cisco Analog Access
Counters
Counter Description
OutboundBusyAttempts
This counter represents the total number of times that Cisco Unified
Communications Manager attempts a call through the analog access gateway
when all ports were busy.
PortsActive
This counter represents the number of ports that are currently in use (active). A
port appears active when a call is in progress on that port.
PortsOutOfService
This counter represents the number of ports that are currently out of service.
Counter applies only to loop-start and ground-start trunks.
Cisco Annunciator Device
The Cisco Annunciator Device object provides information about registered Cisco annunciator devices.
Table 5-4 contains information about Cisco Annunciator counters.
Table 5-4
Cisco Annunciator Device
Counters
Counter Description
OutOfResources
This counter represents the total number of times that Cisco Unified
Communications Manager attempted to allocate an annunciator resource from an
annunciator device and failed; for example, because all resources were already in
use.
ResourceActive
This counter represents the total number of annunciator resources that are
currently active (in use) for an annunciator device.
ResourceAvailable
This counter represents the total number of resources that are not active and are
still available to be used at the current time for the annunciator device.
ResourceTotal
This counter represents the total number of annunciator resources that are
configured for an annunciator device.
Cisco CallManager
The Cisco CallManager object provides information about calls, applications, and devices that are
registered with the Cisco Unified Communications Manager. Table 5-5 contains information about
Cisco CallManager counters.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
5-5
Chapter 5
Cisco Unified Real-Time Monitoring Tool Tracing, PerfMon Counters, and Alerts
Performance Monitoring in RTMT
Table 5-5
Cisco CallManager
Counters
Counter Description
AnnunciatorOutOfResources
This counter represents the total number of times that Cisco Unified
Communications Manager attempted to allocate an annunciator resource from
those that are registered to a Cisco Unified Communications Manager when none
were available.
AnnunciatorResourceActive
This counter represents the total number of annunciator resources that are
currently in use on all annunciator devices that are registered with a Cisco
Unified Communications Manager.
AnnunciatorResourceAvailable
This counter represents the total number of annunciator resources that are not
active and are currently available.
AnnunciatorResourceTotal
This counter represents the total number of annunciator resources that are
provided by all annunciator devices that are currently registered with Cisco
Unified Communications Manager.
AuthenticatedCallsActive
This counter represents the number of authenticated calls that are currently active
(in use) on Cisco Unified Communications Manager. An authenticated call
designates one in which all the endpoints that are participating in the call are
authenticated. An authenticated phone uses the Transport Layer Security (TLS)
authenticated Skinny protocol signaling with Cisco Unified Communications
Manager.
AuthenticatedCallsCompleted
This counter represents the number of authenticated calls that connected and
subsequently disconnected through Cisco Unified Communications Manager. An
authenticated call designates one in which all the endpoints that are participating
in the call are authenticated. An authenticated phone uses the TLS authenticated
Skinny protocol signaling with Cisco Unified Communications Manager.
AuthenticatedPartiallyRegisteredPhone
This counter represents the number of partially registered, authenticated SIP
phones.
AuthenticatedRegisteredPhones
This counter represents the total number of authenticated phones that are
registered to Cisco Unified Communications Manager. An authenticated phone
uses the TLS authenticated Skinny protocol signaling with Cisco Unified
Communications Manager.
BRIChannelsActive
This counter represents the number of BRI voice channels that are currently in an
active call on this Cisco Unified Communications Manager.
BRISpansInService
This counter represents the number of BRI spans that are currently available for
use.
CallManagerHeartBeat
This counter represents the heartbeat of Cisco Unified Communications
Manager. This incremental count indicates that Cisco Unified Communications
Manager is up and running. If the count does not increment, that indicates that
Cisco Unified Communications Manager is down.
CallsActive
This counter represents the number of voice or video streaming connections that
are currently in use (active); in other words, the number of calls that actually have
a voice path that is connected on Cisco Unified Communications Manager.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
5-6
OL-20105-01
Chapter 5
Cisco Unified Real-Time Monitoring Tool Tracing, PerfMon Counters, and Alerts
Performance Monitoring in RTMT
Table 5-5
Cisco CallManager (continued)
Counters
Counter Description
CallsAttempted
This counter represents the total number of attempted calls. An attempted call
occurs any time that a phone goes off hook and back on hook, regardless of
whether any digits were dialed, or whether it connected to a destination. The
system considers some call attempts during feature operations (such as transfer
and conference) to be attempted calls.
CallsCompleted
This counter represents the number of calls that were actually connected (a voice
path or video stream was established) through Cisco Unified Communications
Manager. This number increases when the call terminates.
CallsInProgress
This counter represents the number of voice or video calls that are currently in
progress on Cisco Unified Communications Manager, including all active calls.
When a phone that is registered with Skinny Client Control Protocol (SCCP) goes
off hook, the CallsInProgress progress counter increments until it goes back on
hook.
For Cisco Unified IP Phones 7902, 7905, 7912, 7940, and 7960 that register with
SIP, the CallsInProgress counter increments when the dial softkey is pressed.
For all other phones that are running SIP, the CallsInProgress counter increments
when the first digit is pressed.
When all voice or video calls that are in progress are connected, the number of
CallsInProgress represents the number of CallsActive. The counter decreases by
one when a phone goes back on hook.
CM_MediaTermPointsRequestsThrottled
This counter represents the total number of media termination point (MTP)
resource requests that have been denied due to throttling (a resource from this
MTP was not allocated because, as specified by the Cisco CallManager service
parameter, MTP and Transcoder Resource Throttling Percentage, the MTP was
being utilized beyond the configured throttle percentage). This counter
increments each time a request for an MTP on this Cisco Unified
Communications Manager (Cisco Unified CM) node is requested and denied due
to MTP throttling and reflects a running total since the start of the Cisco
CallManager service.
CM_TranscoderRequestsThrottled
This counter represents the total number of transcoder resource requests that have
been denied due to throttling (a resource from this transcoder was not allocated
because, as specified by the Cisco CallManager service parameter MTP and
Transcoder Resource Throttling Percentage, the transcoder was being utilized
beyond the configured throttle percentage). This counter increments each time a
request for a transcoder on this Cisco Unified Communications Manager (Cisco
Unified CM) node is requested and denied due to transcoder throttling and
reflects a running total since the start of the Cisco CallManager service
EncryptedCallsActive
This counter represents the number of encrypted calls that are currently active (in
use) on this Cisco Unified Communications Manager. An encrypted call
represents one in which all the endpoints that are participating in the call are
encrypted.
EncryptedCallsCompleted
This counter represents the number of encrypted calls that were connected and
subsequently disconnected through this Cisco Unified Communications
Manager. An encrypted call represents one in which all the endpoints that are
participating in the call are encrypted.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
5-7
Chapter 5
Cisco Unified Real-Time Monitoring Tool Tracing, PerfMon Counters, and Alerts
Performance Monitoring in RTMT
Table 5-5
Cisco CallManager (continued)
Counters
Counter Description
EncryptedPartiallyRegisteredPhones
This counter represents the number of partially registered, encrypted SIP phones.
EncryptedRegisteredPhones
This counter represents the total number of encrypted phones that are registered
on this Cisco Unified Communications Manager.
FXOPortsActive
This counter represents the number of FXO ports that are currently in use (active)
on a Cisco Unified Communications Manager.
FXOPortsInService
This counter represents the number of FXO ports that are currently available for
use in the system.
FXSPortsActive
This counter represents the number of FXS ports that are currently in use (active)
on a Cisco Unified Communications Manager.
FXSPortsInService
This counter represents the number of FXS ports that are currently available for
use in the system.
HuntListsInService
This counter represents the number of hunt lists that are currently in service on
Cisco Unified Communications Manager.
HWConferenceActive
This counter represents the total number of hardware conference resources that
are provided by all hardware conference bridge devices that are currently
registered with Cisco Unified Communications Manager.
HWConferenceCompleted
This counter represents the total number of conferences that used a hardware
conference bridge (hardware-based conference devices such as Cisco Catalyst
6000, Cisco Catalyst 4000, Cisco VG200, Cisco series 26xx and 36xx) that is
allocated from Cisco Unified Communications Manager and that have
completed, which means that the conference bridge has been allocated and
released. A conference activates when the first call connects to the bridge. The
conference completes when the last call disconnects from the bridge.
HWConferenceOutOfResources
This counter represents the total number of times that Cisco Unified
Communications Manager attempted to allocate a hardware conference resource
from those that are registered to a Cisco Unified Communications Manager when
none was available.
HWConferenceResourceActive
This counter represents the total number of conference resources that are in use
on all hardware conference devices (such as Cisco Catalyst 6000, Catalyst 4000,
Cisco VG200, Cisco series 26xx and 36xx) that are registered with Cisco Unified
Communications Manager. System considers conference to be active when one
or more calls are connected to a bridge.
HWConferenceResourceAvailable
This counter represents the number of hardware conference resources that are not
in use and that are available to be allocated on all hardware conference devices
(such as Cisco Catalyst 6000, Cisco Catalyst 4000, Cisco VG200, Cisco series
26xx and 36xx) that are allocated fromCisco Unified Communications Manager
and that have been completed, which means that the conference bridge has been
allocated and released. A conference activates when the first call connects to the
bridge. The conference completes when the last call disconnects from the bridge.
HWConferenceResourceTotal
This counter represents the number of active conferences on all hardware
conference devices that are registered with Cisco Unified Communications
Manager.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
5-8
OL-20105-01
Chapter 5
Cisco Unified Real-Time Monitoring Tool Tracing, PerfMon Counters, and Alerts
Performance Monitoring in RTMT
Table 5-5
Cisco CallManager (continued)
Counters
Counter Description
InitializationState
This counter represents the current initialization state of Cisco Unified
Communications Manager. Cisco Unified Communications Manager includes the
following initialization state values:
1-Database; 2-Regions; 3-Locations; 4-QoS Policy; 5-Time Of Day; 6-AAR
Neighborhoods; 7-Digit Analysis; 8-Route Plan; 9-Call Control; 10-RSVP
Session Manager; 11-Supplementary Services; 12-Directory; 13-SDL Link;
14-Device; 100-Initialization Complete.
Not all states display when this counter is used. This does not indicate that an
error occurred; it simply indicates that the state(s) initialized and completed
within the refresh period of the performance monitor.
LocationOutOfResources
This counter represents the total number of times that a call through Locations
failed due to the lack of bandwidth.
MOHMulticastResourceActive
This counter represents the total number of multicast MOH resources that are
currently in use (active) on all MOH servers that are registered with a Cisco
Unified Communications Manager.
MOHMulticastResourceAvailable
This counter represents the total number of active multicast MOH connections
that are not being used on all MOH servers that are registered with a Cisco
Unified Communications Manager.
MOHOutOfResources
This counter represents the total number of times that the Media Resource
Manager attempted to allocate an MOH resource when all available resources on
all MOH servers that are registered with a Cisco Unified Communications
Manager were already active.
MOHTotalMulticastResources
This counter represents the total number of multicast MOH resources or
connections that are provided by all MOH servers that are currently registered
with a Cisco Unified Communications Manager.
MOHTotalUnicastResources
This counter represents the total number of unicast MOH resources or streams
that are provided by all MOH servers that are currently registered with Cisco
Unified Communications Manager. Each MOH unicast resource uses one stream.
MOHUnicastResourceActive
This counter represents the total number of unicast MOH resources that are
currently in use (active) on all MOH servers that are registered with Cisco
Unified Communications Manager. Each MOH unicast resource uses one stream.
MOHUnicastResourceAvailable
This counter represents the total number of unicast MOH resources that are
currently available on all MOH servers that are registered with Cisco Unified
Communications Manager. Each MOH unicast resource uses one stream.
MTPOutOfResources
This counter represents the total number of times that Cisco Unified
Communications Manager attempted but failed to allocate an MTP resource from
one MTP device that is registered with Cisco Unified Communications Manager.
This also means that no transcoders were available to act as MTPs.
MTPResourceActive
This counter represents the total number of MTP resources that are currently in
use (active) on all MTP devices that are registered with a Cisco Unified
Communications Manager. Each MTP resource uses two streams. An MTP in use
represents one MTP resource that has been allocated for use in a call.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
5-9
Chapter 5
Cisco Unified Real-Time Monitoring Tool Tracing, PerfMon Counters, and Alerts
Performance Monitoring in RTMT
Table 5-5
Cisco CallManager (continued)
Counters
Counter Description
MTPResourceAvailable
This counter represents the total number of MTP resources that are not in use and
are available to be allocated on all MTP devices that are registered with Cisco
Unified Communications Manager. Each MTP resource uses two streams. An
MTP in use represents one MTP resource that has been allocated for use in a call.
MTPResourceTotal
This counter represents the total number of media termination point (MTP)
resources that are provided by all MTP devices that are currently registered with
Cisco Unified Communications Manager.
MTP_RequestsThrottled
This counter represents the total number of media termination point (MTP)
resource requests that have been denied due to throttling (a resource from this
MTP was not allocated because, as specified by the Cisco CallManager service
parameter MTP and Transcoder Resource Throttling Percentage, the MTP was
being utilized beyond the configured throttle percentage). This counter
increments each time a resource is requested from this MTP and is denied due to
throttling. This counter reflects a running total since the MTP device registered
with the Cisco CallManager service.
PartiallyRegisteredPhone
This counter represents the number of partially registered phones that are running
SIP.
PRIChannelsActive
This counter represents the number of PRI voice channels that are in an active
call on a Cisco Unified Communications Manager.
PRISpansInService
This counter represents the number of PRI spans that are currently available for
use.
RegisteredAnalogAccess
This counter represents the number of registered Cisco analog access gateways
that are registered with system. The count does not include the number of Cisco
analog access ports.
RegisteredHardwarePhones
This counter represents the number of Cisco hardware IP phones (for example,
Cisco Unified IP Phones 7960, 7940, 7910, and so on.) that are currently
registered in the system.
RegisteredMGCPGateway
This counter represents the number of MGCP gateways that are currently
registered in the system.
RegisteredOtherStationDevices
This counter represents the number of station devices other than Cisco hardware
IP phones that are currently registered in the system (for example,
Cisco IP SoftPhone, CTI port, CTI route point, Cisco voice-mail port).
SIPLineServerAuthorizationChallenges
This counter represents the number of authentication challenges for incoming SIP
requests that the Cisco Unified Communications Manager server issued to
phones that are running SIP. An authentication challenge occurs when a phone
that is running SIP with Digest Authentication enabled sends a SIP line request
to Cisco Unified Communications Manager.
SIPLineServerAuthorizationFailures
This counter represents the number of authentication challenge failures for
incoming SIP requests from SIP phones to the Cisco Unified Communications
Manager server. An authentication failure occurs when a SIP phone with Digest
Authentication enabled sends a SIP line request with bad credentials to Cisco
Unified Communications Manager.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
5-10
OL-20105-01
Chapter 5
Cisco Unified Real-Time Monitoring Tool Tracing, PerfMon Counters, and Alerts
Performance Monitoring in RTMT
Table 5-5
Cisco CallManager (continued)
Counters
Counter Description
SIPTrunkAuthorization
This counter represents the number of application-level authorization checks for
incoming SIP requests that Cisco Unified Communications Manager has issued
to SIP trunks. An application-level authorization check occurs when Cisco
Unified Communications Manager compares an incoming SIP request to the
application-level settings on the SIP Trunk Security Profile Configuration
window in Cisco Unified Communications Manager Administration.
SIPTrunkAuthorizationFailures
This counter represents the number of application-level authorization failures for
incoming SIP requests that have occurred on Cisco Unified Communications
Manager SIP trunks. An application-level authorization failure occurs when
Cisco Unified Communications Manager compares an incoming SIP request to
the application-level authorization settings on the SIP Trunk Security Profile
Configuration window in Cisco Unified Communications Manager
Administration and finds that authorization for one or more of the SIP features
on that window is not allowed.
SIPTrunkServerAuthenticationChallenge
s
This counter represents the number of authentication challenges for incoming SIP
requests that Cisco Unified Communications Manager issued to SIP trunks. An
authentication challenge occurs when a SIP trunk with Digest Authentication
enabled sends a SIP request to Cisco Unified Communications Manager.
SIPTrunkServerAuthenticationFailures
This counter represents the number of authentication challenge failures that
occurred for incoming SIP requests from SIP trunks to Cisco Unified
Communications Manager. An authentication failure occurs when a SIP trunk
with Digest Authentication enabled sends a SIP request with bad credentials to
Cisco Unified Communications Manager.
SWConferenceActive
This counter represents the number of active conferences on all software
conference devices that are registered with Cisco Unified Communications
Manager.
SWConferenceCompleted
This counter represents the total number of conferences that used a software
conference bridge that was allocated from a Cisco Unified Communications
Manager and that have been completed, which means that the conference bridge
has been allocated and released. A conference activates when the first call
connects to the bridge. The conference completes when the last call disconnects
from the bridge.
SWConferenceOutOfResources
This counter represents the total number of times that Cisco Unified
Communications Manager attempted to allocate a software conference resource
from those that are registered to Cisco Unified Communications Manager when
none was available. Counter includes failed attempts to add a new participant to
an existing conference.
SWConferenceResourceActive
This counter represents the total number of conference resources that are in use
on all software conference devices that are registered with Cisco Unified
Communications Manager. The system considers a conference to be active when
one or more calls connect to a bridge. One resource equals one stream.
SWConferenceResourceAvailable
This counter represents the number of new software-based conferences that can
be started at the same time, for Cisco Unified Communications Manager. You
must have a minimum of three streams available for each new conference. One
resource equals one stream
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
5-11
Chapter 5
Cisco Unified Real-Time Monitoring Tool Tracing, PerfMon Counters, and Alerts
Performance Monitoring in RTMT
Table 5-5
Cisco CallManager (continued)
Counters
Counter Description
SWConferenceResourceTotal
This counter represents the total number of software conference resources that
are provided by all software conference bridge devices that are currently
registered with Cisco Unified Communications Manager.
SystemCallsAttempted
This counter represents the total number of server-originated calls and attempted
calls to the Unity message waiting indicator (MWI).
T1ChannelsActive
This counter represents the number of T1 CAS voice channels that are in an
active call on a Cisco Unified Communications Manager.
T1SpansInService
This counter represents the number of T1 CAS spans that are currently available
for use.
TLSConnectedSIPTrunks
This counter represents the number of SIP trunks that are configured and
connected via Transport Layer Security (TLS).
TLSConnectedWSM
This counter represents the number of WSM Connectors that are configured and
connected to Motorola WSM via Transport Layer Security (TLS).
TranscoderOutOfResources
This counter represents the total number of times that Cisco Unified
Communications Manager attempted to allocate a transcoder resource from a
transcoder device that is registered to a Cisco Unified Communications Manager
when none was available.
TranscoderResourceActive
This counter represents the total number of transcoders that are in use on all
transcoder devices that are registered with Cisco Unified Communications
Manager. A transcoder in use represents one transcoder resource that has been
allocated for use in a call. Each transcoder resource uses two streams.
TranscoderResourceAvailable
This counter represents the total number of transcoders that are not in use and that
are available to be allocated on all transcoder devices that are registered with
Cisco Unified Communications Manager. Each transcoder resource uses two
streams.
TranscoderResourceTotal
This counter represents the total number of transcoder resources that are provided
by all transcoder devices that are currently registered with Cisco Unified
Communications Manager.
VCBConferenceActive
This counter represents the total number of active video conferences on all video
conference bridge devices that are registered with Cisco Unified
Communications Manager.
VCBConferenceAvailable
This counter represents the total number of new video conferences on all video
conference bridge devices that are registered with Cisco Unified
Communications Manager.
VCBConferenceCompleted
This counter represents the total number of video conferences that used a video
conference bridge that are allocated from Cisco Unified Communications
Manager and that have been completed, which means that the conference bridge
has been allocated and released. A conference activates when the first call
connects to the bridge. The conference completes when the last call disconnects
from the bridge.
VCBConferenceTotal
This counter represents the total number of video conferences that are supported
on all video conference bridge devices that are registered with Cisco Unified
Communications Manager.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
5-12
OL-20105-01
Chapter 5
Cisco Unified Real-Time Monitoring Tool Tracing, PerfMon Counters, and Alerts
Performance Monitoring in RTMT
Table 5-5
Cisco CallManager (continued)
Counters
Counter Description
VCBOutOfConferences
This counter represents the total number of times that Cisco Unified
Communications Manager attempted to allocate a video conference resource
from those that are registered to Cisco Unified Communications Manager when
none was available.
VCBOutOfResources
This counter represents the total number of failed new video conference requests.
A conference request can fail because, for example, the configured number of
conferences is already in use.
VCBResourceActive
This counter represents the total number of video conference resources that are
currently in use on all video conference devices that are registered with Cisco
Unified Communications Manager.
VCBResourceAvailable
This counter represents the total number of video conference resources that are
not active and are currently available.
VCBResourceTotal
This counter represents the total number of video conference resources that are
provided by all video conference bridge devices that are currently registered with
Cisco Unified Communications Manager.
VideoCallsActive
This counter represents the number of active video calls with active video
streaming connections on all video conference bridge devices that are registered
with Cisco Unified Communications Manager.
VideoCallsCompleted
This counter represents the number of video calls that were actually connected
with video streams and then released.
VideoOutOfResources
This counter represents the total number of times that Cisco Unified
Communications Manager attempted to allocate a video-streaming resource from
one of the video conference bridge devices that is registered to Cisco Unified
Communications Manager when none was available.
XCODE_RequestsThrottled
This counter represents the total number of transcoder resource requests that have
been denied due to throttling (a resource from this transcoder was not allocated
because, as specified by the Cisco CallManager service parameter MTP and
Transcoder Resource Throttling Percentage, the transcoder was being utilized
beyond the configured throttle percentage). This counter increments each time a
resource is requested from this transcoder and is denied due to throttling. This
counter reflects a running total since the transcoder device registered with the
Cisco CallManager service.
Cisco CallManager External Call Control
The Cisco CallManager External Call Control feature provides information about the counters that are
added to support the External Call Control feature. Table 5-6 contains information about the External
Call Control counters.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
5-13
Chapter 5
Cisco Unified Real-Time Monitoring Tool Tracing, PerfMon Counters, and Alerts
Performance Monitoring in RTMT
Table 5-6
Cisco CallManager External Call Control
Counters
Counter Description
Cisco Unified Communication Manager (Cisco CallManager) Object
ExternalCallControlEnabledCallsAttemp This counter specifies the total number of calls to devices that have the External
ted
Call Control feature enabled. This is a cumulative count of all calls to
intercept-enabled patterns or DNs since the last restart of the Cisco CallManager
service.
ExternalCallControlEnabledCallsCompl
eted
This counter specifies the total number of calls that were connected to a device
that had the External Call Control feature enabled. This is a cumulative count of
all calls to intercept-enabled patterns or DNs since the last restart of the Cisco
CallManager service.
ExternalCallControlEnabledFailureTreat This counter specifies the total number of calls that were cleared or routed based
mentApplied
on failure treatments (such as Allow or Deny) that are defined in the External Call
Control profile.
External Call Control Objects
PDPServersTotal
This counter defines the total number of PDP servers in all External Call Control
Profiles configured in Cisco Unified CM Administration. This counter increments
when a new PDP server is added and decrements when a PDP server is removed.
PDPServersInService
This counter defines the total number of in-service (active) PDP servers.
PDPServersOutOfService
This counter defines the total number of times that PDP servers have transitioned
from in-service to out-of-service. This is a cumulative count of out-of-service
PDP servers since the last restart of the Cisco CallManager service.
ConnectionsActiveToPDPServer
This counter specifies the total number of connections that Cisco Unified
Communications Manager has established (currently active) with PDP servers.
ConnectionsLostToPDPServer
This counter specifies the total number of times that active connections between
Cisco Unified Communications Manager and the PDP servers were disconnected.
This is a cumulative count since the last restart of the Cisco CallManager service.
Cisco CallManager SAF
The Cisco SAF Client object provides information about SAF counters that are specific to each node.
Table 5-7 contains information about Cisco SAF Client object counters.
Table 5-7
Cisco CallManager SAF Client Object
Counters
Counter Description
SAFConnectionsSucceeded (range from
0 to 2)
Total number of SAF client connections currently active on this Unified CM node.
SAFFConnectionsFailed (range from 0 to Total number of SAF client connections that failed on the Unified CM node. A
2)
failed connection is a connection that did not register with the SAF Forwarder.
Note
A Cisco Unified CM node restart causes a counter reset.
See Real-Time Monitoring Tool Guide for more information.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
5-14
OL-20105-01
Chapter 5
Cisco Unified Real-Time Monitoring Tool Tracing, PerfMon Counters, and Alerts
Performance Monitoring in RTMT
Cisco CallManager System Performance
The Cisco CallManager System Performance object provides system performance information about
Cisco Unified Communications Manager. Table 5-8 contains information about Cisco CallManager
system performance counters.
Table 5-8
Cisco CallManager System Performance
Counters
Counter Description
AverageExpectedDelay
This counter represents the current average expected delay before any incoming
message gets handled.
CallsRejectedDueToICTThrottling
This counter represents the total number of calls that were rejected since the start
of Cisco CallManager service due to Intercluster Trunk (ICT) call throttling.
When the threshold limit of 140 calls per 5 seconds is met, the ICT will start
throttling (rejecting) new calls. One cause for ICT call throttling occurs when
calls across an ICT enter a route loop condition.
CallThrottlingGenericCounter3
This counter represents a generic counter that is used for call-throttling purpose.
CodeRedEntryExit
This counter indicates whether Cisco Unified Communications Manager has
entered or exited a Code state (call-throttling mode). Valid values include 0 (Exit)
and 1 (Entry).
CodeYellowEntryExit
This counter indicates whether Cisco Unified Communications Manager has
entered or exited a Code Yellow state (call-throttling mode). Valid values include
0 (Exit) and 1 (Entry).
EngineeringCounter1
Do not use this counter unless directed by a Cisco Engineering Special build.
Cisco uses information in this counter for diagnostic purposes.
EngineeringCounter2
Do not use this counter unless directed by a Cisco Engineering Special build.
Cisco uses information in this counter for diagnostic purposes.
EngineeringCounter3
Do not use this counter unless directed by a Cisco Engineering Special build.
Cisco uses information in this counter for diagnostic purposes.
EngineeringCounter4
Do not use this counter unless directed by a Cisco Engineering Special build.
Cisco uses information in this counter for diagnostic purposes.
EngineeringCounter5
Do not use this counter unless directed by a Cisco Engineering Special build.
Cisco uses information in this counter for diagnostic purposes.
EngineeringCounter6
Do not use this counter unless directed by a Cisco Engineering Special build.
Cisco uses information in this counter for diagnostic purposes.
EngineeringCounter7
Do not use this counter unless directed by a Cisco Engineering Special build.
Cisco uses information in this counter for diagnostic purposes.
EngineeringCounter8
Do not use this counter unless directed by a Cisco Engineering Special build.
Cisco uses information in this counter for diagnostic purposes.
QueueSignalsPresent 1-High
This counter indicates the number of high-priority signals in the Cisco Unified
Communications Manager queue. High-priority signals include timeout events,
internal Cisco Unified Communications Manager keepalives, certain gatekeeper
events, and internal process creation, among other events. A large number of
high-priority events will cause degraded performance on Cisco Unified
Communications Manager and result in slow call connection or loss of dial tone.
Use this counter in conjunction with the QueueSignalsProcessed 1-High counter
to determine the processing delay on Cisco Unified Communications Manager.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
5-15
Chapter 5
Cisco Unified Real-Time Monitoring Tool Tracing, PerfMon Counters, and Alerts
Performance Monitoring in RTMT
Table 5-8
Cisco CallManager System Performance (continued)
Counters
Counter Description
QueueSignalsPresent 2-Normal
This counter indicates the number of normal-priority signals in the Cisco Unified
Communications Manager queue. Normal-priority signals include call-processing
functions, key presses, on-hook and off-hook notifications, among other events.
A large number of normal-priority events will cause degraded performance on
Cisco Unified Communications Manager, sometimes resulting in delayed dial
tone, slow call connection, or loss of dial tone. Use this counter in conjunction
with the QueueSignalsProcessed 2-Normal counter to determine the
call-processing delay on Cisco Unified Communications Manager. Remember
that high-priority signals must complete before normal-priority signals begin to
process, so check the high-priority counters as well to get an accurate picture of
the potential delay.
QueueSignalsPresent 3-Low
This counter indicates the number of low-priority signals in the Cisco Unified
Communications Manager queue. Low-priority signals include station device
registration (except the initial station registration request message), among other
events. A large number of signals in this queue could result in delayed device
registration, among other events.
QueueSignalsPresent 4-Lowest
This counter indicates the number of lowest priority signals in the Cisco Unified
Communications Manager queue. Lowest priority signals include the initial
station registration request message during device registration, among other
events. A large number of signals in this queue could result in delayed device
registration, among other events.
QueueSignalsProcessed 1-High
This counter indicates the number of high-priority signals that Cisco Unified
Communications Manager processes for each 1-second interval. Use this counter
in conjunction with the QueueSignalsPresent 1-High counter to determine the
processing delay on this queue.
QueueSignalsProcessed 2-Normal
This counter indicates the number of normal-priority signals that Cisco Unified
Communications Manager processes for each 1-second interval. Use this counter
in conjunction with the QueueSignalsPresent 2-Normal counter to determine the
processing delay on this queue. Remember that high-priority signals get
processed before normal-priority signals.
QueueSignalsProcessed 3-Low
This counter indicates the number of low-priority signals that Cisco Unified
Communications Manager processes for each 1-second interval. Use this counter
in conjunction with the QueueSignalsPresent 3-Low counter to determine the
processing delay on this queue. The number of signals processed gives an
indication of how much device registration activity is being processed in this time
interval.
QueueSignalsProcessed 4-Lowest
This counter indicates the number of lowest priority signals that Cisco Unified
Communications Manager processes for each 1-second interval. Use this counter
in conjunction with the QueueSignalsPresent 4-Lowest counter to determine the
processing delay on this queue. The number of signals that are processed gives an
indication of how many devices began the Cisco Unified Communications
Manager registration process in this time interval.
QueueSignalsProcessed Total
This counter provides a sum total of all queue signals that Cisco Unified
Communications Manager processes for each 1-second interval for all queue
levels: high, normal, low, and lowest.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
5-16
OL-20105-01
Chapter 5
Cisco Unified Real-Time Monitoring Tool Tracing, PerfMon Counters, and Alerts
Performance Monitoring in RTMT
Table 5-8
Cisco CallManager System Performance (continued)
Counters
Counter Description
SkinnyDevicesThrottled
This counter represents the total number of Skinny devices that are being
throttled. A Skinny device gets throttled (asked to shut down and reregister) when
the total number of events that the Skinny device generated exceeds the
configured maximum threshold value (default value specifies 2000 events) within
a 5-second interval.
ThrottlingSampleActivity
This counter indicates how many samples, out of the configured sample size, have
non-zero averageExpectedDelay values. This counter gets reset when any sample
has an averageExpectedDelay value of zero. This process repeats for each batch
of samples. A batch represents the configured sample size.
TotalCodeYellowEntry
This counter indicates the number of times that Cisco Unified Communications
Manager call processing enters the code yellow state. This counter remains
cumulative from the start of the Cisco Unified Communications Manager process.
Cisco CTIManager
The Cisco CTI Manager object provides information about Cisco CTI Manager. Table 5-9 contains
information about Cisco CTIManager counters.
Table 5-9
Cisco CTI Manager
Counters
Counter Description
CcmLinkActive
This counter represents the total number of active Cisco Unified Communications
Manager links. CTI Manager maintains links to all active servers in a cluster, if
applicable.
CTIConnectionActive
This counter represents the total number of CTI clients that are currently
connected to the CTIManager. This counter increases by one when a new
connection is established and decreases by one when a connection is released. The
CTIManager service parameter MaxCTIConnections determines the maximum
number of active connections.
DevicesOpen
This counter represents the total number of devices that are configured in Cisco
Unified Communications Manager that CTI applications control and/or monitor.
Devices include hardware IP phones, CTI ports, CTI route points, and so on.
LinesOpen
This counter represents the total number of lines that are configured in Cisco
Unified Communications Manager that control and/or monitor CTI applications.
QbeVersion
This counter represents the version number of the Quick Buffer Encoding (QBE)
interface that the CTIManager uses.
Cisco Dual-Mode Mobility
The Cisco Dual-Mode Mobility object provides information about the dual-mode mobility application
on Cisco Unified Communications Manager. Table 5-10 contains information about Cisco Dual-Mode
Mobility counters.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
5-17
Chapter 5
Cisco Unified Real-Time Monitoring Tool Tracing, PerfMon Counters, and Alerts
Performance Monitoring in RTMT
Table 5-10
Cisco Dual-Mode Mobility
Counters
Counter Description
CallsAnchored
This counter represents the number of calls that are placed or received on
dual-mode phones that are anchored in Cisco Unified Communications Manager.
The counter increments when a call is received from or placed to a dual-mode
phone. The counter increments twice if a dual-mode phone calls another
dual-mode phone.
DMMSRegistered
This counter represents the number of Dual-mode Mobile Station (DMMS)
subscribers that are registered in the wireless LAN (WLAN).
FollowMeAborted
This counter represents the number of failed follow-me operations.
FollowMeAttempted
This counter represents the number of follow-me operations that Cisco Unified
Communications Manager attempted. The counter increments when a SIP 302 Moved Temporarily message is received from the Wireless Service Manager
(WSM) and Cisco Unified Communications Manager redirects the call to the
DMMS in WLAN.
FollowMeCompleted
This counter represents the number of follow-me operations that were
successfully completed. The counter increments when the DMMS in WLAN
answers the call and the media (voice path) successfully gets established with the
calling device.
FollowMeInProgress
This counter represents the number of follow-me operations that are currently in
progress. The counter increments when a follow-me is attempted, and it
decrements when the follow-me operation aborts or completes.
H1HandOutAttempted
This counter represents the number of H1 hand-out operations that dual-mode
phones attempt. The counter increments when Cisco Unified Communications
Manager processes a call to the H1 number from a DMMS.
H1HandOutCompleted
This counter represents the number of successfully completed H1 hand-out
operations. The counter increments when the DMMS in WLAN successfully
reestablishes a media (voice path).
H2HandOutCompleted
This counter represents the number of successfully completed H2 hand-out
operations. The counter increments when the DMMS in WLAN successfully
reestablishes a media (voice path).
H2HandOutsAttempted
This counter represents the number of H2 hand-out operations that dual-mode
phones attempt. The counter increments when Cisco Unified Communications
Manager receives a call to the H2 number from a DMMS.
HandInAborted
This counter represents the number of hand-in operations that failed.
HandInAttempted
This counter represents the number of hand-in operations that dual-mode phones
attempt.
HandInCompleted
This counter represents the number of successfully completed hand-in operations.
The counter increments when the DMMS in WLAN successfully reestablishes a
media (voice path).
HandInInProgress
This counter represents the number of hand-in operations that are currently in
progress. The counter increments when a hand-in is attempted, and the counter
decrements when the hand-in is aborted or completed.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
5-18
OL-20105-01
Chapter 5
Cisco Unified Real-Time Monitoring Tool Tracing, PerfMon Counters, and Alerts
Performance Monitoring in RTMT
Table 5-10
Cisco Dual-Mode Mobility (continued)
Counters
Counter Description
HandOutAborted
This counter represents the number of hand-out operations that failed.
HandOutInProgress
This counter represents the number of H1 and H2 hand-out operations that are
currently in progress. The counter increments when a H1 or H2 hand-out is
attempted, and it decrements when the hand-out is aborted or completed.
Cisco Extension Mobility
The Cisco Extension Mobility object provides information about the extension mobility application.
Table 5-11 contains information about Cisco Extension Mobility counters.
Table 5-11
Cisco Extension Mobility Application
Counters
Counter Description
RequestsHandled
This counter represents the total number of HTTP requests that the extension
mobility application handled since the last restart of the Cisco CallManager
service. A typical login would constitute two HTTP requests: one to query the
initial login state of the device and another to log in the user on a device.
Similarly, a typical logout also results in two HTTP requests.
RequestsInProgress
This counter represents the number of HTTP requests that the extension mobility
application currently is handling. A typical login would constitute two HTTP
requests: one to query the initial login state of the device and another to log in the
user on a device. Similarly, a typical logout also results in two HTTP requests.
RequestsThrottled
This counter represents the total number of Login/Logout Requests that failed due
to throttling.
LoginsSuccessful
This counter represents the total number of successful login requests that were
completed through Extension Mobility Service.
LogoutsSuccessful
This counter represents the total number of successful logout requests that were
completed through Extension Mobility Service
Total Login/LogoutRequestsAttempted
This counter represents the total number of Login and Logout requests that were
attempted through this Extension Mobility Service. This number includes both
successful and unsuccessful attempts.
Total Number of EMCC Messages
This represents the total number of messages related to EMCC Requests that came
from remote clusters.
Number of Remote Devices
This represents the total number of devices from other clusters that are currently
using a EMCC Base Device (EMCC Logged in).
Number of Unknown Remote Users
This represents the total number of users who were not found in any of the remote
cluster during inter-cluster extension mobility login.
Active Inter-cluster Sessions
This represents the total number of inter cluster Extension Mobility requests that
are currently in progress.
Total Number of Remote Users
This represents the total number of users from other cluster who use a local device
of this cluster and have logged into a remote cluster.
EMCC Check User Requests Handled
This represents the total number of EMCC check user requests that came from
remote clusters.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
5-19
Chapter 5
Cisco Unified Real-Time Monitoring Tool Tracing, PerfMon Counters, and Alerts
Performance Monitoring in RTMT
Cisco Feature Control Policy
The Cisco Feature Control Policy feature provides information about the two new counters for TFTP.
Table 5-12 contains information about Cisco Feature Control Policy feature counters.
Table 5-12
Cisco Feature Control Policy
Counters
Counter Description
BuildFeaturePolicyCount
Indicates the number of built FCP files
FeaturePolicyChangeNotifications
Indicates the number of sent FCP change notifications
Cisco Gatekeeper
The Cisco Gatekeeper object provides information about registered Cisco gatekeeper devices.
Table 5-13 contains information about Cisco gatekeeper device counters.
Table 5-13
Cisco Gatekeeper
Counters
Counter Description
ACFsReceived
This counter represents the total number of RAS Admission Confirm messages
that are received from the configured gatekeeper and its alternate gatekeepers.
ARQsAttempted
This counter represents the total number of RAS Admission Request messages
that are attempted by using the configured gatekeeper and its alternate
gatekeepers.
RasRetries
This counter represents the number of retries due to loss or delay of all RAS
acknowledgement messages on the configured gatekeeper and its alternate
gatekeepers.
VideoOutOfResources
This counter represents the total number of video-stream requests to the
configured gatekeeper or its alternate gatekeepers that failed, most likely due to
lack of bandwidth.
Cisco H.323
The Cisco H.323 object provides information about registered Cisco H.323 devices. Table 5-14 contains
information about Cisco H.323 device counters.
Table 5-14
Cisco H.323
Counters
Counter Description
CallsActive
This counter represents the number of streaming connections that are currently
active (in use) on the configured H.323 device; in other words, the number of calls
that actually have a voice path that is connected.
CallsAttempted
This counter represents the total number of calls that have been attempted on a
device, including both successful and unsuccessful call attempts.
CallsCompleted
This counter represents the total number of successful calls that were made from
a device.
CallsInProgress
This counter represents the number of calls that are currently in progress on a
device.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
5-20
OL-20105-01
Chapter 5
Cisco Unified Real-Time Monitoring Tool Tracing, PerfMon Counters, and Alerts
Performance Monitoring in RTMT
Table 5-14
Cisco H.323 (continued)
Counters
Counter Description
CallsRejectedDueToICTCallThrottling
This counter represents the total number of calls that are rejected due to
Intercluster Trunk (ICT) call throttling since the start of the Cisco CallManager
service. When the system reaches a threshold limit of 140 calls per 5 seconds, ICT
will start throttling (rejecting) new calls. One cause for ICT call throttling occurs
when calls across an ICT enter a route loop condition.
VideoCallsActive
This counter represents the number of video calls with video streaming
connections that are currently active (in use) on all H.323 trunks that are
registered with a Cisco Unified Communications Manager; in other words, the
number of calls that actually have video-streaming connections on a Cisco
Unified Communications Manager.
VideoCallsCompleted
This counter represents the number of video calls that were actually connected
with video streams for all H.323 trunks that were registered with a Cisco Unified
Communications Manager. This number increases when the call terminates.
Cisco Hunt Lists
The Cisco Hunt Lists object provides information about the hunt lists that are defined in Cisco Unified
Communications Manager Administration. Table 5-15 contains information about Cisco hunt list
counters.
Table 5-15
Cisco Hunt Lists
Counters
Counter Description
CallsAbandoned
This counter represents the number of abandoned calls that occurred through a
hunt list. An abandoned call represents one in which a caller hangs up before the
call is answered.
CallsActive
This counter represents the number of calls that are currently active (in use) that
occurred through a hunt list. An active call represents one that gets distributed and
answered, and to which a voice path connects.
CallsBusyAttempts
This counter represents the number of times that calls through a hunt list were
attempted when all members of the line and/or route groups were busy.
CallsInProgress
This counter represents the number of calls that are currently in progress through
a hunt list. A call in progress represents one that the call distributor is attempting
to extend to a member of a line or route group and that has not yet been answered.
Examples of a hunt list member include a line, a station device, a trunk device, or
a port/channel of a trunk device.
CallsRingNoAnswer
This counter represents the total number of calls through a hunt list that rang but
that called parties did not answer.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
5-21
Chapter 5
Cisco Unified Real-Time Monitoring Tool Tracing, PerfMon Counters, and Alerts
Performance Monitoring in RTMT
Table 5-15
Cisco Hunt Lists (continued)
Counters
Counter Description
HuntListInService
This counter specifies whether the particular hunt list is currently in service. A
value of 0 indicates that the hunt list is out of service; a value of 1 indicates that
the hunt list is in service. Reasons that a hunt list could be out of service include
the hunt list is not running on a primary Cisco Unified Communications Manager
based on its Cisco Unified Communications Manager Group or the hunt list has
been disabled in Cisco Unified Communications Manager Administration.
MembersAvailable
This counter represents the total number of available or idle members of line and
route groups that belong to an in-service hunt list. An available member currently
handles a call and will accept a new call. An idle member does not handle any call
and will accept a new call. A hunt list member can comprise a route group, line
group, or a combination. A member of a line group represents a directory number
of a line on an IP phone or a voice-mail port. A member of a route group
represents a station gateway, a trunk gateway, or port/channel of a trunk gateway.
Cisco HW Conference Bridge Device
The Cisco HW Conference Bridge Device object provides information about registered Cisco hardware
conference bridge devices. Table 5-16 contains information about Cisco hardware conference bridge
device counters.
Table 5-16
Cisco HW Conference Bridge Device
Counters
Counter Description
HWConferenceActive
This counter represents the number of conferences that are currently active (in
use) on a HW conference bridge device. One resource represents one stream.
HWConferenceCompleted
This counter represents the total number of conferences that have been allocated
and released on a HW conference device. A conference starts when the first call
connects to the bridge. The conference completes when the last call disconnects
from the bridge.
OutOfResources
This counter represents the total number of times that an attempt was made to
allocate a conference resource from a HW conference device and failed, for
example, because all resources were already in use.
ResourceActive
This counter represents the number of resources that are currently in use (active)
for this HW conference device. One resource represents one stream.
ResourceAvailable
This counter represents the total number of resources that are not active and are
still available to be used now for a HW conference device. One resource
represents one stream.
ResourceTotal
This counter represents the total number of resources for a HW conference bridge
device. This counter equals the sum of the counters ResourceAvailable and
ResourceActive. One resource represents one stream.
Cisco IME Server
The Cisco IME Server provides information about the Performance Object and Counters for IME.
The following contains the Performance Object for Cisco IME Server:
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
5-22
OL-20105-01
Chapter 5
Cisco Unified Real-Time Monitoring Tool Tracing, PerfMon Counters, and Alerts
Performance Monitoring in RTMT
VAPStatus (range from 0 to 2)—This flag indicates the overall health of the connection to the IME
servers for a particular IME service. If 1, it means that Unified CM has successfully established a
connection to its primary and, if configured, backup servers for the IME service. 2 = Unhealthy.
0 = Unknown.
The following contains the Performance Counters for Cisco IME Server. Table 5-17 contains
information about the Performance Counters for Cisco IME Server.
Table 5-17
Cisco IME Server
Counters
Counter Description
PublishedRoutes
Total number of DIDs published successfully into the DHT across all IME
services. It is a dynamic measurement, and as such, gives you an indication of
your own provisioned usage in addition to a sense of how successful the system
has been in storing them into the network.
RejectedRoutes
Number of learned routes which were rejected because the number or domain
were blacklisted by the administrator. This provides an indication of the number
of 'missed opportunities' - cases where a VoIP call could happen in the future, but
will not due to the blocked validation.
LearnedRoutes
Total number of distinct phone numbers which have been learned by IME and are
present as routes in Unified CM's routing tables. If this number grows too large,
it may exceed the per-cluster limit, and require additional clusters for scale.
UniqueDomains
Number of unique domain names of peer enterprises discovered by IME. It is an
indicator of overall usage of the system.
FailedB2BLinkSetups
Total number of call attempts for which a IME route was available, but which
were set up through the PSTN due to a failure to connect to the target over the IP
network.
B2BLinkCallsAttempted
Number of calls initiated by UCM through IME. This includes calls that are
accepted, as well as busy, no-answer and failed calls. The metric is strictly on
initiation.
B2BLinkCallsSetup
Number of IME calls successfully placed by Unified CM and answered by the
remote party, resulting in an IP call.
FailedFallbackCalls
Total number of failed fallback attempts.
e164 DIDs Learned
Number of DIDs learned from the IME server.
B2BLinkCallsAccepted
Number of IME calls successfully received by UCM and answered by the called
party, resulting in an IP call.
B2BLinkCallsReceived
Number of calls received by Unified CM through IME. This includes calls that are
accepted, as well as busy, no-answer and failed calls. The metric is strictly on
initiation.
Cisco IP Manager Assistant
The Cisco IP Manager Assistant (IPMA) Service object provides information about the Cisco Unified
Communications Manager Assistant application. Table 5-18 contains information on Cisco IPMA
counters.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
5-23
Chapter 5
Cisco Unified Real-Time Monitoring Tool Tracing, PerfMon Counters, and Alerts
Performance Monitoring in RTMT
Table 5-18
Cisco IP Manager Assistant Service
Counters
Counter Description
AssistantsActive
This counter represents the number of assistant consoles that are currently active.
An active assistant console exists when an assistant is logged in from the assistant
console desktop application.
LinesOpen
This counter represents the number of phone lines that the Cisco Unified
Communications Manager Assistant application opened. An open phone line
exists when the application assumes line control from CTI.
ManagersActive
This counter represents the current number of managers that the Cisco IPMA is
servicing.
SessionsCurrent
This counter represents the total number of managers assistants that are currently
using the Cisco Unified Communications Manager Assistant application. Each
manager and each assistant constitute an active session; so, for one
manager/assistant pair, this counter would reflect two sessions.
Cisco Lines
The Cisco Lines object represents the number of Cisco lines (directory numbers) that can dial and
connect to a device. Lines represent all directory numbers that terminate on an endpoint. The directory
number that is assigned to it identifies the line. The Cisco Lines object does not include directory
numbers that include wildcards such as a pattern for a Digital or Analog Access gateway.
The Active counter represents the state of the line, either active or not active. A zero indicates that the
line is not in use. When the number is greater than zero, this indicates that the line is active, and the
number represents the number of calls that are currently in progress on that line. If more than one call is
active, this indicates that the call is on hold either because of being placed on hold specifically (user
hold) or because of a network hold operation (for example, a transfer is in progress, and it is on transfer
hold). This applies to all directory numbers that are assigned to any device.
Cisco Locations
The Cisco Location object provides information about locations that are defined in Cisco Unified
Communications Manager. Table 5-19 contains information on Cisco location counters.
Table 5-19
Cisco Locations
Counters
Counter Description
BandwidthAvailable
This counter represents the current bandwidth in a given location. A value of 0
indicates that no bandwidth is available.
BandwidthMaximum
This counter represents the maximum bandwidth that is available in a given
location. A value of 0 indicates that infinite bandwidth is available.
CallsInProgress
This counter represents the number of calls that are currently in progress on a
particular Cisco Unified Communications Manager.
OutOfResources
This counter represents the total number of times that a call on a particular Cisco
Unified Communications Manager through the location failed due to lack of
bandwidth.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
5-24
OL-20105-01
Chapter 5
Cisco Unified Real-Time Monitoring Tool Tracing, PerfMon Counters, and Alerts
Performance Monitoring in RTMT
Table 5-19
Cisco Locations (continued)
Counters
Counter Description
RSVP AudioReservationErrorCounts
This counter represents the number of RSVP reservation errors in the audio
stream.
RSVP MandatoryConnectionsInProgress This counter represents the number of connections with mandatory RSVP that are
in progress.
RSVP OptionalConnectionsInProgress
This counter represents the number of connections with optional RSVP that are in
progress.
RSVP TotalCallsFailed
This counter represents the total number of failed calls due to a RSVP reservation
failure.
RSVP VideoCallsFailed
This counter represents the number of video calls that failed due to a RSVP
reservation failure.
RSVP VideoReservationErrorCounts
This counter represents the number of RSVP reservation errors in the video
stream
VideoBandwidthAvailable
This counter represents the bandwidth that is currently available for video in the
location where the person who initiated the video conference resides. A value of
0 indicates that no bandwidth is available.
VideoBandwidthMaximum
This counter represents the maximum bandwidth that is available for video in the
location where the person who initiated the video conference resides. A value of
0 indicates that no bandwidth is allocated for video.
VideoOutOfResources
This counter represents the total number of failed video-stream requests (most
likely due to lack of bandwidth) in the location where the person who initiated the
video conference resides.
Cisco Media Streaming Application
The Cisco IP Voice Media Streaming Application object provides information about the registered
MTPs, MOH servers, conference bridge servers, and annunciators. Table 5-20 contains information on
Cisco IP Voice Media Streaming Application counters.
Note
One object exists for each Cisco Unified Communications Manager in the Cisco Unified
Communications Manager group that is associated with the device pool that the annunciator device is
configured to use.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
5-25
Chapter 5
Cisco Unified Real-Time Monitoring Tool Tracing, PerfMon Counters, and Alerts
Performance Monitoring in RTMT
Table 5-20
Cisco Media Streaming Application
Counter
Counter Description
ANNConnectionsLost
This counter represents the total number of times since the last restart of the Cisco
IP Voice Media Streaming Application that a Cisco Unified Communications
Manager connection was lost.
ANNConnectionState
For each Cisco Unified Communications Manager that is associated with an
annunciator, this counter represents the current registration state to Cisco Unified
Communications Manager; 0 indicates no registration to Cisco Unified
Communications Manager; 1 indicates registration to the primary Cisco Unified
Communications Manager; 2 indicates connection to the secondary Cisco Unified
Communications Manager (connected to Cisco Unified Communications
Manager but not registered until the primary Cisco Unified Communications
Manager connection fails).
ANNConnectionsTotal
This counter represents the total number of annunciator instances that have been
started since the Cisco IP Voice Media Streaming Application service started.
ANNInstancesActive
This counter represents the number of actively playing (currently in use)
announcements.
ANNStreamsActive
This counter represents the total number of currently active simplex (one
direction) streams for all connections. Each stream direction counts as one stream.
One internal stream provides the audio input and another output stream to the
endpoint device.
ANNStreamsAvailable
This counter represents the remaining number of streams that are allocated for the
annunciator device that are available for use. This counter starts as 2 multiplied
by the number of configured connections (defined in the Cisco IP Voice Media
Streaming App service parameter for the Annunciator, Call Count) and is reduced
by one for each active stream that started.
ANNStreamsTotal
This counter represents the total number of simplex (one direction) streams that
connected to the annunciator device since the Cisco IP Voice Media Streaming
Application service started.
CFBConferencesActive
This counter represents the number of active (currently in use) conferences.
CFBConferencesTotal
This counter represents the total number of conferences that started since the
Cisco IP Voice Media Streaming Application service started.
CFBConnectionsLost
This counter represents the total number of times since the last restart of the Cisco
IP Voice Media Streaming Application that a Cisco Unified Communications
Manager connection was lost.
CFBConnectionState
For each Cisco Unified Communications Manager that is associated with a SW
Conference Bridge, this counter represents the current registration state to Cisco
Unified Communications Manager; 0 indicates no registration to Cisco Unified
Communications Manager; 1 indicates registration to the primary Cisco Unified
Communications Manager; 2 indicates connection to the secondary Cisco Unified
Communications Manager (connected to Cisco Unified Communications
Manager but not registered until the primary Cisco Unified Communications
Manager connection fails).
CFBStreamsActive
This counter represents the total number of currently active simplex (one
direction) streams for all conferences. Each stream direction counts as one stream.
In a three-party conference, the number of active streams equals 6.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
5-26
OL-20105-01
Chapter 5
Cisco Unified Real-Time Monitoring Tool Tracing, PerfMon Counters, and Alerts
Performance Monitoring in RTMT
Table 5-20
Cisco Media Streaming Application (continued)
Counter
Counter Description
CFBStreamsAvailable
This counter represents the remaining number of streams that are allocated for the
conference bridge that are available for use. This counter starts as 2 multiplied by
the number of configured connections (defined in the Cisco IP Voice Media
Streaming App service parameter for Conference Bridge, Call Count) and is
reduced by one for each active stream that started.
CFBStreamsTotal
This counter represents the total number of simplex (one direction) streams that
connected to the conference bridge since the Cisco IP Voice Media Streaming
Application service started.
MOHAudioSourcesActive
This counter represents the number of active (currently in use) audio sources for
this MOH server. Be aware that some of these audio sources may not be actively
streaming audio data if no devices are listening. The exception exists for multicast
audio sources, which will always be streaming audio.
When an audio source is in use, even after the listener has disconnected, this
counter will always have one input stream for each configured MOH codec. For
unicast streams, the stream may exist in a suspended state where no audio data is
received until a device connects to listen to the stream. Each MOH multicast
resource uses one stream for each audio source and codec combination. For
example, if the default audio source is configured for multicast, G.711 mu-law
and wideband codecs, then two streams get used (default audio source + G.711
mu-law and default audio source + wideband).
MOHConnectionsLost
This counter represents the total number of times since the last restart of the Cisco
IP Voice Media Streaming Application that a Cisco Unified Communications
Manager connection was lost.
MOHConnectionState
For each Cisco Unified Communications Manager that is associated with an
MOH, this counter represents the current registration state to Cisco Unified
Communications Manager; 0 indicates no registration to Cisco Unified
Communications Manager; 1 indicates registration to the primary Cisco Unified
Communications Manager; 2 indicates connection to the secondary Cisco Unified
Communications Manager (connected to Cisco Unified Communications
Manager but not registered until the primary Cisco Unified Communications
Manager connection fails).
MOHStreamsActive
This counter represents the total number of active (currently in use) simplex (one
direction) streams for all connections. One output stream exists for each device
that is listening to a unicast audio source, and one input stream exists for each
active audio source, multiplied by the number of MOH codecs.
When an audio source has been used once, it will always have one input stream
for each configured MOH codec. For unicast streams, the stream may exist in a
suspended state where no audio data is received until a device connects to listen
to the stream. Each MOH multicast resource uses one stream for each audio
source and codec combination. For example, if the default audio source is
configured for multicast, G.711 mu-law and wideband codecs, then two streams
get used (default audio source + G.711 mu-law and default audio source +
wideband).
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
5-27
Chapter 5
Cisco Unified Real-Time Monitoring Tool Tracing, PerfMon Counters, and Alerts
Performance Monitoring in RTMT
Table 5-20
Cisco Media Streaming Application (continued)
Counter
Counter Description
MOHStreamsAvailable
This counter represents the remaining number of streams that are allocated for the
MOH device that are available for use. This counter starts as 408 plus the number
of configured half-duplex unicast connections and is reduced by 1 for each active
stream that started. The counter gets reduced by 2 for each multicast audio source,
multiplied by the number of MOH codecs that are configured. The counter gets
reduced by 1 for each unicast audio source, multiplied by the number of MOH
codecs that are configured.
MOHStreamsTotal
This counter represents the total number of simplex (one direction) streams that
have connected to the MOH server since the Cisco IP Voice Media Streaming
Application service started.
MTPConnectionsLost
This counter represents the total number of times since the last restart of the Cisco
IP Voice Streaming Application that a Cisco Unified Communications Manager
connection was lost.
MTPConnectionState
For each Cisco Unified Communications Manager that is associated with an MTP,
this counter represents the current registration state to Cisco Unified
Communications Manager; 0 indicates no registration to Cisco Unified
Communications Manager; 1 indicates registration to the primary Cisco Unified
Communications Manager; 2 indicates connection to the secondary Cisco Unified
Communications Manager (connected to Cisco Unified Communications
Manager but not registered until the primary Cisco Unified Communications
Manager connection fails).
MTPConnectionsTotal
This counter represents the total number of MTP instances that have been started
since the Cisco IP Voice Media Streaming Application service started.
MTPInstancesActive
This counter represents the number of active (currently in use) instances of MTP.
MTPStreamsActive
This counter represents the total number of currently active simplex (one
direction) streams for all connections. Each stream direction counts as one stream.
MTPStreamsAvailable
This counter represents the remaining number of streams that are allocated for the
MTP device that are available for use. This counter starts as 2 multiplied by the
number of configured connections (defined in the Cisco IP Voice Media
Streaming App service parameter for MTP, Call Count) and is reduced by one for
each active stream that started.
MTPStreamsTotal
This counter represents the total number of simplex (one direction) streams that
connected to the MTP device since the Cisco IP Voice Media Streaming
Application service started.
Cisco Messaging Interface
The Cisco Messaging Interface object provides information about the Cisco Messaging Interface (CMI)
service. Table 5-21 contains information on Cisco Messaging Interface (CMI) counters.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
5-28
OL-20105-01
Chapter 5
Cisco Unified Real-Time Monitoring Tool Tracing, PerfMon Counters, and Alerts
Performance Monitoring in RTMT
Table 5-21
Cisco Messaging Interface
Counters
Counter Description
HeartBeat
This counter represents the heartbeat of the CMI service. This incremental count
indicates that the CMI service is up and running. If the count does not increase
(increment), this means that the CMI service is down.
SMDIMessageCountInbound
This counter represents the running count of inbound SMDI messages since the
last restart of the CMI service.
SMDIMessageCountInbound24Hour
This counter represents the rolling count of inbound SMDI messages in the last
24 hours.
SMDIMessageCountOutbound
This counter represents the running count of outbound SMDI messages since the
last restart of the CMI service.
SMDIMessageCountOutbound24Hour
This counter represents the rolling count of outbound SMDI messages in the last
24 hours.
StartTime
This counter represents the time in milliseconds when the CMI service started.
The real-time clock in the computer, which simply acts as a reference point that
indicates the current time and the time that has elapsed, in milliseconds, since the
service started, provides the basis for this time. The reference point specifies
midnight, January 1, 1970.
Cisco MGCP BRI Device
The Cisco Media Gateway Control Protocol (MGCP) Foreign Exchange Office (FXO) Device object
provides information about registered Cisco MGCP BRI devices. Table 5-22 contains information on
Cisco MGCP BRI device counters.
Table 5-22
Cisco MGCP BRI Device
Counters
Counter Description
CallsCompleted
This counter represents the total number of successful calls that were made from
this MGCP Basic Rate Interface (BRI) device
Channel 1 Status
This counter represents the status of the indicated B-Channel that is associated
with the MGCP BRI device. Possible values: 0 (Unknown) indicates the status of
the channel could not be determined; 1 (Out of service) indicates that this channel
is not available for use; 2 (Idle) indicates that this channel has no active call and
is ready for use; 3 (Busy) indicates an active call on this channel; 4 (Reserved)
indicates that this channel has been reserved for use as a D-channel or for use as
a Synch-Channel for BRI.
Channel 2 Status
This counter represents the status of the indicated B-Channel that is associated
with the MGCP BRI device. Possible values: 0 (Unknown) indicates the status of
the channel could not be determined; 1 (Out of service) indicates that this channel
is not available for use; 2 (Idle) indicates that this channel has no active call and
is ready for use; 3 (Busy) indicates an active call on this channel; 4 (Reserved)
indicates that this channel has been reserved for use as a D-channel or for use as
a Synch-Channel for BRI.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
5-29
Chapter 5
Cisco Unified Real-Time Monitoring Tool Tracing, PerfMon Counters, and Alerts
Performance Monitoring in RTMT
Table 5-22
Cisco MGCP BRI Device (continued)
Counters
Counter Description
DatalinkInService
This counter represents the state of the Data Link (D-Channel) on the
corresponding digital access gateway. This value will get set to 1 (one) if the Data
Link is up (in service) or 0 (zero) if the Data Link is down (out of service).
OutboundBusyAttempts
This counter represents the total number of times that a call through this MGCP
BRI device was attempted when no voice channels were available.
Cisco MGCP FXO Device
The Cisco Media Gateway Control Protocol (MGCP) Foreign Exchange Office (FXO) Device object
provides information about registered Cisco MGCP FXO devices. Table 5-23 contains information on
Cisco MGCP FXO device counters.
Table 5-23
Cisco MGCP FXO Device
Counters
Counter Description
CallsCompleted
This counter represents the total number of successful calls that were made from
the port on an MGCP FXO device.
OutboundBusyAttempts
This counter represents the total number of times that a call through the port on
this MGCP FXO device was attempted when no voice channels were available.
PortStatus
This counter represents the status of the FXO port that is associated with this
MGCP FXO device.
Cisco MGCP FXS Device
The Cisco MGCP Foreign Exchange Station (FXS) Device object provides information about registered
Cisco MGCP FXS devices. One instance of this object gets created for each port on a Cisco Catalyst
6000 24 port FXS Analog Interface Module gateway. For example, a fully configured Catalyst 6000
Analog Interface Module would represent 24 separate instances of this object. Table 5-24 contains
information on Cisco MGCP FXS device counters.
Table 5-24
Cisco MGCP FXS Device
Counters
Counter Description
CallsCompleted
This counter represents the total number of successful calls that were made from
this port on the MGCP FXS device.
OutboundBusyAttempts
This counter represents the total number of times that a call through this port on
the MGCP FXS device was attempted when no voice channels were available.
PortStatus
This counter represents the status of the FXS port that is associated with a MGCP
FXS device.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
5-30
OL-20105-01
Chapter 5
Cisco Unified Real-Time Monitoring Tool Tracing, PerfMon Counters, and Alerts
Performance Monitoring in RTMT
Cisco MGCP Gateways
The Cisco MGCP Gateways object provides information about registered MGCP gateways. Table 5-25
contains information on Cisco MGCP gateway counters.
Table 5-25
Cisco MGCP Gateways
Counters
Counter Description
BRIChannelsActive
This counter represents the number of BRI voice channels that are currently active
in a call in the gateway
BRISpansInService
This counter represents the number of BRI spans that are currently available for
use in the gateway.
FXOPortsActive
This counter represents the number of FXO ports that are currently active in a call
in the gateway.
FXOPortsInService
This counter represents the number of FXO ports that are currently available for
use in the gateway.
FXSPortsActive
This counter represents the number of FXS ports that are currently active in a call
in the gateway.
FXSPortsInService
This counter represents the number of FXS ports that are currently available for
use in the gateway.
PRIChannelsActive
This counter represents the number of PRI voice channels that are currently active
in a call in the gateway.
PRISpansInService
This counter represents the number of PRI spans that are currently available for
use in the gateway.
T1ChannelsActive
This counter represents the number of T1 CAS voice channels that are currently
active in a call in the gateway.
T1SpansInService
This counter represents the number of T1 CAS spans that are currently available
for use in the gateway.
Cisco MGCP PRI Device
The Cisco MGCP Primary Rate Interface (PRI) Device object provides information about registered
Cisco MGCP PRI devices. Table 5-26 contains information on Cisco MGCP PRI device counters.
Table 5-26
Cisco MGCP PRI Device
Counters
Counter Description
CallsActive
This counter represents the number of calls that are currently active (in use) on
this MGCP PRI device.
CallsCompleted
This counter represents the total number of successful calls that were made from
this MGCP PRI device.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
5-31
Chapter 5
Cisco Unified Real-Time Monitoring Tool Tracing, PerfMon Counters, and Alerts
Performance Monitoring in RTMT
Table 5-26
Cisco MGCP PRI Device (continued)
Counters
Counter Description
Channel 1 Status through Channel 15
Status (consecutively numbered)
This counter represents the status of the indicated B-Channel that is associated
with a MGCP PRI device. Possible values: 0 (Unknown) indicates that the status
of the channel could not be determined; 1 (Out of service) indicates that this
channel is not available for use; 2 (Idle) indicates that this channel has no active
call and is ready for use; 3 (Busy) indicates that an active call exists on this
channel; 4 (Reserved) indicates that this channel has been reserved for use as a
D-Channel or for use as a Synch-Channel for E-1.
Channel 16 Status
This counter represents the status of the indicated B-Channel that is associated
with a MGCP PRI Device. Possible values: 0-Unknown, 1-Out of service, 2-Idle,
3-Busy, 4-Reserved, for an E1 PRI Interface, this channel is reserved for use as a
D-Channel.
Channel 17 Status through Channel 31
Status (consecutively numbered)
This counter represents the status of the indicated B-Channel that is associated
with the MGCP PRI Device. 0-Unknown, 1-Out of service, 2-Idle, 3-Busy,
4-Reserved.
DatalinkInService
This counter represents the state of the Data Link (D-Channel) on the
corresponding digital access gateway. This value will get set to 1 (one) if the Data
Link is up (in service) or 0 (zero) if the Data Link is down (out of service).
OutboundBusyAttempts
This counter represents the total number of times that a call through an MGCP
PRI device was attempted when no voice channels were available.
Cisco MGCP T1 CAS Device
The Cisco MGCP T1 Channel Associated Signaling (CAS) Device object provides information about
registered Cisco MGCP T1 CAS devices. Table 5-27 contains information on Cisco MGCP TI CAS
device counters.
Table 5-27
Cisco MGCP T1 CAS Device
Counters
Counter Description
CallsActive
This counter represents the number of calls that are currently active (in use) on
this MGCP T1 CAS device.
CallsCompleted
This counter represents the total number of successful calls that were made from
this MGCP T1 CAS device.
Channel 1 Status through Channel 24
Status (consecutively numbered)
This counter represents the status of the indicated B-Channel that is associated
with an MGCP T1 CAS device. Possible values: 0 (Unknown) indicates the status
of the channel could not be determined; 1 (Out of service) indicates that this
channel is not available for use; 2 (Idle) indicates that this channel has no active
call and is ready for use; 3 (Busy) indicates that an active call exists on this
channel; 4 (Reserved) indicates that this channel has been reserved for use as a
D-Channel or for use as a Synch-Channel for E-1.
OutboundBusyAttempts
This counter represents the total number of times that a call through the MGCP
T1 CAS device was attempted when no voice channels were available.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
5-32
OL-20105-01
Chapter 5
Cisco Unified Real-Time Monitoring Tool Tracing, PerfMon Counters, and Alerts
Performance Monitoring in RTMT
Cisco Mobility Manager
The Cisco Mobility Manager object provides information on registered Cisco Unified Mobility Manager
devices. Table 5-28 contains information on Cisco Unified Mobility Manager device counters.
Table 5-28
Cisco Mobility Manager
Counters
Counter Description
MobileCallsAnchored
This counter represents the total number of paths that are associated with
single-mode/dual-mode phone call that is currently anchored on a Cisco Unified
Communications Manager. Call anchoring occurs when a call enters an enterprise
gateway and connects to a mobility application that then uses redirection to send
the call back out an enterprise gateway. For example, this counter increments
twice for a dual-mode phone-to-dual-mode phone call: once for the originating
call and once for the terminating call. When the call terminates, this counter
decrements accordingly.
MobilityHandinsAborted
This counter represents the total number of aborted handins.
MobileHandinsCompleted
This counter represents the total number of handins that were completed by
dual-mode phones. A completed handin occurs when the call successfully
connects in the enterprise network and the phone moves from WAN to WLAN.
MobilityHandinsFailed
This counter represents the total number of handins (calls on mobile devices that
move from cellular to the wireless network) that failed.
MobilityHandoutsAborted
This counter represents the total number of aborted handouts.
MobileHandoutsCompleted
This counter represents the total number of handouts (calls on mobile devices that
move from the enterprise WLAN network to the cellular network) that were
completed. A completed handout occurs when the call successfully connects.
MobileHandoutsFailed
This counter represents the total number of handouts (calls on mobile devices that
move from cellular to the wireless network) that failed.
MobilityFollowMeCallsAttempted
This counter represents the total number of follow-me calls that were attempted.
MobilityFollowMeCallsIgnoredDueToA
nswerTooSoon
This counter represents the total number of follow-me calls that were ignored
before the AnswerTooSoon timer went off.
MobilityIVRCallsAttempted
This counter represents the total number of attempted IVR calls.
MobilityIVRCallsFailed
This counter represents the total number of failed IVR calls.
MobilityIVRCallsSucceeded
This counter represents the total number of successful IVR calls.
MobilitySCCPDualModeRegistered
This counter represents the total number of dual-mode SCCP devices that are
registered.
MobilitySIPDualModeRegistered
This counter represents the total number of dual-mode SIP devices that are
registered.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
5-33
Chapter 5
Cisco Unified Real-Time Monitoring Tool Tracing, PerfMon Counters, and Alerts
Performance Monitoring in RTMT
Cisco Music On Hold (MOH) Device
The Cisco Music On Hold (MOH) Device object provides information about registered Cisco MOH
devices. Table 5-29 contains information on Cisco MOH device counters.
Table 5-29
Cisco MOH Device
Counters
Counter Description
MOHHighestActiveResources
This counter represents the largest number of simultaneously active MOH
connections for an MOH server. This number includes both multicast and unicast
connections.
MOHMulticastResourceActive
This counter represents the number of currently active multicast connections to
multicast addresses that are served by an MOH server.
Each MOH multicast resource uses one stream for each audio source and codec
combination. For example, if the default audio source is configured for multicast,
G.711 mu-law and wideband codecs, two streams get used (default audio source
+ G.711 mu-law and default audio source + wideband).
MOHMulticastResourceAvailable
This counter represents the number of multicast MOH connections to multicast
addresses that are served by an MOH server that are not active and are still
available to be used now for the MOH server.
Each MOH multicast resource uses one stream for each audio source and codec
combination. For example, if the default audio source is configured for multicast,
G.711 mu-law and wideband codecs, two streams get used (default audio source
+ G.711 mu-law and default audio source + wideband).
MOHOutOfResources
This counter represents the total number of times that the Media Resource
Manager attempted to allocate an MOH resource when all available resources on
all MOH servers that are registered with a Cisco Unified Communications
Manager were already active.
MOHTotalMulticastResources
This counter represents the total number of multicast MOH connections that are
allowed to multicast addresses that are served by an MOH server.
Each MOH multicast resource uses one stream for each audio source and codec
combination. For example, if the default audio source is configured for multicast,
G.711 mu-law and wideband codecs, two streams get used (default audio source
+ G.711 mu-law and default audio source + wideband).
MOHTotalUnicastResources
This counter represents the total number of unicast MOH connections that are
allowed by an MOH server.
Each MOH unicast resource uses one stream.
MOHUnicastResourceActive
This counter represents the number of active unicast MOH connections to an
MOH server.
Each MOH unicast resource uses one stream.
MOHUnicastResourceAvailable
This counter represents the number of unicast MOH connections that are not
active and are still available to be used now for an MOH server.
Each MOH unicast resource uses one stream.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
5-34
OL-20105-01
Chapter 5
Cisco Unified Real-Time Monitoring Tool Tracing, PerfMon Counters, and Alerts
Performance Monitoring in RTMT
Cisco MTP Device
The Cisco Media Termination Point (MTP) Device object provides information about registered Cisco
MTP devices. Table 5-30 contains information on Cisco MTP device counters.
Table 5-30
Cisco MTP Device
Counters
Counter Description
OutOfResources
This counter represents the total number of times that an attempt was made to
allocate an MTP resource from an MTP device and failed; for example, because
all resources were already in use.
ResourceActive
This counter represents the number of MTP resources that are currently in use
(active) for an MTP device.
Each MTP resource uses two streams. An MTP in use represents one MTP
resource that has been allocated for use in a call.
ResourceAvailable
This counter represents the total number of MTP resources that are not active and
are still available to be used now for an MTP device.
Each MTP resource uses two streams. An MTP in use represents one MTP
resource that has been allocated for use in a call.
ResourceTotal
This counter represents the total number of MTP resources that an MTP device
provides. This counter equals the sum of the counters ResourceAvailable and
ResourceActive.
Cisco Phones
The Cisco Phones object provides information about the number of registered Cisco Unified IP Phones,
including both hardware-based and other station devices.
The CallsAttempted counter represents the number of calls that have been attempted from this phone.
This number increases each time that the phone goes off hook and on hook.
Cisco Presence Feature
The Cisco Presence object provides information about presence subscriptions, such as statistics that are
related to the speed dial or call list Busy Lamp Field (BLF) subscriptions. Table 5-31 contains
information on Cisco Presence feature.
Table 5-31
Cisco Presence
Counters
Counter Description
ActiveCallListAndTrunkSubscriptions
This counter represents the active presence subscriptions for the call list feature
as well as presence subscriptions through SIP trunk.
ActiveSubscriptions
This counter represents all active incoming and outgoing presence subscriptions.
CallListAndTrunkSubscriptionsThrottled
This counter represents the cumulative number of rejected call list and trunk side
presence subscriptions due to throttling for the call list feature.
IncomingLineSideSubscriptions
This counter represents the cumulative number of presence subscriptions that
were received on the line side.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
5-35
Chapter 5
Cisco Unified Real-Time Monitoring Tool Tracing, PerfMon Counters, and Alerts
Performance Monitoring in RTMT
Table 5-31
Cisco Presence
Counters
Counter Description
IncomingTrunkSideSubscriptions
This counter represents the cumulative number of presence subscriptions that
were received on the trunk side.
OutgoingTrunkSideSubscriptions
This counter represents the cumulative number of presence subscriptions that
were sent on the trunk side.
Cisco QSIG Feature
The Cisco QSIG Feature object provides information regarding the operation of various QSIG features,
such as call diversion and path replacement. Table 5-32 contains information on the Cisco QSIG feature
counters.
Table 5-32
Cisco QSIG Feature
Counters
Counter Description
CallForwardByRerouteCompleted
This counter represents the number of successful calls that has been forwarded by
rerouting. Call forward by rerouting enables the path for a forwarded call to be
optimized (minimizes the number of B-Channels in use) from the originator
perspective. This counter gets reset when the Cisco CallManager service
parameter Call Forward by Reroute Enabled is enabled or disabled, or when the
Cisco CallManager service restarts.
PathReplacementCompleted
This counter represents the number of successful path replacements that have
occurred. Path replacement in a QSIG network optimizes the path between two
edge PINX (PBXs) that are involved in a call. This counter resets when the
Cisco CallManager service parameter Path Replacement Enabled is enabled or
disabled, or when the Cisco CallManager service restarts.
Cisco Signaling Performance
The Cisco Signaling Performance object provides call-signaling data on transport communications on
Cisco Unified Communications Manager. Table 5-33 contains information on the Cisco Signaling
Performance counter.
Table 5-33
Cisco Signaling Performance
Counters
Counter Description
UDPPacketsThrottled
This counter represents the total number of incoming UDP packets that were
throttled (dropped) because they exceeded the threshold for the number of
incoming packets per second that is allowed from a single IP address. Configure
the threshold via the SIP Station UDP Port Throttle Threshold and SIP Trunk
UDP Port Throttle Threshold service parameters in Cisco Unified
Communications Manager Administration. This counter increments for every
throttled UDP packet that was received since the last restart of the Cisco
CallManager Service.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
5-36
OL-20105-01
Chapter 5
Cisco Unified Real-Time Monitoring Tool Tracing, PerfMon Counters, and Alerts
Performance Monitoring in RTMT
Cisco SIP
The Cisco Session Initiation Protocol (SIP) object provides information about configured SIP devices.
Table 5-34 contains information on the Cisco SIP counters.
Table 5-34
Cisco SIP
Counters
Counter Description
CallsActive
This counter represents the number of calls that are currently active (in use) on
this SIP device.
CallsAttempted
This counter represents the number of calls that have been attempted on this SIP
device, including both successful and unsuccessful call attempts.
CallsCompleted
This counter represents the number of calls that were actually connected (a voice
path was established) from a SIP device. This number increases when the call
terminates.
CallsInProgress
This counter represents the number of calls that are currently in progress on a SIP
device, including all active calls. When all calls that are in progress are connected,
the number of CallsInProgress equals the number of CallsActive.
VideoCallsActive
This counter represents the number of video calls with streaming video
connections that are currently active (in use) on this SIP device.
VideoCallsCompleted
This counter represents the number of video calls that were actually connected
with video streams for this SIP device. This number increments when the call
terminates.
Cisco SIP Stack
The Cisco SIP Stack object provides information about Session Initiation Protocol (SIP) stack statistics
that are generated or used by SIP devices such as SIP Proxy, SIP Redirect Server, SIP Registrar, and SIP
User Agent. Table 5-35 contains information on Cisco SIP Stack counters.
Table 5-35
Cisco SIP Stack
Counters
Counter Description
AckIns
This counter represents the total number of ACK requests that the SIP device
received.
AckOuts
This counter represents the total number of ACK requests that the SIP device sent.
ByeIns
This counter represents the total number of BYE requests that the SIP device
received. This number includes retransmission.
ByeOuts
This counter represents the total number of BYE requests that the SIP device sent.
This number includes retransmission.
CancelIns
This counter represents the total number of CANCEL requests that the SIP device
received. This number includes retransmission.
CancelOuts
This counter represents the total number of CANCEL requests that the SIP device
sent. This number includes retransmission.
CCBsAllocated
This counter represents the number of Call Control Blocks (CCB) that are
currently in use by the SIP stack. Each active SIP dialog uses one CCB.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
5-37
Chapter 5
Cisco Unified Real-Time Monitoring Tool Tracing, PerfMon Counters, and Alerts
Performance Monitoring in RTMT
Table 5-35
Cisco SIP Stack (continued)
Counters
Counter Description
GlobalFailedClassIns
This counter represents the total number of 6xx class SIP responses that the SIP
device received. This number includes retransmission. This class of responses
indicates that a SIP device, that is providing a client function, received a failure
response message. Generally, the responses indicate that a server had definitive
information on a particular called party and not just the particular instance in the
Request-URI.
GlobalFailedClassOuts
This counter represents the total number of 6xx class SIP responses that the SIP
device sent. This number includes retransmission. This class of responses
indicates that a SIP device, that is providing a server function, received a failure
response message. Generally, the responses indicate that a server had definitive
information on a particular called party and not just the particular instance in the
Request-URI.
InfoClassIns
This counter represents the total number of 1xx class SIP responses that the SIP
device received. This includes retransmission. This class of responses provides
information on the progress of a SIP request.
InfoClassOuts
This counter represents the total number of 1xx class SIP responses that the SIP
device sent. This includes retransmission. This class of responses provides
information on the progress of processing a SIP request.
InfoIns
This counter represents the total number of INFO requests that the SIP device has
received. This number includes retransmission.
InfoOuts
This counter represents the total number of INFO requests that the SIP device has
sent. This number includes retransmission.
InviteIns
This counter represents the total number of INVITE requests that the SIP device
received. This number includes retransmission.
InviteOuts
This counter represents the total number of INVITE requests that the SIP device
sent. This number includes retransmission.
NotifyIns
This counter represents the total number of NOTIFY requests that the SIP device
received. This number includes retransmission.
NotifyOuts
This counter represents the total number of NOTIFY requests that the SIP device
sent. This number includes retransmission.
OptionsIns
This counter represents the total number of OPTIONS requests that the SIP device
received. This number includes retransmission.
OptionsOuts
This counter represents the total number of OPTIONS requests that the SIP device
sent. This number includes retransmission.
PRAckIns
This counter represents the total number of PRACK requests that the SIP device
received. This number includes retransmission.
PRAckOuts
This counter represents the total number of PRACK requests that the SIP device
sent. This number includes retransmission.
PublishIns
This counter represents the total number of PUBLISH requests that the SIP device
received. This number includes retransmissions.
PublishOuts
This counter represents the total number of PUBLISH requests that the SIP device
sent. This number includes retransmission
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
5-38
OL-20105-01
Chapter 5
Cisco Unified Real-Time Monitoring Tool Tracing, PerfMon Counters, and Alerts
Performance Monitoring in RTMT
Table 5-35
Cisco SIP Stack (continued)
Counters
Counter Description
RedirClassIns
This counter represents the total number of 3xx class SIP responses that the SIP
device received. This number includes retransmission. This class of responses
provides information about redirections to addresses where the callee may be
reachable.
RedirClassOuts
This counter represents the total number of 3xx class SIP responses that the SIP
device sent. This number includes retransmission. This class of responses
provides information about redirections to addresses where the callee may be
reachable.
ReferIns
This counter represents the total number of REFER requests that the SIP device
received. This number includes retransmission.
ReferOuts
This counter represents the total number of REFER requests that the SIP device
sent. This number includes retransmission.
RegisterIns
This counter represents the total number of REGISTER requests that the SIP
device received. This number includes retransmission.
RegisterOuts
This counter represents the total number of REGISTER requests that the SIP
device sent. This number includes retransmission.
RequestsFailedClassIns
This counter represents the total number of 4xx class SIP responses that the SIP
device received. This number includes retransmission. This class of responses
indicates a request failure by a SIP device that is providing a client function.
RequestsFailedClassOuts
This counter represents the total number of 4xx class SIP responses that the SIP
device sent. This number includes retransmission. This class of responses
indicates a request failure by a SIP device that is providing a server function.
RetryByes
This counter represents the total number of BYE retries that the SIP device sent.
To determine the number of first BYE attempts, subtract the value of this counter
from the value of the sipStatsByeOuts counter.
RetryCancels
This counter represents the total number of CANCEL retries that the SIP device
sent. To determine the number of first CANCEL attempts, subtract the value of
this counter from the value of the sipStatsCancelOuts counter.
RetryInfo
This counter represents the total number of INFO retries that the SIP device sent.
To determine the number of first INFO attempts, subtract the value of this counter
from the value of the sipStatsInfoOuts counter.
RetryInvites
This counter represents the total number of INVITE retries that the SIP device
sent. To determine the number of first INVITE attempts, subtract the value of this
counter from the value of the sipStatsInviteOuts counter.
RetryNotify
This counter represents the total number of NOTIFY retries that the SIP device
sent. To determine the number of first NOTIFY attempts, subtract the value of this
counter from the value of the sipStatsNotifyOuts counter.
RetryPRAck
This counter represents the total number of PRACK retries that the SIP device
sent. To determine the number of first PRACK attempts, subtract the value of this
counter from the value of the sipStatsPRAckOuts counter.
RetryPublish
This counter represents the total number of PUBLISH retries that the SIP device
sent. To determine the number of first PUBLISH attempts, subtract the value of
this counter from the value of the sipStatsPublishOuts counter.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
5-39
Chapter 5
Cisco Unified Real-Time Monitoring Tool Tracing, PerfMon Counters, and Alerts
Performance Monitoring in RTMT
Table 5-35
Cisco SIP Stack (continued)
Counters
Counter Description
RetryRefer
This counter represents the total number of REFER retries that the SIP device
sent. To determine the number of first REFER attempts, subtract the value of this
counter from the value of the sipStatsReferOuts counter.
RetryRegisters
This counter represents the total number of REGISTER retries that the SIP device
sent. To determine the number of first REGISTER attempts, subtract the value of
this counter from the value of the sipStatsRegisterOuts counter.
RetryRel1xx
This counter represents the total number of Reliable 1xx retries that the SIP
device sent.
RetryRequestsOut
This counter represents the total number of Request retries that the SIP device
sent.
RetryResponsesFinal
This counter represents the total number of Final Response retries that the SIP
device sent.
RetryResponsesNonFinal
This counter represents the total number of non-Final Response retries that the
SIP device sent.
RetrySubscribe
This counter represents the total number of SUBSCRIBE retries that the SIP
device sent. To determine the number of first SUBSCRIBE attempts, subtract the
value of this counter from the value of the sipStatsSubscribeOuts counter.
RetryUpdate
This counter represents the total number of UPDATE retries that the SIP device
sent. To determine the number of first UPDATE attempts, subtract the value of
this counter from the value of the sipStatsUpdateOuts counter.
SCBsAllocated
This counter represents the number of Subscription Control Blocks (SCB) that are
currently in use by the SIP stack. Each subscription uses one SCB.
ServerFailedClassIns
This counter represents the total number of 5xx class SIP responses that the SIP
device received. This number includes retransmission. This class of responses
indicates that failure responses were received by a SIP device that is providing a
client function.
ServerFailedClassOuts
This counter represents the total number of 5xx class SIP responses that the SIP
device sent. This number includes retransmission. This class of responses
indicates that failure responses were received by a SIP device that is providing a
server function.
SIPGenericCounter1
Do not use this counter unless directed to do so by a Cisco Engineering Special
build. Cisco uses information in this counter for diagnostic purposes.
SIPGenericCounter2
Do not use this counter unless directed to do so by a Cisco Engineering Special
build. Cisco uses information in this counter for diagnostic purposes.
SIPGenericCounter3
Do not use this counter unless directed to do so by a Cisco Engineering Special
build. Cisco uses information in this counter for diagnostic purposes.
SIPGenericCounter4
Do not use this counter unless directed to do so by a Cisco Engineering Special
build. Cisco uses information in this counter for diagnostic purposes.
SIPHandlerSDLQueueSignalsPresent
This counter represents the number of SDL signals that are currently on the four
SDL priority queues of the SIPHandler component. The SIPHandler component
contains the SIP stack.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
5-40
OL-20105-01
Chapter 5
Cisco Unified Real-Time Monitoring Tool Tracing, PerfMon Counters, and Alerts
Performance Monitoring in RTMT
Table 5-35
Cisco SIP Stack (continued)
Counters
Counter Description
StatusCode1xxIns
This counter represents the total number of 1xx response messages, including
retransmission, that the SIP device received. This count includes the following
1xx responses:
StatusCode1xxOuts
StatusCode2xxIns
StatusCode2xxOuts
StatusCode3xxins
StatusCode302Outs
•
100 Trying
•
180 Ringing
•
181 Call is being forwarded
•
182 Queued
•
183 Session Progress
This counter represents the total number of 1xx response messages, including
retransmission, that the SIP device sent. This count includes the following 1xx
responses:
•
100 Trying
•
180 Ringing
•
181 Call is being forwarded
•
182 Queued
•
183 Session Progress
This counter represents the total number of 2xx response messages, including
retransmission, that the SIP device received. This count includes the following
2xx responses:
•
200 OK
•
202 Success Accepted
This counter represents the total number of 2xx response messages, including
retransmission, that the SIP device sent. This count includes the following 2xx
responses:
•
200 OK
•
202 Success Accepted
This counter represents the total number of 3xx response messages, including
retransmission, that the SIP device received. This count includes the following
3xx responses:
•
300 Multiple Choices
•
301 Moved Permanently
•
302 Moved Temporarily
•
303 Incompatible Bandwidth Units
•
305 Use Proxy
•
380 Alternative Service
This counter represents the total number of 302 Moved Temporarily response
messages, including retransmission, that the SIP device sent.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
5-41
Chapter 5
Cisco Unified Real-Time Monitoring Tool Tracing, PerfMon Counters, and Alerts
Performance Monitoring in RTMT
Table 5-35
Cisco SIP Stack (continued)
Counters
Counter Description
StatusCode4xxIns
This counter represents the total number of 4xx response messages, including
retransmission, that the SIP device received. This count includes the following
4xx responses:
•
400 Bad Request
•
401 Unauthorized
•
402 Payment Required
•
403 Forbidden
•
404 Not Found
•
405 Method Not Allowed
•
406 Not Acceptable
•
407 Proxy Authentication Required
•
408 Request Timeout
•
409 Conflict
•
410 Gone
•
413 Request Entity Too Large
•
414 Request-URI Too Long
•
415 Unsupported Media Type
•
416 Unsupported URI Scheme
•
417 Unknown Resource Priority
•
420 Bad Extension
•
422 Session Expires Value Too Small
•
423 Interval Too Brief
•
480 Temporarily Unavailable
•
481 Call/Transaction Does Not Exist
•
482 Loop Detected
•
483 Too Many Hops
•
484 Address Incomplete
•
485 Ambiguous
•
486 Busy Here
•
487 Request Terminated
•
488 Not Acceptable Here
•
489 Bad Subscription Event
•
491 Request Pending
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
5-42
OL-20105-01
Chapter 5
Cisco Unified Real-Time Monitoring Tool Tracing, PerfMon Counters, and Alerts
Performance Monitoring in RTMT
Table 5-35
Cisco SIP Stack (continued)
Counters
Counter Description
StatusCode4xxOuts
This counter represents the total number of 4xx response messages, including
retransmission, that the SIP device sent. This count includes the following 4xx
responses:
•
400 Bad Request
•
401 Unauthorized
•
402 Payment Required
•
403 Forbidden
•
404 Not Found
•
405 Method Not Allowed
•
406 Not Acceptable
•
407 Proxy Authentication Required
•
408 Request Timeout
•
409 Conflict
•
410 Gone
•
413 Request Entity Too Large
•
414 Request-URI Too Long
•
415 Unsupported Media Type
•
416 Unsupported URI Scheme
•
417 Unknown Resource Priority
•
420 Bad Extension
•
422 Session Expires Value Too Small
•
423 Interval Too Brief
•
480 Temporarily Unavailable
•
481 Call/Transaction Does Not Exist
•
482 Loop Detected
•
483 Too Many Hops
•
484 Address Incomplete
•
485 Ambiguous
•
486 Busy Here
•
487 Request Terminated
•
488 Not Acceptable Here
•
489 Bad Subscription Event
•
491 Request Pending
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
5-43
Chapter 5
Cisco Unified Real-Time Monitoring Tool Tracing, PerfMon Counters, and Alerts
Performance Monitoring in RTMT
Table 5-35
Cisco SIP Stack (continued)
Counters
Counter Description
StatusCode5xxIns
This counter represents the total number of 5xx response messages, including
retransmission, that the SIP device received. This count includes the following
5xx responses:
StatusCode5xxOuts
StatusCode6xxIns
StatusCode6xxOuts
•
500 Server Internal Error
•
501 Not Implemented
•
502 Bad Gateway
•
503 Service Unavailable
•
504 Server Timeout
•
505 Version Not Supported
•
580 Precondition Failed
This counter represents the total number of 5xx response messages, including
retransmission, that the SIP device sent. This count includes the following 5xx
responses:
•
500 Server Internal Error
•
501 Not Implemented
•
502 Bad Gateway
•
503 Service Unavailable
•
504 Server Timeout
•
505 Version Not Supported
•
580 Precondition Failed
This counter represents the total number of 6xx response messages, including
retransmission, that the SIP device received. This count includes the following
6xx responses:
•
600 Busy Everywhere
•
603 Decline
•
604 Does Not Exist Anywhere
•
606 Not Acceptable
This counter represents the total number of 6xx response messages, including
retransmission, that the SIP device sent. This count includes the following 6xx
responses:
•
600 Busy Everywhere
•
603 Decline
•
604 Does Not Exist Anywhere
•
606 Not Acceptable
SubscribeIns
This counter represents the total number of SUBSCRIBE requests that the SIP
device received. This number includes retransmission.
SubscribeOuts
This counter represents the total number of SUBSCRIBE requests that the SIP
device sent. This number includes retransmission.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
5-44
OL-20105-01
Chapter 5
Cisco Unified Real-Time Monitoring Tool Tracing, PerfMon Counters, and Alerts
Performance Monitoring in RTMT
Table 5-35
Cisco SIP Stack (continued)
Counters
Counter Description
SuccessClassIns
This counter represents the total number of 2xx class SIP responses that the SIP
device received. This includes retransmission. This class of responses provides
information on the successful completion of a SIP request.
SuccessClassOuts
This counter represents the total number of 2xx class SIP responses that the SIP
device sent. This includes retransmission. This class of responses provides
information on the successful completion of a SIP request.
SummaryRequestsIn
This counter represents the total number of SIP request messages that the SIP
device received. This number includes retransmissions.
SummaryRequestsOut
This counter represents the total number of SIP request messages that the device
sent. This number includes messages that originate on the device and messages
that are being relayed by the device. When a particular message gets sent more
than once, each transmission gets counted separately; for example, a message that
is re-sent as a retransmission or as a result of forking.
SummaryResponsesIn
This counter represents the total number of SIP response messages that the SIP
device received. This number includes retransmission.
SummaryResponsesOut
This counter represents the total number of SIP response messages that the SIP
device sent (originated and relayed). This number includes retransmission.
UpdateIns
This counter represents the total number of UPDATE requests that the SIP device
received. This number includes retransmission.
UpdateOuts
This counter represents the total number of UPDATE requests that the SIP device
sent. This number includes retransmission.
Cisco SIP Station
The Cisco SIP Station object provides information about SIP line-side devices. Table 5-36 contains
information on the Cisco SIP Station counters.
Table 5-36
Cisco SIP Station
Counters
Counter Description
ConfigMismatchesPersistent
This counter represents the number of times that a phone that is running SIP was
persistently unable to register due to a configuration version mismatch between
the TFTP server and Cisco Unified Communications Manager since the last
restart of the Cisco Unified Communications Manager. This counter increments
each time that Cisco Unified Communications Manager cannot resolve the
mismatch and manual intervention is required (such as a configuration update or
device reset).
ConfigMismatchesTemporary
This counter represents the number of times that a phone that is running SIP was
temporarily unable to register due to a configuration version mismatch between
the TFTP server and Cisco Unified Communications Manager since the last
restart of the Cisco CallManager service. This counter increments each time
Cisco Unified Communications Manager can resolve the mismatch automatically.
DBTimeouts
This counter represents the number of new registrations that failed because a
timeout occurred while the system was attempting to retrieve the device
configuration from the database.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
5-45
Chapter 5
Cisco Unified Real-Time Monitoring Tool Tracing, PerfMon Counters, and Alerts
Performance Monitoring in RTMT
Table 5-36
Cisco SIP Station (continued)
Counters
Counter Description
NewRegAccepted
This counter represents the total number of new REGISTRATION requests that
have been removed from the NewRegistration queue and processed since the last
restart of the Cisco CallManager service.
NewRegQueueSize
This counter represents the number of REGISTRATION requests that are
currently on the NewRegistration queue. The system places REGISTRATION
requests that are received from devices that are not currently registered on this
queue before they are processed.
NewRegRejected
This counter represents the total number of new REGISTRATION requests that
were rejected with a 486 Busy Here response and not placed on the
NewRegistration queue since the last restart of the Cisco CallManager service.
The system rejects REGISTRATION requests if the NewRegistration queue
exceeds a programmed size.
TokensAccepted
This counter represents the total number of token requests that have been granted
since the last Cisco Communications Manager restart. Cisco Unified
Communications Manager grants tokens as long as the number of outstanding
tokens remains below the number that is specified in the Cisco CallManager
service parameter Maximum Phone Fallback Queue Depth.
TokensOutstanding
This counter represents the number of devices that have been granted a token but
have not yet registered. The system requires that devices that are reconnecting to
a higher priority Cisco Unified Communications Manager server be granted a
token before registering. Tokens protect Cisco Unified Communications Manager
from being overloaded with registration requests when it comes back online after
a failover situation.
TokensRejected
This counter represents the total number of token requests that have been rejected
since the last Cisco Unified Communications Manager restart. Cisco Unified
Communications Manager will reject token request if the number of outstanding
tokens is greater than the number that is specified in the Cisco CallManager
service parameter Maximum Phone Fallback Queue Depth.
Cisco SW Conf Bridge Device
The Cisco SW Conference Bridge Device object provides information about registered Cisco software
conference bridge devices. Table 5-37 contains information on the Cisco software conference bridge
device counters.
Table 5-37
Cisco SW Conf Bridge Device
Counters
Counter Description
OutOfResources
This counter represents the total number of times that an attempt was made to
allocate a conference resource from a SW conference device and failed because
all resources were already in use.
ResourceActive
This counter represents the number of resources that are currently in use (active)
for a SW conference device. One resource represents one stream.
ResourceAvailable
This counter represents the total number of resources that are not active and are
still available to be used now for a SW conference device. One resource represents
one stream.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
5-46
OL-20105-01
Chapter 5
Cisco Unified Real-Time Monitoring Tool Tracing, PerfMon Counters, and Alerts
Performance Monitoring in RTMT
Table 5-37
Cisco SW Conf Bridge Device (continued)
Counters
Counter Description
ResourceTotal
This counter represents the total number of conference resources that a SW
conference device provides. One resource represents one stream.This counter
equals the sum of the ResourceAvailable and ResourceActive counters.
SWConferenceActive
This counter represents the number of software-based conferences that are
currently active (in use) on a SW conference device.
SWConferenceCompleted
This counter represents the total number of conferences that have been allocated
and released on a SW conference device. A conference starts when the first call
connects to the bridge. The conference completes when the last call disconnects
from the bridge.
Cisco TFTP Server
The Cisco Trivial File Transfer Protocol (TFTP) Server object provides information about the
Cisco TFTP server. Table 5-38 contains information on Cisco TFTP server counters.
Table 5-38
Cisco TFTP Server
Counters
Counter Description
BuildAbortCount
This counter represents the number of times that the build process aborted when
it received a Build all request. This counter increases when building of
device/unit/softkey/dial rules gets aborted as a result of group level change
notifications.
BuildCount
This counter represents the number of times since the TFTP service started that
the TFTP server has built all the configuration files in response to a database
change notification that affects all devices. This counter increases by one every
time the TFTP server performs a new build of all the configuration files.
BuildDeviceCount
This counter represents the number of devices that were processed in the last build
of all the configuration files. This counter also updates while processing device
change notifications. The counter increases when a new device is added and
decreases when an existing device is deleted.
BuildDialruleCount
This counter represents the number of dial rules that were processed in the last
build of the configuration files. This counter also updates while processing dial
rule change notifications. The counter increases when a new dial rule is added and
decreases when an existing dial rule is deleted.
BuildDuration
This counter represents the time in seconds that it took to build the last
configuration files.
BuildSignCount
This counter represents the number of security-enabled phone devices for which
the configuration file was digitally signed with the Cisco Unified
Communications Manager server key in the last build of all the configuration
files. This counter also updates while processing security-enabled phone device
change notifications.
BuildSoftKeyCount
This counter represents the number of softkeys that were processed in the last
build of the configuration files. This counter increments when a new softkey is
added and decrements when an existing softkey is deleted.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
5-47
Chapter 5
Cisco Unified Real-Time Monitoring Tool Tracing, PerfMon Counters, and Alerts
Performance Monitoring in RTMT
Table 5-38
Cisco TFTP Server (continued)
Counters
Counter Description
BuildUnitCount
This counter represents the number of gateways that were processed in the last
build of all the configuration files. This counter also updates while processing unit
change notifications. The counter increases when a new gateway is added and
decreases when an existing gateway is deleted.
ChangeNotifications
This counter represents the total number of all the Cisco Unified Communications
Manager database change notifications that the TFTP server received. Each time
that a device configuration is updated in Cisco Unified Communications Manager
Administration, the TFTP server gets sent a database change notification to
rebuild the XML file for the updated device.
DeviceChangeNotifications
This counter represents the number of times that the TFTP server received
database change notification to create, update, or delete configuration files for
devices.
DialruleChangeNotifications
This counter represents the number of times that the TFTP server received
database change notification to create, update, or delete configuration files for
dial rules.
EncryptCount
This counter represents the number of configuration files that were encrypted.
This counter gets updated each time a configuration file is successfully encrypted
GKFoundCount
This counter represents the number of GK files that were found in the cache. This
counter gets updated each time a GK file is found in the cache
GKNotFoundCount
This counter represents the number of GK files that were not found in the cache.
This counter gets updated each time a request to get a GK file results in the cache
not finding it
HeartBeat
This counter represents the heartbeat of the TFTP server. This incremental count
indicates that the TFTP server is up and running. If the count does not increase,
this means that the TFTP server is down.
HttpConnectRequests
This counter represents the number of clients that are currently requesting the
HTTP GET file request.
HttpRequests
This counter represents the total number of file requests (such as requests for
XML configuration files, phone firmware files, audio files, and so on.) that the
HTTP server handled. This counter represents the sum total of the following
counters since the HTTP service started: RequestsProcessed, RequestsNotFound,
RequestsOverflow, RequestsAborted, and RequestsInProgress.
HttpRequestsAborted
This counter represents the total number of HTTP requests that the HTTP server.
canceled (aborted) unexpectedly. Requests could get aborted if the requesting
device cannot be reached (for instance, the device lost power) or if the file transfer
was interrupted due to network connectivity problems.
HttpRequestsNotFound
This counter represents the total number of HTTP requests where the requested
file was not found. When the HTTP server does not find the requested file, a
message gets sent to the requesting device.
HttpRequestsOverflow
This counter represents the total number of HTTP requests that were rejected
when the maximum number of allowable client connections was reached. The
requests may have arrived while the TFTP server was building the configuration
files or because of some other resource limitation. The Cisco TFTP advanced
service parameter, Maximum Serving Count, sets the maximum number of
allowable connections.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
5-48
OL-20105-01
Chapter 5
Cisco Unified Real-Time Monitoring Tool Tracing, PerfMon Counters, and Alerts
Performance Monitoring in RTMT
Table 5-38
Cisco TFTP Server (continued)
Counters
Counter Description
HttpRequestsProcessed
This counter represents the total number of HTTP requests that the HTTP server.
successfully processed.
HttpServedFromDisk
This counters represents the number of requests that the HTTP server completed
with the files that are on disk and not cached in memory.
LDFoundCount
This counter represents the number of LD files that were found in the cache. This
counter gets updated each time that a LD file is found in cache memory.
LDNotFoundCount
This counter represents the number of LD files that were not found in cache
memory. This counter gets updated each time that a request to get an LD file
results in the cache not finding it.
MaxServingCount
This counter represents the maximum number of client connections that the TFTP
can serve simultaneously. The Cisco TFTP advanced service parameter,
Maximum Serving Count, sets this value.
Requests
This counter represents the total number of file requests (such as requests for
XML configuration files, phone firmware files, audio files, and so on.) that the
TFTP server handles. This counter represents the sum total of the following
counters since the TFTP service started: RequestsProcessed, RequestsNotFound,
RequestsOverflow, RequestsAborted, and RequestsInProgress.
RequestsAborted
This counter represents the total number of TFTP requests that the TFTP server
canceled (aborted) unexpectedly. Requests could get aborted if the requesting
device cannot be reached (for instance, the device lost power) or if the file transfer
was interrupted due to network connectivity problems.
RequestsInProgress
This counter represents the number of file requests that the TFTP server currently
is processing. This counter increases for each new file request and decreases for
each file request that completes. This counter indicates the current load of the
TFTP server.
RequestsNotFound
This counter represents the total number of TFTP requests for which the requested
file was not found. When the TFTP server does not find the requested file, a
message gets sent to the requesting device. If this counter increments in a cluster
that is configured as secure, this event usually indicates an error condition. If,
however, the cluster is configured as non-secure, it is normal for the CTL file to
be absent (not found), which results in a message being sent to the requesting
device and a corresponding increment in this counter. For non-secure clusters,
this normal occurrence does not represent an error condition.
RequestsOverflow
This counter represents the total number of TFTP requests that were rejected
because the maximum number of allowable client connections was exceeded,
because requests arrived while the TFTP server was building the configuration
files, or because of some other resource limitation. The Cisco TFTP advanced
service parameter, Maximum Serving Count, sets the maximum number of
allowable connections.
RequestsProcessed
This counter represents the total number of TFTP requests that the TFTP server
successfully processed.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
5-49
Chapter 5
Cisco Unified Real-Time Monitoring Tool Tracing, PerfMon Counters, and Alerts
Performance Monitoring in RTMT
Table 5-38
Cisco TFTP Server (continued)
Counters
Counter Description
SegmentsAcknowledged
This counter represents the total number of data segments that the client devices
acknowledged. Files get sent to the requesting device in data segments of 512
bytes, and for each 512-byte segment, the device sends the TFTP server an
acknowledgment message. Each additional data segment gets sent upon receipt of
the acknowledgment for the previous data segment until the complete file
successfully gets transmitted to the requesting device.
SegmentsFromDisk
This counter represents the number of data segments that the TFTP server reads
from the files on disk, while serving files.
SegmentSent
This counter represents the total number of data segments that the TFTP server
sent. Files get sent to the requesting device in data segments of 512 bytes.
SEPFoundCount
This counter represents the number of SEP files that were successfully found in
the cache. This counter gets updated each time that a SEP file is found in the
cache.
SEPNotFoundCount
This counter represents the number of SEP files that were not found in the cache.
This counter gets updated each time that a request to get a SEP file produces a not
found in cache memory result.
SIPFoundCount
This counter represents the number of SIP files that were successfully found in
the cache. This counter gets updated each time that a SIP file is found in the cache
SIPNotFoundCount
This counter represents the number of SIP files that were not found in the cache.
This counter gets updated each time that a request to get a SIP file produces a not
found in cache memory result.
SoftkeyChangeNotifications
This counter represents the number of times that the TFTP server received
database change notification to create, update, or delete configuration files for
softkeys.
UnitChangeNotifications
This counter represents the number of times that the TFTP server received
database change notification to create, update, or delete gateway-related
configuration files.
Cisco Transcode Device
The Cisco Transcode Device object provides information about registered Cisco transcoding devices.
Table 5-39 contains information on Cisco transcoder device counters.
Table 5-39
Cisco Transcode Device
Counters
Counter Description
OutOfResources
This counter represents the total number of times that an attempt was made to
allocate a transcoder resource from a transcoder device and failed; for example,
because all resources were already in use.
ResourceActive
This counter represents the number of transcoder resources that are currently in
use (active) for a transcoder device.
Each transcoder resource uses two streams.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
5-50
OL-20105-01
Chapter 5
Cisco Unified Real-Time Monitoring Tool Tracing, PerfMon Counters, and Alerts
Performance Monitoring in RTMT
Table 5-39
Cisco Transcode Device (continued)
Counters
Counter Description
ResourceAvailable
This counter represents the total number of resources that are not active and are
still available to be used now for a transcoder device.
Each transcoder resource uses two streams.
ResourceTotal
This counter represents the total number of transcoder resources that a transcoder
device provided. This counter equals the sum of the ResourceActive and
ResourceAvailable counters.
Cisco Video Conference Bridge
The Cisco Video Conference Bridge object provides information about registered Cisco video
conference bridge devices. Table 5-40 contains information on Cisco video conference bridge device
counters.
Table 5-40
Cisco Video Conference Bridge
Counters
Counter Description
ConferencesActive
This counter represents the total number of video conferences that are currently
active (in use) on a video conference bridge device. The system specifies a
conference as active when the first call connects to the bridge.
ConferencesAvailable
This counter represents the number of video conferences that are not active and
are still available on a video conference device.
ConferencesCompleted
This counter represents the total number of video conferences that have been
allocated and released on a video conference device. A conference starts when the
first call connects to the bridge. The conference completes when the last call
disconnects from the bridge.
ConferencesTotal
This counter represents the total number of video conferences that are configured
for a video conference device.
OutOfConferences
This counter represents the total number of times that an attempt was made to
initiate a video conference from a video conference device and failed because the
device already had the maximum number of active conferences that is allowed (as
specified by the TotalConferences counter).
OutOfResources
This counter represents the total number of times that an attempt was made to
allocate a conference resource from a video conference device and failed, for
example, because all resources were already in use.
ResourceActive
This counter represents the total number of resources that are currently active (in
use) on a video conference bridge device. One resource gets used per participant.
ResourceAvailable
This counter represents the total number of resources that are not active and are
still available on a device to handle additional participants for a video conference
bridge device.
ResourceTotal
This counter represents the total number of resources that are configured on a
video conference bridge device. One resource gets used per participant.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
5-51
Chapter 5
Cisco Unified Real-Time Monitoring Tool Tracing, PerfMon Counters, and Alerts
Performance Monitoring in RTMT
Cisco Web Dialer
The Cisco Web Dialer object provides information about the Cisco Web Dialer application and the
Redirector servlet. Table 5-41 contains information on the Cisco Web Dialer counters.
Table 5-41
Cisco Web Dialer
Counters
Counter Description
CallsCompleted
This counter represents the number of Make Call and End Call requests that the
Cisco Web Dialer application successfully completed.
CallsFailed
This counter represents the number of Make Call and End Call requests that were
unsuccessful.
RedirectorSessionsHandled
This counter represents the total number of HTTP sessions that the Redirector
servlet handled since the last service startup.
RedirectorSessionsInProgress
This counter represents the number of HTTP sessions that are currently being
serviced by the Redirector servlet.
RequestsCompleted
This counter represents the number of Make Call and End Call requests that the
Web Dialer servlet successfully completed.
RequestsFailed
This counter represents the number of Make Call and End Call requests that
failed.
SessionsHandled
This counter represents the total number of CTI sessions that the Cisco
Web Dialer servlet handled since the last service startup.
SessionsInProgress
This counter represents the number of CTI sessions that the Cisco Web Dialer
servlet is currently servicing.
Cisco WSM Connector
The WSM object provides information on WSMConnectors that are configured on Cisco Unified
Communications Manager. Each WSMConnector represents a physical Motorola WSM device.
Table 5-42 contains information on the Cisco WSM Connector counters.
Table 5-42
Cisco WSM Connector
Counters
Counter Description
CallsActive
This counter represents the number of calls that are currently active (in use) on
the WSMConnector device.
CallsAttempted
This counter represents the number of calls that have been attempted on the
WSMConnector device, including both successful and unsuccessful call attempts.
CallsCompleted
This counter represents the number of calls that are connected (a voice path was
established) through the WSMConnector device. The counter increments when
the call terminates.
CallsInProgress
This counter represents the number of calls that are currently in progress on the
WSMConnector device. This includes all active calls. When the number of
CallsInProgress equals the number of CallsActive, this indicates that all calls are
connected.
DMMSRegistered
This counter represents the number of DMMS subscribers that are registered to
the WSM.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
5-52
OL-20105-01
Chapter 5
Cisco Unified Real-Time Monitoring Tool Tracing, PerfMon Counters, and Alerts
Performance Monitoring in RTMT
PerfMon Objects and Counters for System
This section provides information on Cisco Unified Communications Manager System PerfMon objects
and counters.
Cisco Tomcat Connector
The Tomcat Hypertext Transport Protocol (HTTP)/HTTP Secure (HTTPS) Connector object provides
information about Tomcat connectors. A Tomcat HTTP connector represents an endpoint that receives
requests and sends responses. The connector handles HTTP/HTTPS requests and sends HTTP/HTTPS
responses that occur when Cisco Unified Communications Manager related web pages are accessed. The
Secure Socket Layer (SSL) status of the URLs for web applications provides the basis for the instance
name for each Tomcat HTTP Connector. For example, https://<IP Address>:8443 for SSL or http://<IP
Address>:8080 for non-SSL. Table 5-43 contains information on the Tomcat HTTP connector counters.
Table 5-43
Cisco Tomcat Connector
Counters
Counter Description
Errors
This counter represents the total number of HTTP errors (for example, 401
Unauthorized) that the connector encountered. A Tomcat HTTP connector
represents an endpoint that receives requests and sends responses. The connector
handles HTTP/HTTPS requests and sends HTTP/HTTPS responses that occur
when Cisco Unified Communications Manager related windows are accessed.
The Secure Socket Layer (SSL) status of the URLs for the web application
provides basis for the instance name for each Tomcat HTTP connector. For
example, https://<IP Address>:8443 for SSL or http://<IP Address>:8080 for
non-SSL.
MBytesReceived
This counter represents the amount of data that the connector received. A Tomcat
HTTP connector represents an endpoint that receives requests and sends
responses. The connector handles HTTP/HTTPS requests and sends
HTTP/HTTPS responses that occur when Cisco Unified Communications
Manager related windows are accessed. The Secure Socket Layer (SSL) status of
the URLs for the web application provides basis for the instance name for each
Tomcat HTTP connector.For example, https://<IP Address>:8443 for SSL or
http://<IP Address>:8080 for non-SSL.
MBytesSent
This counter represents the amount of data that the connector sent. A Tomcat
HTTP connector represents an endpoint that receives requests and sends
responses. The connector handles HTTP/HTTPS requests and sends
HTTP/HTTPS responses that occur when Cisco Unified Communications
Manager related windows are accessed. The Secure Socket Layer (SSL) status of
the URLs for the web application provides basis for the instance name for each
Tomcat HTTP connector. For example, https://<IP Address>:8443 for SSL or
http://<IP Address>:8080 for non-SSL.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
5-53
Chapter 5
Cisco Unified Real-Time Monitoring Tool Tracing, PerfMon Counters, and Alerts
Performance Monitoring in RTMT
Table 5-43
Cisco Tomcat Connector (continued)
Counters
Counter Description
Requests
This counter represents the total number of request that the connector handled. A
Tomcat HTTP connector represents an endpoint that receives requests and sends
responses. The connector handles HTTP/HTTPS requests and sends
HTTP/HTTPS responses that occur when Cisco Unified Communications
Manager related windows are accessed. The Secure Socket Layer (SSL) status of
the URLs for the web application provides basis for the instance name for each
Tomcat HTTP connector. For example, https://<IP Address>:8443 for SSL or
http://<IP Address>:8080 for non-SSL.
ThreadsTotal
This counter represents the current total number of request processing threads,
including available and in-use threads, for the connector. A Tomcat HTTP
connector represents an endpoint that receives requests and sends responses. The
connector handles HTTP/HTTPS requests and sends HTTP/HTTPS responses
that occur when Cisco Unified Communications Manager related windows are
accessed. The Secure Socket Layer (SSL) status of the URLs for the web
application provides basis for the instance name for each Tomcat HTTP
connector. For example, https://<IP Address>:8443 for SSL or http://<IP
Address>:8080 for non-SSL.
ThreadsMax
This counter represents the maximum number of request processing threads for
the connector. Each incoming request on a Cisco Unified Communications
Manager related window requires a thread for the duration of that request. If more
simultaneous requests are received than the currently available request processing
threads can handle, additional threads will get created up to the configured
maximum shown in this counter. If still more simultaneous requests are received,
they accumulate within the server socket that the connector created, up to an
internally specified maximum number. Any further simultaneous requests will
receive connection refused messages until resources are available to process
them.
A Tomcat HTTP connector represents an endpoint that receives requests and
sends responses. The connector handles HTTP/HTTPS requests and sends
HTTP/HTTPS responses that occur when Cisco Unified Communications
Manager related windows are accessed. The Secure Socket Layer (SSL) status of
the URLs for the web application provides basis for the instance name for each
Tomcat HTTP connector. For example, https://<IP Address>:8443 for SSL or
http://<IP Address>:8080 for non-SSL.
ThreadsBusy
This counter represents the current number of busy/in-use request processing
threads for the connector. A Tomcat Connector represents an endpoint that
receives requests and sends responses. The connector handles HTTP/HTTPS
requests and sends HTTP/HTTPS responses that occur when web pages that are
related to Cisco Unified Communications Manager are accessed. The Secure
Sockets Layer (SSL) status of the URLs for the web application provides the basis
for the instance name for each Tomcat connector. For example, https://<IP
Address>:8443 for SSL or http://<IP Address>:8080 for non-SSL.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
5-54
OL-20105-01
Chapter 5
Cisco Unified Real-Time Monitoring Tool Tracing, PerfMon Counters, and Alerts
Performance Monitoring in RTMT
Cisco Tomcat JVM
The Cisco Tomcat Java Virtual Machine (JVM) object provides information about the Tomcat JVM,
which represents, among other things, a pool of common resource memory that Cisco Unified
Communications Manager related web applications such as Cisco Unified Communications Manager
Administration, Cisco Unified Serviceability, Cisco Unity Connection Administration, and more use.
Table 5-44 contains information on the Tomcat JVM counters.
Table 5-44
Tomcat JVM
Counters
Counter Description
KBytesMemoryFree
This counter represents the amount of free dynamic memory block (heap memory)
in the Tomcat Java Virtual Machine. The dynamic memory block stores all
objects that Tomcat and its web applications, such as Cisco Unified
Communications Manager Administration, Cisco Unified Serviceability, and
Cisco Unity Connection create. When the amount of free dynamic memory is low,
more memory gets automatically allocated, and total memory size (represented by
the KbytesMemoryTotal counter) increases but only up to the maximum
(represented by the KbytesMemoryMax counter). You can determine the amount
of memory in use by subtracting KBytesMemoryFree from KbytesMemoryTotal.
KBytesMemoryMax
This counter represents the amount of free dynamic memory block (heap memory)
in the Tomcat Java Virtual Machine. The dynamic memory block stores all
objects that Tomcat and its web applications, such as Cisco Unified
Communications Manager Administration, Cisco Unified Serviceability, and
Cisco Unity Connection Administration, create.
KBytesMemoryTotal
This counter represents the current total dynamic memory block size, including
free and in-use memory, of Tomcat Java Virtual Machine. The dynamic memory
block stores all objects that Tomcat and its web applications, such as Cisco
Unified Communications Manager Administration, Cisco Unified Serviceability,
and Cisco Unity Connection Administration, create.
Cisco Tomcat Web Application
The Cisco Tomcat Web Application object provides information about how to run Cisco Unified
Communications Manager web applications. The URLs for the web application provide basis for the
instance name for each Tomcat Web Application. For example, Cisco Unified Communications Manager
Administration (https://<IP Address>:8443/ccmadmin) gets identified by ccmadmin, Cisco Unified
Serviceability gets identified by ccmservice, Cisco Unified Communications Manager User Options gets
identified by ccmuser, Cisco Unity Connection Administration (https://<IP Address>:8443/cuadmin)
gets identified by cuadmin, and URLs that do not have an extension, such as https://<IP Address>:8443
or http://<IP Address>:8080), get identified by _root. Table 5-45 contains information on the Tomcat
Web Application counters.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
5-55
Chapter 5
Cisco Unified Real-Time Monitoring Tool Tracing, PerfMon Counters, and Alerts
Performance Monitoring in RTMT
Table 5-45
Tomcat Web Application
Counters
Counter Description
Errors
This counter represents the total number of HTTP errors (for example, 401
Unauthorized) that a Cisco Unified Communications Manager related web
application encountered. The URLs for the web application provide the basis
instance name for each Tomcat Web Application. For example, Cisco Unified
Communications Manager Administration (https://<IP
Address>:8443/ccmadmin) gets identified by ccmadmin, Cisco Unified
Serviceability gets identified by ccmservice, Cisco Unified Communications
Manager User Options gets identified by ccmuser, Cisco Unity Connection
Administration (https://<IP Address>:8443/cuadmin) gets identified by cuadmin,
and URLs that do not have an extension, such as https://<IP Address>:8443 or
http://<IP Address>:8080), get identified by _root.
Requests
This counter represents the total number of requests that the web application
handles. Each time that a web application is accessed, its Requests counter
increments accordingly. The URLs for the web application provide the basis
instance name for each Tomcat Web Application. For example, Cisco Unified
Communications Manager Administration (https://<IP
Address>:8443/ccmadmin) gets identified by ccmadmin, Cisco Unified
Serviceability gets identified by ccmservice, Cisco Unified Communications
Manager User Options gets identified by ccmuser, Cisco Unity Connection
Administration (https://<IP Address>:8443/cuadmin) gets identified by cuadmin,
and URLs that do not have an extension, such as https://<IP Address>:8443 or
http://<IP Address>:8080), get identified by _root.
SessionsActive
This counter represents the number of sessions that the web application currently
has active (in use). The URLs for the web application provide the basis instance
name for each Tomcat Web Application. For example, Cisco Unified
Communications Manager Administration (https://<IP
Address>:8443/ccmadmin) gets identified by ccmadmin, Cisco Unified
Serviceability gets identified by ccmservice, Cisco Unified Communications
Manager User Options gets identified by ccmuser, Cisco Unity Connection
Administration (https://<IP Address>:8443/cuadmin) gets identified by cuadmin,
and URLs that do not have an extension, such as https://<IP Address>:8443 or
http://<IP Address>:8080), get identified by _root.
Database Change Notification Client
The Database Change Notification Client object provides information on change notification clients.
Table 5-46 contains information on the Database Change Notification Client counters.
Table 5-46
Database Change Notification Client
Counters
Counter Descriptions
MessagesProcessed
This counter represents the number of database change notifications that have
been processed. This counter refreshes every 15 seconds.
MessagesProcessing
This counter represents the number of change notification messages that are
currently being processed or are waiting to be processed in the change notification
queue for this client. This counter refreshes every 15 seconds.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
5-56
OL-20105-01
Chapter 5
Cisco Unified Real-Time Monitoring Tool Tracing, PerfMon Counters, and Alerts
Performance Monitoring in RTMT
Table 5-46
Database Change Notification Client (continued)
Counters
Counter Descriptions
QueueHeadPointer
This counter represents the head pointer to the change notification queue. The
head pointer acts as the starting point in the change notification queue. To
determine the number of notifications in the queue, subtract the head pointer value
from the tail pointer value. By default, this counter refreshes every 15 seconds.
QueueMax
This counter represents the largest number of change notification messages that
will be processed for this client. This counter remains cumulative since the last
restart of the Cisco Database Layer Monitor service.
QueueTailPointer
This counter represents the tail pointer to the change notification queue. The tail
pointer represents the ending point in the change notification queue. To determine
the number of notifications in the queue, subtract the head pointer value from the
tail pointer value. By default, this counter refreshes every 15 seconds
TablesSubscribed
This counter represents the number of tables in which this client has subscribed.
Database Change Notification Server
The Database Change Notification Server object provides information on different
change-notification-related statistics. Table 5-47 contains information on the Database Change
Notification Server counters.
Table 5-47
Database Change Notification Server
Counter
Counter Descriptions
Clients
This counter represents the number of change notification clients
(services/servlets) that have subscribed for change notification.
Queue Delay
This counter provides the number of seconds that the change notification process
has messages to process but is not processing them. This condition is true if:
•
Either Change Notification Requests Queued in Database
(QueuedRequestsInDB) and Change Notification Requests Queued in
Memory (QueuedRequestsInMemory) are non-zero, or
•
The Latest Change Notification Messages Processed count is not changing.
This condition gets checked every 15 seconds.
QueuedRequestsInDB
This counter represents the number of change notification records that are in the
DBCNQueue (Database Change Notification Queue) table via direct TCP/IP
connection (not queued in shared memory). This counter refreshes every 15
seconds.
QueuedRequestsInMemory
This counter represents the number of change notification requests that are
queued in shared memory.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
5-57
Chapter 5
Cisco Unified Real-Time Monitoring Tool Tracing, PerfMon Counters, and Alerts
Performance Monitoring in RTMT
Database Change Notification Subscription
The Database Change Notification Subscription object displays the names of tables where the client will
receive Change Notifications.
The SubscribedTable object displays the table with the service or servlet that will receive change
notifications. Because the counter does not increment, this display occurs for informational purposes
only.
Database Local DSN
The Database Local Data Source Name (DSN) object and LocalDSN counter provide the DSN
information for the local machine. Table 5-48 contains information on the Database local DSN.
Table 5-48
Database Local Data Source Name
Counters
Counter Descriptions
CcmDbSpace_Used
This counter represents the amount of Ccm DbSpace that is being consumed
CcmtempDbSpace_Used
This counter represents the amount of Ccmtemp DbSpace that is being consumed.
CNDbSpace_Used
This counter represents the percentage of CN dbspace consumed.
LocalDSN
This counter represents the data source name (DSN) that is being referenced from
the local machine.
SharedMemory_Free
This counter represents total shared memory that is free.
SharedMemory_Used
This counter total shared memory that is used.
RootDbSpace_Used
This counter represents the amount of RootDbSpace that is being consumed.
DB User Host Information Counters
The DB User Host Information object provides information on DB User Host. The DB:User:Host
Instance object displays the number of connections that are present for each instance of DB:User:Host.
Enterprise Replication DBSpace Monitors
The enterprise replication DBSpace monitors object displays the usage of various ER DbSpaces.
Table 5-49 contains information on the enterprise replication DB monitors.
Table 5-49
Enterprise Replication DBSpace Monitors
Counters
Counter Descriptions
ERDbSpace_Used
This counter represents the amount of enterprise replication DbSpace that was
consumed.
ERSBDbSpace_Used
This counter represents the amount of ERDbSpace that was consumed.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
5-58
OL-20105-01
Chapter 5
Cisco Unified Real-Time Monitoring Tool Tracing, PerfMon Counters, and Alerts
Performance Monitoring in RTMT
Enterprise Replication Perfmon Counters
The Enterprise Replication Perfmon Counter object provides information on the various replication
counters. The ServerName:ReplicationQueueDepth counter displays the server name followed by the
replication queue depth.
IP
The IP object provides information on the IP statistics on your system. Table 5-50 contains information
on the IP counters.
Table 5-50
IP
Counters
Counter Descriptions
Frag Creates
This counter represents the number of IP datagrams fragments that have been
generated at this entity.
Frag Fails
This counter represents the number of IP datagrams that were discarded at this
entity because the datagrams could not be fragmented, such as datagrams where
the Do not Fragment flag was set.
Frag OKs
This counter represents the number of IP datagrams that were successfully
fragmented at this entity.
In Delivers
This counter represents the number of input datagrams that were delivered to IP
user protocols. This includes Internet Control Message Protocol (ICMP).
In Discards
This counter represents the number of discarded input IP datagrams when no
problems were encountered. Lack of buffer space provides one possible reason.
This counter does not include any datagrams that were discarded while they were
awaiting reassembly.
In HdrErrors
This counter represents the number of discarded input datagrams that had header
errors. This includes bad checksums, version number mismatch, other format
errors, time-to-live exceeded, and other errors that were discovered in processing
IP options.
In Receives
This counter represents the number of input datagrams that were received from all
network interfaces. This counter includes datagrams that were received with
errors
In UnknownProtos
This counter represents the number of locally addressed datagrams that were
received successfully but discarded because of an unknown or unsupported
protocol.
InOut Requests
This counter represents the number of incoming IP datagrams that were received
and the number of outgoing IP datagrams that were sent.
Out Discards
This counter represents the number of output IP datagrams that were not
transmitted and were discarded. Lack of buffer space provides one possible
reason.
Out Requests
This counter represents the total number of IP datagrams that local IP protocols,
including ICMP, supply to IP in requests transmission. This counter does not
include any datagrams that were counted in ForwDatagrams.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
5-59
Chapter 5
Cisco Unified Real-Time Monitoring Tool Tracing, PerfMon Counters, and Alerts
Performance Monitoring in RTMT
Table 5-50
IP (continued)
Counters
Counter Descriptions
Reasm Fails
This counter represents the number of IP reassembly failures that the IP
reassembly algorithm detected, including time outs, errors, and so on. This
counter does not represent the discarded IP fragments because some algorithms,
such as the algorithm in RFC 815, can lose track of the number of fragments
because it combines them as they are received.
Reasm OKs
This counter represents the number of IP datagrams that were successfully
reassembled.
Reasm Reqds
This counter represents the number of IP fragments that were received that
required reassembly at this entity.
Memory
The memory object provides information about the usage of physical memory and swap memory on the
server. Table 5-51 contains information on memory counters.
Table 5-51
Memory
Counters
Counter Descriptions
% Mem Used
This counter displays the system physical memory utilization as a percentage. The
value of this counter equals (Total KBytes - Free KBytes - Buffers KBytes Cached KBytes + Shared KBytes) / Total KBytes, which also corresponds to the
Used KBytes/Total KBytes.
% Page Usage
This counter represents the percentage of active pages.
% VM Used
This counter displays the system virtual memory utilization as a percentage. The
value of this counter equals (Total KBytes - Free KBytes - Buffers KBytes Cached KBytes + Shared KBytes + Used Swap KBytes) / (Total KBytes + Total
Swap KBytes), which also corresponds to Used VM KBytes/Total VM KBytes.
Buffers KBytes
This counter represents the capacity of buffers in your system in kilobytes.
Cached KBytes
This counter represents the amount of cached memory in kilobytes.
Free KBytes
This counter represents the total amount of memory that is available in your
system in kilobytes.
Free Swap KBytes
This counter represents the amount of free swap space that is available in your
system in kilobytes.
Faults Per Sec
This counter represents the number of page faults (both major and minor) that the
system made per second (post 2.5 kernels only). This does not necessarily
represent a count of page faults that generate I/O because some page faults can get
resolved without I/O.
Low Total
This counter represents the total low (non-paged) memory for kernel.
Low Free
This counter represents the total free low (non-paged) memory for kernel.
Major Faults Per Sec
This counter represents the number of major faults that the system has made per
second that have required loading a memory page from disk (post 2.5 kernels
only).
Pages
This counter represents the number of pages that the system paged in from the
disk plus the number of pages that the system paged out to the disk.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
5-60
OL-20105-01
Chapter 5
Cisco Unified Real-Time Monitoring Tool Tracing, PerfMon Counters, and Alerts
Performance Monitoring in RTMT
Table 5-51
Memory (continued)
Counters
Counter Descriptions
Pages Input
This counter represents the number of pages that the system paged in from the
disk.
Pages Input Per Sec
This counter represents the total number of kilobytes that the system paged in
from the disk per second.
Pages Output
This counter represents the number of pages that the system paged out to the disk.
Pages Output Per Sec
This counter represents the total number of kilobytes that the system paged out to
the disk per second.
Shared KBytes
This counter represents the amount of shared memory in your system in kilobytes.
Total KBytes
This counter represents the total amount of memory in your system in kilobytes.
Total Swap KBytes
This counter represents the total amount of swap space in your system in
kilobytes.
Total VM KBytes
This counter represents the total amount of system physical and memory and swap
space (Total Kbytes + Total Swap Kbytes) that is in use in your system in
kilobytes.
Used KBytes
This counter represents the amount of system physical memory that is in use in
kilobytes. The value of the Used KBytes counter equals Total KBytes minus Free
KBytes minus Buffers KBytes minus Cached KBytes plus Shared KBytes. In a
Linux environment, the Used KBytes value that displays in the top or free
command output equals the difference of Total KBytes and Free KBytes and also
includes the sum of Buffers KBytes and Cached KBytes.
Used Swap KBytes
This counter represents the amount of swap space that is in use on your system in
kilobytes.
Used VM KBytes
This counter represents the system physical memory and the amount of swap
space that is in use on your system in kilobytes. The value equals Total KBytes Free KBytes - Buffers KBytes - Cached KBytes + Shared KBytes + Used Swap
KBytes. This corresponds to Used Mem KBytes + Used Swap KBytes.
Network Interface
The network interface object provides information about the network interfaces on the system.
Table 5-52 contains information on network interface counters.
Table 5-52
Network Interface
Counters
Counter Descriptions
Rx Bytes
This counter represents the number of bytes, including framing characters, that
were received on the interface.
Rx Dropped
This counter represents the number of inbound packets that were chosen to be
discarded even though no errors had been detected. This prevents the packet from
being delivered to a higher layer protocol. Discarding packets to free up buffer
space provides one reason.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
5-61
Chapter 5
Cisco Unified Real-Time Monitoring Tool Tracing, PerfMon Counters, and Alerts
Performance Monitoring in RTMT
Table 5-52
Network Interface (continued)
Counters
Counter Descriptions
Rx Errors
This counter represents the number of inbound packets (packet-oriented
interfaces) and the number of inbound transmission units (character-oriented or
fixed-length interfaces) that contained errors that prevented them from being
deliverable to a higher layer protocol.
Rx Multicast
This counter represents the number of multicast packets that were received on this
interface.
Rx Packets
This counter represents the number of packets that this sublayer delivered to a
higher sublayer. This does not include the packets that were addressed to a
multicast or broadcast address at this sublayer.
Total Bytes
This counter represents the total number of received (Rx) bytes and transmitted
(Tx) bytes.
Total Packets
This counter represents the total number of Rx packets and Tx packets.
Tx Bytes
This counter represents the total number of octets, including framing characters,
that were transmitted out from the interface.
Tx Dropped
This counter represents the number of outbound packets that were chosen to be
discarded even though no errors were detected. This action prevents the packet
from being delivered to a higher layer protocol. Discarding a packet to free up
buffer space represents one reason.
Tx Errors
This counter represents the number of outbound packets (packet-oriented
interfaces) and the number of outbound transmission units (character-oriented or
fixed-length interfaces) that could not be transmitted because of errors.
Tx Packets
This counter represents the total number of packets that the higher level protocols
requested for transmission, including those that were discarded or not sent. This
does not include packets that were addressed to a multicast or broadcast address
at this sublayer.
Tx QueueLen
This counter represents the length of the output packet queue (in packets).
Number of Replicates Created and State of Replication
The Number of Replicates Created and State of Replication object provides real-time replication
information for the system. Table 5-53 contains information on replication counters.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
5-62
OL-20105-01
Chapter 5
Cisco Unified Real-Time Monitoring Tool Tracing, PerfMon Counters, and Alerts
Performance Monitoring in RTMT
Table 5-53
Number of Replicates Created and State of Replication
Counters
Counter Descriptions
Number of Replicates Created
This counter displays the number of replicates that were created by Informix for
the DB tables. This counter displays information during Replication Setup.
Replicate_State
This counter represents the state of replication. The following list provides
possible values:
•
0—Initializing. The counter equals 0 when the server is not defined or when
the server is defined but the template has not completed.
•
1—Replication setup script fired from this node. Cisco recommends that you
run utils dbreplication status on the CLI to determine the location and cause
of the failure.
•
2—Good Replication.
•
3—Bad Replication. A counter value of 3 indicates replication in the cluster
is bad. It does not mean that replication failed on a particular server in the
cluster. Cisco recommends that you run utils dbreplication status on the CLI
to determine the location and cause of the failure.
•
4—Replication setup did not succeed.
Partition
The partition object provides information about the file system and its usage in the system. Table 5-54
contains information on partition counters. Be aware that these counters are available for the spare
partition, if present.
Table 5-54
Partition
Counters
Counter Descriptions
% CPU Time
This counter represents the percentage of CPU time that is dedicated to handling
I/O requests that were issued to the disk. This counter is no longer valid when the
counter value equals -1.
% Used
This counter represents the percentage of disk space that is in use on this file
system.
% Wait in Read
Not Used. The Await Read Time counter replaces this counter. This counter is no
longer valid when the counter value equals -1.
% Wait in Write
Not Used. The Await Write Time counter replaces this counter.This counter is no
longer valid when the counter value equals -1.
Await Read Time
This counter represents the average time, measured in milliseconds, for Read
requests that are issued to the device to be served. This counter is no longer valid
when the counter value equals -1.
Await Time
This counter represents the average time, measured in milliseconds, for I/O
requests that were issued to the device to be served. This includes the time that
the requests spent in queue and the time that was spent servicing them.This
counter is no longer valid when the counter value equals -1.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
5-63
Chapter 5
Cisco Unified Real-Time Monitoring Tool Tracing, PerfMon Counters, and Alerts
Performance Monitoring in RTMT
Table 5-54
Partition (continued)
Counters
Counter Descriptions
Await Write Time
This counter represents the average time, measured in milliseconds, for write
requests that are issued to the device to be served. This counter is no longer valid
when the counter value equals -1.
Queue Length
This counter represents the average queue length for the requests that were issued
to the disk.This counter is no longer valid when the counter value equals -1.
Read Bytes Per Sec
This counter represents the amount of data in bytes per second that was read from
the disk.
Total Mbytes
This counter represents the amount of total disk space in megabytes that is on this
file system.
Used Mbytes
This counter represents the amount of disk space in megabytes that is in use on
this file system.
Write Bytes Per Sec
This counter represents the amount of data that was written to the disk in bytes
per second.
Process
The process object provides information about the processes that are running on the system. Table 5-55
contains information on process counters.
Table 5-55
Process
Counters
Counter Descriptions
% CPU Time
This counter, which is expressed as a percentage of total CPU time, represents the
tasks share of the elapsed CPU time since the last update.
% MemoryUsage
This counter represents the percentage of physical memory that a task is currently
using.
Data Stack Size
This counter represents the stack size for task memory status.
Nice
This counter represents the nice value of the task. A negative nice value indicates
that the process has a higher priority while a positive nice value indicates that the
process has a lower priority. If the nice value equals zero, do not adjust the
priority when you are determining the dispatchability of a task.
Page Fault Count
This counter represents the number of major page faults that a task encountered
that required the data to be loaded into memory.
PID
This counter displays the task-unique process ID. The ID periodically wraps, but
the value will never equal zero.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
5-64
OL-20105-01
Chapter 5
Cisco Unified Real-Time Monitoring Tool Tracing, PerfMon Counters, and Alerts
Performance Monitoring in RTMT
Table 5-55
Process (continued)
Counters
Counter Descriptions
Process Status
This counter displays the process status:
•
0—Running
•
1—Sleeping
•
2—Uninterruptible disk sleep
•
3—Zombie
•
4—Stopped
•
5— Paging
•
6—Unknown
Shared Memory Size
This counter displays the amount of shared memory (KB) that a task is using.
Other processes could potentially share the same memory.
STime
This counter displays the system time (STime), measured in jiffies, that this
process has scheduled in kernel mode. A jiffy corresponds to a unit of CPU time
and gets used as a base of measurement. One second comprises 100 jiffies.
Thread Count
This counter displays the number of threads that are currently grouped with a task.
A negative value (-1) indicates that this counter is currently not available. This
happens when thread statistics (which includes all performance counters in the
Thread object as well as the Thread Count counter in the Process object) are
turned off because the system total processes and threads exceeded the default
threshold value.
Total CPU Time Used
This counter displays the total CPU time in jiffies that the task used in user mode
and kernel mode since the start of the task. A jiffy corresponds to a unit of CPU
time and gets used as a base of measurement. One second comprises 100 jiffies.
UTime
This counter displays the time, measured in jiffies, that a task has scheduled in
user mode.
VmData
This counter displays the virtual memory usage of the heap for the task in
kilobytes (KB).
VmRSS
This counter displays the virtual memory (Vm) resident set size (RSS) that is
currently in physical memory in kilobytes (KB). This includes the code, data, and
stack.
VmSize
This counter displays the total virtual memory usage for a task in kilobytes (KB).
It includes all code, data, shared libraries, and pages that have been swapped out:
Virtual Image = swapped size + resident size.
Wchan
This counter displays the channel (system call) in which the process is waiting.
Processor
The processor object provides information on different processor time usage in percentages. Table 5-56
contains information on processor counters.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
5-65
Chapter 5
Cisco Unified Real-Time Monitoring Tool Tracing, PerfMon Counters, and Alerts
Performance Monitoring in RTMT
Table 5-56
Processor
Counters
Counter Descriptions
% CPU Time
This counter displays the processors share of the elapsed CPU time, excluding
idle time, since the last update. This share gets expressed as a percentage of total
CPU time.
Idle Percentage
This counter displays the percentage of time that the processor is in the idle state
and did not have an outstanding disk I/O request.
IOwait Percentage
This counter represents the percentage of time that the processor is in the idle state
while the system had an outstanding disk I/O request.
Irq Percentage
This counter represents the percentage of time that the processor spends executing
the interrupt request that is assigned to devices, including the time that the
processor spends sending a signal to the computer.
Nice Percentage
This counter displays the percentage of time that the processor spends executing
at the user level with nice priority.
Softirq Percentage
This counter represents the percentage of time that the processor spends executing
the soft IRQ and deferring task switching to get better CPU performance.
System Percentage
This counter displays the percentage of time that the processor is executing
processes in system (kernel) level.
User Percentage
This counter displays the percentage of time that the processor is executing
normal processes in user (application) level.
System
The System object provides information on file descriptors on your system. Table 5-57 contains
information on system counters.
Table 5-57
System
Counters
Counter Descriptions
Allocated FDs
This counter represents the total number of allocated file descriptors.
Being Used FDs
This counter represents the number of file descriptors that are currently in use in
the system.
Freed FDs
This counter represents the total number of allocated file descriptors on the
system that are freed.
Max FDs
This counter represents the maximum number of file descriptors that are allowed
on the system.
Total CPU Time
This counter represents the total time in jiffies that the system has been up and
running.
Total Processes
This counter represents the total number of processes on the system.
Total Threads
This counter represents the total number of threads on the system.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
5-66
OL-20105-01
Chapter 5
Cisco Unified Real-Time Monitoring Tool Tracing, PerfMon Counters, and Alerts
Performance Monitoring in RTMT
TCP
The TCP object provides information on the TCP statistics on your system. Table 5-58 contains
information on the TCP counters.
Table 5-58
TCP
Counters
Counter Description
Active Opens
This counter displays the number of times that the TCP connections made a direct
transition to the SYN-SENT state from the CLOSED state.
Attempt Fails
This counter displays the number of times that the TCP connections have made a
direct transition to the CLOSED state from either the SYN-RCVD state or the
SYN-RCVD state, plus the number of times TCP connections have made a direct
transition to the LISTEN state from the SYS-RCVD state.
Curr Estab
This counter displays the number of TCP connections where the current state is
either ESTABLISHED or CLOSE- WAIT.
Estab Resets
This counter displays the number of times that the TCP connections have made a
direct transition to the CLOSED state from either the ESTABLISHED state or the
CLOSE-WAIT state.
In Segs
This counter displays the total number of segments that were received, including
those received in error. This count only includes segments that are received on
currently established connections.
InOut Segs
This counter displays the total number of segments that were sent and the total
number of segments that were received.
Out Segs
This counter displays the total number of segments that were sent. This count only
includes segments that are sent on currently established connections, but excludes
retransmitted octets.
Passive Opens
This counter displays the number of times that TCP connections have made a
direct transition to the SYN-RCVD state from the LISTEN state.
RetransSegs
This counter displays the total number of segments that were retransmitted
because the segment contains one or more previously transmitted octets.
Thread
The Thread object provides a list of running threads on your system. Table 5-59 contains information on
the Thread counters.
Table 5-59
Thread
Counters
Counter Description
% CPU Time
This counter displays the thread share of the elapsed CPU time since the last
update. This counter expresses the share as a percentage of the total CPU time.
PID
This counter displays the threads leader process ID.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
5-67
Chapter 5
Cisco Unified Real-Time Monitoring Tool Tracing, PerfMon Counters, and Alerts
Performance Monitoring in RTMT
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
5-68
OL-20105-01
CH A P T E R
6
Cisco Unified Serviceability Alarms and
CiscoLog Messages
This chapter describes the Cisco Unified Serviceability alarms and error messages and CiscoLog
message format. Network alarms tracked by Cisco Unified Serviceability for Cisco Unified
Communications Manager generate the error messages.
Note
A History table lists Cisco Unified Serviceability error messages that have been added, changed, or
removed beginning in Cisco Unified Communications Manager Release 7.0(1).
This chapter contains the following sections:
•
Cisco Unified Serviceability Alarms and CiscoLog Messages, page 6-2
•
Preconfigured System Alarm Notifications, page 6-19
•
Preconfigured CallManager Alarm Notifications, page 6-31
•
Emergency-Level Alarms, page 6-45
•
Alert-Level Alarms, page 6-54
•
Critical-Level Alarms, page 6-72
•
Error-Level Alarms, page 6-85
•
Warning-Level Alarms, page 6-186
•
Notice-Level Alarms, page 6-280
•
Informational-Level Alarms, page 6-297
•
Debug-Level Alarms, page 6-374
•
Obsolete Alarms in Cisco Unified Communications Manager Release 8.0(1), page 6-375
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
6-1
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Cisco Unified Serviceability Alarms and CiscoLog Messages
Cisco Unified Serviceability Alarms and CiscoLog Messages
Cisco Unified Serviceability alarms provide information on runtime status and the state of the system,
so you can troubleshoot problems that are associated with your system. The alarm or error message
information includes the application name, machine name, and recommended action and other critical
information to help you troubleshoot.
You configure the alarm interface to send alarm information to multiple locations, and each location can
have its own alarm event level (from debug to emergency). You can direct alarms to the Syslog Viewer
(local syslog), SNMP traps, Syslog file (remote syslog), SDI trace log file, SDL trace log file (for Cisco
Unified CM and CTIManager services only), or to all destinations.
You use the Trace and Log Central option in the Cisco Unified Real-Time Monitoring Tool (RTMT) to
collect alarms that get sent to an SDI or SDL trace log file. To view the alarm information sent to the
local syslog, use the SysLog Viewer in RTMT.
CiscoLog Format
CiscoLog, a specification for unified logging in Cisco software applications, gets used in the Cisco
Unified RTMT. It defines the message format when messages are logged into file or by using the syslog
protocol. The output that is provided by Cisco software applications gets used for auditing,
fault-management, and troubleshooting of the services that are provided by these applications.
Be aware that CiscoLog message format is compatible with one of the message formats that is produced
by Cisco IOS Release 12.3 by using the syslog protocol when Cisco IOS Software is configured with the
following commands:
Note
•
service sequence-numbers—A default sequence number that is produced by Cisco IOS. An
additional sequence number can also be enabled with this command. This command forces sequence
numbers to be shown in terminal output, but results in two sequence numbers in the syslog output.
CiscoLog standardizes on a format with just one sequence number. Thus, the compliant Cisco IOS
Software configuration occurs when the second number is disabled by using the no service
sequence-numbers command.
•
logging origin-id hostname—The CiscoLog HOST field remains consistent with that produced by
the Cisco IOS Release 12.3 when configured with this command. This command does not get
documented in the Cisco IOS Software documentation but is available in Cisco IOS Release 12.3.
CiscoLog stays compatible with the results that Cisco IOS Software produces in this field.
•
service timestamps log datetime localtime msec show-timezone year—The CiscoLog
TIMESTAMP field remains consistent with the timestamp format produced by Cisco IOS Release
12.3 when configured with this command.
CiscoLog uses the same field delimiters as Cisco IOS Software Release 12.3.
The following topics are described in this section:
•
Log File and Syslog Outputs, page 6-3
•
Standard Syslog Server Implementations, page 6-4
•
Clock Synchronization, page 6-4
•
Multipart Messages, page 6-4
•
CiscoLog Message Format, page 6-5
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
6-2
OL-20105-01
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Cisco Unified Serviceability Alarms and CiscoLog Messages
•
Internationalization, page 6-18
•
Versioning, page 6-18
Log File and Syslog Outputs
When CiscoLog messages are written directly into a log file by an application, each message is on a
separate line. The line separator should be a standard line separator used on a given platform. On
Windows, the line separator must be the sequence of carriage return and line feed characters (ASCII
decimal values 13 and 10; often designated as “\r\n” in programming languages). On Solaris and Linux,
the line separator is a single line feed character (ASCII decimal value 10 and in programming languages
typically “\n”). Two line separators must never appear one after another, for example, you cannot have
“\r\n\r\n” on Windows, but “\r\n” is fine because these two characters are a single line separator.
In practical terms, this means that applications should be careful when appending data to an existing log.
In some cases an initial line break is required and in others not. For example, if application crashes when
writing CiscoLog message, but before it wrote a line break to file, then when the application starts up,
it should print an initial line break before printing the next message. An application can determine if an
initial line break is necessary during startup by checking the last character sequence in the log file that
will be used for appending.
CiscoLog message format is identical for messages written directly to a log file or those generated by
using the syslog protocol with two minor exceptions. When CiscoLog messages are written directly into
to a file they must be appended with line separators. When CiscoLog messages are sent by using the
syslog protocol then the syslog RFC 3164 protocol PRI header must be prepended to each CiscoLog
message.
The syslog PRI field encodes syslog message severity and syslog facility. The severity encoded in the
PRI field must match the value of the CiscoLog SEVERITY field. Any syslog facility can be used
regardless of the content of the message. Typically, a given application is configured to send all its
messages to a single syslog facility (usually RFC 3164 facilities local 0 through local 7). Refer to RFC
3164 for details about how to encode the PRI field. Below is an example of a CiscoLog message with
the syslog protocol PRI field <165> which encodes the severity level of notice (5) and facility value
local4.
<165>11: host.cisco.com: Jun 13 2003 12:11:52.454 UTC: %BACC-5-CONFIG: Configured from
console by vty0 [10.0.0.0]
Messages as shown in the example above can be sent to UDP port 514 if using RFC 3164 logging
mechanism.
Syslog RFC 3164 provides additional guidelines for message content formatting beyond the PRI field.
However, RFC 3164 is purely information (not on IETF standards track) and actually allows messages
in any format to be generated to the syslog UDP port 514 (see section 4.2 of RFC 3164). The RFC
provides observation about content structure often encountered in implementations, but does not dictate
or recommend its use. CiscoLog format does not follow these observations due to practical limitations
of the format defined in the RFC. For example, the time stamp is specified without a year, time zone or
milliseconds while the hostname can only be provided without the domain name.
CiscoLog messages must remain unaltered when relayed. The PRI field is not part of a CiscoLog
message, but rather a protocol header. It can be stripped or replaced if necessary. Additional headers
or footers can be added to and stripped from the CiscoLog message for transport purposes.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
6-3
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Cisco Unified Serviceability Alarms and CiscoLog Messages
Standard Syslog Server Implementations
Standard syslog server implementations can be configured to forward received log messages or to store
the messages locally. Most syslog server implementations strip the PRI field from the received
messages and prefix additional information to the message before storage. This additional information
typically includes two extra fields: the local time stamp and the host identifier (IP or DNS name) of the
server, which generated or relayed the message.
The following example of a CiscoLog message shown the output after being logged by the Solaris 8
syslog server:
Jun 13 12:12:09 host.cisco.com 11: host.cisco.com: Jun 13 2003 12:11:52.454 UTC:
%BACC-5-CONFIG: Configured from console by vty0 [10.0.0.0]
There is no standard that defines how syslog servers must store messages. Implementations vary greatly.
CiscoLog only addresses the format in which messages are sent to the syslog server, not how they are
stored by the server that receives them. Specifically, the format and presence of any additional header
fields in syslog log files is outside of the scope of this specification.
Note
The CiscoLog specification recommends that the syslog server implementation store CiscoLog
messages in exactly the same format as it receives them only stripping the PRI field and without any
extra headers. This would provide an identical storage format for CiscoLog messages written directly
to the log file by an application or logged through syslog protocol.
Clock Synchronization
It is important that the clocks of all hosts of a distributed application be synchronized with one
authoritative clock. This can be accomplished by using protocols such as NTP. Clock synchronization
is recommended because the time stamps in log messages are required in order to be able to re-construct
the correct sequence of events based on messages originating from multiple processes or multiple hosts.
Clock drifts can still occur, but ongoing synchronization should reduce this issue to a minimum.
Multipart Messages
ASCII control characters are not permitted in any of the fields of CiscoLog message format. Control
characters include characters such as line feed, form feed and carriage returns. This means that multi-line
messages are not allowed unless to allow:
•
Better presentation (for example, a stack trace)
•
Fragmenting messages which exceed 800 octet limit
Multi-part CiscoLog message consists of a set of multiple valid CiscoLog messages. Messages are
grouped together using a special tag key “part”, which identifies the part number and the sequence
number of the original message.
All messages which are part of a multi-part message must have a “part” tag as well as identical values
for the HOST, TIMESTAMP, APPNAME, SEVERITY fields and other TAG values. However, the
sequence number of each message has to be incremented as usual.
Example of a multi-part message:
16: host.cisco.com: Jun 13 2003 23:11:52.468 UTC: %BACC-3-UNEXPECTED_EXCEPTION:
%[pname.orig=rdu][part=16.1/3]: Null pointer exception
17: host.cisco.com: Jun 13 2003 23:11:52.468 UTC: %BACC-3-UNEXPECTED_EXCEPTION:
%[pname.orig=rdu][part=16.2/3]:
com.cisco.Source:123
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
6-4
OL-20105-01
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Cisco Unified Serviceability Alarms and CiscoLog Messages
18: host.cisco.com: Jun 13 2003 23:11:52.468 UTC: %BACC-3-UNEXPECTED_EXCEPTION:
%[pname.orig=rdu][part=16.3/3]:
com.cisco.Main:1112
In this example, the first message has part number 1 and its sequence number, 16, embedded in the part
tag. Subsequent messages embed the sequence number of the first message part and provide their own
part number. The trailing “/3” in each part tag value means that the message consists of three parts.
CiscoLog Message Format
The CiscoLog message format follows:
<SEQNUM>: <HOST>: <TIMESTAMP>: %<HEADER>: [TAGS: ]<MESSAGE>
All fields gets separated by a single colon character (ASCII decimal value 58) and a single space
character (ASCII decimal value 32). The HEADER field is also preceded by a percent character (ASCII
decimal value 37).
The TIMESTAMP, HEADER and TAGS fields have internal formatting. Below is a complete format
with details for TIMESTAMP and HEADER fields:
<SEQNUM>: <HOST>: [ACCURACY]<MONTH> <DAY> <YEAR>
<HOUR>:<MINUTES>:<SECONDS>.<MILLISECONDS> <TIMEZONE>:
%<APPNAME>-<SEVERITY>-<MSGNAME>: [TAGS: ]<MESSAGE>
All fields except for ACCURACY and TAGS are required.
The following example shows a CiscoLog message:
11: host.cisco.com: Jun 13 2003 23:11:52.454 UTC: %BACC-5-CONFIG: Configured from
console by vty0 [10.10.10.0]
The following example shows the optional TAGS and ACCURACY fields in a CiscoLog message:
12: host.cisco.com: *Jun 13 2003 23:11:52.454 UTC: %BACC-4-BAD_REQUEST:
%[pname.orig=rdu][comp=parser][mac=1,6,aa:bb:cc:11:22:33][txn=mytxn123]: Bad request
received from device [1,6,aa:bb:cc:11:22:33]. Header missing.
The values of the specific fields in the above example are as follows:
•
SEQNUM – “12”
•
HOST – “host.cisco.com”
•
ACCURACY – “*”
•
MONTH - “Jun”
•
DAY – “13”
•
YEAR – “2003”
•
HOUR – “23”
•
MINUTES – “11”
•
SECONDS – “52”
•
MILLISECONDS – “454”
•
TIMEZONE – “UTC”
•
APPNAME – “BACC”
•
SEVERITY – “4”
•
MSGNAME – “BAD_REQUEST”
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
6-5
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Cisco Unified Serviceability Alarms and CiscoLog Messages
•
TAGS – “%[pname.orig=rdu][comp=parser][mac=1,6,aa:bb:cc:11:22:33][txn=mytxn123]”
•
MESSAGE – “Bad request received from device [1,6,aa:bb:cc:11:22:33]. Header missing.”
Message Length Limit
The maximum length of a complete CiscoLog message must not exceed 800 octets.The term octet is used
for 8-bit data type instead of byte because byte is not 8 bits on some platforms. The words “character”
and “octet” are not synonyms in parts of this specification because in places were internationalization is
supported a single character may need to be represented with multiple octets. This limit is dictated by
RFC 3164. The limit of 1024 octets reserves some extra space for syslog forwarding headers and/or
fields that may be formalized in later specifications.
When CiscoLog message includes the syslog PRI field, then the combined CiscoLog messages and PRI
field length must not exceed 805 octets.
SEQNUM Field
The SEQNUM field contains a sequence number, which can be used to order messages in the time
sequence order when multiple messages are produced with the same time stamp by the same process.
The sequence number begins at 0 for the first message fired by a process since the last startup and is
incremented by 1 for every subsequent logging message originated by the same process. Every time the
application process is restarted, its sequence number is reset back to 0. The sequence number of each
message must be in the exact order in which messages are fired/logged by the application.
This may mean that in a multi-threaded application there must be some kind of synchronization to ensure
this and another consideration may have to be made for Java applications that have some native (C) code
in JNI. If log messages originate in both native and Java parts of the same process, the implementation
needs to be synchronized to use the same sequence number counter across the two process parts and to
fire messages in the order of sequence numbers.
The maximum numeric value of the SEQNUM field is 4,294,967,295 at which point the counter must
be reset back to 0. The maximum positive value of a 32-bit unsigned integer as used in Cisco IOS. Cisco
IOS uses ulong for the sequence number counter and ulong is a 32-bit unsigned integer on all current
Cisco IOS platforms including mips, ppc, and 68k.
Sequence numbers are process specific. If application architecture has multiple application processes
on a single host, which share a single logging daemon, the sequence number still has to be
process-specific. Thus, each process has it is own sequence number which it increments.
Sequence numbers also help detect lost messages. Therefore, sequence numbers cannot be skipped. In
other words, a message must be produced for every number in the sequence order.
HOST Field
The HOST field identifies the system originating the message with a Fully Qualified DNS Name
(FQDN), hostname or an IPv4/IPv6 address. If the FQDN or hostname is known, one of the two has to
appear in the HOST field. It is expected that in most deployments the hostname is sufficient. However,
if a deployment spans multiple domains, then using FQDNs is recommend. If an application is expected
to be deployed in both scenarios, then it is recommended that the application default to the FQDNs, but
make it a configurable option.
If neither FQDN nor hostname can be identified, then the IP address of the host must be used. If the IP
address cannot be identified, then a constant “0.0.0.0” (without quotes) must appear in place of the
HOST field.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
6-6
OL-20105-01
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Cisco Unified Serviceability Alarms and CiscoLog Messages
Note
With regards to the compliance with Cisco IOS format. Cisco IOS Release 12.3 supports producing
hostname, IP address, or any user-defined string in the HOST field. If it is configured to provide a
hostname and it is not set on the device, it will use a string such as “Router.”
The length of the HOST field must not exceed 255 octets.
FQDN & Hostname
If multiple FQDNs or hostnames are known for a given system, applications must use the primary
FQDN/hostname or an arbitrary one if no primary is designated. However, applications must use the
same HOST field value until some relevant configuration change takes place. In other words, the
FQDN/hostname value should not arbitrarily change from message to message if system is configured
with multiple FQDNs/hostnames.
Only printable US ASCII characters (those with decimal values 32-126) and foreign language characters
are allowed in the HOST field when encoding an FQDN or hostname. The appropriate character set and
encoding for HOST should be compliant with RFC 1123 / STD-3.
The acceptable character set per these standards includes US ASCII letters, numbers, dash and dot
separator characters (although not starting or ending with a dash). The reason that these are only
recommendations of adhering to these standards is that, in practice, many hosts do not follow the
convention and use characters such as underscore in the hostname. However, the HOST field cannot
contain a character sequence of “: “ (colon and space) as this sequence is used as a field delimiter in the
CiscoLog format.
Foreign language characters outside of the printable US ASCII characters have to be encoded according
to internationalization rules.
Use of non-printable (control) ASCII characters is not allowed in the HOST field. Control characters
include characters with ASCII decimal values 0-31 and 127. If an application provides a
CiscoLog-compliant library with a host string, which includes one or more control characters, the
logging library must do the following. If the horizontal tab character (ASCII decimal value 9) is
encountered, it must be replaced with one or more space characters (ASCII decimal value 32). Eight
spaces per tab are recommended because this is a convention on most Unix and Windows platforms.
Other control characters must each be replaced with a question mark character (ASCII decimal value
63).
While DNS is letter-case agnostic, CiscoLog places an additional recommendation of using only
lower-case characters in the HOST field for ease of readability. The use of the trailing dot at the end of
the FQDN is optional. The following examples are valid HOST fields:
•
host123
•
host-123
•
host123.cisco.com
•
host123.cisco.com.
IP Addresses
The IP address value used in the HOST field can be either an IPv4 or IPv6 address. If a device has
multiple IP addresses, the primary IP address of the device must be used regardless of the interface
through which the CiscoLog message is sent to syslog server. If no primary IP address is designated, a
fixed/static IP address is preferred to a dynamically assigned one. If multiple static IP addresses exist,
any one can be used, but it must be used consistently in all messages until a relevant configuration event
occurs on the system.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
6-7
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Cisco Unified Serviceability Alarms and CiscoLog Messages
•
IPv4 Address—IPv4 address should be represented in dot notation “x.x.x.x”, where x is a decimal
value from 0 to 255 encoded as ASCII text. If an IP address is unknown, “0.0.0.0” (without quotes)
must be used as a place holder. Examples of valid IPv4 addresses are 0.0.0.0 and 212.1.122.11.
Below is an example of a message with an IPv4 address in the HOST field:
11: 212.1.122.11: Jun 13 2003 23:11:52.454 UTC: %BACC-3-BAD_REQUEST: Bad request
received from device [1.2.3.4]. Missing header.
Below is an example of a CiscoLog message when FQDN, hostname or IP are all unknown:
11: 0.0.0.0: Jun 13 2003 23:11:52.454 UTC: %BACC-3-BAD_REQUEST: Bad request received
from device [1.2.3.4]. Missing header.
•
IPv6 Address—IPv6 address representation must follow conventions outlined in RFC 3513,
sections 2.2.1, 2.2.2 and 2.2.3. Specifically, all three conventions are supported. Both lower-case
and upper-case letters can be used in the IPv6 address, but the lower-case letters are recommended.
If an IP address is unknown, “0.0.0.0” (without quotes) should be used as the IP address. Examples
of valid IPv6 addresses:
– 1080:0:0:800:ba98:3210:11aa:12dd (full notation)
– 1080::800:ba98:3210:11aa:12dd (use of “::” convention)
– 0:0:0:0:0:0:13.1.68.3 (last 4 octets expanded as in IPv4)
– 0.0.0.0 (unknown FQDN, hostname and IP address )
Below is an example of a message with an IPv6 address in the HOST field:
11: 1080:0:0:800:ba98:3210:11aa:12dd: Jun 13 2003 23:11:52.454 UTC:
%BACC-3-BAD_REQUEST: Bad request received from device [1.2.3.4]. Missing header.
TIMESTAMP Field
The TIMESTAMP field provides date with year, time with milliseconds and a time zone identifier in the
following format:
[ACCURACY]<MONTH> <DAY> <YEAR>
<HOUR>:<MINUTES>:<SECONDS>.<MILLISECONDS> <TIMEZONE>
Below are several examples of valid time stamps:
Jun 13 2003 23:11:52.454 UTC
Jun 3 2003 23:11:52.454 UTC
Jun 22 2003 05:11:52.525 -0300
*Feb 14 2003 01:02:03.005 EST
In some cases, it is possible that a device may not have the knowledge of the date and/or time due to
hardware or software limitations. In such circumstances, the following string must be produced in the
TIMESTAMP field: “--- 00 0000 00:00:00.000 ---“. Below is an example of a CiscoLog message from
a device which has no knowledge of date and/or time:
11: host.domain.com: --- 00 0000 00:00:00.000 ---: %BACC-3-BAD_REQUEST: Bad request
received from device [1.2.3.4]. Missing header.
Devices which are not aware of their clock, may choose to provide an uptime as a relative measure of
time. If device is capable of providing uptime, it is recommended that does so as a substitute for
unavailable time stamp. If uptime is provided it must be provided with a standard uptime tag as outlined
in the CiscoLog Standard Tags specification.
Table 6-1 details each field specification.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
6-8
OL-20105-01
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Cisco Unified Serviceability Alarms and CiscoLog Messages
Table 6-1
TIMESTAMP Field Specifications
Field
Specification
ACCURACY
This is an optional field. If present, it must be either a single asterisk
character (ASCII decimal value 42), or a single dot character (ASCII
decimal value 46). No separator character is used after this field. This
field indicates the status of clock synchronization.
Cisco IOS uses a special convention for time prefixes to indicate the
accuracy of the time stamp. If dot character appears before the date, it
means that the local time was synchronized at some point via NTP, but
currently no NTP servers are available. The asterisk character in front
of the date means that the local time is not authoritative, i.e. NTP servers
are not setup.
CiscoLog supports the use of this convention, but does not require it. If
an application is integrated with NTP client software, and knows that its
time is out of sync, then it can optionally prefix the message with
asterisk character. However, because applications may choose not to use
this scheme, the lack of “.” or “*” in CiscoLog messages should not be
interpreted to mean that the local time is synchronized.
MONTH
Must be one of the following three-character month designations
followed by a single space (ASCII decimal value 32) as a delimiter
character: Jan, Feb, Mar, Apr, May, Jun, Jul, Sep, Oct, Nov or Dec.
DAY
Must consist of two characters. If day is a single digit, it must be prefixed
with a single space character. The acceptable range of values is from 1
to 31. The day value must be followed by a single space as a delimiter
character.
YEAR
Must consist of exactly 4 digit characters followed by a space as a
delimiter character.
HOUR
Must consist of exactly two number characters. The hour value is based
on a 24-hour clock. Values range from 00 to 23. If hour value is a single
digit, it must be prefixed with a single zero character. The hour value
must be followed by a single colon as a delimiter character.
MINUTES
Must consist of exactly two number characters. Values range from 00 to
59. If minute value is a single digit, it must be prefixed with a single
zero character. The minutes value must be followed by a single colon as
a delimiter character
SECONDS
Must consist of exactly two number characters. Values range from 00 to
59. If seconds value is a single digit, it must be prefixed with a single
zero character. The seconds value must be followed by a period as a
delimiter character.
MILLISECONDS
Must consist of exactly 3 digit characters. Values range from 000 to 999.
If milliseconds value is less then 3 digits in length it must be prefixed
with extra zeros to make it a 3-character field. The milliseconds value
is followed by a space as a delimiter character.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
6-9
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Cisco Unified Serviceability Alarms and CiscoLog Messages
Table 6-1
TIMESTAMP Field Specifications (continued)
Field
Specification
TIMEZONE
Must consist of at least one, but no more than 7 characters in the
following ASCII decimal value range: 32-126. The value must not
include a combination of colon-space-percent of characters – “: %“
(ASCII decimal values 58, 32, 37) – as this character combination is
reserved as a field delimiter that follows the time stamp.
There is no standard set of acronyms for time zones1. A list of common
time zone acronyms and corresponding time offsets from UTC is
provided in the UTC specification.
Uppercase letters are recommended for time zone acronym values.
CiscoLog recommends the use of time offset instead of time zone
identifier in this field. The offset, if provided, must follow the following
format “-hhmm” or “+hhmm” to indicate hour and minute offset from
UTC.
In this format time zone field must always contain 5 characters, with the
last 4 characters being constrained to numbers only. Unlike a textual
time zone identifier, this format provides a specific time offset from
universal standard time.
Cisco IOS Release 12.3 supports any 7-character string as a time zone
identifier, so it can be configured in a way which is compatible with this
recommendation. Multiple messages may and sometimes must be
produced with exactly the same time stamp. This can happen naturally
on a non-preemptive operating system or may need to be deliberately
induced as in the case of multi-part messages. Sequence numbers then
become helpful for establishing message order. Time stamp should
always be accurate to the millisecond unless it can significantly hinder
performance of the application.
In either case, applications must always provide the administrator with
an option to output messages with exact time stamp in milliseconds. If
an application uses time stamp with accuracy to the second (instead of a
millisecond), it must put the last known milliseconds value or 000 in
place of the milliseconds. Whatever convention is chosen by the
application, it should be followed consistently.
1.
Neither Cisco IOS nor CiscoLog define a standard set of time zone acronyms because there is no single established standard.
HEADER Field
The HEADER field has the following format:
<APPNAME>-<SEVERITY>-<MSGNAME>
A single dash character (ASCII decimal value 45) serves a separator for the three fields.
APPNAME Field
The APPNAME field in the HEADER defines the name of the application producing the message. Cisco
IOS uses FACILITY in place of APPNAME that names the logical component producing the message.
Cisco IOS 12.3 defines approximately 287 facilities for 3950 messages. Example of some easily
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
6-10
OL-20105-01
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Cisco Unified Serviceability Alarms and CiscoLog Messages
recognizable facilities: AAAA, SYS, ATM, BGP, CRYPTO, ETHERNET, FTPSERVER, CONFIG_I,
IP, ISDN, RADIUS, SNMP, SYS, TCP, UBR7200, X25. A complete list of defined facilities is available
in Cisco IOS documentation at http://.
Outside of the Cisco IOS, there can be multiple applications on the same host originating log messages.
Therefore, it is necessary that APPNAME field identify the specific application. Additional source
identifiers are available in the HOST field as well as various standard TAGS field values (pname, pid,
comp, etc).
The APPNAME field must consist of at least two uppercase letters or digits and may include underscore
characters. More precisely, the acceptable character set is limited to characters with the following
ASCII decimal values: 48-57 (numbers), 65-90 (upper-case letters) and 95 (underscore).
The length of the APPNAME field must not exceed 24 characters.
Application names cannot conflict with other Cisco software applications and with Cisco IOS facilities.
On the Solaris platform, it is recommended (not required) that the application name values used in the
APPNAME field be consistent with those used for the application installation package name, only in
upper case and without the CSCO prefix. For example, an application registering as “CSCObacc” on
Solaris should use “BACC” as the value of the APPNAME field.
Some applications may choose to specify a version as part of the APPNAME field. This is acceptable
and may be useful in cases where the meaning of certain messages is re-defined from one release to
another. For example, an APPNAME value could be “BACC_2_5” for BACC version 2.5. The use the
version within an application name is optional and may be introduced by applications in any release.
SEVERITY Field
The SEVERITY field is a numeric value from 0 to 7, providing eight different severities. The severities
defined below match Cisco IOS severity levels. They are also standard syslog severities.
It is important that messages use the correct severity. An error in a certain component may be severe as
far as the component is concerned, but if the overall application handles it gracefully, then the severity
may be lower for the application as a whole. Table 6-2 lists guidelines that should be followed in
determining the severity of a message.
Table 6-2
Name and Severity Level and Descriptions in Error Messages
Name/
Severity Level
Description
Emergency (0)
System or service is unusable. Examples:
Alert (1)
•
Service repeatedly fails to startup
•
System ran out of disk space while disk space is essential for this system
to operate
•
Application requires root privileges to run but does not have them
Action must be taken immediately. Examples:
•
Application is about to run out of licenses
•
Application is about to run out of disk space
•
Too many unauthorized access attempts detected
•
Denial of service attack is detected
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
6-11
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Cisco Unified Serviceability Alarms and CiscoLog Messages
Table 6-2
Name/
Severity Level
Critical (2)
Error (3)
Warning (4)
Notice (5)
Name and Severity Level and Descriptions in Error Messages (continued)
Description
Critical condition. Similar to alert, but not necessarily requiring an
immediate action. Examples:
•
Received an invalid authentication request
•
Service crashed due to an error that could not be handled, like an out of
memory condition, (provided it has a watchdog process to restart it, it
does not necessarily require immediate action)
•
Unexpected code error that could not be handled
An error condition, which does not necessarily impact the ability of the
service to continue to function. Examples:
•
Problem parsing/processing a particular request which does not prevent
the application from handling other requests
•
Unexpected, but handled code exception
A warning about some bad condition, which is not necessarily an error.
Examples:
•
Lost network connection to some resource
•
Timed out waiting for a response
Notifications about system-level conditions, which are not error conditions.
Examples:
•
Configuration was updated (not audit level information)
•
Process has started
•
Process is shutting down gracefully on request
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
6-12
OL-20105-01
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Cisco Unified Serviceability Alarms and CiscoLog Messages
Table 6-2
Name and Severity Level and Descriptions in Error Messages (continued)
Name/
Severity Level
Informational (6)
Debug (7)
Description
Informational messages are distinguished from notification in that they
provide information for internal flows of the application or per-request
information instead of system-wide notifications. Informational messages
are used for troubleshooting by users who are familiar with the basic flows
of the application. Examples:
•
Request received
•
Request was parsed successfully
•
Request being processed
•
Response sent back
•
Acknowledgement received
•
Detailed audit information
Debugging messages are similar to informational messages, but provide
more detail and require the user to have better knowledge of system internal
processing. These messages are typically reserved for very advanced users
or Cisco technical support. Examples:
•
Complete details for a request packet
•
Internal state machine state changes
•
Internal profiling statistics
•
Internal events
If an application uses a default severity level to determine which messages should be logged, then it is
recommended that this level be set at 5 (notice). This ensures that all messages of severity 5 or higher
are logged by default.
MSGNAME Field
The MSGNAME field of the HEADER uniquely identifies the message within the context of a given
APPNAME. A fixed severity and logical meaning is associated with a specific MSGNAME within a
specific APPNAME. In other words, the same message name cannot appear with different severity or a
completely different logical meaning for the same APPNAME value even if the message is originated
by a different process.
Message names are only unique within a given application (a given APPNAME value) unless the
message is one of the standard messages. Thus, applications interpreting CiscoLog messages should be
careful not to assume that a message with a given name has the same meaning for all applications that
may use this message name. Indeed, if the message is not one of the standard messages, it may have a
different severity and meaning in a different application.
The MSGNAME field must consist of at least two characters. Acceptable characters are limited to the
following ASCII decimal values: 48-57 (numbers), 65-90 (upper-case letters) and 95 (underscore).
While IOS allows lower-case letters as well, the vast majority of IOS messages use only the upper-case
letters. In order to be consistent with established conventions we opted to restrict the character set to
upper-case letters, numbers and underscore characters.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
6-13
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Cisco Unified Serviceability Alarms and CiscoLog Messages
Both numeric-only or alphanumeric message names are acceptable. However, per IOS convention, it is
recommended that a user-friendly alphanumeric label be preferred to a numeric-only label. For example,
“NO_MEMORY” message name is preferred to a “341234” identifier.
A special tag mid is defined in the CiscoLog Standard Tags specification for identifying a numeric id
corresponding to a message name. This tag can be used to provide a numeric message is in addition to
the MSGNAME. When this tag is used, a given MSGNAME must always correspond to a single
message id value. CiscoLog defines mid tag values for each standard message.
The length of the MSGNAME field must not exceed 30 characters, but most message names should be
more concise. MSGNAME value may not conflict with the names defined in this standard.
A separate message name must be defined for each logically different message. In other words, while
the message text for a given message name can vary by virtue of some substitutable parameters, logically
different messages must have different message names.
The following is an example of correct use of message name:
11: host.cisco.com: Jun 13 2003 23:11:52.454
%[pname.orig=rdu]: Server lost connection to
12: host.cisco.com: Jun 13 2003 23:11:52.458
%[pname.orig=rdu]: Server lost connection to
UTC:
host
UTC:
host
%BACC-4-CONNECTION_LOST:
[1.1.1.1]
%BACC-4-CONNECTION_LOST:
[2.2.2.2]
Notice that while the IP address of the host changes, it is still logically the same type of message. The
following is an example of an INCORRECT use of the message name:
15: host.cisco.com: Jun 13 2003 23:11:52.458 UTC: %BACC-4-CONNECTION:
%[pname.orig=rdu]: Server lost connection to host [2.2.2.2]
16: host.cisco.com: Jun 13 2003 23:11:52.468 UTC: %BACC-4-CONNECTION:
%[pname.orig=rdu]: Server re-established connection to host [2.2.2.2]
The use of a single message name for two different events in the above example is wrong and
unacceptable. This is referred to as a “catch-all” message name and they must be avoided. Another
extreme example is defining a message named “ERROR” and providing all error log messages under the
same message name. This defeats the purpose of having the message name field, which is to enable
external filtering of messages or easily trigger actions.
The only exception to the “no-catch-all” rule is when message cannot be identified ahead of time with
anything better than a generic description or the users will not benefit from distinguishing the various
subtypes of the message.
Although some applications may choose to do so, there is generally no need to define a separate message
name for all debugging messages because debugging messages are not intended for automated filtering
and action triggering based on message name. The sheer number of debugging messages and the highly
dynamic nature of what is produced in them makes it very hard to define separate messages.
This specification proposes establishing a mailing list that could be used by groups for consulting
purposes when in doubt about how to define certain messages. Currently, the mailing list alias used for
this purpose is “cmn-logging”.
TAGS Field
The TAGS field is optional in the message format. It provides a standard mechanism for applications
to provide structured content in the form of key-value pairs which can be used to categorize or filter a
set of messages externally.
Tags can be used to identify virtual logging channels. A set of messages flagged with the same tag can
later be grouped together. For example, an application may flag messages belonging to a particular
thread by supplying the corresponding tag. This would then allow filtering and viewing messages based
on threads.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
6-14
OL-20105-01
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Cisco Unified Serviceability Alarms and CiscoLog Messages
Virtual logging channels can also be established across multiple applications. For example, if all
applications could tag requests from a device with device id (mac, ip, etc), then it would be easy to filter
all messages related to that device even thought it communicates with multiple components.
Each application may define its own set of supported tags. A single tag consists of key and value pair
separated by the equals sign and surrounded by square bracket characters as in the following format:
[KEY=VALUE]. This is an example of a valid tag key-value pair [ip=123.23.22.22].
The TAGS field is prefixed with a percent character (ASCII decimal value 37) and ends with a sequence
of colon and space characters (ASCII decimal values 58 and 32). When multiple tags are assembled
together, no characters should appear between the tags as separators. The following example has a
complete CiscoLog message with four tags:
12: host.cisco.com: Jun 13 2003 23:11:52.454 UTC: %BACC-4-BAD_REQUEST:
%[pname.orig=rdu][comp=parser][mac=1,6,aa:bb:cc:11:22:33][txn=mytxn123]: Bad request
received from device [1,6,aa:bb:cc:11:22:33]. Missing header.
If TAGS field is missing, the percent character prefix and the trailing colon and space must be omitted.
Thus, when the TAGS field is missing, the HEADER and MESSAGE fields must be separated by just a
single colon and a space which follows the HEADER field. For example:
12: host.cisco.com: Jun 13 2003 23:11:52.454 UTC: %BACC-4-BAD_REQUEST: Bad request
received from device [1,6,aa:bb:cc:11:22:33]. Missing header.
Multiple tags with the same tag key can be provided in the same message. This essentially provides the
capability for handling multi-valued keys. Below is an example of a message produced from a device
which has two IP addresses where the application chose to provide both IP addresses in the TAGS field
as well as the process name:
12: host.cisco.com: Jun 13 2003 23:11:52.454 UTC: %BACC-4-BAD_REQUEST:
%[pname.orig=rdu][ip.orig=1.1.1.1][ip.orig=1.1.1.2]: Bad request received from device
[1,6,aa:bb:cc:11:22:33]. Missing header.
Any number of tags can be provided in a given message. The only limit is the overall length limit of the
CiscoLog message of 800 octets.
If multiple tags are present, it is recommended that they appear in the alphanumeric order of the keys.
This insures that tags are always produced in the same order. However, a different order may be chosen
by an application if the order of tags is used to communicate some semantic value.
Tag Keys
Tag key must contain at least one character. The characters are limited to ASCII characters with decimal
values 48-57 (numbers), 65-90 (upper-case letters), 95 (underscore), 97-122 (lower case letters). Use
of lower-case letters is recommended. There is no strict limit on tag key length, although a general
message limit of 800 octets applies and dictates that one should attempt to define short tag key names.
Tag Semantic Extensions
In some cases, a tag can have a standard value syntax, but different meaning depending on the content
in which it is used. Tag semantic extensions are used to differentiate the contextual meaning of tags.
The semantic extension tags are created by appending the tag key with a single dot character (ASCII
decimal value 46) and a text string consisting of characters from a proper character set.
For example, an “ip” tag defines syntax for an IP address representation, but no semantic value. An “ip”
tag found in a CiscoLog message generally means only that this IP address is somehow related to the
message. In some cases, such vague association is sufficient. However, sometimes, communicating
semantic value could be useful.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
6-15
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Cisco Unified Serviceability Alarms and CiscoLog Messages
A message may have two IP address tags associated with it, for example, from and to IP addresses. In
this case, using tags “ip.from” and “ip.to” would communicate both the syntax of the tags and some
semantic value. Another example, is a standard tag “ip.orig”, which specifies the IP address of the host
which originated the message. The following is an example of all three tags appearing together:
[ip.from=1.1.1.1][ip.to=2.2.2.2][ip.orig=123.12.111.1]
Multiple levels of semantic extension tags are allowed with each extension providing meaning that is
more specific. For example, tag key “ip.to.primary” is valid and could mean the primary IP address of
the destination host.
The semantic value is much harder to standardize than the syntax because there can an infinite number
of meanings for a given value depending on the context. Thus, it is anticipated that defining tag
semantics extensions will be largely application specific.
Tag Values
Tag values may contain zero or more characters. The empty (zero characters) value is interpreted as
unknown or undetermined value. The value must only include printable US ASCII characters (those in
the ASCII decimal value range 32-126) and foreign language characters
There is a restriction on the use of three characters: “[“, “]” and “\”. The bracket characters (ASCII
decimal values 91 & 93) must be escaped with a back slash character (ASCII decimal value 92) . This
helps to avoid confusion with the brackets that signify the start/end of the tag. Thus, when the tag value
needs to represent characters “[“ or “]”, a sequence of “\[“ or “\]” is used instead respectively. When
the escape character itself needs to be represented in the tag value, then instead of the “\” character a
sequence of “\\” is used.
Use of non-printable (control) ASCII characters is not allowed in the TAG value field. Control
characters include characters with ASCII decimal values 0-31 and 127. If application provides to a
CiscoLog-compliant library a tag value string, which includes one or more control characters, the
logging library must do the following. If the horizontal tab character (ASCII decimal value 9) is
encountered, it must be replaced with one or more space characters (ASCII decimal value 32). Eight
spaces per tab are recommended because this is a convention on most Unix and Windows platforms.
Other control characters must each be replaced with a question mark character (ASCII decimal value
63). Technically, we only need to require escaping a closing bracket. However, requiring escaping both
open and closing brackets simplifies parser code and provides for a more consistent display in raw form.
There is no strict limit on tag value length; although a general message length limit of 800 octets applies
and dictates that one must be conservative.
Tag Guidelines
The TAGS field is optional in the CiscoLog message format. Tags do not replace substitutable
parameters in the message body. Tags merely provide an additional way to identify and categorize
messages.
Since tags are optional, they can be enabled or disabled by the application/user as required. There is no
requirement for the same message to always be produced with the same set of tags. If the application
supports a given tag, it does not necessarily mean that it must always produce it. This can be
configurable. Indeed, it is recommended that applications provide the administrator with at least limited
control over which tags get produces.
Application developers have a choice as to what information to make available in the tags and what in
the message body. In some cases, the information may be duplicated between the two. This is
acceptable.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
6-16
OL-20105-01
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Cisco Unified Serviceability Alarms and CiscoLog Messages
The general guideline is to put all required information in the message body and make appropriate
information available via tags. In other words, the message should provide sufficient meaning even
when all tags are disabled. Tags merely provide additional useful information and a way to present it in
a standard, easily filtered, form.
The following are two valid examples of a message where both the message and the message tags contain
a MAC address. Example with tags disabled:
11: host.cisco.com: Jun 13 2003 23:11:52.454 UTC: %BACC-3-BAD_REQUEST: Bad request
received from device [1,6,aa:bb:11:22:33:aa]. Missing header.
In the above example, the MAC address appears as part of the message field – it is not a tag. In the
following example, the tags are enabled. Even though MAC address is duplicated between the tag and
the message, it is acceptable.
11: host.cisco.com: Jun 13 2003 23:11:52.454 UTC: %BACC-3-BAD_REQUEST:
%[mac=1,6,aa:bb:11:22:33:aa][tid=thread1][txn=mytxn123]: Bad request received from
device [1,6,aa:bb:11:22:33:aa]. Missing header.
Process Identification Tag
One of the standard tags, pname.orig, is used to identify the logical process name which originates the
message. Any application that seeks to provide originating process information must do so using the
“pname.orig” tag.
This tag is extremely valuable in addition to information in the APPNAME field because some
applications consist of multiple processes, each of which may originate logging messages. It is
recommended that any application which consists of multiple processes always provide the
“pname.orig” tag.
MESSAGE Field
The MESSAGE field provides a descriptive message about the logging event. This field may consist of
one or more characters. The character set is limited to printable US ASCII characters (ASCII decimal
values 32-126) and foreign language characters.
Use of non-printable (control) ASCII characters is not permitted in the MESSAGE field. Control
characters include characters with ASCII decimal values 0-31 and 127. If application provides a
CiscoLog-compliant library with message string, which includes one or more control characters, the
logging library must do the following. If the horizontal tab character (ASCII decimal value 9) is
encountered, it must be replaced with one or more space characters (ASCII decimal value 32). Eight
spaces per tab are recommended because this is a convention on most Unix and Windows platforms.
Other control characters must each be replaced with a question mark character (ASCII decimal value
63).
The maximum length of the MESSAGE field is constrained only by the maximum length of the entire
message. The maximum length of the CiscoLog message must not exceed 800 octets. Another practical
limitation is a potentially highly variable length of the TAGS field.
Message text may contain substitutable parameters, which provide necessary details about the message.
For example, the IP address in the following example is a substitutable parameter.
11: host.cisco.com: Jun 13 2003 23:11:52.454 UTC: %BACC-3-INVALID_REQUEST: Invalid
request received from device [1.22.111.222]. Missing header.
It is recommended (but not required) that substitutable parameters be surrounded by bracket characters
“[“ and “]” as in the above example. It is further recommended that the message text and values of
substitutable parameters do not include bracket characters. When it is not possible to avoid brackets
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
6-17
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Cisco Unified Serviceability Alarms and CiscoLog Messages
characters in the values of substitutable parameters, it is recommended that the value at least does not
include unbalances brackets (like an opening bracket without a closing one). When these
recommendations are followed, it would be possible to programmatically extract substitutable parameter
values out of a CiscoLog message. However, this recommendation is not a strict requirement.
Message text should be spell-checked. Editorial review is recommended. This includes all messages that
can be seen by the customers, even debugging messages.
If the first word of the message is an English word, the first letter should be capitalized. Single sentence
messages do not require a period at the end.
Internationalization
Foreign language characters are defined as characters with ASCII decimal values 0-126. Foreign
language characters are supported in the HOST field, the value part of the TAGS field and the
MESSAGE field.
Foreign language characters must be encoded using the Unicode standard UTF-8. UTF-8 provides
encoding for any language without requiring the application to know local encoding/decoding rules for
a particular language. In fact, the application encoding the message does not even need to know the
language of the message. UTF-8 can encode any Unicode character.
UTF-8 encodes US ASCII characters exactly as they would normally be encoded in a 7-bit ASCII
convention. This means that applications interpreting CiscoLog messages can assume that entire
messages are encoded in UTF-8. On the other hand, applications producing CiscoLog messages can
encode the entire message using US-ASCII 7-bit convention if they are known not to support foreign
languages in their products.
Since UTF-8 can encode characters in any language, it is possible to mix and match languages. For
example, it is anticipated that a one use-case would be the inclusion of just some parameters in foreign
language in an otherwise English message. For example, an English message about user authentication
could have a username in Japanese. Similarly, any number of languages can be combined in a CiscoLog
message.
In order to take advantage of messages, which include a foreign language, a log viewer capable of
interpreting UTF-8 would be necessary. Most likely, the log viewer would also require that the
appropriate language fonts be installed on a given system. In a US-ASCII only editor, the user will see
garbage for non-US-ASCII characters encoded in UTF-8, but should be able to see all US-ASCII text.
Internationalization support can be readily used with CiscoLog messages written to a local file. Syslog
RFC 3164, however, does not currently define foreign language support. Thus, in order to take
advantage of internationalization with a syslog server, one would need to use a server implementation,
which was tested to correctly relay or store all 8-bits of each octet unchanged. This would ensure that
UTF-8 encoded parts of the message retain all their information when foreign languages are used.
In UTF-8, a single character is encoded with one or more octets. The CiscoLog message length limit is
specified as 800 octets. Developers must be aware that with foreign languages, the 800-octet length limit
may mean fewer than 800 characters. When a message is split into a multi-part message using guidelines
provided in Multipart Messages, page 6-4, octets belonging to a single character must never be split into
separate lines.
Versioning
CiscoLog does not provide any versioning information in the message format. Extensions to the format
must be made within the restrictions of the format. CiscoLog message formats provides for extensions
by way of defining additional tags.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
6-18
OL-20105-01
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Preconfigured System Alarm Notifications
If applications require changes to existing messages, the value of APPNAME can redefine message
within the new space. For example, the application version can be appended to the application name as
BACC_2_5 for BACC 2.5.
Preconfigured System Alarm Notifications
The following list contains the preconfigured system alerts in RTMT. Refer to the Real-Time Monitoring
Tool Administration Guide for information on configuration.
•
AuthenticationFailed, page 6-19
•
CiscoDRFFailure, page 6-20
•
CoreDumpFileFound, page 6-20
•
CpuPegging, page 6-21
•
CriticalServiceDown, page 6-22
•
HardwareFailure, page 6-22
•
LogFileSearchStringFound, page 6-23
•
LogPartitionHighWaterMarkExceeded, page 6-23
•
LogPartitionLowWaterMarkExceeded, page 6-24
•
LowActivePartitionAvailableDiskSpace, page 6-25
•
LowAvailableVirtualMemory, page 6-25
•
LowInactivePartitionAvailableDiskSpace, page 6-26
•
LowSwapPartitionAvailableDiskSpace, page 6-26
•
ServerDown, page 6-27
•
SparePartitionHighWaterMarkExceeded, page 6-27
•
SparePartitionLowWaterMarkExceeded, page 6-28
•
SyslogSeverityMatchFound, page 6-29
•
SyslogStringMatchFound, page 6-30
•
SystemVersionMismatched, page 6-30
•
TotalProcessesAndThreadsExceededThreshold, page 6-31
AuthenticationFailed
Authentication validates the user ID and password that are submitted during log in. An alarm gets raised
when an invalid user ID and/or the password gets used.
Table 6-3
Default Configuration for the AuthenticationFailed RTMT Alert
Value
Default Configuration
Enable Alert
Selected
Severity
Critical
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
6-19
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Preconfigured System Alarm Notifications
Table 6-3
Default Configuration for the AuthenticationFailed RTMT Alert (continued)
Value
Default Configuration
Enable/Disable this alert
on the following servers
Enabled on listed servers
Threshold
Number of AuthenticationFailed events exceeds:
1 time in the last 1 minute
Duration
Trigger alert immediately
Frequency
Trigger alert on every poll
Schedule
24 hours daily
Enable e-mail
Selected
Trigger Alert Action
Default
CiscoDRFFailure
This alert occurs when the DRF backup or restore process encounters errors.
Table 6-4
Default Configuration for the CiscoDRFFailure RTMT Alert
Value
Default Configuration
Enable Alert
Selected
Severity
Critical
Enable/Disable this
alert on the
following servers
Enabled on listed servers
Threshold
Trigger alert when following condition met:
CiscoDRFFailure event generated
Duration
Trigger alert immediately
Frequency
Trigger alert on every poll
Schedule
24 hours daily
Enable E-mail
Selected
Trigger Alert Action Default
CoreDumpFileFound
This alert occurs when the CoreDumpFileFound event gets generated. This indicates that a core dump
file exists in the system.
Table 6-5
Default Configuration for the CoreDumpFileFound RTMT Alert
Value
Default Configuration
Enable Alert
Selected
Severity
Critical
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
6-20
OL-20105-01
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Preconfigured System Alarm Notifications
Table 6-5
Default Configuration for the CoreDumpFileFound RTMT Alert (continued)
Value
Default Configuration
Enable/Disable this
alert on the
following servers
Enabled on listed servers
Threshold
Trigger alert when following condition met:
CoreDumpFileFound event generated
Duration
Trigger alert immediately
Frequency
Trigger alert on every poll
Schedule
24 hours daily
Trace download
Parameters
Not Selected
Enable E-mail
Selected
Trigger Alert Action Default
CpuPegging
CPU usage gets monitored based on configured thresholds. If the usage goes above the configured
threshold, this alert gets generated.
Table 6-6
Default Configuration for the CpuPegging RTMT Alert
Value
Default Configuration
Enable Alert
Selected
Severity
Critical
Enable/Disable this
alert on the
following servers
Enabled on listed servers
Threshold
Trigger alert when following condition met:
99%
Duration
Trigger alert only when value remains constantly below or over threshold for 60
seconds
Frequency
Trigger up to 3 alerts within 30 minutes
Schedule
24 hours daily
Enable E-mail
Selected
Trigger Alert Action Default
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
6-21
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Preconfigured System Alarm Notifications
CriticalServiceDown
The CriticalServiceDown alert gets generated when the service status equals down (not for other states).
Table 6-7
Default Configuration for the CriticalServiceDown RTMT Alert
Value
Default Configuration
Enable Alert
Selected
Severity
Critical
Enable/Disable this
alert on the
following servers
Enabled on listed servers
Threshold
Trigger alert when following condition met:
Service status is DOWN
Duration
Trigger alert immediately
Frequency
Trigger alert on every poll
Schedule
24 hours daily
Trace download
Parameters
Enable Trace Download not selected
Enable E-mail
Selected
Trigger Alert Action Default
HardwareFailure
This alert occurs when a hardware failure event (disk drive failure, power supply failure, and others)
triggers.
Table 6-8
Default Configuration for the HardwareFailure RTMT Alert
Value
Default Configuration
Enable Alert
Selected
Severity
Critical
Enable/Disable this
alert on the
following servers
Enabled on listed servers
Threshold
Trigger alert when following condition met:
HardwareFailure event generated
Duration
Trigger alert immediately
Frequency
Trigger alert on every poll
Schedule
24 hours daily
Enable E-mail
Selected
Trigger Alert Action Default
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
6-22
OL-20105-01
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Preconfigured System Alarm Notifications
LogFileSearchStringFound
This alert occurs when the LogFileSearchStringFound event gets generated. This indicates that the
search string was found in the log file.
Table 6-9
Default Configuration for the LogFileSearchStringFound RTMT Alert
Value
Default Configuration
Enable Alert
Selected
Severity
Warning
Enable/Disable this
alert on the
following servers
Enabled on listed servers
Threshold
Trigger alert when following condition met:
LogFileSearchStringFound event generated
Duration
Trigger alert immediately
Frequency
Trigger alert on every poll
Schedule
24 hours daily
Enable E-mail
Selected
Trigger Alert Action Default
LogPartitionHighWaterMarkExceeded
This alert occurs when the percentage of used disk space in the log partition exceeds the configured high
water mark. When this alert gets generated, LPM deletes files in the log partition (down to low water
mark) to avoid running out of disk space.
Note
LPM may delete files that you want to keep. You should act immediately when you receive the
LogPartitionHighWaterMarkExceeded alert.
Table 6-10
Default Configuration for the LogPartitionHighWaterMarkExceeded
RTMT Alert
Value
Default Configuration
Enable Alert
Selected
Severity
Critical
Enable/Disable this
alert on the
following servers
Enabled on listed servers
Threshold
Trigger alert when following condition met:
Log Partition Used Disk Space Exceeds High Water Mark (95%)
Duration
Trigger alert immediately
Frequency
Trigger alert on every poll
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
6-23
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Preconfigured System Alarm Notifications
Table 6-10
Default Configuration for the LogPartitionHighWaterMarkExceeded
RTMT Alert (continued)
Value
Default Configuration
Schedule
24 hours daily
Enable E-mail
Selected
Trigger Alert Action Default
LogPartitionLowWaterMarkExceeded
This alert occurs when the LogPartitionLowWaterMarkExceeded event gets generated. This indicates
that the percentage of used disk space in the log partition exceeded the configured low water mark.
Note
Be aware that this alert is an early warning. The administrator should start freeing up disk space.
Using RTMT/TLC, you can collect trace/log files and delete them from the server. The
administrator should adjust the number of trace files that are kept to avoid hitting the low water
mark again.
Table 6-11
Default Configuration for the LogPartitionLowWaterMarkExceeded RTMT Alert
Value
Default Configuration
Enable Alert
Selected
Severity
Critical
Enable/Disable this
alert on the
following servers
Enabled on listed servers
Threshold
Trigger alert when following condition met:
Log Partition Used Disk Space Exceeds Low Water Mark (95%)
Duration
Trigger alert immediately
Frequency
Trigger alert on every poll
Schedule
24 hours daily
Enable E-mail
Selected
Trigger Alert Action Default
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
6-24
OL-20105-01
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Preconfigured System Alarm Notifications
LowActivePartitionAvailableDiskSpace
This alert occurs when the percentage of available disk space on the active partition is lower than the
configured value.
Table 6-12
Default Configuration for the LowActivePartitionAvailableDiskSpace
RTMT Alert
Value
Default Configuration
Enable Alert
Selected
Severity
Critical
Enable/Disable this
alert on the
following servers
Enabled on listed servers
Threshold
Trigger alert when following condition met:
Active Partition available diskspace below (4%)
Duration
Trigger alert immediately
Frequency
Trigger up to 3 alerts within 30 minutes
Schedule
24 hours daily
Enable E-mail
Selected
Trigger Alert Action Default
LowAvailableVirtualMemory
RTMT monitors virtual memory usage. When memory runs low, a LowAvailableVirtualMemory alert
gets generated.
Table 6-13
Default Configuration for the LowAvailableVirtualMemory RTMT Alert
Value
Default Configuration
Enable Alert
Selected
Severity
Critical
Enable/Disable this
alert on the
following servers
Enabled on listed servers
Threshold
Trigger alert when following condition met:
Available virtual memory below (30%)
Duration
Trigger alert immediately
Frequency
Trigger up to 3 alerts within 30 minutes
Schedule
24 hours daily
Enable E-mail
Selected
Trigger Alert Action Default
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
6-25
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Preconfigured System Alarm Notifications
LowInactivePartitionAvailableDiskSpace
This alert occurs when the percentage of available disk space of the inactive partition equals less than
the configured value.
Table 6-14
Default Configuration for the LowInactivePartitionAvailableDiskSpace RTMT Alert
Value
Default Configuration
Enable Alert
Selected
Severity
Critical
Enable/Disable this
alert on the
following servers
Enabled on listed servers
Threshold
Trigger alert when following condition met:
Inactive Partition available disk space below (4%)
Duration
Trigger alert immediately
Frequency
Trigger up to 3 alerts within 30 minutes
Schedule
24 hours daily
Enable E-mail
Selected
Trigger Alert Action Default
LowSwapPartitionAvailableDiskSpace
This alert indicates that the available disk space on the swap partition is low.
Note
The swap partition makes up part of virtual memory, so low available swap partition disk space
means low virtual memory as well.
Table 6-15
Default Configuration for the LowSwapPartitionAvailableDiskSpace
RTMT Alert
Value
Default Configuration
Enable Alert
Selected
Severity
Critical
Enable/Disable this
alert on the
following servers
Enabled on listed servers
Threshold
Trigger alert when following condition met:
Swap Partition available disk space below (105)
Duration
Trigger alert immediately
Frequency
Trigger up to 3 alerts within 30 minutes
Schedule
24 hours daily
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
6-26
OL-20105-01
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Preconfigured System Alarm Notifications
Table 6-15
Default Configuration for the LowSwapPartitionAvailableDiskSpace
RTMT Alert (continued)
Value
Default Configuration
Enable E-mail
Selected
Trigger Alert Action Default
ServerDown
This alert occurs when a remote node cannot be reached.
Note
Cisco Unified CM clusters only—The ServerDown alert gets generated when the currently
“active” AMC (primary AMC or the backup AMC, if the primary is not available) cannot reach
another server in a cluster. This alert identifies network connectivity issues in addition to a
server down condition.
Table 6-16
Default Configuration for the ServerDown RTMT Alert
Value
Default Configuration
Enable Alert
Selected
Severity
Critical
Enable/Disable this
alert on the
following servers
Enabled on listed servers
Threshold
Trigger alert when following condition met:
ServerDown occurred
Duration
Trigger alert immediately
Frequency
Trigger up to 1 alert within 60 minutes
Schedule
24 hours daily
Enable E-mail
Selected
Trigger Alert Action Default
SparePartitionHighWaterMarkExceeded
This alert occurs when the SparePartitionHighWaterMarkExceeded event gets generated. It indicates
that the percentage of used disk space in the spare partition exceeds the configured high water mark.
Some core file or log files are purged until the percentage of used disk space in the spare partition is
below the configured low water mark. Check if the configured high water mark for used disk space in
the spare partition is too low.
Cisco Log Partition Monitoring Tool (LPM) starts purging trace log files in the spare partition and keeps
deleting trace log files in the spare partition until spare partition disk usage is just below the low water
mark.
Name of the service generating this alarm is Cisco Log Partition Monitoring Tool.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
6-27
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Preconfigured System Alarm Notifications
Check if the configured high water mark for used disk space in the spare partition is too low; if it is,
change the high water mark setting to a higher value. Also examine each application trace log files under
spare partition and delete those trace log files that are too old or too big.
Note
Spare Partition is not used for Intercompany Media Engine server. So this alert will not be triggered for
Intercompany Media Engine.
Table 6-17
Default Configuration for the SparePartitionHighWaterMarkExceeded RTMT Alert
Value
Default Configuration
Enable Alert
Selected
Severity
Critical
Enable/Disable this
alert on the
following servers
Enabled on listed servers
Threshold
Trigger alert when following condition met:
Spare Partition Used Disk Space Exceeds High Water Mark (95%)
Duration
Trigger alert immediately
Frequency
Trigger alert on every poll
Schedule
24 hours daily
Enable E-mail
Selected
Trigger Alert Action Default
SparePartitionLowWaterMarkExceeded
This alert occurs when the SparePartitionLowWaterMarkExceeded event gets generated. It indicates that
the percentage of used disk space in the spare partition has exceeded the configured low water mark
threshold. There are files to be purged by Cisco Log Partition Monitoring Tool (LPM). If the spare
partition disk usage keeps increasing until it exceeded the configured high water mark, Cisco LPM starts
purging the trace log files in the spare partition. Cisco LPM sends the alarm periodically if the spare
partition disk usage has not changed.
Name of the service generating this alarm is Cisco Log Partition Monitoring Tool.
Check if the configured low water mark for used disk space in the spare partition is too low; if, change
the low/high water mark settings to the higher values. Also examine each application trace log files
under spare partition and clean up those trace log files that are too old or too big before the used disk
space exceeds the high water mark.
Note
Spare Partition is not used for Intercompany Media Engine server. So this alert will not be triggered for
Intercompany Media Engine.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
6-28
OL-20105-01
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Preconfigured System Alarm Notifications
Table 6-18
Default Configuration for the SparePartitionLowWaterMarkExceeded
RTMT Alert
Value
Default Configuration
Enable Alert
Selected
Severity
Critical
Enable/Disable this
alert on the
following servers
Enabled on listed servers
Threshold
Trigger alert when following condition met:
Spare Partition Used Disk Space Exceeds Low Water Mark (90%)
Duration
Trigger alert immediately
Frequency
Trigger alert on every poll
Schedule
24 hours daily
Enable E-mail
Selected
Trigger Alert Action Default
SyslogSeverityMatchFound
This alert occurs when the SyslogSeverityMatchFound event gets generated. This indicates that a syslog
message with the matching severity level exists.
Table 6-19
Default Configuration for the SyslogSeverityMatchFound RTMT Alert
Value
Default Configuration
Enable Alert
Selected
Severity
Critical
Enable/Disable this
alert on the
following servers
Enabled on listed servers
Threshold
Trigger alert when following condition met:
SyslogSeverityMatchFound event generated
Duration
Trigger alert immediately
Frequency
Trigger alert on every poll
Schedule
24 hours daily
Syslog Severity
Parameters
Critical
Enable E-mail
Selected
Trigger Alert Action Default
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
6-29
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Preconfigured System Alarm Notifications
SyslogStringMatchFound
This alert occurs when the SyslogStringMatchFound event gets generated. The alert indicates that a
syslog message with the matching search string exists.
Table 6-20
Default Configuration for the SyslogStringMatchFound RTMT Alert
Value
Default Configuration
Enable Alert
Selected
Severity
Critical
Enable/Disable this
alert on the
following servers
Enabled on listed servers
Threshold
Trigger alert when following condition met:
SyslogStringMatchFound event generated
Duration
Trigger alert immediately
Frequency
Trigger alert on every poll
Schedule
24 hours daily
Syslog Alert
Parameters
(Text box for search string)
Enable E-mail
Selected
Trigger Alert Action Default
SystemVersionMismatched
This alert occurs when a mismatch in system version exists.
Table 6-21
Default Configuration for the SystemVersionMismatched RTMT Alert
Value
Default Configuration
Enable Alert
Selected
Severity
Critical
Enable/Disable this
alert on the
following servers
Enabled on listed servers
Threshold
Trigger alert when following condition met:
SystemVersionMismatched occurred
Duration
Trigger alert immediately
Frequency
Trigger up to 1 alert within 60 minutes
Schedule
24 hours daily
Enable E-mail
Selected
Trigger Alert Action Default
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
6-30
OL-20105-01
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Preconfigured CallManager Alarm Notifications
TotalProcessesAndThreadsExceededThreshold
This alert occurs when the TotalProcessesAndThreadsExceededThreshold event gets generated. The
alert indicates that the current total number of processes and threads exceeds the maximum number of
tasks that are configured for the Cisco RIS Data Collector Service Parameter. This situation could
indicate that a process is leaking or that a process has thread leaking.
Table 6-22
Default Configuration for the TotalProcessesAndThreadsExceededThreshold RTMT
Alert
Value
Default Configuration
Enable Alert
Selected
Severity
Critical
Enable/Disable this
alert on the
following servers
Enabled on listed servers
Threshold
Trigger alert when following condition met:
TotalProcessesAndThreadsExceededThreshold event generated
Duration
Trigger alert immediately
Frequency
Trigger alert on every poll
Schedule
24 hours daily
Enable E-mail
Selected
Trigger Alert Action Default
Preconfigured CallManager Alarm Notifications
The following list comprises the preconfigured CallManager alerts in RTMT. Refer to the Real-Time
Monitoring Tool Administration Guide for information on configuration.
•
BeginThrottlingCallListBLFSubscriptions, page 6-32
•
CallProcessingNodeCpuPegging, page 6-32
•
CDRAgentSendFileFailed, page 6-33
•
CDRFileDeliveryFailed, page 6-34
•
CDRHighWaterMarkExceeded, page 6-34
•
CDRMaximumDiskSpaceExceeded, page 6-35
•
CodeYellow, page 6-35
•
DBChangeNotifyFailure, page 6-36
•
DBReplicationFailure, page 6-36
•
DDRBlockPrevention, page 6-37
•
DDRDown, page 6-38
•
ExcessiveVoiceQualityReports, page 6-38
•
LowCallManagerHeartbeatRate, page 6-39
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
6-31
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Preconfigured CallManager Alarm Notifications
•
LowCallManagerHeartbeatRate, page 6-39
•
LowTFTPServerHeartbeatRate, page 6-39
•
MaliciousCallTrace, page 6-40
•
MediaListExhausted, page 6-40
•
MgcpDChannelOutOfService, page 6-41
•
NumberOfRegisteredDevicesExceeded, page 6-41
•
NumberOfRegisteredGatewaysDecreased, page 6-42
•
NumberOfRegisteredGatewaysIncreased, page 6-42
•
NumberOfRegisteredMediaDevicesDecreased, page 6-42
•
NumberOfRegisteredMediaDevicesIncreased, page 6-43
•
NumberOfRegisteredPhonesDropped, page 6-43
•
RouteListExhausted, page 6-44
•
SDLLinkOutOfService, page 6-44
BeginThrottlingCallListBLFSubscriptions
This alert occurs when the BeginThrottlingCallListBLFSubscriptions event gets generated. This
indicates that the Cisco Unified Communications Manager initiated a throttling of the CallList BLF
Subscriptions to prevent a system overload.
Table 6-23
Default Configuration for the BeginThrottlingCallListBLFSubscriptions RTMT Alert
Value
Default Configuration
Enable Alert
Selected
Severity
Critical
Enable/Disable this
alert on the
following servers
Enabled on listed servers
Threshold
Trigger alert when following condition met:
BeginThrottlingCallListBLFSubscriptions event generated
Duration
Trigger alert immediately
Frequency
Trigger alert on every poll
Schedule
24 hours daily
Enable E-mail
Selected
Trigger Alert Action Default
CallProcessingNodeCpuPegging
This alert occurs when the percentage of CPU load on a call processing server exceeds the configured
percentage for the configured time.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
6-32
OL-20105-01
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Preconfigured CallManager Alarm Notifications
Note
If the administrator takes no action, high CPU pegging can lead to a crash, especially in
CallManager service. CoreDumpFound and CriticalServiceDown alerts might also get issued.
The CallProcessingNodeCpuPegging alert gives you time to work proactively to avoid a Cisco
Unified Communications Manager crash.
Table 6-24
Default Configuration for the CallProcessingNodeCpuPegging RTMT Alert
Value
Default Configuration
Enable Alert
Selected
Severity
Critical
Enable/Disable this
alert on the
following servers
Enabled on listed servers
Threshold
Trigger alert when following condition met:
Processor load over (90%)
Duration
Trigger alert only when value constantly below or over threshold for 60 seconds
Frequency
Trigger up to 3 alerts within 30 minutes
Schedule
24 hours daily
Enable E-mail
Selected
Trigger Alert Action Default
CDRAgentSendFileFailed
This alert gets raised when the CDR Agent cannot send CDR files from a Cisco Unified Communications
Manager node to a CDR repository node within the Cisco Unified Communications Manager cluster.
Table 6-25
Default Configuration for the CDRAgentSendFileFailed RTMT Alert
Value
Default Configuration
Enable Alert
Selected
Severity
Critical
Enable/Disable this
alert on the
following servers
Enabled on listed servers
Threshold
Trigger alert when following condition met:
CDRAgentSendFileFailed event generated
Duration
Trigger alert immediately
Frequency
Trigger alert on every poll
Schedule
24 hours daily
Enable E-mail
Selected
Trigger Alert Action Default
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
6-33
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Preconfigured CallManager Alarm Notifications
CDRFileDeliveryFailed
This alert gets raised when(s) FTP delivery of CDR files to the outside billing server fails.
(
Table 6-26
Default Configuration for the CDRFileDeliveryFailed RTMT Alert
Value
Default Configuration
Enable Alert
Selected
Severity
Critical
Enable/Disable this
alert on the
following servers
Enabled on listed servers
Threshold
Trigger alert when following condition met:
CDRFileDeliveryFailed event generated
Duration
Trigger alert immediately
Frequency
Trigger alert on every poll
Schedule
24 hours daily
Enable E-mail
Selected
Trigger Alert Action Default
CDRHighWaterMarkExceeded
This alert gets raised when the high water mark for CDR files gets exceeded. It also indicates that some
successfully delivered CDR files got deleted.
Table 6-27
Default Configuration for the CDRHighWaterMarkExceeded RTMT Alert
Value
Default Configuration
Enable Alert
Selected
Severity
Critical
Enable/Disable this
alert on the
following servers
Enabled on listed servers
Threshold
Trigger alert when following condition met:
CDRHighWaterMarkExceeded event generated
Duration
Trigger alert immediately
Frequency
Trigger alert on every poll
Schedule
24 hours daily
Enable E-mail
Selected
Trigger Alert Action Default
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
6-34
OL-20105-01
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Preconfigured CallManager Alarm Notifications
CDRMaximumDiskSpaceExceeded
This alarm gets raised when the CDR files disk usage exceeds the maximum disk allocation. It also
indicates that some undeliverable files got deleted.
Table 6-28
Default Configuration for the CDRMaximumDiskSpaceExceeded RTMT Alert
Value
Default Configuration
Enable Alert
Selected
Severity
Critical
Enable/Disable this
alert on the
following servers
Enabled on listed servers
Threshold
Trigger alert when following condition met:
CDRMaximumDiskSpaceExceeded event generated
Duration
Trigger alert immediately
Frequency
Trigger alert on every poll
Schedule
24 hours daily
Enable E-mail
Selected
Trigger Alert Action Default
CodeYellow
The AverageExpectedDelay counter represents the current average expected delay to handle any
incoming message. If the value exceeds the value that is specified in Code Yellow Entry Latency service
parameter, the CodeYellow alarm gets generated. You can configure the CodeYellow alert to download
trace files for troubleshooting purposes.
Table 6-29
Default Configuration for the CodeYellow RTMT Alert
Value
Default Configuration
Enable Alert
Selected
Severity
Critical
Enable/Disable this
alert on the
following servers
Enabled on listed servers
Threshold
Trigger alert when following condition met:
Cisco CallManager CodeYellowEntry event generated
Duration
Trigger alert immediately
Frequency
Trigger alert on every poll
Schedule
24 hours daily
Trace Download
Parameters
Enable Trace Download not selected
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
6-35
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Preconfigured CallManager Alarm Notifications
Table 6-29
Default Configuration for the CodeYellow RTMT Alert (continued)
Value
Default Configuration
Enable E-mail
Selected
Trigger Alert Action Default
DBChangeNotifyFailure
This alert occurs when the Cisco Database Notification Service experiences problems and might stop.
This condition indicates change notification requests that are queued in the database got stuck and
changes made to the system will not take effect. Ensure that the Cisco Database Layer Monitor is running
on the node where the alert exists. If it is, restart the service. If that does not return this alert to safe range,
collect the output of show tech notify and show tech dbstateinfo and contact TAC for information
about how to proceed.
Table 6-30
Default Configuration for the DBChangeNotifyFailure RTMT Alert
Value
Default Configuration
Enable Alert
Selected
Severity
Critical
Enable/Disable this
alert on the
following servers
Enabled on listed servers
Threshold
Trigger alert when following condition met:
DBChangeNotify queue delay over 2 minutes
Duration
Trigger alert immediately
Frequency
Trigger up to 1 alert within 30 minutes
Schedule
24 hours daily
Enable E-mail
Selected
Trigger Alert Action Default
DBReplicationFailure
This alarm indicates a failure in IDS replication and requires database administrator intervention.
Note
Be aware that DBReplicationFailure is based on the replication status perfmon counter (instead
of DBReplicationFailure alarm as was previously the case). This alert gets triggered whenever
the corresponding replication status perfmon counter specifies a value of 3 (Bad Replication) or
4 (Replication Setup Not Successful).
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
6-36
OL-20105-01
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Preconfigured CallManager Alarm Notifications
Table 6-31
Default Configuration for the DBReplicationFailure RTMT Alert
Value
Default Configuration
Enable Alert
Selected
Severity
Critical
Enable/Disable this
alert on the
following servers
Enabled on listed servers
Threshold
Trigger alert when following condition met:
DBReplicationFailure occurred
Duration
Trigger alert immediately
Frequency
Trigger up to 1 alert within 60 minutes
Schedule
24 hours daily
Enable E-mail
Selected
Trigger Alert Action Default
DDRBlockPrevention
This alert gets triggered when the IDSReplicationFailure alarm with alarm number 31 occurs, which
invokes a proactive procedure to avoid denial of service. This procedure does not impact call processing;
you can ignore replication alarms during this process.
The procedure takes up to 60 minutes to finish. Check that RTMT replication status equals 2 on each
node to make sure that the procedure is complete. Do not perform a system reboot during this process.
Table 6-32
Default Configuration for the DDRBlockPrevention RTMT Alert
Value
Default Configuration
Enable Alert
Selected
Severity
Critical
Enable/Disable this
alert on the
following servers
Enabled on listed servers
Threshold
Trigger alert when following condition met:
IDSReplicationFailure alarm with alarm number 31 generated
Duration
Trigger alert immediately
Frequency
Trigger up to 1 alert within 60 minutes
Schedule
24 hours daily
Enable E-mail
Selected
Trigger Alert Action Default
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
6-37
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Preconfigured CallManager Alarm Notifications
DDRDown
This alert gets triggered when the IDSReplicationFailure alarm with alarm number 32 occurs. An auto
recover procedure runs in the background, and no action is needed.
The procedure takes about 15 minutes to finish. Check that RTMT replication status equals 2 on each
node to make sure the procedure is complete.
Table 6-33
Default Configuration for the DDRDown RTMT Alert
Value
Default Configuration
Enable Alert
Selected
Severity
Critical
Enable/Disable this
alert on the
following servers
Enabled on listed servers
Threshold
Trigger alert when following condition met:
IDSReplicationFailure alarm with alarm number 32 generated
Duration
Trigger alert immediately
Frequency
Trigger up to 1 alert within 60 minutes
Schedule
24 hours daily
Enable E-mail
Selected
Trigger Alert Action Default
ExcessiveVoiceQualityReports
This alert gets generated when the number of QRT problems that are reported during the configured time
interval exceed the configured value. The default threshold specifies 0 within 60 minutes.
Table 6-34
Default Configuration for the ExcessiveVoiceQualityReports RTMT Alert
Value
Default Configuration
Enable Alert
Selected
Severity
Critical
Enable/Disable this
alert on the
following servers
Enabled on listed servers
Threshold
Trigger alert when following condition met:
Number of quality reports exceeds 0 times within the last 60 minutes
Duration
Trigger alert immediately
Frequency
Trigger alert on every poll
Schedule
24 hours daily
Enable E-mail
Selected
Trigger Alert Action Default
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
6-38
OL-20105-01
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Preconfigured CallManager Alarm Notifications
LowCallManagerHeartbeatRate
This alert occurs when the CallManager heartbeat rate equals less than the configured value.
Table 6-35
Default Configuration for the LowCallManagerHeartbeatRate RTMT Alert
Value
Default Configuration
Enable Alert
Selected
Severity
Warning
Enable/Disable this
alert on the
following servers
Enabled on listed servers
Threshold
Trigger alert when following condition met:
CallManager Server heartbeat rate below 24 beats per minute.
Duration
Trigger alert immediately
Frequency
Trigger alert on every poll
Schedule
24 hours daily
Enable E-mail
Selected
Trigger Alert Action Default
LowTFTPServerHeartbeatRate
This alert occurs when TFTP server heartbeat rate equals less than the configured value.
Table 6-36
Default Configuration for the LowTFTPServerHeartbeatRate RTMT Alert
Value
Default Configuration
Enable Alert
Selected
Severity
Warning
Enable/Disable this
alert on the
following servers
Enabled on listed servers
Threshold
Trigger alert when following condition met:
TFTP server heartbeat rate below 24 beats per minute
Duration
Trigger alert immediately
Frequency
Trigger alert on every poll
Schedule
24 hours daily
Enable E-mail
Selected
Trigger Alert Action Default
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
6-39
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Preconfigured CallManager Alarm Notifications
MaliciousCallTrace
This indicates that a malicious call exists in Cisco Unified Communications Manager. The malicious call
identification (MCID) feature gets invoked.
Table 6-37
Default Configuration for the MaliciousCallTrace RTMT Alert
Value
Default Configuration
Enable Alert
Selected
Severity
Critical
Enable/Disable this
alert on the
following servers
Enabled on listed servers
Threshold
Trigger alert when following condition met:
Malicious call trace generated
Duration
Trigger alert immediately
Frequency
Trigger alert on every poll
Schedule
24 hours daily
Enable E-mail
Selected
Trigger Alert Action Default
MediaListExhausted
This alert occurs when the number of MediaListExhausted events exceeds the configured threshold
during the configured time interval. This indicates that all available media resources that are defined in
the media list are busy. The default specifies 0 within 60 minutes.
Table 6-38
Default Configuration for the MediaListExhausted RTMT Alert
Value
Default Configuration
Enable Alert
Selected
Severity
Warning
Enable/Disable this
alert on the
following servers
Enabled on listed servers
Threshold
Trigger alert when following condition met:
Number of MediaListExhausted events exceeds 0 times within the last 60
minutes
Duration
Trigger alert immediately
Frequency
Trigger alert on every poll
Schedule
24 hours daily
Enable E-mail
Selected
Trigger Alert Action Default
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
6-40
OL-20105-01
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Preconfigured CallManager Alarm Notifications
MgcpDChannelOutOfService
This alert gets triggered when the MGCP D-Channel remains out of service.
Table 6-39
Default Configuration for the MgcpDChannelOutOfService RTMT Alert
Value
Default Configuration
Enable Alert
Selected
Severity
Critical
Enable/Disable this
alert on the
following servers
Enabled on listed servers
Threshold
Trigger alert when following condition met:
MGCP D-Channel is out-of-service
Duration
Trigger alert immediately
Frequency
Trigger alert on every poll
Schedule
24 hours daily
Enable E-mail
Selected
Trigger Alert Action Default
NumberOfRegisteredDevicesExceeded
This alert occurs when the NumberOfRegisteredDevicesExceeded event gets generated.
Table 6-40
Default Configuration for the NumberOfRegisteredDevicesExceeded RTMT Alert
Value
Default Configuration
Enable Alert
Selected
Severity
Critical
Enable/Disable this
alert on the
following servers
Enabled on listed servers
Threshold
Trigger alert when following condition met:
NumberOfRegisteredDevicesExceeded event generated
Duration
Trigger alert immediately
Frequency
Trigger alert on every poll
Schedule
24 hours daily
Enable E-mail
Selected
Trigger Alert Action Default
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
6-41
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Preconfigured CallManager Alarm Notifications
NumberOfRegisteredGatewaysDecreased
This alert occurs when the number of registered gateways in a cluster decreases between consecutive
polls.
Table 6-41
Default Configuration for the NumberOfRegisteredGatewaysDecreased RTMT Alert
Value
Default Configuration
Enable Alert
Selected
Severity
Critical
Enable/Disable this
alert on the
following servers
Enabled on listed servers
Threshold
Trigger alert when following condition met:
Number of registered gateway decreased
Duration
Trigger alert immediately
Frequency
Trigger alert on every poll
Schedule
24 hours daily
Enable E-mail
Selected
Trigger Alert Action Default
NumberOfRegisteredGatewaysIncreased
This alert occurs when the number of registered gateways in the cluster increased between consecutive
polls.
Table 6-42
Default Configuration for the NumberOfRegisteredGatewaysIncreased RTMT Alert
Value
Default Configuration
Enable Alert
Selected
Severity
Critical
Threshold
Trigger alert when following condition met:
Number of registered gateways increased
Duration
Trigger alert immediately
Frequency
Trigger alert on every poll
Schedule
24 hours daily
Enable E-mail
Selected
Trigger Alert Action Default
NumberOfRegisteredMediaDevicesDecreased
This alert occurs when the number of registered media devices in a cluster decreases between
consecutive polls.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
6-42
OL-20105-01
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Preconfigured CallManager Alarm Notifications
Table 6-43
Default Configuration for the NumberOfRegisteredMediaDevicesDecreased RTMT
Alert
Value
Default Configuration
Enable Alert
Selected
Severity
Critical
Threshold
Trigger alert when following condition met:
Number of registered media devices decreased
Duration
Trigger alert immediately
Frequency
Trigger alert on every poll
Schedule
24 hours daily
Enable E-mail
Selected
Trigger Alert Action Default
NumberOfRegisteredMediaDevicesIncreased
This alert occurs when the number of registered media devices in a cluster increases between
consecutive polls.
Table 6-44
Default Configuration for the NumberOfRegisteredMediaDevicesIncreased RTMT
Alert
Value
Default Configuration
Enable Alert
Selected
Severity
Critical
Threshold
Trigger alert when following condition met:
Number of registered media devices increased
Duration
Trigger alert immediately
Frequency
Trigger alert on every poll
Schedule
24 hours daily
Enable E-mail
Selected
Trigger Alert Action Default
NumberOfRegisteredPhonesDropped
This alert occurs when the number of registered phones in a cluster drops more than the configured
percentage between consecutive polls.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
6-43
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Preconfigured CallManager Alarm Notifications
Table 6-45
Default Configuration for the NumberOfRegisteredPhonesDropped RTMT Alert
Value
Default Configuration
Enable Alert
Selected
Severity
Critical
Threshold
Trigger alert when following condition met:
Number of registered phones in the cluster drops (10%)
Duration
Trigger alert immediately
Frequency
Trigger alert on every poll
Schedule
24 hours daily
Enable E-mail
Selected
Trigger Alert Action Default
RouteListExhausted
An available route could not be found in the indicated route list.
Table 6-46
Default Configuration for the RouteListExhausted RTMT Alert
Value
Default Configuration
Enable Alert
Selected
Severity
Warning
Enable/Disable this
alert on the
following servers
Enabled on listed servers
Threshold
Trigger alert when following condition met:
Number of RouteListExhausted exceeds 0 times within the last 60 minutes
Duration
Trigger alert immediately
Frequency
Trigger alert on every poll
Schedule
24 hours daily
Enable E-mail
Selected
Trigger Alert Action Default
SDLLinkOutOfService
This alert occurs when the SDLLinkOutOfService event gets generated. This event indicates that the
local Cisco Unified Communications Manager cannot communicate with the remote Cisco Unified
Communications Manager. This event usually indicates network errors or a nonrunning, remote Cisco
Unified Communications Manager.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
6-44
OL-20105-01
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Emergency-Level Alarms
Table 6-47
Default Configuration for the SDLLinkOutOfService RTMT Alert
Value
Default Configuration
Enable Alert
Selected
Severity
Critical
Enable/Disable this
alert on the
following servers
Enabled on listed servers
Threshold
Trigger alert when following condition met:
SDLLinkOutOfService event generated
Duration
Trigger alert immediately
Frequency
Trigger alert on every poll
Schedule
24 hours daily
Enable E-mail
Selected
Trigger Alert Action Default
Emergency-Level Alarms
The emergency-level alarm equals zero (0) and means that your system or service is unusable. These
alarms generally indicate platform failures. Examples follow:
•
Service repeatedly fails to startup
•
System ran out of disk space while disk space is essential for this system to operate
•
System ran out of memory
•
Motherboard failure occurred
This level is not suitable for events associated with an individual end point.
IPAddressResolveError
The host IP address was not resolved.
Facility/Sub-Facility
CCM_TCD-TCD
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/TCD SRV
Severity
Emergency (0)
Parameters
HostName [String]
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
6-45
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Emergency-Level Alarms
Recommended Action
None
NoCMEntriesInDB
There are no CallManager entries in the database.
Facility/Sub-Facility
CCM_TCD-TCD
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/TCD SRV
Severity
Emergency (0)
Parameters
None
Recommended Action
None
NoFeatureLicense
No feature license found. Cisco Unified Communications Manager (Unified CM) requires a license to
function. Also, Unified CM licenses are version-specific so be certain that the license is for the version
you are trying to run. You can run a license unit report in Cisco Unified CM Administration (System >
Licensing > License Unit Report).
History
Cisco Unified Communications
Release
Action
8.0(1)
Severity changed from Error to Emergency.
Facility/Sub-Facility
CCM_CALLMANAGER-CALLMANAGER
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/CallManager
Severity
Emergency
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
6-46
OL-20105-01
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Emergency-Level Alarms
Recommended Action
Request license generation for Cisco Unified Communications Manager SW FEATURE for your version
of Unified CM and upload the license in Cisco Unified CM Administration (System > Licensing >
License File Upload).
LineStateSrvEngCreationError
There was an error during the LineStateSrvEng creation.
Facility/Sub-Facility
CCM_TCD-TCD
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/TCD SRV
Severity
Emergency (0)
Parameters
None
Recommended Action
None
GlobalSPUtilsCreationError
There was an error during the GlobalSPUtils creation.
Facility/Sub-Facility
CCM_TCD-TCD
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/TCD SRV
Severity
Emergency (0)
Parameters
None
Recommended Action
None
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
6-47
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Emergency-Level Alarms
TapiLinesTableCreationError
There was an error during the TapiLinesTable creation.
Facility/Sub-Facility
CCM_TCD-TCD
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/TCD SRV
Severity
Emergency (0)
Parameters
None
Recommended Action
None
HuntGroupControllerCreationError
There was an error during the HuntGroupController creation.
Facility/Sub-Facility
CCM_TCD-TCD
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/TCD SRV
Severity
Emergency (0)
Parameters
None
Recommended Action
None
HuntGroupCreationError
There was an error during the Hunt Group creation.
Facility/Sub-Facility
CCM_TCD-TCD
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/TCD SRV
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
6-48
OL-20105-01
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Emergency-Level Alarms
Severity
Emergency (0)
Parameters
None
Recommended Action
None
CallDirectorCreationError
There was an error during the CallDirector creation.
Facility/Sub-Facility
CCM_TCD-TCD
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/TCD SRV
Severity
Emergency (0)
Parameters
None
Recommended Action
None
SysControllerCreationError
There was an error during the SysController creation.
Facility/Sub-Facility
CCM_TCD-TCD
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/TCD SRV
Severity
Emergency (0)
Parameters
None
Recommended Action
None
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
6-49
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Emergency-Level Alarms
TimerServicesCreationError
There was an error during the TimerServices creation.
Facility/Sub-Facility
CCM_TCD-TCD
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/TCD SRV
Severity
Emergency (0)
Parameters
None
Recommended Action
None
ExcceptionInInitSDIConfiguration
Exception occured in InitSDIConfiguration function.
Facility/Sub-Facility
CCM_TCD-TCD
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/TCD SRV
Severity
Emergency (0)
Parameters
None
Recommended Action
None
SyncDBCreationError
There was an error during the SyncDB creation in SysController.
Facility/Sub-Facility
CCM_TCD-TCD
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/TCD SRV
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
6-50
OL-20105-01
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Emergency-Level Alarms
Severity
Emergency (0)
Parameters
None
Recommended Action
None
LostConnectionToCM
TCD connection to CallManager was lost.
Facility/Sub-Facility
CCM_TCD-TCD
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/TCD SRV
Severity
Emergency (0)
Parameters
None
Recommended Action
None
IPMANotStarted
IPMA application not started because of an error.
Facility/Sub-Facility
CCM_JAVA_APPS-TOMCATAPPLICATIONS
Cisco Unified Serviceability Alarm Definition Catalog
System/Java Applications
Severity
Emergency (0)
Parameters
Servlet Name [String] Reason [String]
Recommended Action
See application logs for error
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
6-51
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Emergency-Level Alarms
BDINotStarted
BDI application not started because of an error.
Facility/Sub-Facility
CCM_JAVA_APPS-TOMCATAPPLICATIONS
Cisco Unified Serviceability Alarm Definition Catalog
System/Java Applications
Severity
Emergency (0)
Parameters
Reason [String]
Recommended Action
See application logs for error.
WDNotStarted
Failed to startup WebDialer application because of an error.
Facility/Sub-Facility
CCM_JAVA_APPS-TOMCATAPPLICATIONS
Cisco Unified Serviceability Alarm Definition Catalog
System/Java Applications
Severity
Emergency (0)
Parameters
Servlet Name [String] Reason [String]
Recommended Action
See application logs for error
CiscoDirSyncStartFailure
Cisco DirSymc application failed to start successfully. Error occurred while starting application
Facility/Sub-Facility
CCM_JAVA_APPS-TOMCATAPPLICATIONS
Cisco Unified Serviceability Alarm Definition Catalog
System/Java Applications
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
6-52
OL-20105-01
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Emergency-Level Alarms
Severity
Emergency (0)
Recommended Action
See application logs for error, may require restarting the application
TestAlarmEmergency
Testing emergency alarm.
Facility/Sub-Facility
CCM_CALLMANAGER-CALLMANAGER
Cisco Unified Serviceability Alarm Definition Catalog
System/Test
Severity
Emergency (0)
Recommended Action
None
OutOfMemory
The process has requested memory from the operating system, and there was not enough memory
available.
Cisco Unified Serviceability Alarm Definition Catalog
System/Generic
Severity
Emergency (0)
Parameters
None
Recommended Action
None
ServiceNotInstalled
An executable is trying to start but cannot because it is not configured as a service in the service control
manager. The service is %s. Service is not installed.
Cisco Unified Serviceability Alarm Definition Catalog
System/Generic
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
6-53
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Alert-Level Alarms
Severity
Emergency (0)
Parameters
Service (String)
Recommended Action
Reinstall the service.
FileWriteError
Cannot write into a file. Failed to write into the primary file path.
Cisco Unified Serviceability Alarm Definition Catalog
System/Generic
Severity
Emergency (0)
Parameters
Primary File Path(String)
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.
Alert-Level Alarms
The alert-level alarm equals 1 and action must take place immediately. A system error occurred and will
not recover without manual intervention. Examples follow:
•
Application is about to run out of licenses
•
Application is about to run out of disk space
•
Application is almost out of memory
•
100% CPU occurs for long period of time
Be aware that this level is not suitable for events that are associated with an individual end point.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
6-54
OL-20105-01
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Alert-Level Alarms
CertValidLessthanADay
Certificate is about to expire in less than 24 hours or has expired.
Cisco Unified Serviceability Alarm Definition Catalog
System/CertMonitorAlarmCatalog
Severity
Alert(1)
Routing List
Event Log
Sys Log
Parameters
Message(String)
Recommended Action
Regenerate the certificate that is about to expire by accessing the Cisco Unified Operating System and
go to Certificate Management. If the certificate is issued by a CA, generate a CSR, submit the CSR to
CA, obtain a fresh certificate from CA, and upload it to Cisco Unified CM.
CMIException
Error while reading the database.
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.
History
Cisco Unified Communications
Release
Action
8.0(1)
Name changed from kCMIException.
Cisco Unified Serviceability Alarm Definition Catalog
CMIAlarmCatalog/CMI
Severity
ALERT
Routing List
Event Log
SDI
Parameter(s)
CMI Exception(String)
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
6-55
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Alert-Level Alarms
Recommended Action
Refer to the associated alarm for further information.
CMOverallInitTimeExceeded
Initialization of the Cisco Unified Communications Manager system has taken longer than allowed by
the value specified in the System Initialization Timer service parameter; as a result, the system will
automatically restart now to attempt initialization again. Initialization may have failed due a database
error, or due to a large amount of new devices added to the system, or any number of other potential
causes. The required time to initialize Cisco Unified Communications Manager has exceeded the time
allowed by the Cisco CallManager service parameter, System Initialization Timer. This could be due to
an increase in system size.
History
Cisco Unified Communications
Release
8.0(1)
Action
•
Name changed from CUCMOverallInitTimeExceeded.
•
Severity changed from Error to Alert.
Facility/Sub-Facility
CCM_CALLMANAGER-CALLMANAGER
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/CallManager
Severity
Alert
Parameters
Cisco Unified Communications Manager Overall Initialization Time (in minutes) [Int]
Recommended Action
Try increasing the value of the Cisco CallManager service parameter, System Initialization Timer, in the
Service Parameters Configuration window in Cisco Unified CM Administration. Use RTMT to discover
the number of devices and number of users in the system and evaluate whether the numbers seem
accurate. Try increasing the value of the Cisco CallManager service parameter, System Initialization
Timer, in the Service Parameters Configuration window in Cisco Unified CM Administration. If
increasing the time in the System Initialization Timer service parameter does not correct this issue,
contact the Cisco Technical Assistance Center (TAC).
ConfigThreadChangeNotifyServerInstanceFailed
Failed to allocate resources to handle configuration change notification from database. This usually
indicates a lack of memory when there is a system issue such as running out of resources.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
6-56
OL-20105-01
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Alert-Level Alarms
History
Cisco Unified Communications
Release
Action
7.0(1)
Name changed from
kConfigThreadChangeNotifyServerInstanceFailed
8.0(1)
Severity changed from Error to Alert.
Facility/Sub-Facility
CCM_TFTP-TFTP
Cisco Unified Serviceability Alarm Definition Catalog
System/TFTP
Severity
Alert
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.
ConfigThreadChangeNotifyServerSingleFailed
Failed to allocate resources to handle configuration change notification from database. This usually
indicates a lack of memory when there is a system issue such as running out of resources.
History
Cisco Unified Communications
Release
Action
7.0(1)
Name changed from
kConfigThreadChangeNotifyServerSingleFailed.
8.0(1)
Severity changed from Error to Alert.
Facility/Sub-Facility
CCM_TFTP-TFTP
Cisco Unified Serviceability Alarm Definition Catalog
System/TFTP
Severity
Alert
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.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
6-57
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Alert-Level Alarms
ConfigThreadChangeNotifyServerStartFailed
Failed to start listening to configuration change notification from database. This usually indicates a lack
of memory when there is a system issue such as running out of resources.
History
Cisco Unified Communications
Release
Action
7.0(1)
Name changed from
kConfigThreadChangeNotifyServerStartFailed.
8.0(1)
Severity changed from Error to Alert.
Facility/Sub-Facility
CCM_TFTP-TFTP
Cisco Unified Serviceability Alarm Definition Catalog
System/TFTP
Severity
ALERT
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.
CreateThreadFailed
Failed to create a new thread. See Reason string for where it failed. This usually happens when there are
system issues such as running out of memory resources.
History
Cisco Unified Communications
Release
Action
7.0(1)
Name changed from kCreateThreadFailed.
8.0(1)
Severity changed from Error to Alert.
Facility/Sub-Facility
CCM_TFTP/TFTP
Cisco Unified Serviceability Alarm Definition Catalog
System/TFTP
Severity
Alert
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
6-58
OL-20105-01
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Alert-Level Alarms
Parameters
Error [Int] Reason [String]
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.
CMVersionMismatch
One or more Unified CM nodes in a cluster are running different Cisco CallManager versions.
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.
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/CallManager
Severity
ALERT
Routing List
SDL
SDI
Sys Log
Event Log
Data Collector
Parameter(s)
Remote Application Link Protocol Version(String)
Local Application Link Protocol Version(String)
Remote Node ID(UInt)
Remote Application ID(Enum)
Remote Application Version(String)
Enum Definitions -Remote Application ID
Value
Definition
100
CallManager
200
CTIManager
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.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
6-59
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Alert-Level Alarms
DBLException
An error occurred while performing database activities. A severe database layer interface error occurred.
Possible causes for this include the database being unreachable or down or a DNS error.
History
Cisco Unified Communications
Release
Action
8.0(1)
Severity changed from Error to Alert.
Facility/Sub-Facility
CCM_CALLMANAGER-CALLMANAGER
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/CallManager
Severity
Alert
Parameters
ErrorCode [Int] ExceptionString [String]
Recommended Action
Review the System Reports provided in the Cisco Unified Reporting tool, specifically the Cisco Unified
CM Database Status report, for any anomalous activity. Check network connectivity to the server that is
running the database. If your system uses DNS, check the DNS configuration for any errors.
InvalidCredentials
Credential Failure to IME server.
The connection to the IME server could not be completed, because the username and/or password
configured on Unified CM do not match those configured on the IME server.
History
Cisco Unified Communications
Release
Action
8.0(1)
New Alarm for this release.
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/CallManager
Severity
ALERT
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
6-60
OL-20105-01
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Alert-Level Alarms
Recommended Action
The alarm will include the username and password which were used to connect to the IME server, along
with the IP address of the target IME server and its name. Log into the IME server and check that the
username and password configured there match those configured in Unified CM.
Routing List
SDL
SDI
Sys Log
Event Log
Alert Manager
Parameter(s)
User name(String)
IP address(String)
Server name(String)
MemAllocFailed
Memory allocation failed.
History
Cisco Unified Communications
Release
Action
8.0(1)
Name changed from kMemAllocFailed.
Severity changed to Alert.
Recommended action changed.
Facility/Sub-Facility
CCM_SUMI-CMI
Cisco Unified Serviceability Alarm Definition Catalog
System/Service Manager
Severity
Alert
Parameters
Memory Allocation Failure(String)
Recommended Action
1.
Check the syslog for the system error number.
2.
If the Alert is seen repeatedly, restart Service Manager.
3.
If the problem still persist, reboot the Cisco Unified CM node.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
6-61
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Alert-Level Alarms
NoDbConnectionAvailable
No database connection available. Database layer could not find any working database connection.
Facility/Sub-Facility
CCM_DB_LAYER-DB
Cisco Unified Serviceability Alarm Definition Catalog
System/DB
Severity
Alert (1)
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.
ParityConfigurationError
The CMI service parameter, Parity, has an invalid configuration.
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 and the value can be validated against the
accepted range of values for this field.
History
Cisco Unified Communications
Release
Action
8.0(1)
New name changed from kParityConfigurationError.
Cisco Unified Serviceability Alarm Definition Catalog
CMIAlarmCatalog/CMI
Severity
ALERT
Routing List
Event Log
SDI
Parameter(s)
Illegal Parity(String)
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
6-62
OL-20105-01
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Alert-Level Alarms
Recommended Action
Verify that the Cisco Messaging Interface service parameter Parity is set to a valid (allowable) value.
SerialPortOpeningError
When CMI tries to open the serial port, the operating system returns an error.
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.
History
Cisco Unified Communications
Release
Action
8.0(1)
New name changed from kSerialPortOpeningError.
Cisco Unified Serviceability Alarm Definition Catalog
CMIAlarmCatalog/CMI
Severity
ALERT
Routing List
Event Log
SDI
Parameter(s)
Serial Port Opening Error(String)
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.
StopBitConfigurationError
The Cisco Messaging Interface service parameter, Stop Bits, has an invalid configuration.
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 and the value can be validated
against the accepted range of values for this field.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
6-63
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Alert-Level Alarms
History
Cisco Unified Communications
Release
Action
8.0(1)
New name changed from kStopBitConfigurationError.
Cisco Unified Serviceability Alarm Definition Catalog
CMIAlarmCatalog/CMI
Severity
ALERT
Routing List
Event Log
SDI
Parameter(s)
Illegal Stop Bit(String)
Recommended Action
Verify that the Cisco Messaging Interface service parameter Stop Bits is set to a valid (allowable) value.
UnknownException
Unknown error while connecting to database.
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.
Cisco Unified Serviceability Alarm Definition Catalog
CMIAlarmCatalog/CMI
Severity
ALERT
Routing List
Event Log
SDI
Recommended Action
Report to Customer Service representative.
VMDNConfigurationError
The Voice Mail DN for CMI is invalid.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
6-64
OL-20105-01
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Alert-Level Alarms
CMI cannot 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 and the value can be validated against the accepted range of values for this field.
History
Cisco Unified Communications
Release
Action
8.0(1)
Name changed from kVMDNConfigurationError.
Cisco Unified Serviceability Alarm Definition Catalog
CMIAlarmCatalog/CMI
Severity
ALERT
Routing List
Event Log
SDI
Parameter(s)
Invalid Voice Mail DN(String)
Recommended Action
Check the CMI service parameter Voice Mail DN to confirm that a valid directory number has been
configured.
CiscoLicenseOverDraft
Overdraft licenses in use.
Facility/Sub-Facility
CCM_JAVA_APPS_TOMCATAPPLICATIONS
Cisco Unified Serviceability Alarm Definition Catalog
System/Java Applications
Severity
Alert (1)
Parameters
Reason [String]
Recommended Action
None
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
6-65
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Alert-Level Alarms
CiscoLicenseApproachingLimit
License units consumption approaching its authorized limit.
Facility/Sub-Facility
CCM_JAVA_APPS_TOMCATAPPLICATIONS
Cisco Unified Serviceability Alarm Definition Catalog
System/Java Applications
Severity
Alert (1)
Parameters
Reason [String]
Recommended Action
None
SDIControlLayerFailed
Failed to update trace logging or alarm subsystem for new settings. This usually indicates a lack of
system resources or a failure in database access by the trace logging or alarm subsystem.
History
Cisco Unified Communications
Release
Action
8.0(1)
Severity changed from Critical to Alert.
7.0(1)
Name changed from kSDIControlLayerFailed.
Facility/Sub-Facility
CCM_TFTP_TFTP
Cisco Unified Serviceability Alarm Definition Catalog
System/TFTP
Severity
Alert
Parameters
Error [Int] Reason [String]
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
6-66
OL-20105-01
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Alert-Level Alarms
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 errors 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.
SocketError
Failed to open network connection for receiving file requests. This usually happens when the IP address
that the TFTP service uses to open the network connection is invalid.
History
Cisco Unified Communications
Release
Action
7.0(1)
Name changed from kSocketError.
Facility/Sub-Facility
CCM_TFTP-TFTP
Cisco Unified Serviceability Alarm Definition Catalog
System/TFTP
Severity
Alert (1)
Parameters
Error [Int] Reason [String]
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).
SDLLinkOOS
SDL link to remote application out of service.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).
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
6-67
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Alert-Level Alarms
History
Cisco Unified Communications
Release
Action
8.0(1)
Severity changed from Error to Alert.
Facility/Sub-Facility
CCM_CALLMANAGER-CALLMANAGER
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/CallManager
Severity
Alert
Parameters
Remote IP address of remote application [String] Unique Link ID. [String] Local node ID [UInt] Local
Application ID. [Enum]RemoteNodeID [UInt] Remote application ID. [Enum]
Enum Definitions for LocalApplicationID and RemoteApplicationID
Code
Reason
100
CallManager
200
CTI
Recommended Action
In the Cisco Unified Reporting tool, run a CM Cluster Overview report and check to see if all servers
can talk to 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.
TFTPServerListenSetSockOptFailed
Failed to increase the size of the network buffer for receiving file requests. This usually indicates a lack
of memory when there is a system issue such as running out of resources.
History
Cisco Unified Communications
Release
Action
7.0(1)
Name changed from kTFTPServerListenSetSockOptFailed.
Facility/Sub-Facility
CCM_TFTP-TFTP
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
6-68
OL-20105-01
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Alert-Level Alarms
Cisco Unified Serviceability Alarm Definition Catalog
System/TFTP
Severity
Alert (1)
Parameters
Error [Int] IPAddress [String] Port [Int]
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.
TFTPServerListenBindFailed
Fail to connect to the network port through which file requests are received. 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.
History
Cisco Unified Communications
Release
Action
7.0(1)
Name changed from kTFTPServerListenBindFailed.
Facility/Sub-Facility
CCM_TFTP-TFTP
Cisco Unified Serviceability Alarm Definition Catalog
System/TFTP
Severity
Alert (1)
Parameters
Error [Int] IPAddress [String] Port [Int]
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).
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
6-69
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Alert-Level Alarms
TestAlarmAlert
Testing alert alarm.
Facility/Sub-Facility
CCM_CALLMANAGER-CALLMANAGER
Cisco Unified Serviceability Alarm Definition Catalog
System/Test
Severity
Alert (1)
Recommended Action
None
TLSConnectionToIMEFailed
TLS Failure to IME service.
A TLS connection to the IME server could not be established because of a problem with the certificate
presented by the IME server. (For example, not in the Unified CM CTL, or is in the CTL but has
expired).
History
Cisco Unified Communications
Release
Action
8.0(1)
New Alarm for this release.
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/CallManager
Severity
ALERT
Recommended Action
Check to see that the certificate of the IME server is configured properly in the Unified CM.
Routing List
SDL
SDI
Sys Log
Event Log
Alert Manager
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
6-70
OL-20105-01
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Alert-Level Alarms
Parameter(s)
SSLErrorCode(UInt)
SSLErrorText(String)
TVSServerListenBindFailed
Fail to connect to the network port through which file requests are received. 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.
Cisco Unified Serviceability Alarm Catalog
System/TVS
Severity
ALERT
Routing List
SDI
Event Log
Data Collector
Sys Log
Parameter(s)
nError(Int)
IPAddress(String)
Port(Int)
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).
TVSServerListenSetSockOptFailed
Failed to increase the size of the network buffer for receiving file requests. This usually indicates a lack
of memory when there is a system issue such as running out of resources.
Cisco Unified Serviceability Alarm Catalog
System/TVS
Severity
ALERT
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
6-71
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Critical-Level Alarms
Routing List
SDI
Event Log
Data Collector
Sys Log
Parameter(s)
nError(Int)
IPAddress(String)
Port(Int)
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.
Critical-Level Alarms
The critical-level alarm equals 2 and action may need to be taken immediately; auto-recovery is
expected, but monitor the condition.
This alarm acts similar to the alert-level alarm but not necessarily requiring an immediate action. A
system-affecting service had a failure but recovered without intervention. Examples follow:
•
Service crashed due to an error that could not be handled but a watchdog process exists that will
restart the service. The crash does not necessarily require immediate action. Examples are:
– Out of memory conditions
– Uninitialized variables
– Memory scribblers
•
Unexpected code error occurred that could not be handled but for which the system automatically
restarts.
BChannelOOS
The B-channel is out of service. 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 are as follows:
•
Taking the channel out of service intentionally to perform maintenance on either the near- or far-end
•
MGCP gateway returns an error code 501 or 510 for a MGCP command sent from Cisco Unified
Communications Manager (Cisco Unified CM)
•
MGCP gateway does not respond to an MGCP command sent by Cisco Unified CM three times
•
Speed and duplex mismatch exists on the Ethernet port between Cisco Unified CM and the MGCP
gateway.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
6-72
OL-20105-01
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Critical-Level Alarms
History
Cisco Unified Communications
Release
Action
8.0(1)
Changed severity level from Error to Critical.
Facility/Sub-Facility
CCM_CALLMANAGER-CALLMANAGER
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/CallManager
Severity
Critical
Routing List
SDL
SDI
Sys Log
Event Log
Parameters
Unique channel Id [String] Device Name. [String] Reason. [Enum]Channel Id. [UInt]
Enum Definitions
•
0—None Defined
Recommended Action
Check the Cisco Unified CM 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; Reset
the MGCP gateway; Check the speed and duplex settings on the Ethernet port.
CallManagerFailure
Indicates an internal failure in the Cisco Unified Communications system. The service should restart in
an attempt to clear the failure.
History
Cisco Unified Communications
Release
Action
8.0(1)
Severity changed from Error to Critical.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
6-73
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Critical-Level Alarms
Facility/Sub-Facility
CCM_CALLMANAGER-CALLMANAGER
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/CallManager
Severity
Critical
Parameters
Additional Text [Optional] [String] Host name of hosting node. [String] IP address of hosting node.
[String] Reason code. [Enum]
Enum Definitions
Code
Reason
1
Unknown—Unified CM has failed for an unknown reason.
2
HeartBeatStopped—An internal heart beat has stopped after the preceding heart beat interval.
3
RouterThreadDied—An internal thread has failed.
4
TimerThreadDied—An internal thread has failed.
5
CriticalThreadDied—An internal thread has failed.
Recommended Action
Monitor for other alarms and restart the Cisco CallManager service, if necessary. Collect the existing
trace files in case the alarm persists.
CISCO-CCM-MIB
Part of ccmCallManagerAlarmEnable. See CISCO-CCM-MIB, page 7-1 in Chapter 7, “Cisco
Management Information Base.”
CertValidfor7days
Alarm indicates that the certificate has expired or expires in less than seven days.
Cisco Unified Serviceability Alarm Definition Catalog
System/CertMonitorAlarmCatalog
Severity
Critical(2)
Routing List
Event Log
Sys Log
Parameters
Message(String)
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
6-74
OL-20105-01
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Critical-Level Alarms
Recommended Action
Regenerate the certificate that is about to expire by accessing the Cisco Unified Operating System and
go to Certificate Management. If the certificate is issued by a CA, generate a CSR, submit the CSR to
CA, obtain a fresh certificate from CA, and upload it to Cisco Unified CM.
CodeRedEntry
Unified CM has entered Code Red condition and will restart.
Unified CM has been in Code Yellow state for an extended period and is unlikely to recover on its own.
The Cisco CallManager service automatically restarts in an attempt to clear the condition that is causing
the Code Yellow state. The amount of time that the system will remain in Code Yellow state is
configurable in the Code Yellow Duration service parameter. If the duration of this parameter is set to
99999, Code Red condition will never occur.
History
Cisco Unified Communications
Release
Action
8.0(1)
Severity changed from Error to Critical.
Facility/Sub-Facility
CCM_CALLMANAGER-CALLMANAGER
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/CallManager
Severity
Critical
Parameters
Expected Average Delay [UInt] Entry Latency [UInt] Exit Latency [UInt] Sample Size [UInt] Code
Yellow Duration [UInt] Number of Calls Rejected Due to Call Throttling [UInt] Total Code Yellow
Entry [UInt] Total Code Yellow Exit [UInt]
Recommended Action
You should have attempted the steps in the recommended actions defined in the CodeYellowEntry
alarm. If you have not, try those after the system is online. There is no other action for Code Red because
the only action is to restart which is performed for you automatically.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
6-75
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Critical-Level Alarms
CodeYellowEntry
CallManager has initiated call throttling due to unacceptably high delay in handling incoming calls.
History
Cisco Unified Communications
Release
Action
8.0(1)
Severity changed from Error to Critical.
Facility/Sub-Facility
CCM_CALLMANAGER-CALLMANAGER
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/CallManager
Severity
Critical
Parameters
Expected Average Delay [UInt] Entry Latency [UInt] Exit Latency [UInt] Sample Size [UInt] Total
Code Yellow Entry [UInt]
Recommended Action
Memory problems or high CPU usage are generally at the root of a Code Yellow state. A bad disk could
also be the cause. Also, trace level settings can consume tremendous amounts of CPU (especially when
the Enable SDL TCP Event Trace checkbox is enabled on the SDL Trace Configuration window in Cisco
Unified Serviceability). Check these areas to try to correct the Code Yellow condition. You can also
determine the level of fragmentation on the hard disk by issuing the File Fragmentation command from
the CLI for the trace directories. Monitor the situation and collect existing trace files. If the
CodeYellowExit alarm is not issued in a reasonable amount of time as deemed by your organization, or
if the system is frequently entering Code Yellow state, contact TAC and supply the trace information
you have collected.
DChannelOOS
The D-channel is out of service. D-channel indicated by this alarm has gone out of service. Common
reasons for a D-channel going 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 gateway reset.
History
Cisco Unified Communications
Release
Action
8.0(1)
Severity changed from Error to Critical.
Facility/Sub-Facility
CCM_CALLMANAGER-CALLMANAGER
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
6-76
OL-20105-01
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Critical-Level Alarms
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/CallManager
Severity
Critical
Parameters
Channel Id. [UInt] Unique channel Id [String] Device Name. [String] Device IP address [String]
Reason. [Enum]
Enum Definitions
•
0—None Defined
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 Communications Manager
Administration and the gateway terminal.
LogPartitionHighWaterMarkExceeded
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.
History
Cisco Unified Communications
Release
Action
8.0(1)
Severity changed from Error to Critical.
Facility/Sub-Facility
CCM_TCT-LPMTCT
Cisco Unified Serviceability Alarm Definition Catalog
System/LpmTct
Severity
Critical
Parameters
UsedDiskSpace [String] MessageString [Optional]. [String]
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.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
6-77
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Critical-Level Alarms
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.
MGCPGatewayLostComm
The MGCP gateway is no longer in communication with Cisco Unified Communications Manager
(Cisco Unified CM). This could occur because Cisco Unified CM receives an MGCP unregister signal
from the gateway such as RSIP graceful/forced; Cisco Unified CM doesn't receive the MGCP KeepAlive
signal from the gateway; the MGCP gateway doesn't response to an MGCP command sent by Cisco
Unified CM three times; a speed and duplex mismatch exists on the Ethernet port between Cisco Unified
CM and the MGCP gateway; the gateway has reset.
Facility/Sub-Facility
CCM_CALLMANAGER-CALLMANAGER
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/CallManager
Severity
Critical (2)
Parameters
Device Name [String]
Recommended Action
Reset the MGCP gateway in an attempt to restore communication with Cisco Unified CM; check the
speed and duplex settings on the Ethernet port. In the case of an unwanted reset of the gateway which
caused communication to be lost, take precautions to ensure that no unauthorized personnel resets the
gateway from Cisco Unified CM Administration or via the gateway terminal.
CISCO-CCM-MIB
See Chapter 7, “Cisco Management Information Base.”
CDRMaximumDiskSpaceExceeded
The CDR files disk usage exceeded maximum disk allocation. Some undeliverable files may have been
deleted to bring disk usage down. 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
undeliverable files or not depends on how deletionDisable flag is configured at CDRM Configuration
page. E-mail alert will be sent to the admin.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
6-78
OL-20105-01
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Critical-Level Alarms
History
Cisco Unified Communications
Release
8.0(1)
Action
Facility and sub-facility changed. Added Routing List and changed
Data Collector to Alert Manager.
Facility/Sub-Facility
CDRREP
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/CDR Management
Severity
Critical (2)
Routing List
Event Log
Sys Log
Alert Manager
Parameters
DiskUsageInMB [String]
Recommended Action
1.
Check if there are too many undeliverable 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.
ErrorChangeNotifyClientBlock
A change notification client is busy (blocked). If the change notification client continues to be blocked
for 10 minutes, the system automatically clears the block and change notification should resume
successfully. 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.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
6-79
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Critical-Level Alarms
History
Cisco Unified Communications
Release
Action
8.0(1)
Changed severity level to Critical from Error.
Facility/Sub-Facility
CCM_DB_LAYER-DB
Cisco Unified Serviceability Alarm Definition Catalog
System/DB
Severity
Critical (2)
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 a change that may have occurred around the time of the alarm.
MaxCallsReached
The maximum number of simultaneous connections in a Cisco Unified Communications Manager
(Unified CM) node has been reached. This is an internally-set value and when it is exceeded, Unified
CM starts throttling calls to keep the number of calls below the internal threshold.
History
Cisco Unified Communications
Release
Action
8.0(1)
Severity changed from Error to Critical.
Facility/Sub-Facility
CCM_CALLMANAGER-CALLMANAGER
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/CallManager
Severity
Critical
Parameters
Description [Int]
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
6-80
OL-20105-01
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Critical-Level Alarms
Recommended Action
In the Real-Time Monitoring Tool, check the CallsActive counter in the Cisco CallManager object for
an unusually high number of calls. Internal mechanisms will attempt to correct this condition. If this
alarm continues to occur, collect existing SDL and CCM trace files and check to be sure that CM
Services trace collection in Cisco Unified CM Serviceability is set to Detailed level.
StationTCPInitError
An error during initialization was encountered.
History
Cisco Unified Communications
Release
Action
8.0(1)
•
Severity changed from Error to Critical.
•
Following parameters are removed:
– Error Number [String]
– ErrorCode [Int]
Facility/Sub-Facility
CCM_CALLMANAGER-CALLMANAGER
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/CallManager
Severity
Critical
Recommended Action
Verify the Cisco Unified Communications Manager IP address is configured and is not configured as the
loop back address for the IP version. If the IP settings are correct, collect SDL and SDI traces and contact
TAC.
TCPSetupToIMEFailed
Connection Failure to IME server.
This alarm occurs when Unified CM is unable to establish a TCP connection to an IME server. It
typically occurs when the IP address and port of the IME server are misconfigured or an Intranet
connectivity problem is preventing the connection from being set up.
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/CallManager
Severity
CRITICAL_ALARM
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
6-81
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Critical-Level Alarms
Recommended Action
Check to make sure that the IP address and port of the IME server - which are present in the alarm - are
valid. If so, this may be due to a network connectivity problem. Test the connectivity between the
Unified CM servers and the IME server.
Routing List
SDL
SDI
Sys Log
Event Log
Alert Manager
Parameter(s)
IP address(String)
Port number(UInt)
TimerThreadSlowed
Verification of the Cisco Unified Communications Manager (Unified CM) internal timing mechanism
has slowed beyond acceptable limits. This generally indicates an increased load on the system or an
internal anomaly.
History
Cisco Unified Communications
Release
Action
8.0(1)
Severity changed from Warning to Critical.
Facility/Sub-Facility
CCM_CALLMANAGER-CALLMANAGER
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/CallManager
Severity
Critical
Recommended Action
If this alarm occurs at the same general day or time, or if it occurs with increasing frequency, collect all
system performance data in Real-Time Monitoring Tool as well as all trace information for the 30
minutes prior to the time that this alarm occurred and contact TAC.
CiscoDirSyncProcessFailToStart
LDAPSync process failed to start on particular sync agreement.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
6-82
OL-20105-01
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Critical-Level Alarms
Facility/Sub-Facility
CCM_JAVA_APPS-TOMCATAPPLICATIONS
Cisco Unified Serviceability Alarm Definition Catalog
System/Java Applications
Severity
Critical (2)
Parameters
AgreementId [String]
Recommended Action
See application logs for error
CoreDumpFileFound
The new core dump files have been found in the system. One of the component has crashed and
generated a core dump. Use admin cli or RTMT to featch the backtrace.
Facility/Sub-Facility
CCM_TCT-LPMTCT
Cisco Unified Serviceability Alarm Definition Catalog
System/LpmTct
Severity
Critical (2)
Parameters
TotalCoresFound [String] CoreDetails [String] Core1 [String] Core2 [String] Core3 [String]
Core4 [String] Core5 [String] Core6 [String]
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.
TestAlarmCritical
Testing critical alarm.
Facility/Sub-Facility
CCM_CALLMANAGER-CALLMANAGER
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
6-83
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Critical-Level Alarms
Cisco Unified Serviceability Alarm Definition Catalog
System/Test
Severity
Critical (2)
Recommended Action
None
DUPLEX_MISMATCH
This alarm is generated by Cisco CDP whenever there is a duplex mismatch between local interface and
switch interface.
History
Cisco Unified Communications
Release
Action
7.1
Added DUPLEX_MISMATCH to the CDPAlarmCatalog.
Facility/Sub-Facility
CCM_CDP/CDP
Cisco Unified Serviceability Alarm Definition Catalog
System/CDP
Severity
Critical (2)
Parameters
Switch Duplex Settings(String)
Local Interface Duplex Settings(String)
Recommended Action
Ensure that duplex settings are set to auto or full on local interface as well as switch interface.
CertExpiryCritical
Certificate is about to expire in less than 7 days. Regenerate or reimport certificate. Name of the service
generating this alarm is Cisco Certificate Expiry Monitor. The alarms are generated when any certificate
generated by the system or uploaded into the system expires. Cisco Unified CM uses certificates for
Tomcat (Web Server), CallManager, IPSEc and Directory. Refer Security guide for more details on
various certificates. When a certificate generated by Cisco Unified CM, the default validity of the
self-signed certificate is for 5 years. In case of Certificates signed by a CA, the validity is dependent on
the Expiry date set by CA while issuing the certificate. Once a certificate is about to expire “Cisco
Certificate Expiry Monitor”” service generates alarms. The severity of the alarm is dependent on how
much time is left for the certificate to expire.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
6-84
OL-20105-01
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Error-Level Alarms
The impact to system operation depends on the which certificate expired. This information is contained
in the alarm. If Tomcat certificate expired, while connecting to Cisco Unified CM web pages, browser
will throw an error stating certificate has expired. One can still ignore the warning and continue to
connect to Cisco Unified CM pages.
In case of Directory-trust, if Directory trust certificate uploaded to Cisco Unified CM expires, Cisco
Unified CM may not be able to establish SSL connection with external LDAP server. The overall impact
is that SSL connection between Cisco Unified CM and other external Servers will fail.
History
Cisco Unified Communications
Release
Action
7.0(1)
Error message added.
Facility/Sub-Facility
/CERT
Cisco Unified Serviceability Alarm Definition Catalog
System/Cert Monitor
Severity
Critical (2)
Parameters
None
Recommended Action
Login to CUOS page. Go to Security->Certificate Management and re-generate the certificate that has
expired (based on the information in alarm). This will generate a new self-signed certificate with a new
expiry date. In case the certificate is signed by a CA, Generate a new CSR, send it to the CA, get the
certificate signed by CA and upload the new certificate.
Error-Level Alarms
The error-level alarm is 3 and you should investigate important devices or subsystems and determine if
immediate action is needed. Errors that do not necessarily impact the ability of the service to continue
to function and do not create a system outage. More related to device or subsystems.
An example would be a device or subsystem failing for an unexpected reason.
AwaitingResponseFromPDPTimeout
Cisco Unified Communication Manager timed out waiting for the routing response from the policy
decision point. Cisco Unified Communications Manager (Unified CM) did not receive a call routing
response from the policy decision point (PDP) within the time specified by the Cisco CallManager
service parameter, Call Intercept Routing Request Timer, or on the Call Intercept Profile Configuration
window in Cisco Unified CM Administration.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
6-85
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Error-Level Alarms
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/CallManager
Severity
ERROR_ALARM
Routing List
SDL
SDI
Sys Log
Event Log
Parameter(s)
Policy Decision Point(String)
Recommended Action
Check whether the PDP is in service and working normally. Verify that the PDP is not overloaded; if it
is, take appropriate action to reduce the load on the PDP by following some or all of these
recommendations:
•
Consider adding more PDPs and provisioning Unified CM with additional call intercept profiles and
call intercept trigger points in the various configuration pages under the Call Routing menu in Cisco
Unified CM Administration.
•
Provision a pair of policy servers per call-intercept profile to enable load balancing.
OR
•
Verify that the PDP server in your deployment meets or exceed the hardware requirements specified
in the documentation for Cisco Enterprise Policy Manager (CEPM) or the third-party PDP solution
you have deployed. If necessary, increase the value in the Cisco CallManager service parameter,
Call Intercept Routing Request Timer or the value in the Call Intercept Profile for this PDP.
CCDIPReachableTimeOut
CCD Requesting Service IP Reachable Duration times out.
The CCD requesting service detected that it can no longer reach the learned patterns through IP. All
learned patterns from this forward will be marked as unreachable (via IP) and to allow calls to learned
patterns to continue to be routed until IP becomes reachable again, all calls to learned patterns will be
routed through the PSTN. Calls can be routed through the PSTN for a certain period of time before PSTN
failover times out.
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/CallManager
Severity
ERROR
Routing List
SDL
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
6-86
OL-20105-01
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Error-Level Alarms
SDI
Sys Log
Event Log
Recommended Action
Check IP connectivity and resolve any TCP or IP problems in the network.
CCDPSTNFailOverDurationTimeOut
The internal limit on PSTN failover has expired.
When learned patterns are not reachable through IP, Unified CM routes calls through the PSTN instead.
Calls can be routed through PSTN for an internally-controlled duration. When this alarm occurs, the
PSTN failover duration has expired and calls to learned patterns cannot be routed. All learned patterns
will be purged from Unified CM.
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/CallManager
Severity
ERROR
Routing List
SDL
SDI
Sys Log
Event Log
Recommended Action
Troubleshoot your network to get IP connectivity restored. After IP connectivity is restored, Unified CM
will automatically relearn Hosted DN patterns and calls to learned patterns will proceed through IP.
CNFFBuffWriteToFilefopenfailed
Failed to create Config File on disk or update existing Config File on disk. This may happen if disk is
full or the file is in use.
History
Cisco Unified Communications
Release
Action
7.0(1)
Name changed from kCNFFBuffWriteToFilefopenfailed.
8.0(1)
Severity changed from Informational to Error.
Facility/Sub-Facility
CCM_TFTP-TFTP
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
6-87
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Error-Level Alarms
Cisco Unified Serviceability Alarm Definition Catalog
System/TFTP
Severity
Error
Parameters
FileName [String]
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).
CNFFBuffWriteToFilefwritefailed
Failed to save Config File to disk. This may happen if disk is full or the file is in use.
History
Cisco Unified Communications
Release
Action
7.0(1)
Name changed from kCNFFBuffWriteToFilefwritefailed.
8.0(1)
Severity changed from Informational to Error.
Facility/Sub-Facility
CCM_TFTP-TFTP
Cisco Unified Serviceability Alarm Definition Catalog
System/TFTP
Severity
Error
Parameters
FileName [String]
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).
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
6-88
OL-20105-01
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Error-Level Alarms
ConfigItAllBuildFilesFailed
A complete rebuild of all device configuration files has failed. Probable causes of this alarm could be
failure to access the Cisco Unified Communications Manager database, or misconfiguration of some
devices.
History
Cisco Unified Communications
Release
Action
7.0(1)
Name changed from kConfigItAllBuildFilesFailed.
8.0(1)
Severity changed from Informational to Error.
Facility/Sub-Facility
CCM_TFTP-TFTP
Cisco Unified Serviceability Alarm Definition Catalog
System/TFTP
Severity
Error
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 errors that may have
occurred around the time of the alarm.
ConfigItAllReadConfigurationFailed
Failed to retrieve enterprise parameter values from database when rebuilding all configuration files. This
is usually caused by a failure to access the Cisco Unified Communications Manager database.
History
Cisco Unified Communications
Release
Action
7.0(1)
Name changed from kConfigItAllReadConfigurationFailed.
8.0(1)
Severity changed from Informational to Error.
Facility/Sub-Facility
CCM_TFTP-TFTP
Cisco Unified Serviceability Alarm Definition Catalog
System/TFTP
Severity
Error
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
6-89
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Error-Level Alarms
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 errors that may have
occurred around the time of the alarm.
ConfigThreadBuildFileFailed
Failed to build all device configuration files at TFTP service startup. This is usually caused by database
access failure.
History
Cisco Unified Communications
Release
Action
7.0(1)
Name changed from kConfigThreadBuildFileFailed
8.0(1)
Severity changed from Informational to Error.
Facility/Sub-Facility
CCM_TFTP-TFTP
Cisco Unified Serviceability Alarm Definition Catalog
System/TFTP
Severity
Error
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 errors that may have
occurred around the time of the alarm.
ConfigThreadCNCMGrpBuildFileFailed
Failed to rebuild configuration files for changes in Cisco Unified Communications Manager Group
settings. This is usually caused by a failure to access the Cisco Unified Communications Manager
database.
History
Cisco Unified Communications
Release
Action
7.0(1)
Name changed from kConfigThreadCNCMGrpBuildFileFailed.
8.0(1)
Severity changed from Informational to Error.
Facility/Sub-Facility
CCM_TFTP-TFTP
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
6-90
OL-20105-01
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Error-Level Alarms
Cisco Unified Serviceability Alarm Definition Catalog
System/TFTP
Severity
Error
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 errors that may have
occurred around the time of the alarm.
ConfigThreadCNGrpBuildFileFailed
Failed to rebuild configuration files for changes at group level settings such as Device Pool or Common
Device Config settings. This is usually caused by a failure to access the Cisco Unified Communications
Manager database.
History
Cisco Unified Communications
Release
Action
7.0(1)
Name changed from kConfigThreadCNGrpBuildFileFailed.
8.0(1)
Severity changed from Informational to Error.
Facility/Sub-Facility
CCM_TFTP-TFTP
Cisco Unified Serviceability Alarm Definition Catalog
System/TFTP
Severity
Error
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 errors that may have
occurred around the time of the alarm.
ConfigThreadReadConfigurationFailed
Failed to retrieve enterprise parameter values from database at TFTP service startup. This is usually
caused by database access failure.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
6-91
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Error-Level Alarms
History
Cisco Unified Communications
Release
Action
7.0(1)
Name changed from
kConfigThreadReadConfigurationFailed.
8.0(1)
Severity changed from Informational to Error.
Facility/Sub-Facility
CCM_TFTP-TFTP
Cisco Unified Serviceability Alarm Definition Catalog
System/TFTP
Severity
Error
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 errors that may have
occurred around the time of the alarm.
ConflictingDataIE
A call has been rejected because the incoming PRI/BRI Setup message had an invalid IE.
A call has been rejected because an incoming PRI/BRI Setup message contained an invalid Coding
Standard value in the Bearer Capability information element (IE). Unified CM only accepts PRI/BRI
Setup messages with Coding Standard values of 0 or 1. When an invalid IE is received, Unified CM
rejects the call setup and issues this alarm.
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/CallManager
Severity
ERROR
Routing List
SDL
SDI
Sys Log
Event Log
Parameter(s
Device Name(String)
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
6-92
OL-20105-01
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Error-Level Alarms
Recommended Action
Notify the service provider responsible for sending the Setup message that an IE with Coding Standard
values of 0 or 1 must be included in Setup messages.
ConnectionFailureToPDP
A connection request from Unified CM to the policy decision point (PDP) failed. The failure may have
been a result of the following conditions:
•
Network error causing limited or no connectivity between Unified CM and the PDP
•
Authentication errors when Unified CM established an HTTPS connection to the PDP
•
PDP was not in service.
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/CallManager
Severity
Error(3)
Routing List
SDL
SDI
Sys Log
Event Log
Data Collector
Parameters
Policy Decision Point(String)
The cause of the connection failure(String)
Recommended Action
Verify the network connectivity between Unified CM and the PDP by pinging the policy server host
from Cisco Unified OS Administration and take steps to establish connectivity if it has been lost. If the
connection failure is due to an authentication problem, verify that the valid certificate of the PDP has
been imported to Cisco Unified OS Administration and certificates from every node in the Unified CM
cluster have been imported to every node in the PDP. Also, check whether the PDP service is active.
CtiProviderOpenFailure
CTI application is unable to open the provider. The IP address is shown in either IPv4 or IPv6 format
depending on the IP addressing mode of the application.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
6-93
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Error-Level Alarms
History
Cisco Unified Communications
Release
Action
8.0(1)
Name changed from kCtiProviderOpenFailure.
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/CtiManager
Severity
ERROR
Routing List
SDL
SDI
Sys Log
Event Log
Data Collector
Parameter(s)
Login User Id(String)
Reason code.(Enum)
IPAddress(String)
IPV6Address(String)
Enum Definitions - Reason Code
Value
Definition
0
Unknown
0x8CCC0075
(2362179701)
Login request to authenticate user has timed out. Possible causes
include LDAP server misconfiguration such as LDAP server referrals
misconfiguration or Unified CM node experiencing high CPU usage.
Recommended action is to verify the CPU utilization is in the safe range
for Unified CM (this can be monitored using RTMT via CPU Pegging
Alert)
0x8CCC0060
(2362179680)
Directory login failed. Verify that credentials are not misconfigured,
check the userID and password configured in the application matches
with what is configured in Unified CM Admin under (User Management > End User or Application User)
0x8CCC005E
(2362179678)
Directory is unavailable. Verify that the LDAP server is reachable from
Unified CM node, make sure that the network connectivity between
Unified CM and the LDAP server by pinging the LDAP server host
from Cisco Unified OS Administration and take steps to establish connectivity if it has been lost
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
6-94
OL-20105-01
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Error-Level Alarms
Value
Definition
0x8CCC00D1
(2362179793)
Application is connecting to a non secure port but has security privileges enabled for the user associated with the application. Check the user
group configuration for the user in Unified CM Admin under (User
Management > End User/Application User), select the user and verify
the associated permissions information
0x8CCC005F
(2362179679)
Standard CTI Use permission is not enabled. Users associated with applications are required to be included in "Standard CTI Enabled" user
group. Verify the user group configuration for the user in Unified CM
Admin under (User Management > End User/Application User), select
the user and review the associated permissions information
0x8CCC00D0
(2362179792)
User is not enabled for a secure connection but the application connecting to secure port. Consider the application configuration and security
configuration for the user, for TAPI applications review the Control
Panel >Phone and Modem Options > Advanced > select a CiscoTSP >
Configure... > Security and disable "Secure Connection to CTIManager". For JTAPI applications from JTPrefs choose Security and disable
"Enable Secure Connection". Also check the user group configuration
for the user in Unified CM Admin under (User Management > End User/Application User), select the user and verify the associated permissions information
Recommended Action
Review the reason code and the recommended action within the reason code.
DeviceTypeMismatch
Device type mismatch between the information contained in the device's TFTP config file and what is
configured in the database for that device.
The device type indicated in the device's configuration file does not match the database configuration.
This could indicate that a change was made in the database configuration that failed to get updated at
the device itself.
History
Cisco Unified Communications
Release
Action
8.0(1)
Following information is updated:
•
Enum Definitions for DBDeviceType
•
Enum Definitions for DeviceType
Facility/Sub-Facility
CCM_CALLMANAGER-CALLMANAGER
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/CallManager
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
6-95
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Error-Level Alarms
Severity
Error
Parameters
Database device type [Enum]Device type. [Enum]Name of device. [String]
Enum Definitions for DBDeviceType
Code
Device Type
1
CISCO_30SP+
2
CISCO_12SP+
3
CISCO_12SP
4
CISCO_12S
5
CISCO_30VIP
6
CISCO_7910
7
CISCO_7960
8
CISCO_7940
9
CISCO_7935
12
CISCO_ATA_186
20
SCCP_PHONE
61
H323_PHONE
72
CTI_PORT
115
CISCO_7941
119
CISCO_7971
255
UNKNOWN
302
CISCO_7989
307
CISCO_7911
308
CISCO_7941G_GE
309
CISCO_7961G_GE
335
MOTOROLA_CN622
336
BASIC_3RD_PARTY_SIP_DEVICE
348
CISCO_7931
358
CISCO_UNIFIED_COMMUNICATOR
365
CISCO_7921
369
CISCO_7906
374
ADVANCED_3RD_PARTY_SIP_DEVICE
375
CISCO_TELEPRESENCE
404
CISCO_7962
412
CISCO_3951
431
CISCO_7937
434
CISCO_7942
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
6-96
OL-20105-01
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Error-Level Alarms
435
CISCO_7945
436
CISCO_7965
437
CISCO_7975
446
CISCO_3911
468
CISCO_UNIFIED_MOBILE_COMMUNICATOR
478
CISCO_TELEPRESENCE_1000
479
CISCO_TELEPRESENCE_3000
480
CISCO_TELEPRESENCE_3200
481
CISCO_TELEPRESENCE_500
484
CISCO_7925
493
CISCO_9971
495
CISCO_6921
496
CISCO_6941
497
CISCO_6961
20000
CISCO_7905
30002
CISCO_7920
30006
CISCO_7970
30007
CISCO_7912
30008
CISCO_7902
30016
CISCO_IP_COMMUNICATOR
30018
CISCO_7961
30019
CISCO_7936
30035
IP_STE
Enum Definitions for DeviceType
Code
Device Type
1
CISCO_30SP+
2
CISCO_12SP+
3
CISCO_12SP
4
CISCO_12S
5
CISCO_30VIP
6
CISCO_7910
7
CISCO_7960
8
CISCO_7940
9
CISCO_7935
12
CISCO_ATA_186
20
SCCP_PHONE
61
H323_PHONE
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
6-97
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Error-Level Alarms
72
CTI_PORT
115
CISCO_7941
119
CISCO_7971
255
UNKNOWN
302
CISCO_7989
307
CISCO_7911
308
CISCO_7941G_GE
309
CISCO_7961G_GE
335
MOTOROLA_CN622
336
BASIC_3RD_PARTY_SIP_DEVICE
348
CISCO_7931
358
CISCO_UNIFIED_COMMUNICATOR
365
CISCO_7921
369
CISCO_7906
374
ADVANCED_3RD_PARTY_SIP_DEVICE
375
CISCO_TELEPRESENCE
404
CISCO_7962
412
CISCO_3951
431
CISCO_7937
434
CISCO_7942
435
CISCO_7945
436
CISCO_7965
437
CISCO_7975
446
CISCO_3911
468
CISCO_UNIFIED_MOBILE_COMMUNICATOR
478
CISCO_TELEPRESENCE_1000
479
CISCO_TELEPRESENCE_3000
480
CISCO_TELEPRESENCE_3200
481
CISCO_TELEPRESENCE_500
484
CISCO_7925
493
CISCO_9971
495
CISCO_6921
496
CISCO_6941
497
CISCO_6961
20000
CISCO_7905
30002
CISCO_7920
30006
CISCO_7970
30007
CISCO_7912
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
6-98
OL-20105-01
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Error-Level Alarms
30008
CISCO_7902
30016
CISCO_IP_COMMUNICATOR
30018
CISCO_7961
30019
CISCO_7936
30035
IP_STE
Recommended Action
Check the Unified CM Database Status report in Cisco Unified Reporting to verify that database
replication is working. 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. Restart the phone
to download a new configuration file from TFTP. Also, refer to the reason code definitions for additional
recommended actions.
DbInfoCorrupt
Database information returned is corrupt. Database configuration error was encountered.
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/CallManager
Severity
ERROR
Routing List
SDL
SDI
Sys Log
Event Log
Parameter(s)
Name of Device(String)
Recommended Action
Investigate configuration for the identified device.
DbInfoError
Error in the database information retrieved. Database configuration error was encountered.
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/CallManager
Severity
ERROR
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
6-99
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Error-Level Alarms
Routing List
SDL
SDI
Sys Log
Event Log
Parameter(s)
Name of Device(String)
Recommended Action
Investigate configuration for identified device.
DbInfoTimeout
Database Information request timed out. Timeout was encountered while trying to read database
configuration.
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/CallManager
Severity
ERROR
Routing List
SDL
SDI
Event Log
Sys Log
Parameter(s)
Name of Device(String)
Recommended Action
Investigate configuration for identified device.
DRFLocalDeviceError
DRF unable to access local device.
Cisco Unified Serviceability Alarm Definition Catalog
System/DRF
Severity
ERROR
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
6-100
OL-20105-01
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Error-Level Alarms
Routing List
Event Log
Sys Log
Parameter(s)
Reason(String)
Recommended Action
Check if local location exists and is accessible.
EMAppInitializationFailed
EM Application not started. Error occurred while starting application.
Cisco Unified Serviceability Alarm Definition Catalog
System/EMAlarmCatalog
Severity
ERROR
Routing List
Sys Log
Event Log
Data Collector
Parameter(s)
Servlet Name(String)
Recommended Action
Action See application logs for error. Default location for the logs are at
/var/log/active/tomcat/logs/em/log4j/
EMCCFailedInLocalCluster
EMCC login failure occurred due to one of the following conditions:
•
Devices are incompatible with EMCC.
•
Unable to retrieve remote cluster information.
•
EMCC is restricted by the local cluster.
•
Untrusted certificate received from the remote end while trying to establish a connection
Reason Codes:
•
31—User is not enabled for EMCC
•
211/38—EMCC or PSTN is not activated in InterClusterServiceProfile page
•
23—User does not exist in the end user table
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
6-101
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Error-Level Alarms
•
35—No remote cluster entry is present for the home cluster
Cisco Unified Serviceability Alarm Definition Catalog
System/EMAlarmCatalog
Severity
ERROR(3)
Routing List
Sys Log
Event Log
Alert Manager
Parameters
Device Name(String)
Login Date/Time(String)
Login UserID(String)
Reason(String)
Recommended Action
Perform the following steps:
Step 1
Validate if the device model supports EMCC.
Step 2
Ensure that every remote cluster added for EMCC has valid hostname/IP address for EM and PSTN
access in the Remote Cluster administration window (From Unified CM Administration window, go to
System -> EMCC -> Remote Cluster).
Step 3
Ensure that the entries are enabled.
Step 4
Ensure that a bundle of all Tomcat certificates (PKCS12) has been imported into the local tomcat-trust
keystore (From the OS Administration window, go to Security -> Certificate Management and check the
certificates in tomcat-trust).
EMServiceConnectionError
EM Service not reachable. EM Service might be down in one or more nodes in the cluster.
Cisco Unified Serviceability Alarm Definition Catalog
System/EMAlarmCatalog
Severity
ERROR
Routing List
Sys Log
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
6-102
OL-20105-01
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Error-Level Alarms
Event Log
Parameter(s)
Servlet Name(String)
Recommended Action
Check if Cisco Extension Mobility service is running on all nodes of the cluster where the service is
activated.
EndPointTransientConnection
End point transient connection attempt.
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.
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/CallManager
Severity
ERROR
Routing List
SDL
SDI
Sys Log
Data Collector
SNMP Traps
Alternate Syslog
Parameter(s)
Device IP address(String)
Device name(String)
Device MAC address(String)
Protocol(String)
Device type(Enum)
Reason Code(Enum)
Connecting Port(UInt)
Registering SIP User(String)
IPv6Address(String)
IPAddressAttributes(Enum)
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
6-103
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Error-Level Alarms
IPv6AddressAttributes(Enum)
Enum Definitions -Device type
Value
Definition
1
CISCO_30SP+
2
CISCO_12SP+
3
CISCO_12SP
4
CISCO_12S
5
CISCO_30VIP
6
CISCO_7910
7
CISCO_7960
8
CISCO_7940
9
CISCO_7935
12
CISCO_ATA_186
20
SCCP_PHONE
61
H323_PHONE
72
CTI_PORT
115
CISCO_7941
119
CISCO_7971
255
UNKNOWN
302
CISCO_7989
307
CISCO_7911
308
CISCO_7941G_GE
309
CISCO_7961G_GE
335
MOTOROLA_CN622
336
BASIC_3RD_PARTY_SIP_DEVICE
348
CISCO_7931
358
CISCO_UNIFIED_COMMUNICATOR
365
CISCO_7921
369
CISCO_7906
374
ADVANCED_3RD_PARTY_SIP_DEVICE
375
CISCO_TELEPRESENCE
404
CISCO_7962
412
CISCO_3951
431
CISCO_7937
434
CISCO_7942
435
CISCO_7945
436
CISCO_7965
437
CISCO_7975
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
6-104
OL-20105-01
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Error-Level Alarms
446
CISCO_3911
468
CISCO_UNIFIED_MOBILE_COMMUNICATOR
478
CISCO_TELEPRESENCE_1000
479
CISCO_TELEPRESENCE_3000
480
CISCO_TELEPRESENCE_3200
481
CISCO_TELEPRESENCE_500
484
CISCO_7925
493
CISCO_9971
495
CISCO_6921
496
CISCO_6941
497
CISCO_6961
20000
CISCO_7905
30002
CISCO_7920
30006
CISCO_7970
30007
CISCO_7912
30008
CISCO_7902
30016
CISCO_IP_COMMUNICATOR
30018
CISCO_7961
30019
CISCO_7936
30035
IP_STE
Enum Definitions -Reason Code
Value
Definition
1
Unknown - (SCCP only) The device failed to register for an unknown reason. If this persists,
collect SDL/SDI traces with "Enable SCCP Keep Alive Trace" enabled and contact TAC.
2
NoEntryInDatabase - (MGCP only) The device is not configured in the Cisco Unified CM
database and auto-registration is either not supported for the device type or is not enabled. To
correct this problem, configure this device via Cisco Unified CM Administration.
3
DatabaseConfigurationError - The device is not configured in the Cisco Unified CM database
and auto-registration is either not supported for the device type or is not enabled. To correct
this problem, configure this device via Cisco Unified CM Administration.
4
DeviceNameUnresolveable - For SIP third-party devices this means that Cisco Unified CM
could not determine the name of the device from the Authorization header in the REGISTER
message. The device did not provide an Authorization header after Cisco Unified CM
challenged with a 401 Unauthorized message. Verify the device is configured with digest
credentials and is able to respond to 401 challenges with an Authorization header. If this is a
Cisco IP phone, the configuration may be out-of-sync. First go to the Cisco Unified Reporting
web page, generate a Unified CM Database Status report, and verify "all servers have a good
replication status". If DB replications looks good, reset the phone. If that still doesn't fix the
problem, restart the TFTP and the Cisco CallManager services. For all other devices, this
reason code means that DNS lookup failed. Verify the DNS server configured via the OS
Administration CLI is correct and that the DNS name used by the device is configured in the
DNS server.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
6-105
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Error-Level Alarms
6
ConnectivityError - The network connection between the device and Cisco Unified CM
dropped before the device was fully registered. Possible causes include device power outage,
network power outage, network configuration error, network delay, packet drops and packet
corruption. It is also possible to get this error if the Cisco Unified CM node is experiencing
high CPU usage. Verify the device is powered up and operating, verify network connectivity
between the device and Cisco Unified CM, and verify the CPU utilization is in the safe range
(this can be monitored using RTMT via CPU Pegging Alert).
7
InitializationError - An internal error occurred within Cisco Unified CM while processing the
device registration. It is recommended to restart the Cisco CallManager service. If this occurs
repeatedly, collect SDL/SDI detailed traces with "Enable SIP Keep Alive (REGISTER
Refresh) Trace" and "Enable SCCP Keep Alive Trace" under Cisco CallManager services
turned on and contact TAC.
10
AuthenticationError - The device failed either TLS or SIP digest security authentication. If
the device is a SIP phone and is enabled for digest authentication (on the System > Security
Profile > Phone Security Profile, check if "Enable Digest Authentication" checkbox is
checked), verify the "Digest Credentials" in the End User config page are configured. Also,
check the phone config page to see if the phone is associated with the specified end user in
the Digest User drop box. If the device is a third-party SIP device, verify the digest credentials
configured on the phone match the "Digest Credentials" configured in the End User page.
11
InvalidX509NameInCertificate - Configured "X.509 Subject Name" doesn't match what's in
the certificate from the device. Check the Security profile of the indicated device and verify
the "Device Security Mode" is either "Authenticated" or "Encrypted". Verify the "X.509
Subject Name" field has the right content. It should match the Subject Name in the certificate
from the peer.
12
InvalidTLSCipher - Unsupported cipher algorithm used by the device; Cisco Unified CM
only supports AES_128_SHA cipher algorithm. Recommended action is for the device to
regenerate its certificate with the AES_128_SHA cipher algorithm.
14
MalformedRegisterMsg - (SIP only) A SIP REGISTER message could not be processed
because of an illegal format. Possible causes include a missing Call-ID header, a missing AoR
in the To header, and an expires value too small. Verify the REGISTER message does not
suffer from any of these ills.
15
ProtocolMismatch - The protocol of the device (SIP or SCCP) does not match the configured
protocol in Cisco Unified CM. Recommended actions: 1) Verify the device is configured with
the desired protocol; 2) Verify the firmware load ID on the Device Defaults page is correct
and actually exists on the TFTP server; 3) If there is a firmware load ID configured on the
device page, verify it is correct and exists on the TFTP server (On Cisco Unified OS
Administration page, Software Upgrades > TFTP File Management, look for the file name as
specified by load ID); 4) Restart the TFTP and Cisco CallManager services. Use the Cisco
Unified OS Administration TFTP File Management page to verify the configured firmware
loads exist.
16
DeviceNotActive - The device has not been activated.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
6-106
OL-20105-01
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Error-Level Alarms
17
AuthenticatedDeviceAlreadyExists - A device with the same name is already registered. If
this occurs repeatedly, collect SDL/SDI detailed traces with "Enable SIP Keep Alive
(REGISTER Refresh) Trace" and "Enable SCCP Keep Alive Trace" under Cisco
CallManager services turned on and contact TAC. There may be an attempt by unauthorized
devices to register.
18
ObsoleteProtocolVersion - (SCCP only) A SCCP device registered with an obsolete protocol
version. Power cycle the phone. Verify that the TFTP service is activated. Verify that the
TFTP server is reachable from the device. If there is a firmware load ID configured on the
Phone Config page, verify that the firmware load ID exists on the TFTP server (On Cisco
Unified OS Administration page, Software Upgrades > TFTP File Management, look for the
file name as specified by load ID).
Enum Definitions -IPAddressAttributes
Value
Definition
0
Unknown - The device has not indicated what this IPv4 address is used for
1
Administrative only - The device has indicated that this IPv4 address is used for
administrative communication (web interface) only
2
Signal only - The device has indicated that this IPv4 address is used for control
signaling only
3
Administrative and signal - The device has indicated that this IPv4 address is used for
administrative communication (web interface) and control signaling
Enum Definitions -IPv6AddressAttributes
Value
0
1
2
3
Definition
Unknown - The device has not indicated what this IPv6 address is used for
Administrative only - The device has indicated that this IPv6 address is used for
administrative communication (web interface) only
Signal only - The device has indicated that this IPv6 address is used for control signaling
only
Administrative and signal - The device has indicated that this IPv6 address is used for
administrative communication (web interface) and control signaling
Recommended Action
Investigate any network connectivity problems in the system. It's possible that you have reached the
maximum number of devices; the Cisco Unified Communications Manager service parameter,
Maximum Number of Registered Devices, controls the number of devices allowed in the system. 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 for recommended actions. No action
is required if this event was issued as a result of a normal device rehome.
EndPointUnregistered
An endpoint that has previously registered with Cisco Unified Communications Manager has
unregistered. In cases of normal unregistration with reason code 'CallManagerReset',
'CallManagerRestart', 'DeviceInitiatedReset', 'EMLoginLogout', or 'EMCCLoginLogout', the severity of
this alarm is lowered to INFORMATIONAL. An endpoint can unregister for many reasons, both
intentional, such as manually resetting the device after a configuration change, or unintentional, such as
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
6-107
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Error-Level Alarms
loss of network connectivity. Other causes for this alarm could include a phone being registered to a
secondary node and then the primary node come back online, causing the phone to rehome to the primary
Unified CM node or lack of a KeepAlive being returned from the Unified CM node to which this
endpoint was registered. Unregistration also occurs if Unified CM receives a duplicate registration
request for this same device.
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/CallManager
Severity
ERROR
Routing List
SDL
SDI
Sys Log
Data Collector
SNMP Traps
Alternate Syslog
Parameter(s)
Device name(String)
Device MAC address(String)
Device IP address(String)
Protocol(String)
Device type(Enum)
Device description(String)
Reason Code(Enum)
IPV6Address(String)
IPAddressAttributes(Enum)
IPV6AddressAttributes(Enum)
Enum Definitions -Device type
Value
Definition
1
CISCO_30SP+
2
CISCO_12SP+
3
CISCO_12SP
4
CISCO_12S
5
CISCO_30VIP
6
CISCO_7910
7
CISCO_7960
8
CISCO_7940
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
6-108
OL-20105-01
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Error-Level Alarms
9
CISCO_7935
12
CISCO_ATA_186
20
SCCP_PHONE
61
H323_PHONE
72
CTI_PORT
115
CISCO_7941
119
CISCO_7971
255
UNKNOWN
302
CISCO_7989
307
CISCO_7911
308
CISCO_7941G_GE
309
CISCO_7961G_GE
335
MOTOROLA_CN622
336
BASIC_3RD_PARTY_SIP_DEVICE
348
CISCO_7931
358
CISCO_UNIFIED_COMMUNICATOR
365
CISCO_7921
369
CISCO_7906
374
ADVANCED_3RD_PARTY_SIP_DEVICE
375
CISCO_TELEPRESENCE
404
CISCO_7962
412
CISCO_3951
431
CISCO_7937
434
CISCO_7942
435
CISCO_7945
436
CISCO_7965
437
CISCO_7975
446
CISCO_3911
468
CISCO_UNIFIED_MOBILE_COMMUNICATOR
478
CISCO_TELEPRESENCE_1000
479
CISCO_TELEPRESENCE_3000
480
CISCO_TELEPRESENCE_3200
481
CISCO_TELEPRESENCE_500
484
CISCO_7925
493
CISCO_9971
495
CISCO_6921
496
CISCO_6941
497
CISCO_6961
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
6-109
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Error-Level Alarms
20000
CISCO_7905
30002
CISCO_7920
30006
CISCO_7970
30007
CISCO_7912
30008
CISCO_7902
30016
CISCO_IP_COMMUNICATOR
30018
CISCO_7961
30019
CISCO_7936
30035
IP_STE
Enum Definitions -Reason Code
Value
Definition
1
Unknown - The device has unregistered for an unknown reason. If the device does not
re-register within 5 minutes, verify it is powered-up and verify network connectivity between
the device and Cisco Unified CM.
6
ConnectivityError - Network communication between the device and Cisco Unified CM has
been interrupted. Possible causes include device power outage, network power outage,
network configuration error, network delay, packet drops and packet corruption. It is also
possible to get this error if the Cisco Unified CM node is experiencing high CPU usage.
Verify the device is powered up and operating, verify network connectivity between the
device and Cisco Unified CM, and verify the CPU utilization is in the safe range (this can be
monitored using RTMT via CPU Pegging Alert).
8
DeviceInitiatedReset - The device has initiated a reset, possibly due to a power cycle or
internal error. No action required; the device will re-register automatically.
9
CallManagerReset - A device reset was initiated from Cisco Unified CM Administration,
either due to an explicit command from an administrator, or due to internal errors
encountered. No action necessary, the device will re-register automatically.
10
DeviceUnregistered - The device has explicitly unregistered. Possible causes include a
change in the IP address or port of the device. No action is necessary, the device will
re-register automatically.
11
MalformedRegisterMsg - (SIP only) A SIP REGISTER message could not be processed
because of an illegal format. Possible causes include a missing Call-ID header, a missing AoR
in the To header, and an expires value too small. Verify the REGISTER message does not
suffer from any of these ills.
12
SCCPDeviceThrottling - (SCCP only) The indicated SCCP device exceeded the maximum
number of events allowed per-SCCP device. Events can be phone calls, KeepAlive messages,
or excessive SCCP or non-SCCP messages. The maximum number of allowed events is
controlled by the Cisco CallManager service parameter, Max Events Allowed. When an
individual device exceeds the number configured in that service parameter, Unified CM
closes the TCP connection to the device; automatic reregistration generally follows. This
action is an attempt to stop malicious attacks on Unified CM or to ward off excessive CPU
usage. No action necessary, the device will re-register automatically.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
6-110
OL-20105-01
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Error-Level Alarms
13
KeepAliveTimeout - A KeepAlive message was not received. Possible causes include device
power outage, network power outage, network configuration error, network delay, packet
drops and packet corruption. It is also possible to get this error if the Unified CM node is
experiencing high CPU usage. Verify the device is powered up and operating, verify network
connectivity between the device and Unified CM, and verify the CPU utilization is in the safe
range (this can be monitored using RTMT via CPU Pegging Alert). No action necessary, the
device will re-register automatically.
14
ConfigurationMismatch (SIP only) The configuration on the device does not match the
configuration in Unified CM. This can be caused by database replication errors or other
internal Unified CM communication errors. First go to the Cisco Unified Reporting web page,
generate a Unified CM Database Status report, and verify "all servers have a good replication
status". If this device continues to unregister with this reason code, go to the Cisco Unified
CMAdmin Device web page for the device and click Save. This allows a change notify to be
generated to the Unified CM and TFTP services and rebuild a new config file. If the problem
still persists, restart the TFTP service and Unified CM service.
15
CallManagerRestart - A device restart was initiated from Cisco Unified CM, either due to an
explicit command from an administrator, or due to a configuration change such as adding,
deleting or changing a DN associated with the device. No action necessary, the device will
re-register automatically.
16
DuplicateRegistration - Cisco Unified CM detected that the device attempted to register to 2
nodes at the same time. Cisco Unified CM initiated a restart to the phone to force it to re-home
to a single node. No action necessary, the device will re-register automatically.
17
CallManagerApplyConfig - An ApplyConfig command was invoked from Unified CM
Administration resulting in an unregistration. No action necessary, the device will re-register
automatically.
18
DeviceNoResponse - The device did not respond to a reset or restart notification, so it is being
forcefully reset. If the device does not re-register within 5 minutes, confirm it is powered-up
and confirm network connectivity between the device and Cisco Unified CM.
19
EMLoginLogout
20
EMCCLoginLogout
Enum Definitions -IPAddressAttributes
Value Definition
0
Unknown - The device has not indicated what this IPv4 address is used for
1
Administrative only - The device has indicated that this IPv4 address is used for administrative
communication (web interface) only
2
Signal only - The device has indicated that this IPv4 address is used for control signaling only
3
Administrative and signal - The device has indicated that this IPv4 address is used for
administrative communication (web interface) and control signaling
Enum Definitions -IPV6AddressAttributes
Value
Definition
0
Unknown - The device has not indicated what this IPv6 address is used for
1
Administrative only - The device has indicated that this IPv6 address is used for
administrative communication (web interface) only
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
6-111
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Error-Level Alarms
2
Signal only - The device has indicated that this IPv6 address is used for control signaling only
3
Administrative and signal - The device has indicated that this IPv6 address is used for
administrative communication (web interface) and control signaling
Recommended Action
Actions to take vary depending on the reason specified for the endpoint unregistration. If the reason is
ConfigurationMismatch, go to the Device Configuration page in Cisco Unified CM Administration,
make a change to the Description field for this device, click Save, then reset the device. In the case of a
network connectivity or loss of KeepAlives problem, use network diagnostic tools and the Cisco Unified
CM Reporting tool to fix any reported network or Unified CM system errors. In the case of an endpoint
rehoming to the primary Unified CM node, watch for a successful registration of the device on the
primary node. In the case of a duplicate registration request, it may be a non-malicious occurrence due
to timing of an endpoint registering and unregistering; if duplicate registration requests continue or if
the same endpoint has different IP addresses, confirm the IP address on the physical device itself by
checking the settings on the device (settings button). If unregistration of this device was expected, no
action is required. Also, refer to the reason code descriptions for recommended actions.
FirewallMappingFailure
Firewall unreachable.
This alarm indicates that Unified CM was unable to contact the firewall in order to make a IME call. As
a consequence, outbound calls are being sent over the PSTN, and inbound calls may be routed over the
PSTN by your partner enterprises.
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/CallManager
Severity
ERROR
Recommended Action
Check to see that your firewall is up. Make sure the mapping service is enabled. Check that the IP
address and port on the firewall for that mapping service match the configuration in Unified CM
Administration. Check general IP connectivity between Unified CM and the firewall.
Routing List
SDL
SDI
Sys Log
Event Log
Parameter(s)
IP address(String)
Port number(UInt)
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
6-112
OL-20105-01
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Error-Level Alarms
InsufficientFallbackIdentifiers
Cannot allocate fallback identifier.
This alarm is generated when Unified CM is processing a IME call, and is attempting to allocate a PSTN
fallback DID and a DTMF digit sequence to associate with this call. However, there are too many IME
calls currently in progress which are utilizing this same fallback DID, and as a result, there are no more
DTMF digit sequences which could be allocated to this call. As such, this call will proceed, however
mid-call fallback will not be possible for this call.
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/CallManager
Severity
ERROR
Routing List
SDL
SDI
Sys Log
Event Log
Alert Manager
Parameter(s)
Fallback profile name(String)
Fallback E.164 number(UInt)
Current number of DTMF digits(UInt)
E.164 called party number(String)
Recommended Action
Your first course of action should be to identify the fallback profile associated with this call. Its name
will be present in the alarm. Check that profile from the admin interface, and examine the current setting
for "Fallback Number of Correlation DTMF Digits". Increase that value by one, and check if that
eliminates these alarms. In general, this parameter should be large enough such that the number of
simultaneous IME calls made to enrolled numbers associated with that profile is always substantially
less than 10 raised to the power of this number. "Substantially" should be at least a factor of ten. For
example, if you always have less than 10,000 simultaneous IME calls for the patterns associated with
this fallback profile, setting this value to 5 (10 to the power of 5 is 100,000) will give you plenty of
headroom and you will not see this alarm.
However, increasing this value also results in a small increase in the amount of time it takes to perform
the fallback. As such, it should not be set arbitrarily large; it should be set just large enough to keep clear
of this alarm. Another alternative to increasing this parameter is to add another fallback profile with a
different fallback DID, and associate that fallback profile with a smaller number of enrolled DID
patterns. This will allow you to get by with a smaller number of digits.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
6-113
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Error-Level Alarms
InvalidPortHandle
The handle for the opened serial port is invalid.
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.
History
Cisco Unified Communications
Release
Action
8.0(1)
Name changed from kInvalidPortHandle.
Cisco Unified Serviceability Alarm Definition Catalog
CMIAlarmCatalog/CMI
Severity
ERROR
Routing List
Event Log
SDI
Parameter(s)
Error Information(String)
Recommended Action
Make sure that the cable connecting the USB0 port and voice messaging system is firmly connected.
kANNDeviceRecordNotFound
ANN device record not found. 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.
History
Cisco Unified Communications
Release
Action
8.0(1)
Severity changed from Warning to Error.
Facility/Sub-Facility
CCM_MEDIA_STREAMING_APP-IPVMS
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/IpVms
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
6-114
OL-20105-01
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Error-Level Alarms
Severity
Error
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.
kCFBDeviceRecordNotFound
CFB device record not found. A device record for the conference bridge device was not found in the
database. The CFB device is normally automatically added when the server is added to the database.
History
Cisco Unified Communications
Release
Action
3.x and 4.x
Added for Windows.
7.0(1)
Obsoleted.
8.0(1)
This alarm is available in 8.0(1). The severity changed from
Informational to Error.
Facility/Sub-Facility
CCM_MEDIA_STREAMING_APP-IPVMS
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/IpVms
Severity
Error
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.
LostConnectionToSAFForwarder
Connection to the SAF Forwarder has been lost.
A TCP connection failure caused the connection between the SAF Forwarder and Unified CM to be lost.
When the TCP connection is restored, Unified CM attempts to connect to the SAF Forwarder
automatically. If IP connectivity is unreachable for longer than the duration of the Cisco CallManager
service parameter CCD Learned Pattern IP Reachable Duration, calls to learned patterns will be routed
through the PSTN instead. Calls through the PSTN to learned patterns will be maintained for a certain
period of time before the PSTN failover times out.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
6-115
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Error-Level Alarms
Cisco Unified Serviceability Alarm Catalog
CallManager/CallManager
Severity
Error
Routing List
SDL
SDI
Sys Log
Event Log
Data Collector
Parameters
IP Address(String)
SafClientHandle(UInt)
Recommended Action
Investigate possible causes of a TCP connection failure, such as power failure, loose cables, incorrect
switch configuration, and so on, and correct any issues that you find. After the connection is restored,
CCD will try to register/sync with the SAF Forwarder automatically.
MultipleSIPTrunksToSamePeerAndLocalPort
Multiple trunks have been configured to the same destination and local port, which resulted in a conflict.
Only one trunk is allowed for one destination/local port combination. The latest trunk invalidated earlier.
Facility/Sub-Facility
CCM_CALLMANAGER-CALLMANAGER
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/CallManager
Severity
Error
Parameters
Peer IP Address. [String] Local IP Port [UInt] Old Device name. [String] Old Device Instance. [String]
New Device name. [String] New Device Instance. [String]
Recommended Action
Check the SIP Trunk Configuration in Cisco Unified CallManager Administration and verify that only
one SIP trunk has been configured to the same destination address and local port.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
6-116
OL-20105-01
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Error-Level Alarms
NodeNotTrusted
Untrusted Node was contacted. Application could not establish secure connection (SSL handshake
failure) with another application. It could be due to certificate for tomcat service where the application
is hosted is not trusted (not present in the keystore).
Cisco Unified Serviceability Alarm Definition Catalog
System/EMAlarmCatalog
Severity
ERROR
Routing List
Sys Log
Event Log
Alert Manager
Parameter(s)
Date/Time(String)
Hostname/Ip Address(String)
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).
PublishFailedOverQuota
Each IME server has a fixed quota on the total number of DIDs it can write into the IME distributed
cache. When this alarm is generated, it means that, even though you should be under quota, due to an
extremely unlikely statistical anomaly, the IME distributed cache rejected your publication, believing
you were over quota. You should only see this alarm if you are near, but below, your quota. This error
is likely to be persistent, so that the corresponding E.164 number from the alarm will not be published
into the IME distributed cache. This means that you will not receive VoIP calls towards that number they will remain over the PSTN.
History
Cisco Unified Communications
Release
Action
8.0(1)
New Alarm for this release.
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/CallManager
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
6-117
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Error-Level Alarms
Severity
ERROR_ALARM
Recommended Action
The alarm will include the name of the IME server, and the current and target quota values. The first
thing to check is to make sure that you have correctly provisioned the right set of DID prefixes on all of
the Unified CM clusters sharing that same IME server on the same IME distributed cache. If that is
correct, it means you have exceeded the capacity of your IME server, and you require another. Once you
have another, you can now split your DID prefixes across two different IME client instances, each on a
different IME server. That will alleviate the quota problem.
Routing List
SDL
SDI
Sys Log
Event Log
Parameter(s)
The DID for which the Publish was attempted(String)
Server name(String)
Current quota(UInt)
Maximum target quota(UInt)
ReadingFileFailure
CMI failed to read SMDI messages from the serial port.
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.
History
Cisco Unified Communications
Release
Action
8.0(1)
Name changed from kReadingFileFailure.
Cisco Unified Serviceability Alarm Definition Catalog
CMIAlarmCatalog/CMI
Severity
ERROR
Routing List
Event Log
SDI
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
6-118
OL-20105-01
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Error-Level Alarms
Parameter(s)
Error Information(String)
Recommended Action
Make sure that the cable connecting the USB0 port and voice messaging system is firmly connected.
SAFForwarderError
SAF Forwarder error response sent to Unified CM.
Cisco Unified Serviceability Alarm Catalog
CallManager/CallManager
Severity
Error
Routing List
SDL
SDI
Sys Log
Event Log
Data Collector
Parameters
IP Address(String)
SafClientHandle(UInt)
Application User Name(String)
Reason Code and Description(Enum)
SAF Protocol Version Number(String)
Service ID(UInt)
Sub Service ID(UInt)
Recommended Action
Refer to the reason code and description (help text) for specific information and actions (where
applicable) for this alarm.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
6-119
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Error-Level Alarms
Enum Definitions - Reason Code
Value
Definition
400
SAF_BAD_REQUEST - SAF Forwarder was unable to accept the request
due to incorrect syntax (malformed), missing required attributes, and other
similar reasons. Investigate the configuration between the SAF Forwarder
and Unified CM to be certain that all settings are correct for your deployment. In particular, check the Client Label configured on the router to make
certain that it matches the Client Label configured in Cisco Unified CM Administration on the SAF Forwarder Configuration window (SAF > SAF Forwarder).
431
SAF_INTEGRITY_CHECK_FAILURE - A message failed to pass SAF
Forwarder security validation. This can occur because of misconfiguration, a
potential attack, or more commonly by incorrect provisioning of the
password on the Forwarder and SAF client. Reprovision the password and
keep a watch on further SAF INTEGRITY CHECK FAILURE alarms. If you
receive a persistent number of SAF INTEGRITY CHECK FAILURE alarms,
close the interface between SAF Forwarder and Unified CM and investigate
the source of the IP packets.
435
**INFO LEVEL** SAF_MISSING_NONCE - A nonce (a random parameter
generated when the message is sent) is missing from the message. The system
will resend with a new nonce automatically. No action is required.
436
SAF_UNKNOWN_USERNAME - Unified CM sent the SAF Forwarder an
Application User name that is not configured on the router or that does not
match the router's configuration. Check the Application User Name on the
router and in the Application User Configuration window in Cisco Unified
CM Administration to be sure they match.
438
**INFO LEVEL** SAF_STALE_NONCE - A nonce (a random parameter
generated when the message is sent) has aged out (gone stale). The system
will resend with a new nonce automatically. No action is required.
471
**INFO LEVEL** SAF_BAD_CLIENT_HANDLE SAF_BAD_CLIENT_HANDLE - Unified CM sent the SAF Forwarder a
Register message (for KeepAlive purposes) or unregister message with the
mandatory CLIENT_HANDLE value, but the SAF Forwarder did not
recognize the client handle. Unified CM will attempt to reregister with the
SAF Forwarder without a client handle. This alarm is for informational
purposes only; no action is required.
472
**INFO LEVEL** SAF_VERSION_NUMBER_TOO_LOW - Unified CM
published a service (such as Hosted DN) whose version number is now lower
than when it was previously published to the SAF Forwarder. The service is
out of sync with the SAF Forwarder. Unified CM will republish the service
in an attempt to resynch with the SAF Forwarder. This alarm is for informational purposes only; no action is required.
473
**INFO LEVEL** SAF_UNKNOWN_SERVICE - Unified CM attempted
to unpublish a service from the SAF network but the SAF Forwarder does not
have a publish record for that service. This alarm is for informational
purposes only; no action is required.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
6-120
OL-20105-01
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Error-Level Alarms
Value
Definition
474
**INFO LEVEL** SAF_UNREGISTERED - Unified CM attempted to
publish or subscribe to the SAF Forwarder, but Unified CM is not registered
with SAF Forwarder. Unified CM will automatically reregister with the SAF
Forwarder before attempting to publish or subscribe. This alarm is for informational purposes only; no action is required.
475
**INFO LEVEL** SAF_BAD_FILTER - Unified CM attempted to
subscribe to the SAF Forwarder with a filter that does not match any of the
SAF Forwarder's current filters. Unified CM will resend the subscribe
message with the appropriate filter value. This alarm is for informational
purposes only; no action is required.
476
SAF_UNKNOWN_SUBSCRIPTION - Unified CM sent a subscribe or unsubscribe message to the SAF Forwarder but the message contained a Service
ID that was not familiar to the SAF Forwarder. Without a recognized Service
ID, Unified CM cannot subscribe to the SAF Forwarder. Recommended
action is to contact the Cisco Technical Assistance Center (TAC).
477
**INFO LEVEL** SAF_ALREADY_REGISTERED - Unified CM
attempted to register with the SAF Forwarder but SAF Forwarder indicates
that Unified CM is already registered. Unified CM will close and reopen the
TCP connection and send a new register request without a client handle to
SAF Forwarder. This alarm is for informational purposes only; no action is
required.
478
SAF_UNSUPPORTED_PROTOCOL_VERSION - Unified CM attempted to
register with the SAF Forwarder using a SAF protocol version number that
is greater than the protocol version number supported by the SAF Forwarder.
Issue a show version command on the SAF Forwarder CLI to determine the
SAF Forwarder protocol version; refer to the information in this alarm for the
SAF protocol version number. If the versions do not match, check the Cisco
Unified Communications Manager Software Compatibility Matrix (available
on Cisco.com) to determine whether the SAF protocol version number that is
in use on this Unified CM is compatible with the SAF Forwarder protocol
version. If it is not, upgrade the lower-versioned component so that both
Unified CM and the SAF Forwarder use the same, compatible version.
479
SAF_UNKNOWN_AS - Unified CM attempted to register to the SAF
Forwarder but the registration message contained a Client Label that was not
familiar to the Autonomous System (AS) on the SAF Forwarder router. Recommended action is to issue the appropriate CLI commands on the SAF
Forwarder to associate the Client Label with the autonomous system on the
router (refer to the Configuration Guide for the router) and configure the
same Client Label in the Client Label field on the SAF Forwarder Configuration window in Cisco Unified CM Administration and click Save. When
the Client Label is saved in Cisco Unified CM Administration, Unified CM
automatically sends a new registration request to the SAF Forwarder with the
updated Client Label information.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
6-121
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Error-Level Alarms
Value
Definition
500
**INFO LEVEL** SAF_RESPONDER_ERROR - Unified CM sent a
message (such as register/unregister/publish/unpublish/subscribe) to the
SAF Forwarder but the SAF Forwarder responded that it is unable to process
the message at this time. This might be due to heavy message queuing,
internal resource issues, and so on. Unified CM will wait several seconds and
then retry the request. This alarm is for informational purposes only; no
action is required.
1000
SAF_INVALID_CONNECTION_DETAILS
SerialPortGetStatusError
When CMI tries to get the status of serial port, the operating system returns an error.
CMI triggers this alarm when it cannot get the status of the serial port. An inability to receive the serial
port status information can be caused by a loose or disconnected USB cable.
History
Cisco Unified Communications
Release
Action
8.0(1)
Name changed from kSerialPortGetStatusError.
Cisco Unified Serviceability Alarm Definition Catalog
CMIAlarmCatalog/CMI
Severity
ERROR
Routing List
Event Log
SDI
Parameter(s)
Serial Port Getting Status Error(String)
Recommended Action
Make sure that the cable connecting the USB0 port and voice messaging system is firmly connected.
SerialPortSetStatusError
When CMI tries to set the status of serial port, the operating system returns an error.
CMI triggers this alarm when it cannot set the status of the serial port. An inability to receive the serial
port status information can be caused by a loose or disconnected USB cable.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
6-122
OL-20105-01
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Error-Level Alarms
History
Cisco Unified Communications
Release
Action
8.0(1)
Name changed from kSerialPortSetStatusError.
Cisco Unified Serviceability Alarm Definition Catalog
CMIAlarmCatalog/CMI
Severity
ERROR
Routing List
Event Log
SDI
Parameter(s)
Serial Port Setting Status Error(String)
Recommended Action
Make sure that the cable connecting the USB0 port and voice messaging system is firmly connected.
UnableToRegisterwithCallManagerService
CTI cannot communicate with Cisco CallManager service to register supplementary service features.
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/CtiManager
Severity
ERROR
Routing List
SDL
SDI
Sys Log
Event Log
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.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
6-123
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Error-Level Alarms
WritingFileFailure
CMI failed to write SMDI messages to the serial port.
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.
History
Cisco Unified Communications
Release
Action
8.0(1)
Name changed from kWritingFileFailure.
Cisco Unified Serviceability Alarm Definition Catalog
CMIAlarmCatalog/CMI
Severity
ERROR
Routing List
Event Log
SDI
Parameter(s)
Error Information(String)
Recommended Action
Make sure that the cable connecting the USB0 port and voice messaging system is firmly connected.
ConnectionFailure
Cisco CallManager failed to open TLS connection for the indicated device. Possible reasons could be
wrong "Device Security Mode" configured, wrong "X.509 Subject Name" configured or unsupported
cipher algorithm.
Facility/Sub-Facility
CCM_CALLMANAGER-CALLMANAGER
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/CallManager
Severity
Error (3)
Parameters
Device Name. [String] IP Address [String] Device type. [Optional] [Enum]Device description
[Optional]. [String] Reason code [Enum]
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
6-124
OL-20105-01
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Error-Level Alarms
Enum Definitions for DeviceType
Value
Definition
1
CISCO_30SP+
2
CISCO_12SP+
3
CISCO_12SP
4
CISCO_12S
5
CISCO_30VIP
6
CISCO_7910
7
CISCO_7960
8
CISCO_7940
9
CISCO_7935
12
CISCO_ATA_186
20
SCCP_PHONE
61
H323_PHONE
72
CTI_PORT
115
CISCO_7941
119
CISCO_7971
131
SIP_TRUNK
255
UNKNOWN
302
CISCO_7989
307
CISCO_7911
308
CISCO_7941G_GE
309
CISCO_7961G_GE
335
MOTOROLA_CN622
336
BASIC_3RD_PARTY_SIP_DEVICE
348
CISCO_7931
358
CISCO_UNIFIED_COMMUNICATOR
365
CISCO_7921
369
CISCO_7906
374
ADVANCED_3RD_PARTY_SIP_DEVICE
375
CISCO_TELEPRESENCE
404
CISCO_7962
412
CISCO_3951
431
CISCO_7937
434
CISCO_7942
435
CISCO_7945
436
CISCO_7965
437
CISCO_7975
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
6-125
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Error-Level Alarms
446
CISCO_3911
468
CISCO_UNIFIED_MOBILE_COMMUNICATOR
478
CISCO_TELEPRESENCE_1000
479
CISCO_TELEPRESENCE_3000
480
CISCO_TELEPRESENCE_3200
481
CISCO_TELEPRESENCE_500
484
CISCO_7925
493
CISCO_9971
495
CISCO_6921
496
CISCO_6941
497
CISCO_6961
20000
CISCO_7905
30002
CISCO_7920
30006
CISCO_7970
30007
CISCO_7912
30008
CISCO_7902
30016
CISCO_IP_COMMUNICATOR
30018
CISCO_7961
30019
CISCO_7936
30035
IP_STE
Enum Reasons
Code
Reason
1
AuthenticationError
2
InvalidX509NameInCertificate
4
InvalidTLSCipher
Recommended Action
Check the Security profile of the indicated device. Make sure "Device Security Mode" is either
"Authenticated" or "Encrypted". Make sure "X.509 Subject Name" field has the right content. It should
match the Subject Name in the certificate from the peer. Unified CM only supports AES_128_SHA
cipher algorithm. Let the peer regenerate its certificate with the right algorithm.
RTMT_ALERT
A Real-Time Monitoring Tool (RTMT) process in the AMC service uses the alarm mechanism to
facilitate delivery of RTMT alerts in the RTMT AlertCentral or through email.
Cisco Unified Serviceability Alarm Definition Catalog
System/RTMT
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
6-126
OL-20105-01
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Error-Level Alarms
Severity
ERROR
Routing List
Event Log
Sys Log
Parameter(s)
Name(String)
Detail(String)
Recommended Action
Check AlertCentral in RTMT or any alerts that you have received through 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.
DeviceInitTimeout
Device initialization timeout occurred. This alarm does not occur under normal working conditions; it
will only occur if a device fails to respond to an initialize request.
Facility/Sub-Facility
CCM_CALLMANAGER-CALLMANAGER
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/CallManager
Severity
Error (3)
Parameters
Device Name [String] Protocol [String] Side Number [UInt]
Recommended Action
Investigate the identified device.
NumDevRegExceeded
The allowed number of registered devices was exceeded.
Facility/Sub-Facility
CCM_CALLMANAGER-CALLMANAGER
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/CallManager
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
6-127
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Error-Level Alarms
Severity
Error (3)
Parameters
Maximum Devices [Int]
Recommended Action
If you did not expect to exceed the number of devices and you have auto-registration enabled, go to
Device > Phones in Cisco Unified CM Administration and search for phones starting with "auto". If you
see any unexpected devices which may not belong in the system (such as intruder devices) locate that
device using it's IP address and remove it from the system. Or, if your licenses and system resources
allow, increase the value in the Cisco CallManager service parameter, Maximum Number of Registered
Devices.
RsvpNoMoreResourcesAvailable
RSVP Agent resource allocation failed.
The alarm occurs when allocation of an RSVP Agent fails for all the registered RSVP Agents (RSVP
Agents are basically MTPs or transcoder devices which provide RSVP functionalities) belonging to the
Media Resource Group List and Default List. Each RSVP Agent may fail for different reasons.
Following are some of the reasons that could cause an RSVP Agent allocation to fail: available
MTP/transcoders do not support RSVP functionality; a capability mismatch between the device endpoint
and MTP/transcoder, codec mismatch between the endpoint and the MTP/transcoder; a lack of available
bandwidth between the endpoint and the MTP/transcoder; or because the MTP/transcoder resources are
already in use.
A capability mismatch may be due to the MTP/transcoder not supporting one or more of the required
capabilities for the call such as Transfer Relay Point (which is needed for QoS or firewall traversal), RFC
2833 DTMF (which is necessary when one side of the call does not support RFC 2833 format for
transmitting DTMF digits and the other side must receive the DTMF digits in RFC2833 format, resulting
in conversion of the DTMF digits), RFC 2833 DTMF passthrough (in this case, the MTP or transcoder
does not need to convert the DTMF digits from one format to another format but it needs to receive
DTMF digits from one endpoint and transmit them to the other endpoint without performing any
modifications), passthrough (where no codec conversion will occur, meaning the media device will
receive media streams in any codec format and transmit them to the other side without performing any
codec conversion), IPv4 to IPv6 conversion (when one side of the call supports only IPv4 and the other
side of the call supports only IPv6 and so MTP needs to be inserted to perform the necessary conversion
between IPv4 and IPv6 packets), or multimedia capability (if a call involving video and/or data in
addition to audio requires insertion of an MTP or transcoder then the MTP/transcoder which supports
multimedia will be inserted).
History
Cisco Unified Communications
Release
Action
8.0(1)
Media Resource List Name(String) parameter is added.
Facility/Sub-Facility
CCM_CALLMANAGER-CALLMANAGER
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
6-128
OL-20105-01
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Error-Level Alarms
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/CallManager
Severity
Error (3)
Parameter(s)
Media Resource List Name(String)
Recommended Action
RSVP Agents are basically Cisco IOS MTPs or transcoder devices which provide RSVP functionalities.
Check the user manual of the configured MTPs and transcoders to see whether they support RSVP
functionality. If none of them support RSVP functionality either they need to be upgraded (if upgraded
version support RSVP functionality) or additional MTP or transcoders need to be installed which support
RSVP functionality. If the RSVP Agent (MTP or transcoder) allocation is failing due to a capability
mismatch, it's possible that the media device does not support the requested capability (such as IPv4 to
IPv6 conversion, passthrough) or the capability might not be configured in the device. Please check the
user guide and documentation of the media device to make sure that device supports all the necessary
capabilities.
Also, caution should be taken care if all the MTP or transcoders are configured with all the supported
capabilities. There are certain capabilities (such as RFC 2833 DTMF or RFC 2833 DTMF passthrough
or passthrough) which could be supported by most of the MTPs or transcoders and there may be certain
capabilities (such as IPv4 to IPv6 conversion and vice versa or RSVP Agent functionality or Transfer
Relay Point or multimedia capability) which can be supported by only by a single MTP or transcoder
depending on the devices that you have.
For example, you may have end devices belonging to different locations and may need to reserve the
bandwidth only between two locations; calls between other locations may not need to reserve the
bandwidth. Now, suppose all the MTPs or transcoders are configured with all the supported capabilities
and only one MTP/transcoder supports RSVP functionality; if this MTP/transcoder is configured with
all the supported capabilities (which all the other MTPs or transcoders in the same MRGL or default
MRGL also support) it may happen that this MTP can get allocated for Transfer Relay Point or RFC
2833 DTMF or RFC 2833 DTMF passthrough or passthrough instead. As a result, when a need arises to
reserve the bandwidth (which other MTPs or transcoders in the same MRGL or default MRGL do not
support), all the resources of this MTP/transcoder may be in use and the RSVP Agent allocation may fail.
To avoid this situation, set the priority of the media resources appropriately. This can be done only in
the Media Resource Group List and not in the Default List of the media resources. In any Media
Resource Group List all the Media Resource Groups have different priorities and during allocation the
first Media Resource Group is checked for availability of the requested type of the media devices. The
first Media Resource Group in the Media Resource Group List will have the highest priority, then the
second one and so on. To check all the Media Resource Groups and their priority go the Media Resources
and Media Resource Group List of Cisco Unified CM Administration page and click the appropriate
Media Resource Group List and check the Selected Media Resource Groups; the priority decreases from
top to bottom. Position the MTP or transcoder that you want to be selected for the basic functionalities
in the higher priority Media Resource Groups whereas the ones with more rare functionality can be
positioned in the Media Resource Groups with lower priority. RSVP Agent allocation may fail due to
codec mismatch between the end point and the RSVP Agent or MTP/transcoder.
A solution may be to configure the MTP/transcoder with all the supported codecs (as specified in the
user guide of the MTP/transcoder), but be aware that doing so might result in too much bandwidth being
allocated for calls. You'll need to weigh different factors such as the total amount of available
bandwidth, the average number of calls, approximate bandwidth use per call (not involving
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
6-129
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Error-Level Alarms
MTP/transcoder), and so on, and accordingly calculate the maximum bandwidth that can be allocated
per call involving an MTP/transcoder and take that into consideration when configuring the supported
codecs in the MTPs and transcoders. A good idea is to configure the media devices with all the supported
codecs and set the region bandwidths to restrict too much bandwidth usage (refer to the Unified CM
documentation for details on region and location settings).
Also, there may be codec mismatch between the endpoint and the MTP/transcoders after considering the
region bandwidth between the MTP/transcoder and the endpoint. Increasing the region bandwidth may
be a solution to the problem, but that decision should be made after careful consideration of the amount
of bandwidth you're willing to allocate per call between the set of regions.
Another possible cause that an MTP/transcoder did not get allocated is because there was not enough
available bandwidth for the call. This can happen if the MTP/transcoder and endpoint belong to different
locations and the bandwidth that is set between the locations is already in use by other calls. Examine
the bandwidth requirements in your deployment to determine whether bandwidth between the locations
can be increased. However, note that increasing the bandwidth between these two locations means that
you may need to reduce the bandwidth between other locations.
Refer to the System Guide, SRNDs, and related Unified CM documentation for more details. Be aware
that reducing the bandwidth or removing the higher bandwidth codecs from configuration may result in
poor voice quality during call. Consider increasing the total amount of network bandwidth. Finally, if
RSVP Agent allocation fails due to MTP/transcoder not supporting RSVP functionality or capability
mismatch or all the resources being in use, consider installing additional MTP or transcoder devices
which support RSVP functionality.
ICTCallThrottlingStart
Cisco CallManager stops handling calls for the indicated H.323 device due to heavy traffic or a route
loop over the H.323 trunk.
Cisco Unified Communications Manager has detected a route loop over the H.323 trunk indicated in this
alarm. As a result, Unified CM has temporarily stopped accepting calls for the indicated H.323 trunk.
It's also possible that a high volume of calls are occurring over the intercluster trunk, which has triggered
throttling.
Facility/Sub-Facility
CCM_CALLMANAGER-CALLMANAGER
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/CallManager
Severity
Error (3)
Parameters
Device Name [String] IP Address [String] Device type. [Optional] [Enum]Device description
[Optional]. [String]
Enum Definitions for DeviceType
125—TRUNK
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
6-130
OL-20105-01
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Error-Level Alarms
Recommended Action
In Real-Time Monitoring Tool, check the CallsActive and CallsInProgress counters for unusual activity
on the indicated H.323 trunk. If the CallsActive count is significantly higher than usual, a traffic load
issue may be occurring where the demand to send calls over the trunk is greater than the trunk's capacity.
Monitor the situation and collect existing trace files. If the ICTCallThrottlingEnd alarm is not issued in
a reasonable amount of time as deemed by your organization, contact TAC and supply the trace
information you have collected. For a routing loop condition, the CallsInProgress counter will be
significantly higher than usual. By examining trace files and CDR data for calls that occurred over the
indicated trunk, you may be able to detect a translation pattern, route list or other routing mechanism
that is part of the loop. Update the routing mechanism that resulted in the loop (generally the same
number is configured on both near end and far end devices) and then reset the affected route list in an
attempt to clear the route loop and if that fails, reset the affected trunk.
DeviceCloseMaxEventsExceeded
The TCP socket for the SCCP device has been closed due to excessive events in a 5-second period.
Under normal conditions, the device will reregister automatically.
The indicated SCCP device exceeded the maximum number of events allowed per-SCCP device. Events
can be phone calls, KeepAlive messages, or excessive SCCP or non-SCCP messages. The maximum
number of allowed events is controlled by the Cisco CallManager service parameter, Max Events
Allowed. When an individual device exceeds the number configured in that service parameter, Unified
CM closes the TCP connection to the device; automatic reregistration generally follows. This action is
an attempt to stop malicious attacks on Unified CM or to ward off excessive CPU usage.
Facility/Sub-Facility
CCM_CALLMANAGER-CALLMANAGER
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/CallManager
Severity
Error (3)
Parameters
Total Events Received [UInt] IP Address [String] TCP Handle [String] Max Events Allowed [UInt]
Number Of Skinny Device Throttled [UInt]
Recommended Action
Check the CCM trace data for the indicated SCCP device to determine the reason for the high number
of events. Confirm that the value configured in the Cisco CallManager service parameter, Max Events
Allowed, is a suitable number for your deployment.
InvalidIPNetPattern
An invalid IP address is configured in one or more SIP route patterns in Cisco Unified CM
Administration.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
6-131
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Error-Level Alarms
Facility/Sub-Facility
CCM_CALLMANAGER/CALLMANAGER
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/CallManager
Severity
Error (3)
Parameters
Description(String)
IPAddress(String)
DeviceName(String)
Recommended Action
In Cisco Unified CM Administration, verify that the route pattern associated with the device that is
identified in this alarm has an accurate and working IP address. You can learn more how to ensure that
the IP address is valid by reviewing RFC 2373.
CDRFileDeliveryFailed
FTP delivery of CDR files to the Billing Server outside of the cluster failed because of timeout or other
reasons. E-mail alert will be sent to the admin.
History
Cisco Unified Communications
Release
Action
8.0(1)
Changed Data Collector Routing List element to Alert Manager.
Facility/Sub-Facility
CDRManagement/CDRREP
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/CDR Rep
Severity
Error (3)
Routing List
Event Log
Sys Log
Alert Manager
Parameters
BillingServerAddress [String]
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
6-132
OL-20105-01
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Error-Level Alarms
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.
CDRAgentSendFileFailed
CDR Agent cannot send CDR files from CCM node to CDR Repository node within the CCM cluster
because of timeout or other reasons. E-mail alert will be sent to the admin.
History
Cisco Unified Communications
Release
Action
8.0(1)
Changed Data Collector Routing List element to Alert Manager.
Facility/Sub-Facility
CDRREP
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/CDR Rep
Severity
Error (3)
Routing List
Event Log
Sys Log
Alert Manager
Parameters
CDRRepositoryNodeAddress [String]
CDRAgentNodeAddress [String]
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.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
6-133
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Error-Level Alarms
7.
Check if the Publisher is being upgraded. If the CDRAgentSendFileFailureContinues alarm is no
longer present, the condition is corrected.
CDRFileDeliveryFailureContinues
(s)FTP delivery of CDR files failed on retries to the Billing Server outside of the cluster failed on retries
after the initial failure.
Facility/Sub-Facility
CCM_CDR_REP-CDRREP
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/CDR Rep
Severity
Error (3)
Routing List
Event Log
Sys Log
Data Collector
Parameters
BillingServerAddress [String]
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.
CDRAgentSendFileFailureContinues
CDR Agent cannot send CDR files from CCM node to CDR Repository node on retries. CDR Agent
cannot send CDR files on retries after the initial failure from CCM node to CDR Repository node within
the cluster.
Facility/Sub-Facility
CCM_CDR_REP-CDRREP
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/CDR Rep
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
6-134
OL-20105-01
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Error-Level Alarms
Severity
Error
Routing List
Event Log
Sys Log
Data Collector
Parameters
CDRRepositoryNodeAddress [String]
CDRAgentNodeAddress [String]
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.
CARSchedulerJobFailed
Critical CAR scheduled job failed. The jobs are PopulateSchedules, DailyCdrLoad, TaskMonitor, or
DatabaseMaintenance. The particular CAR scheduler job that failed cannot be run properly. This can
cause significant impact on CAR functions.
•
If PopulateSchedules job fails, CAR scheduler cannot schedule jobs to run for the day; this would
result some/all of CAR scheduler jobs cannot start.
•
If DailyCdrLoad job fails, CAR loader would not be able to load CDR/CMR records from
CDR/CMR flat files into CAR database; this would result records found upon running CAR reports,
and causes accumulation of CDR/CMR flat files unprocessed.
•
If TaskMonitor job fails, CAR scheduler will not be able to perform the daily DB IDS memory clean
up task; this would result higher DB shared memory usage.
•
If DatabaseMaintenance job fails, CAR scheduler will not be able to perform the daily optimized
database maintenance Update statistics procedures; this would result CAR database not optimized
for its operations.
Name of the service generating this alarm is CAR Scheduler service.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
6-135
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Error-Level Alarms
History
Cisco Unified Communications
Release
Action
8.0(1)
Routing list changed from Data Collector to Alert Manager and
existing parameters added.
7.0(1)
Error message added.
Facility/Sub-Facility
CAR
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/CAR Alarm Catalog
Severity
Error
Routing List
Event Log
Sys Log
Alert manager
Parameters
Job Name(String)
Job Failure Cause(String)
Job Failure Detail(String)
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.
CARSchedulerJobError
CAR scheduled job failed. A normal CAR scheduled job failed such as the pre-generated
Daily/Weekly/Monthly/Monthly-Bill reports jobs. The particular CAR scheduler job that fails cannot be
run properly. This does not cause any significant impact on CAR functions. For pre-generated CAR
report, this would result failure to run on a particular report, which leads to missing of CAR report.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
6-136
OL-20105-01
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Error-Level Alarms
History
Cisco Unified Communications
Release
Action
8.0(1)
Existing parameters added.
7.0(1)
Error message added.
Facility/Sub-Facility
CCM_CAR_SCH-CAR
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/CAR
Severity
Error (3)
Parameters
Job Name(String)
Job Failure Cause(String)
Job Failure Detail(String)
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.
BadCDRFileFound
Bad CDR or CMR flat file found during CDR Load to CAR database. The file could be corrupted.
However, CAR loader is able to skip the bad records and load the good ones to CAR database. The name
of the service generating this alarm is CAR Loader (DailyCdrLoad) job. Part of Cisco CAR Scheduler
service.
History
Cisco Unified Communications
Release
Action
8.0(1)
Existing parameters added.
7.0(1)
Error message added.
Facility/Sub-Facility
CCM_CAR_SCH-CAR
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
6-137
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Error-Level Alarms
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/CDR Rep
Severity
Error (3)
Parameters
File Name(String)
First Bad Record Cause(String)
File Summary(String)
Recommended Action
Find the bad file from the cdr_repository folders, and check its problematic record based on the
information given by the cause and summary. Collect the associated SDI and SDL traces for the bad
records found in this file as soon as possible. Collect and check the CAR Scheduler traces for more
details.
kReadCfgUserLocaleEnterpriseSvcParm
Error reading Enterprise User Locale configuration. A database exception was encountered when
reading the default Enterprise User Locale setting. Default of US English will be used.
Facility/Sub-Facility
CCM_MEDIA_STREAMING_APP-IPVMS
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/IpVms
Severity
Error (3)
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.
kPWavMgrThreadxFailed
WAV playing manager thread creation failed. The process component used for playing WAV files failed
to start, possibly due to low system resources.
Facility/Sub-Facility
CCM_MEDIA_STREAMING_APP-IPVMS
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/IpVms
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
6-138
OL-20105-01
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Error-Level Alarms
Severity
Error (3)
Parameters
OS Error Description(String)
Recommended Action
Restart the Cisco IP Voice Media Streaming App service or restart server.
ANNDeviceRecoveryCreateFailed
ANN device recovery create failure. The ANN device recovery class create 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.
History
Cisco Unified Communications
Release
Action
3.x and 4.x
Added for Windows.
8.0(1)
Added Routing List elements and Parameters.
Facility/Sub-Facility
CCM_MEDIA_STREAMING_APP-IPVMS
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/IpVms
Severity
Error (3)
Routing List
SDI
Event Log
Sys Log
Parameters
OS Error Code(Int)
OS Error Description(String)
Recommended Action
Restart the Cisco IP Voice Media Streaming App service or restart server.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
6-139
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Error-Level Alarms
kRequestedANNStreamsFailed
The requested resources for the configured number of annunciator calls (Call Count service parameter)
was not available. If the value gets shown as “Allocated,” it is non-zero.
History
Cisco Unified Communications
Release
Action
8.0(1)
Added descriptive text and Recommended Actions.
Following parameters are removed:
Requested streams [ULong] Allocated streams [ULong]
Facility/Sub-Facility
CCM_MEDIA_STREAMING_APP-IPVMS
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/IpVms
Severity
Error (3)
Recommended Action
Verify that the ANN Call Count service parameter is correct. A server restart may be needed to recover
resources.
CFBDeviceRecoveryCreateFailed
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.
History
Cisco Unified Communications
Release
Action
8.0(1)
Added Routing List elements and Parameters.
Facility/Sub-Facility
CCM_MEDIA_STREAMING_APP-IPVMS
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/IpVms
Severity
Error (3)
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
6-140
OL-20105-01
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Error-Level Alarms
Routing List
SDI
Event Log
Sys Log
Parameter(s)
OS Error Code(Int)
OS Error Description(String)
Recommended Action
Restart the Cisco IP Voice Media Streaming App service or restart server.
kCreateAudioSourcesFailed
Creating audio source class failed. Unable to create audio source subcombonent to provide audio for
streaming. This may be due to lack of memory.
History
Cisco Unified Communications
Release
Action
3.x and 4.x
Added for Windows.
7.0(1)
Obsoleted.
8.0(1)
This alarm is available in 8.0(1)
Following parameters added:
– OS Error Code(Int)
– OS Error Description(String)
Facility/Sub-Facility
CCM_MEDIA_STREAMING_APP-IPVMS
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/IpVms
Severity
Error (3)
Parameters
OS Error Code(Int)
OS Error Description(String)
Recommended Action
Restart the Cisco IP Voice Media Streaming App service or restart the server.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
6-141
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Error-Level Alarms
kCreateControlFailed
Stream Control create failure. Create stream control subcomponent. The error may be due to lack of
memory.
History
Cisco Unified Communications
Release
Action
3.x and 4.x
Added for Windows.
7.0(1)
Obsoleted.
8.0(1)
This alarm is available in 8.0(1)
Following parameters added:
– OS Error Code(Int)
– OS Error Description(String)
Facility/Sub-Facility
CCM_MEDIA_STREAMING_APP-IPVMS
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/IpVms
Severity
Error (3)
Parameters
Codec Type [String]
OS Error Code [Int]
OS Error Description [String]
Recommended Action
Reset the MOH device. If continues to fail restart the Cisco IP Voice Media Streaming App service or
restart the server.
kIPVMSDeviceDriverNotFound
Cisco IP voice media streaming driver not found. 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.
History
Cisco Unified Communications
Release
Action
3.x and 4.x
Added for Windows.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
6-142
OL-20105-01
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Error-Level Alarms
History
Cisco Unified Communications
Release
Action
7.0(1)
Obsoleted.
8.0(1)
This alarm is available in 8.0(1).
Facility/Sub-Facility
CCM_MEDIA_STREAMING_APP-IPVMS
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/IpVms
Severity
Error (3)
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.
kIpVmsMgrNoLocalHostName
Unable to retrieve 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.
History
Cisco Unified Communications
Release
Action
3.x and 4.x
Added for Windows.
7.0(1)
Obsoleted.
8.0(1)
This alarm is available in 8.0(1).
Facility/Sub-Facility
CCM_MEDIA_STREAMING_APP-IPVMS
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/IpVms
Severity
Error (3)
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.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
6-143
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Error-Level Alarms
kIpVmsMgrNoLocalNetworkIPAddr
Unable to retrieve the network IP address for host server. 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.
History
Cisco Unified Communications
Release
Action
3.x and 4.x
Added for Windows.
7.0(1)
Obsoleted.
8.0(1)
This alarm is available in 8.0(1).
Facility/Sub-Facility
CCM_MEDIA_STREAMING_APP-IPVMS
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/IpVms
Severity
Error (3)
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).
kIPVMSMgrWrongDriverVersion
Wrong version of device driver. 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.
History
Cisco Unified Communications
Release
Action
3.x and 4.x
Added for Windows.
7.0(1)
Obsoleted.
8.0(1)
This alarm is available in 8.0(1).
Following parameters are removed:
•
Found [ULong]
•
Need [ULong]
Facility/Sub-Facility
CCM_MEDIA_STREAMING_APP-IPVMS
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
6-144
OL-20105-01
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Error-Level Alarms
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/IpVms
Severity
Error (3)
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.
kMOHTFTPGoRequestFailed
Transfer of MOH source file to working path failed. An error was encountered when trying to copy or
update a Music-on-Hold audio source file.
History
Cisco Unified Communications
Release
Action
3.x and 4.x
Added for Windows.
7.0(1)
Obsoleted.
8.0(1)
This alarm is available in 8.0(1).
Following parameters added:
Error Description [String] Source Path [String]
Destination Path [String] OS Error Code [Int]
OS Error Description [String]
Facility/Sub-Facility
CCM_MEDIA_STREAMING_APP-IPVMS
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/IpVms
Severity
Error (3)
Parameters
Error Description [String] File Name [String] Source Path [String] Destination Path [String]
OS Error Code [Int] OS Error Description [String]
Recommended Action
Use the Platform CLI to verify the source path and file exist. If the file does not exist then use Cisco
Unified CM Admin to reupload the missing audio source to this specific server. Reinstall the Cisco
Unified Communications Manager to have all required paths created.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
6-145
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Error-Level Alarms
DBLGetVersionInfoError
DBL GetVersionInfo function returned NULL.
Facility/Sub-Facility
CCM_TCD-TCD
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/TCD SRV
Severity
Error (3)
Recommended Action
None
UserLoginFailed
User log in failed because of bad user id or password.
Facility/Sub-Facility
CCM_TCD-TCD
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/TCD SRV
Severity
Error (3)
Parameters
UserID [String]
Recommended Action
None
kDbConnectionFailed
Database connection failed.
Facility/Sub-Facility
CCM_DB_LAYER-DB
Cisco Unified Serviceability Alarm Definition Catalog
System/DB
Severity
Error (3)
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
6-146
OL-20105-01
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Error-Level Alarms
Parameters
Additional Information [String]
Recommended Action
Enable trace for the database layer monitor to get specific error information.
ErrorReadingInstalledRPMS
Could not read installed RPMs to populate component version table. The function that reads the rpm
version information and populates database failed.
Facility/Sub-Facility
CCM_DB_LAYER-DB
Cisco Unified Serviceability Alarm Definition Catalog
System/DB
Severity
Error (3)
Recommended Action
Report this error to the administrator.
ErrorChangeNotifyClientTimeout
A change notification client was responding slowly and has been removed. A change notification
recipient has not responded to change notification in several minutes and was thus removed. This may
delay call processing features, such as call forwarding and so on.
History
Cisco Unified Communications
Release
Action
8.0(1)
Added Routing List elements and deleted Data Collector element.
Facility/Sub-Facility
CCM_DB_LAYER-DB
Cisco Unified Serviceability Alarm Definition Catalog
System/DB
Severity
Error (3)
Routing List
SDI
Event Log
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
6-147
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Error-Level Alarms
Sys Log
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.
IDSEngineFailure
Combined alarm for emergency and error situations. Something unexpected occurred that might
compromise data or access to data or cause IDS to fail. 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
Facility/Sub-Facility
CCM_DB_LAYER-DB
Cisco Unified Serviceability Alarm Definition Catalog
System/DB
Severity
Error (3)
Parameters
Event Class ID [String] Event class message [String] Event Specific Message [String]
Recommended Action
Requires Database Admin. intervention
IDSReplicationFailure
Combined alarm for emergency and error situations. IDS Replication has failed.
History
Cisco Unified Communications
Release
8.0(1)
Action
Route Listing element Data Collector changed to Alert Manager and
existing parameters added.
Facility/Sub-Facility
DB
Cisco Unified Serviceability Alarm Definition Catalog
System/DB
Severity
Error (3)
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
6-148
OL-20105-01
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Error-Level Alarms
Routing List
SDI
Event Log
Sys Log
Alert Manager
Parameters
Event Class ID [String]
Event class message [String]
Event Specific Message [String]
Recommended Action
Requires Database Admin. intervention.
IPMAApplicationError
IPMA Facility/Sub-Facility error.
Facility/Sub-Facility
CCM_JAVA_APPS-TOMCATAPPLICATIONS
Cisco Unified Serviceability Alarm Definition Catalog
System/Java Applications
Severity
Error (3)
Parameters
Servlet Name [String] Reason [String]
Recommended Action
See application logs for details
IPMAOverloaded
IPMA Facility/Sub-Facility overloaded.
Facility/Sub-Facility
CCM_JAVA_APPS-TOMCATAPPLICATIONS
Cisco Unified Serviceability Alarm Definition Catalog
System/Java Applications
Severity
Error (3)
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
6-149
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Error-Level Alarms
Parameters
Servlet Name [String] Reason [String]
Recommended Action
See application logs for details
IPMAFilteringDown
IPMA application filtering is down.
Facility/Sub-Facility
CCM_JAVA_APPS-TOMCATAPPLICATIONS
Cisco Unified Serviceability Alarm Definition Catalog
System/Java Applications
Severity
Error (3)
Parameters
Servlet Name [String] Reason [String]
Recommended Action
Restart Cisco IP Manager Assistant Service.
BDIApplicationError
BDI Facility/Sub-Facility error.
Facility/Sub-Facility
CCM_JAVA_APPS-TOMCATAPPLICATIONS
Cisco Unified Serviceability Alarm Definition Catalog
System/Java Applications
Severity
Error (3)
Parameters
Reason [String]
Recommended Action
See application logs for details
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
6-150
OL-20105-01
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Error-Level Alarms
BDIOverloaded
BDI Facility/Sub-Facility overloaded.
Facility/Sub-Facility
CCM_JAVA_APPS-TOMCATAPPLICATIONS
Cisco Unified Serviceability Alarm Definition Catalog
System/Java Applications
Severity
Error (3)
Parameters
Reason [String]
Recommended Action
See application logs for details
WDApplicationError
WebDialer Facility/Sub-Facility error.
Facility/Sub-Facility
CCM_JAVA_APPS-TOMCATAPPLICATIONS
Cisco Unified Serviceability Alarm Definition Catalog
System/Java Applications
Severity
Error (3)
Parameters
Servlet Name [String] Reason [String]
Recommended Action
See application logs for details
WDOverloaded
WebDialer Facility/Sub-Facility overloaded.
Facility/Sub-Facility
CCM_JAVA_APPS-TOMCATAPPLICATIONS
Cisco Unified Serviceability Alarm Definition Catalog
System/Java Applications
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
6-151
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Error-Level Alarms
Severity
Error (3)
Parameters
Servlet Name [String] Reason [String]
Recommended Action
See application logs for details
CiscoDirSyncProcessFailedRetry
LDAPSync process failed on particular sync agreement.
Facility/Sub-Facility
CCM_JAVA_APPS-TOMCATAPPLICATIONS
Cisco Unified Serviceability Alarm Definition Catalog
System/Java Applications
Severity
Error (3)
Parameters
AgreementId [String] Reason [String]
Recommended Action
The sync process will automatic retry. See application logs for details.
CiscoDirSyncProcessFailedNoRetry
LDAPSync process failed on particular sync agreement
Facility/Sub-Facility
CCM_JAVA_APPS-TOMCATAPPLICATIONS
Cisco Unified Serviceability Alarm Definition Catalog
System/Java Applications
Severity
Error (3)
Parameters
AgreementId [String] Reason [String]
Recommended Action
See application logs for details, the application will try to sync again in the next scheduled time
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
6-152
OL-20105-01
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Error-Level Alarms
CiscoDirSyncProcessConnectionFailed
LDAPSync process failed to connect to LDAP server.
Facility/Sub-Facility
CCM_JAVA_APPS-TOMCATAPPLICATIONS
Cisco Unified Serviceability Alarm Definition Catalog
System/Java Applications
Severity
Error (3)
Parameters
AgreementId [String] LDAPHost [String] Reason [String]
Recommended Action
Ensure that 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
CiscoDirSyncDBAccessFailure
LDAPSync process failed to access local database.
Facility/Sub-Facility
CCM_JAVA_APPS-TOMCATAPPLICATIONS
Cisco Unified Serviceability Alarm Definition Catalog
System/Java Applications
Severity
Error (3)
Parameters
AgreementId [String] Reason [String]
Recommended Action
Ensure that the local CallManager database is working properly. The failed sync process will restart at
the next scheduled time.
DirSyncScheduledTaskFailed
Directory synchronization task failed.
Facility/Sub-Facility
CCM_JAVA_APPS-TOMCATAPPLICATIONS
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
6-153
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Error-Level Alarms
Cisco Unified Serviceability Alarm Definition Catalog
System/Java Applications
Severity
Error (3)
Parameters
SchedulerID [String] ErrorMessage [String]
Recommended Action
Check the DirSync configuration and logs
DirSyncSchedulerFailedToGetDBSchedules
Failed to get directory synchronization schedules from DB.
Facility/Sub-Facility
CCM_JAVA_APPS-TOMCATAPPLICATIONS
Cisco Unified Serviceability Alarm Definition Catalog
System/Java Applications
Severity
Error (3)
Parameters
Message [String]
Recommended Action
Check the DirSync configuration and logs.
DirSyncSchedulerInvalidEventReceived
Invalid event received by DirSync scheduler from database.
Facility/Sub-Facility
CCM_JAVA_APPS-TOMCATAPPLICATIONS
Cisco Unified Serviceability Alarm Definition Catalog
System/Java Applications
Severity
Error (3)
Parameters
Action [String] Message [String]
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
6-154
OL-20105-01
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Error-Level Alarms
Recommended Action
Check the DirSync configuration and logs
DirSyncInvalidScheduleFound
Invalid schedule read by DirSync scheduler from database.
Facility/Sub-Facility
CCM_JAVA_APPS-TOMCATAPPLICATIONS
Cisco Unified Serviceability Alarm Definition Catalog
System/Java Applications
Severity
Error (3)
Parameters
ScheduleID [String]
Recommended Action
Check the DirSync configuration and logs
DirSyncSchedulerFailedToRegisterDBEvents
DirSync scheduler failed to register DB notifications.
Facility/Sub-Facility
CCM_JAVA_APPS-TOMCATAPPLICATIONS
Cisco Unified Serviceability Alarm Definition Catalog
System/Java Applications
Severity
Error (3)
Parameters
ScheduleTable [String]
Recommended Action
Check the DirSync configuration and logs
DirSyncSchedulerEngineFailedToStart
DirSync scheduler engine failed to start.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
6-155
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Error-Level Alarms
Facility/Sub-Facility
CCM_JAVA_APPS-TOMCATAPPLICATIONS
Cisco Unified Serviceability Alarm Definition Catalog
System/Java Applications
Severity
Error (3)
Parameters
ScheduleTable [String]
Recommended Action
Check the DirSync configuration and logs
DirSyncScheduleDeletionFailed
DirSync schedule deletion request failed.
Facility/Sub-Facility
CCM_JAVA_APPS-TOMCATAPPLICATIONS
Cisco Unified Serviceability Alarm Definition Catalog
System/Java Applications
Severity
Error (3)
Parameters
ScheduleID [String]
Recommended Action
Check the DirSync configuration and logs
DirSyncScheduleUpdateFailed
DirSync schedule update request failed.
Facility/Sub-Facility
CCM_JAVA_APPS-TOMCATAPPLICATIONS
Cisco Unified Serviceability Alarm Definition Catalog
System/Java Applications
Severity
Error (3)
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
6-156
OL-20105-01
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Error-Level Alarms
Parameters
ScheduleID [String]
Recommended Action
Check the DirSync configuration and logs.
DRFMasterAgentStartFailure
DRF Master Agent was unable to start because it was unable to open port 4040.
History
Cisco Unified Communications
Release
Action
8.0(1)
New name changed from CiscoDRFMasterAgentStartFailure.
Routing List elements added.
Descriptive text and recommended action changed.
Facility/Sub-Facility
CCM_DRF_LOCAL & CCM_DRF_MASTER/DRF
Cisco Unified Serviceability Alarm Definition Catalog
System/DRF
Severity
Error
Routing List
Event Log
Sys Log
Parameters
Reason [String]
Recommended Action
Check if port 4040 is not already in use.
DRFLocalAgentStartFailure
DRF Local Agent was not able to start because it was unable to connect to the Master Agent on port
4040.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
6-157
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Error-Level Alarms
History
Cisco Unified Communications
Release
Action
8.0(1)
New name changed from CiscoDRFLocalAgentStartFailure.
Routing List elements added.
Descriptive text and recommended action changed.
Facility/Sub-Facility
CCM_DRF_LOCAL & CCM_DRF_MASTER/DRF
Cisco Unified Serviceability Alarm Definition Catalog
System/DRF
Severity
Error (3)
Routing List
Event Log
Sys Log
Parameters
Reason [String]
Recommended Action
Check if the CiscoDRFMaster and CiscoDRFLocal services are running.
DRFRestoreFailure
DRF Restore process encountered errors.
History
Cisco Unified Communications
Release
Action
8.0(1)
New name changed from CiscoDRFRestoreFailure.
Routing List elements added.
Descriptive text and recommended action changed.
Facility/Sub-Facility
CCM_DRF_LOCAL & CCM_DRF_MASTER/DRF
Cisco Unified Serviceability Alarm Definition Catalog
System/DRF
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
6-158
OL-20105-01
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Error-Level Alarms
Severity
Error (3)
Routing List
Event log
Sys Log
Parameters
Reason [String]
Recommended Action
Check DRF logs for further details.
DRFInternalProcessFailure
DRF internal process has some problems.
History
Cisco Unified Communications
Release
Action
8.0(1)
New name changed from CiscoDRFInternalProcessFailure.
Routing list added and recommended action changed.
Facility/Sub-Facility
CCM_DRF_LOCAL & CCM_DRF_MASTER/DRF
Cisco Unified Serviceability Alarm Definition Catalog
System/DRF
Severity
Error (3)
Routing List
Event Log
Sys Log
Parameters
Reason [String]
Recommended Action
Check DRF logs for details.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
6-159
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Error-Level Alarms
DRFTruststoreMissing
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.
History
Cisco Unified Communications
Release
Action
8.0(1)
Name changed from CiscoDRFTruststoreMissing.
Routing List elements added.
7.0(1)
Error message removed.
Facility/Sub-Facility
CCM_DRF_LOCAL & CCM_DRF_MASTER/DRF
Cisco Unified Serviceability Alarm Definition Catalog
System/DRF
Severity
Error (3)
Routing List
Event Log
Sys Log
Parameters
Reason(String)
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.
DRFUnknownClient
The DRF Master Agent running on the Publisher has received a Client connection request from an
unknown server outside the cluster.The request has been rejected.
History
Cisco Unified Communications
Release
Action
8.0(1)
Name changed from CiscoDRFUnknownClient.
Routing List elements added.
7.0(1)
Error message removed.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
6-160
OL-20105-01
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Error-Level Alarms
Facility/Sub-Facility
CCM_DRF_LOCAL & CCM_DRF_MASTER/DRF
Cisco Unified Serviceability Alarm Definition Catalog
System/DRF
Severity
Error (3)
Routing List
event Log
Sys Log
Parameters
Reason(String)
Recommended Action
Remove the suspect server from the network. Refer to the Reason section for suspect servers: Hostname
and IP Address.
DRFSecurityViolation
The DRF System has detected a malicious pattern which could result in a security violation. 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.
History
Cisco Unified Communications
Release
Action
8.0(1)
Name changed from CiscoDRFSecurityViolation.
Routing List elements added.
Facility/Sub-Facility
CCM_DRF_LOCAL & CCM_DRF_MASTER/DRF
Cisco Unified Serviceability Alarm Definition Catalog
System/DRF
Severity
Error (3)
Routing List
Event Log
Sys Log
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
6-161
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Error-Level Alarms
Parameters
Reason(String)
Recommended Action
Stop the Cisco DRF Master and Cisco DRF Local Agent Services.
DRFBackupDeviceError
DRF Backup process is failed due to backup device error.
History
Cisco Unified Communications
Release
Action
8.0(1)
Name changed from CiscoDRFBackupDeviceError.
Routing List elements added.
Facility/Sub-Facility
CCM_DRF_LOCAL & CCM_DRF_MASTER/DRF
Cisco Unified Serviceability Alarm Definition Catalog
System/DRF
Severity
Error (3)
Routing List
Event Log
Sys Log
Parameters
Reason(String)
Recommended Action
Check if the proper device has been specified in the DRF configurations.
DRFTapeDeviceError
DRF is unable to access tape device.
History
Cisco Unified Communications
Release
Action
8.0(1)
Name changed from CiscoDRFTapeDeviceError.
Routing List elements added.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
6-162
OL-20105-01
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Error-Level Alarms
Facility/Sub-Facility
CCM_DRF_LOCAL & CCM_DRF_MASTER/DRF
Cisco Unified Serviceability Alarm Definition Catalog
System/DRF
Severity
Error (3)
Routing List
Event Log
Sys Log
Parameters
Reason(String)
Recommended Action
Check if tape drive is working properly and it contains a valid tape.
DRFRestoreInternalError
DRF Restore operation has encountered an error. Restore cancelled internally.
History
Cisco Unified Communications
Release
Action
8.0(1)
Name changed from CiscoDRFRestoreInternalError.
Routing List elements added.
Facility/Sub-Facility
CCM_DRF_LOCAL & CCM_DRF_MASTER/DRF
Cisco Unified Serviceability Alarm Definition Catalog
System/DRF
Severity
Error (3)
Routing List
Event Log
Sys Log
Parameters
Reason(String)
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
6-163
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Error-Level Alarms
Recommended Action
Check DRF logs for details.
DRFMABackupComponentFailure
DRF was unable to backup at least one component because of an error.
History
Cisco Unified Communications
Release
Action
8.0(1)
Name changed from CiscoDRFMABackupComponentFailure.
Routing List elements added.
Facility/Sub-Facility
CCM_DRF_LOCAL & CCM_DRF_MASTER/DRF
Cisco Unified Serviceability Alarm Definition Catalog
System/DRF
Severity
Error (3)
Routing List
Event Log
Sys Log
Parameters
Reason(String)
Recommended Action
Check the component backup logs and contact support if needed.
DRFMARestoreComponentFailure
DRF was unable to restore at least one component due to an error.
History
Cisco Unified Communications
Release
Action
8.0(1)
Name changed from CiscoDRFMARestoreComponentFailure.
Routing List elements added.
Facility/Sub-Facility
CCM_DRF_LOCAL & CCM_DRF_MASTER/DRF
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
6-164
OL-20105-01
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Error-Level Alarms
Cisco Unified Serviceability Alarm Definition Catalog
System/DRF
Severity
Error (3)
Routing List
Event Log
Sys Log
Parameters
Reason(String)
Recommended Action
Check the component restore logs and contact support if needed.
DRFMABackupNodeDisconnect
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.
History
Cisco Unified Communications
Release
Action
8.0(1)
Name changed from CiscoDRFMABackupNodeDisconnect.
Routing List elements added.
Facility/Sub-Facility
CCM_DRF_LOCAL & CCM_DRF_MASTER/DRF
Cisco Unified Serviceability Alarm Definition Catalog
System/DRF
Severity
Error (3)
Routing List
Event Log
Sys Log
Parameters
Reason(String)
Recommended Action
Check the computer that disconnected during backup. If the computer was accidentally shutdown, restart
the backup.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
6-165
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Error-Level Alarms
DRFNoRegisteredComponent
No registered components available, backup failed.
History
Cisco Unified Communications
Release
Action
8.0(1)
Name changed from CiscoDRFNoRegisteredComponent.
Routing List elements added.
Facility/Sub-Facility
CCM_DRF_LOCAL & CCM_DRF_MASTER/DRF
Cisco Unified Serviceability Alarm Definition Catalog
System/DRF
Severity
Error (3)
Routing List
Event Log
Sys Log
Parameters
Reason(String)
Recommended Action
Ensure at least one component is registered before attempting a backup.
DRFNoRegisteredFeature
No feature selected for backup.
History
Cisco Unified Communications
Release
Action
8.0(1)
Name changed from CiscoDRFNoRegisteredFeature.
Routing List elements added.
Facility/Sub-Facility
CCM_DRF_LOCAL & CCM_DRF_MASTER/DRF
Cisco Unified Serviceability Alarm Definition Catalog
System/DRF
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
6-166
OL-20105-01
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Error-Level Alarms
Severity
Error (3)
Routing List
Event Log
Sys Log
Parameters
Reason(String)
Recommended Action
Ensure at least one feature is configured before attempting a backup.
DRFMARestoreNodeDisconnect
The node being restored disconnected from the Master Agent prior to being fully restored.
History
Cisco Unified Communications
Release
Action
8.0(1)
Name changed from CiscoDRFMARestoreNodeDisconnect.
Routing List elements added.
Facility/Sub-Facility
CCM_DRF_LOCAL & CCM_DRF_MASTER/DRF
Cisco Unified Serviceability Alarm Definition Catalog
System/DRF
Severity
Error (3)
Routing List
Event Log
Sys Log
Parameters
Reason(String)
Recommended Action
Check the computer that disconnected during restore. If the computer was accidentally shutdown, restart
the restore.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
6-167
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Error-Level Alarms
DRFSftpFailure
DRF (s)FTP operation has failed.
History
Cisco Unified Communications
Release
Action
8.0(1)
Name changed from CiscoDRFSftpFailure.
Routing List elements added.
Facility/Sub-Facility
CCM_DRF_LOCAL & CCM_DRF_MASTER/DRF
Cisco Unified Serviceability Alarm Definition Catalog
System/DRF
Severity
Error (3)
Routing List
Event Log
Sys Log
Parameters
Reason(String)
Recommended Action
Ensure that the destination server is available, has appropriate permissions and (s)FTP daemon is
running.
DRFRegistrationFailure
DRF Registration operation failed due to an internal error.
History
Cisco Unified Communications
Release
Action
8.0(1)
Name changed from CiscoDRFRegistrationFailure.
Routing List elements added.
Facility/Sub-Facility
CCM_DRF_LOCAL & CCM_DRF_MASTER/DRF
Cisco Unified Serviceability Alarm Definition Catalog
System/DRF
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
6-168
OL-20105-01
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Error-Level Alarms
Severity
Error (3)
Routing List
Event Log
Sys Log
Parameters
Reason(String)
Recommended Action
Check the DRF logs and contact support if needed.
DRFBackupCancelInternalError
DRF Backup operation has encountered an error. Backup cancelled internally.
History
Cisco Unified Communications
Release
Action
8.0(1)
Name changed from CiscoDRFBackupCancelInternalError.
Routing List elements added.
Facility/Sub-Facility
CCM_DRF_LOCAL & CCM_DRF_MASTER/DRF
Cisco Unified Serviceability Alarm Definition Catalog
System/DRF
Severity
Error (3)
Routing List
Event Log
Sys Log
Parameters
Reason(String)
Recommended Action
Check DRF logs for details.
DRFLogDirAccessFailure
DRF could not access the log directory.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
6-169
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Error-Level Alarms
History
Cisco Unified Communications
Release
Action
8.0(1)
Name changed from CiscoDRFLogDirAccessFailure.
Routing List elements added.
Facility/Sub-Facility
CCM_DRF_LOCAL & CCM_DRF_MASTER/DRF
Cisco Unified Serviceability Alarm Definition Catalog
System/DRF
Severity
Error (3)
Routing List
Event Log
Sys Log
Parameters
Reason(String)
Recommended Action
Ensure that the DRF user has required permission/enough space on DRF Log and Trace directory.
DRFFailure
DRF Backup or Restore process has failed because it encountered errors.
History
Cisco Unified Communications
Release
Action
8.0(1)
Name changed from CiscoDRFFailure.
Changed Routing List element Data Collector to Alert Manager and
added Sys Log.
Facility/Sub-Facility
CCM_DRF_LOCAL & CCM_DRF_MASTER/DRF
Cisco Unified Serviceability Alarm Definition Catalog
System/DRF
Severity
Error (3)
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
6-170
OL-20105-01
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Error-Level Alarms
Routing List
Event Log
Alert Manager
Sys Log
Parameters
Reason(String)
Recommended Action
Check DRF logs for further details.
CiscoDhcpdFailure
DHCP Daemon stopped running. DHCP Daemon cannot be brought up due to configuration error or
crash.
Facility/Sub-Facility
CCM_JAVA_APPS-TOMCATAPPLICATIONS
Cisco Unified Serviceability Alarm Definition Catalog
System/Java Applications
Severity
Error (3)
Parameters
Reason [String]
Recommended Action
Check application log for errors and correct the configuration. May require restarting the application if
nothing found during the previous steps
CiscoLicenseManagerDown
License Manager Down and license provisioning will fail.
Facility/Sub-Facility
CCM_JAVA_APPS-TOMCATAPPLICATIONS
Cisco Unified Serviceability Alarm Definition Catalog
System/Java Applications
Severity
Error (3)
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
6-171
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Error-Level Alarms
Parameters
Reason [String]
Recommended Action
Restart License Manager service on specified node
CiscoLicenseRequestFailed
License Request Unsuccessful because it cannot fulfill the request.
Facility/Sub-Facility
CCM_JAVA_APPS-TOMCATAPPLICATIONS
Cisco Unified Serviceability Alarm Definition Catalog
System/Java Applications
Severity
Error (3)
Parameters
Reason [String]
Recommended Action
See application logs for error
CiscoLicenseDataStoreError
License Database error because it cannot fulfill the request.
Facility/Sub-Facility
CCM_JAVA_APPS-TOMCATAPPLICATIONS
Cisco Unified Serviceability Alarm Definition Catalog
System/Java Applications
Severity
Error (3)
Parameters
Reason [String]
Recommended Action
See application logs for error.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
6-172
OL-20105-01
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Error-Level Alarms
CiscoLicenseInternalError
Licensing Internal Error.
Facility/Sub-Facility
CCM_JAVA_APPS-TOMCATAPPLICATIONS
Cisco Unified Serviceability Alarm Definition Catalog
System/Java Applications
Severity
Error (3)
Parameters
Reason [String]
Recommended Action
See application logs for error.
CiscoLicenseFileError
License File Error due to an invalid or tampered license file.
Facility/Sub-Facility
CCM_JAVA_APPS-TOMCATAPPLICATIONS
Cisco Unified Serviceability Alarm Definition Catalog
System/Java Applications
Severity
Error (3)
Parameters
Reason [String]
Recommended Action
See application logs, verify that the license file is proper.
DirSyncSchedulerFailedToUpdateNextExecTime
Scheduler failed to update next execution time.
Facility/Sub-Facility
CCM_JAVA_APPS-TOMCATAPPLICATIONS
Cisco Unified Serviceability Alarm Definition Catalog
System/Java Applications
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
6-173
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Error-Level Alarms
Severity
Error (3)
Parameters
Message [String]
Recommended Action
Check the DirSync configuration and logs
DuplicateLearnedPattern
This alarm occurs when CCD requesting service received a duplicate Hosted DN.
The Call Control Discovery (CCD) requesting service received the same hosted DN from multiple call
control entities such as Unified CM Express or another Unified CM cluster. The Cisco CallManager
service parameter, Issue Alarm for Duplicate Learned Patterns, controls whether this alarm gets issued.
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/CallManager
Severity
ERROR
Routing List
SDL
SDI
Sys Log
Event Log
Parameter(s)
Client Handle(String)
Service ID(UInt)
Sub Service ID(UInt)
InstanceID1(UInt)
InstancID2(UInt)
InstanceID3(UInt)
InstanceID4(UInt)
Recommended Action
In RTMT, check the Pattern Report (CallManager > Report > Learned Pattern) and look for the duplicate
pattern identified in this alarm. Learned patterns must be unique. Determine which call control entity
(such as Unified CM or Unified CM Express) needs to be changed so that there is no duplicate pattern.
Refer to the call control entity's configuration guide (help text) to learn how to update a hosted DN
pattern. In Unified CM, to change the Hosted DN Pattern go to Cisco Unified CM Administration to
update the Hosted DN Pattern configuration (Call Routing > Call Control Discovery > Hosted DN
Patterns).
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
6-174
OL-20105-01
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Error-Level Alarms
ScheduledCollectionError
An error occurred while executing scheduled collection.
Facility/Sub-Facility
CCM_TCT-LPMTCT
Cisco Unified Serviceability Alarm Definition Catalog
System/LpmTct
Severity
Error (3)
Parameters
JobID [String] Reason [String]
Recommended Action
Review configuration for scheduled collection job under Job Status window.
SparePartitionLowWaterMarkExceeded
The percentage of used disk space in the spare partition has exceeded the configured low water mark.
Note
Spare Partition is not used for Intercompany Media Engine server. So this alert will not be triggered for
Intercompany Media Engine.
History
Cisco Unified Communications
Release
Action
7.0(1)
Error message added.
Facility/Sub-Facility
CCM_TCT-LPMTCT
Cisco Unified Serviceability Alarm Definition Catalog
System/LpmTct
Severity
Error (3)
Parameters
UsedDiskSpace [String] MessageString [Optional]. [String]
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
6-175
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Error-Level Alarms
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.
RTMT-ERROR-ALERT
This alert is generated by RTMT AlertMgr. See Alert Detail for explanation.
Facility/Sub-Facility
CCM_RTMT-RTMT
Cisco Unified Serviceability Alarm Definition Catalog
System/RTMT
Severity
Error (3)
Parameters
Name [String] Detail [String]
Recommended Action
See Alert Detail for more information.
ConfigThreadUnknownExceptionCaught
An exception is caught in the main processing routine. 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.
History
Cisco Unified Communications
Release
Action
7.0(1)
Name changed from kConfigThreadUnknownExceptionCaught.
Facility/Sub-Facility
CCM_TFTP-TFTP
Cisco Unified Serviceability Alarm Definition Catalog
System/TFTP
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
6-176
OL-20105-01
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Error-Level Alarms
Severity
Error (3)
Recommended Action
In Cisco Unified Serviceability, enable Detailed level traces in the Trace Configuration window for
TFTP service. Also, use RTMT to look for errors that may have occurred around the time of the alarm.
ErrorParsingDirectiveFromPDP
Cisco Unified Communications Manager (Unified CM) failed to parse the call routing directive or the
diversion destination in the call routing response from the policy decision point (PDP).
A routing response was received but Cisco Unified Communications Manager (Unified CM) failed to
parse the mandatory elements in the response. This means that a call routing directive or the call
diversion destination could not be parsed correctly, or that the call routing directive was not recognized.
The error may due to a syntax error or because the call routing directive is missing or the call diversion
destination is missing in the call routing response.
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/CallManager
Severity
ERROR
Routing List
SDL
SDI
Sys Log
Event Log
Parameter(s)
Policy Decision Point(String)
Called Party Number(String)
Calling Party Number(String)
Calling User Id(String)
Response XML Data(String)
Recommended Action
Check the external call control documentation, including any applicable API documentation, to
determine whether the call routing directive that was included as part of the policy obligations in the call
routing response are correctly entered according to the information defined in the external call control
documentation.
FailureResponseFromPDP
The policy decision point (PDP) returned a 4xx (client) or 5xx (server) status code in the HTTP response.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
6-177
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Error-Level Alarms
Cisco Unified Communications Manager (Unified CM) received a 4xx or 5xx response from the policy
decision point (PDP). A 4xx response indicates errors in the call routing request from Unified CM, for
example: a 400 response indicates the call routing request could not be understood by the PDP; a 404
indicates that the PDP did not find a matching request URI. A 5xx error indicates a PDP server error, for
example: a 500 response indicates a PDP internal error; A 501 response indicates that the PDP does not
support the functionality to generate a call routing response; a 503 indicates that the PDP is busy and
temporarily cannot generate a response; a 505 indicates that the HTTP version number included in the
call routing request from Unified CM is not supported. Other such errors may be responsible; please
refer to generally available guidelines on HTTP or check the RFC 2616 for detailed explanations about
HTTP Status Code definitions.
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/CallManager
Severity
ERROR
Routing List
SDL
SDI
Sys Log
Event Log
Parameter(s)
Policy Decision Point(String)
The status code and reason phrase for the failure(String)
Recommended Action
If a 4xx response caused the alarm, verify that the PDP has been accurately configured for the
functionality and call routing that you expect it to perform. If a 500 response causes the alarm, check
whether the PDP service is active and check the PDP server's log files for any errors. If a 503 causes the
alarm, the PDP may be overloaded by requests. Take appropriate action to reduce the load on the PDP
by following some or all of these recommendations: 1) consider adding more PDPs and provisioning
Unified CM with additional call intercept profiles and call intercept trigger points in the various
configuration pages under the Call Routing menu in Cisco Unified CM Administration; 2) provision a
pair of policy servers per call-intercept profile to enable load balancing; or 3) verify that the PDP server
in your deployment meets or exceed the hardware requirements specified in the documentation for Cisco
Enterprise Policy Manager (CEPM) or the third-party PDP solution you have deployed. If a 505 response
causes the alarm, check to be sure that the PDP supports HTTP version 1.1.
ReadConfigurationUnknownException
An exception is caught while retrieving enterprise parameters value from database at TFTP service
startup. This is usually caused by a failure to access the Cisco Unified Communications Manager
database.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
6-178
OL-20105-01
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Error-Level Alarms
History
Cisco Unified Communications
Release
Action
7.0(1)
Name changed from kReadConfigurationUnknownException.
Facility/Sub-Facility
CCM_TFTP-TFTP
Cisco Unified Serviceability Alarm Definition Catalog
System/TFTP
Severity
Error (3)
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 errors that may have
occurred around the time of the alarm.
SAFResponderError
SAF Responder Error 500.
This is raised when SAF forwarder doesn't know the transaction ID within SAF response from this Cisco
Unified CM.
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/CallManager
Severity
ERROR
Routing List
SDL
SDI
Sys Log
Event Log
Data Collector
Parameter(s)
Client Handle(String)
Service Id(UInt)
Sub Service ID(UInt)
Instance ID1(UInt)
Instance ID2(UInt)
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
6-179
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Error-Level Alarms
Instance ID3(UInt)
Instance ID4(UInt)
Recommended Action
No action is required.
ThreadPoolProxyUnknownException
Unknown exception was caught while processing file request. This usually indicates a lack of memory
when there is a system issue such as running out of resources.
History
Cisco Unified Communications
Release
Action
7.0(1)
Name changed from kThreadPoolProxyUnknownException.
Facility/Sub-Facility
CCM_TFTP-TFTP
Cisco Unified Serviceability Alarm Definition Catalog
System/TFTP
Severity
Error (3)
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.
IPv6InterfaceNotInstalled
IPv6 network interface is not installed. 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.
History
Cisco Unified Communications
Release
Action
7.0(1)
Added to CallManager Catalog.
Facility/Sub-Facility
CCM_TFTP-TFTP
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
6-180
OL-20105-01
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Error-Level Alarms
Cisco Unified Serviceability Alarm Definition Catalog
System/TFTP
Severity
Error (3)
Parameters
None
Recommended Action
Install IPv6 network interface and then restart TFTP service.
TestAlarmError
Testing error alarm.
Facility/Sub-Facility
CCM_CALLMANAGER-CALLMANAGER
Cisco Unified Serviceability Alarm Definition Catalog
System/Test
Severity
Error (3)
Recommended Action
None
ServiceActivationFailed
Failed to activate a service.
Facility/Sub-Facility
CCM_SERVICEMANAGER-GENERIC
Cisco Unified Serviceability Alarm Definition Catalog
System/Service Manager
Severity
Error (3)
Parameters
Service Name(String)
Reason(String)
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
6-181
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Error-Level Alarms
Recommended Action
None
ServiceDeactivationFailed
Failed to deactivate a service.
Facility/Sub-Facility
CCM_SERVICEMANAGER-GENERIC
Cisco Unified Serviceability Alarm Definition Catalog
System/Service Manager
Severity
Error (3)
Parameters
Service Name(String)
Reason(String)
Recommended Action
None
ServiceFailed
Service terminated.
Facility/Sub-Facility
CCM_SERVICEMANAGER-GENERIC
Cisco Unified Serviceability Alarm Definition Catalog
System/Service Manager
Severity
Error (3)
Parameters
Service Name(String)
Process ID(Int)
Recommended Action
None
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
6-182
OL-20105-01
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Error-Level Alarms
ServiceStartFailed
Failed to start service.
Facility/Sub-Facility
CCM_SERVICEMANAGER-GENERIC
Cisco Unified Serviceability Alarm Definition Catalog
System/Service Manager
Severity
Error (3)
Parameters
Service Name(String)
Reason(String)
Recommended Action
None
ServiceStopFailed
Failed to stop service.
Facility/Sub-Facility
CCM_SERVICEMANAGER-GENERIC
Cisco Unified Serviceability Alarm Definition Catalog
System/Service Manager
Severity
Error (3)
Parameters
Service Name(String)
Reason(String)
Recommended Action
None
ServiceExceededMaxRestarts
Service exceeded maximum allowed restarts.
Facility/Sub-Facility
CCM_SERVICEMANAGER-GENERIC
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
6-183
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Error-Level Alarms
Cisco Unified Serviceability Alarm Definition Catalog
System/Service Manager
Severity
Error (3)
Parameters
Service Name(String)
Reason(Int)
Recommended Action
If service is required to be running, restart it.
FailedToReadConfig
Service Manager failed to read configuration file.
Facility/Sub-Facility
CCM_SERVICEMANAGER-GENERIC
Cisco Unified Serviceability Alarm Definition Catalog
System/Service Manager
Severity
Error (3)
Parameters
File Name(String)
Reason(String)
Recommended Action
None
SystemResourceError
A system call failed.
Facility/Sub-Facility
CCM_SERVICEMANAGER-GENERIC
Cisco Unified Serviceability Alarm Definition Catalog
System/Service Manager
Severity
Error (3)
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
6-184
OL-20105-01
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Error-Level Alarms
Parameters
System Call(String)
Service(String)
Reason(String)
Recommended Action
None
CLM_MsgIntChkError
ClusterMgr message integrity check error. ClusterMgr has received a message which has failed a
message integrity check. This can be an indication that another node in the cluster is configured with the
wrong security password.
Facility/Sub-Facility
CCM_CLUSTERMANAGER/CLUSTERMANAGER
Cisco Unified Serviceability Alarm Definition Catalog
System/Cluster Manager
Severity
Error (3)
Operating System
Appliance
Parameters
Sender IP address(String)
Recommended Action
Verify message is coming from an expected IP address. Verify the security password on that node.
CLM_UnrecognizedHost
ClusterMgr unrecognized host. ClusterMgr has received a message from an IP address which is not
configured as a node in this cluster.
Facility/Sub-Facility
CCM_CLUSTERMANAGER/CLUSTERMANAGER
Cisco Unified Serviceability Alarm Definition Catalog
System/Cluster Manager
Severity
Error (3)
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
6-185
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Warning-Level Alarms
Operating System
Appliance
Parameters
Node IP address(String)
Recommended Action
Verify that this IP address is currently configured as a server in this cluster.
IDSEngineCritical
This alarm does not compromise data or prevent the use of the system but need to be monitored by the
Administrator.
History
Cisco Unified Communications
Release
Action
8.0(1)
Changed severity level to Error from Critical.
Facility/Sub-Facility
CCM_DB_LAYER-DB
Cisco Unified Serviceability Alarm Definition Catalog
System/DB
Severity
Error (3)
Parameters
Event Class ID [String] Event class message [String] Event Specific Message [String]
Recommended Action
This alarm needs monitoring by the db admin.
Warning-Level Alarms
The warning-level alarm is 4 and action is needed but priority of action is determined by the condition.
A warning about some bad condition, which is not necessarily an error. Configuration error or an alarm
that by itself does not indicate a warning but several instances of the same alarm do. Examples are:
•
Configuration error
•
One alarm of this level may not mean that an error has occurred but multiple of these would be
considered an error
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
6-186
OL-20105-01
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Warning-Level Alarms
AnnunciatorNoMoreResourcesAvailable
No more Annunciator resources available.
Annunciator resource allocation failed for one or more of the following reasons: all Annunciator
resources are already in use; there was a codec or capability mismatch (such as the endpoint using one
type of IP addressing such as IPv6, while the Annunciator supports only IPv4) between the endpoint and
the Annunciator resource; not enough bandwidth existed between the endpoint and the Annunciator.
History
Cisco Unified Communications
Release
Action
8.0(1)
Changed severity level from Error to Warning.
Facility/Sub-Facility
CCM_CALLMANAGER-CALLMANAGER
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/CallManager
Severity
Warning
Parameter(s)
Media Resource List Name(String)
Recommended Action
If all the resources of the Annunciator are already in use, check to be sure that all the Annunciators that
belong to the Media Resource Groups of the indicated Media Resource Group List and Default List are
configured and registered in all the applicable Unified CM nodes of the cluster. To check the registration
status go to the Media Resources > Annunciator menu and click the Find button. It will display all the
Annunciators with their status, device pool, and so on.
Check the status field to see whether it is registered with Unified CM. Note that the display on the status
field is not a confirmation that the device is registered to Unified CM. It may happen in a Unified CM
cluster that the Publisher can only write to the Unified CM database before the Publisher goes down.
Because the Subscriber may not be able to write to the database, the devices may still display registered
in Unified CM Administration after they are actually unregistered. However, if the Publisher is down
that should generate another alarm with higher priority than this alarm.
The Annunciator allocation can fail due to codec mismatch or capability mismatch between the endpoint
and the Annunciator. If there is a codec mismatch or capability mismatch (such as the endpoint using
IPv6 addressing but Annunciator supporting only IPv4), an MTP or transcoder should be allocated. So,
if the MTP or transcoder is not allocated then either MediaResourceListExhausted (with Media Resource
Type as Media termination point or transcoder) or MtpNoMoreResourcesAvailable alarm will be
generated for the same Media Resource Group List and you should first concentrate on that.
The Annunciator allocation may even fail after checking the region bandwidth between the regions to
which the held party belongs and the region to which the Annunciator belongs. Increasing the region
bandwidth may be a solution to the problem, but that decision should be made after careful consideration
of the amount of bandwidth you're willing to allocate per call between the set of regions. You'll need to
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
6-187
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Warning-Level Alarms
weigh different factors such as the total amount of available bandwidth, the average number of calls, the
average number of calls using the Annunciator, approximate bandwidth use per call, and so on, and
accordingly calculate the region bandwidth.
Another possible cause is that the bandwidth needed for the call may not be available. This can happen
if the Annunciator and endpoint belong to different locations and the bandwidth that is set between the
locations is already in use by other calls. Examine the bandwidth requirements in your deployment to
determine whether bandwidth between the locations can be increased.
However, note that increasing the bandwidth between these two locations means that you may need to
reduce the bandwidth between other locations. Refer to the System Guide, SRNDs, and related Unified
CM documentation for more details. Be aware that reducing the bandwidth or removing the higher
bandwidth codecs from configuration may result in poor voice quality during call. Consider increasing
the total amount of network bandwidth.
ApplicationConnectionDropped
Application has dropped the connection to CTIManager.
TCP or TLS connection between CTIManager and Application is disconnected.
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/CtiManager
Severity
WARNING
Routing List
SDL
SDI
Sys Log
Event Log
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).
ApplicationConnectionError
CTIManager is unable to allow connections from Applications.
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/CtiManager
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
6-188
OL-20105-01
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Warning-Level Alarms
Severity
WARNING
Routing List
SDL
SDI
Sys Log
Event Log
Parameter(s)
CTI Connection type(String)
Recommended Action
CTIManager has encountered problems initializing TCP connections. Restart the CTIManager service
to resolve this problem.
AuthenticationFailed
Login Authentication failed.
Facility/Sub-Facility
CCM_TOMCAT_APPS-LOGIN
Cisco Unified Serviceability Alarm Definition Catalog
System/Login
Severity
Warning
Parameters
Login IP Address/Hostname [String] Login Date/Time [String] Login UserID [String] Login
Interface [String]
Recommended Action
If this event happens repeatedly, investigate the source of the failed login attempts.
CallAttemptBlockedByPolicy
A call was attempted but blocked or rejected by the policy decision point (PDP).
A call was rejected or blocked because it violated the enterprise policy as defined in a policy decision
point (PDP) that was configured in Cisco Unified Communications Manager (Unified CM). The policy
server returns a call reject decision stating that a policy violation was the reason for rejecting the call.
Calls may be rejected because an unauthorized user attempted to dial a DN or pattern that is not allowed
for him or her or because a call forward directive was invoked and the destination specified in the call
forward operation violated the policy. Depending on email configuration in Real-Time Monitoring Tool
(RTMT), the system may have generated an email alert when the call was rejected.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
6-189
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Warning-Level Alarms
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/CallManager
Severity
WARNING
Routing List
SDL
SDI
Sys Log
Event Log
Alert Manager
Parameter(s)
Policy Decision Point(String)
Reject Reason(String)
Called Party Number(String)
Calling Party Number(String)
Calling User Id(String)
Recommended Action
Evaluate the information provided in this alarm (caller's user ID, to and from DNs, and so on) to
determine if the call attempt was an innocent mistake to dial a number that the user didn't realize was
not routable for him or her, or to discover whether the user is intentionally trying to circumvent the
policy restrictions. If the rejected call was caused by an innocent mistake, educate the affected user about
the numbers that he or she is allowed to dial. Your organization may have a policy or guidelines to follow
when investigating call rejects. In addition to or instead of the steps recommended here, please refer to
your company's guidelines.
CCDLearnedPatternLimitReached
CCD has reached the maximum number of learned patterns allowed.
The CCD requesting service has limited the number of learned patterns to a number defined in the
service parameter, CCD Maximum Numbers of Learned Patterns. This alarm indicates that the CCD
requesting service has met the maximum number of learned patterns allowed.
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/CallManager
Severity
WARNING
Routing List
SDL
SDI
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
6-190
OL-20105-01
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Warning-Level Alarms
Sys Log
Event Log
Parameter(s)
CCD Maximum Numbers of Learned Patterns (UInt)
System Limit of CCD Learned Patterns (UInt)
Recommended Action
This alarm displays the value that is configured in the Cisco CallManager service parameter, CCD
Maximum Numbers of Learned Patterns, as well as the maximum number of learned patterns that are
allowed by the system (an internally-controlled maximum).
Consider whether the specified maximum number of learned patterns is correct for your deployment. If
it is too low, compare it with the number shown in the SystemLimitCCDLearnedPatterns in this alarm.
If the Max number is below the System Limit, you can go to the Service Parameters Configuration
window and increase the CCD Maximum Numbers of Learned Patterns service parameter. If the Max
and System Limit numbers match, the system is already configured to run at capacity of learned patterns;
no action is required.
CertValidLessThanMonth
Alarm indicates that the certificate will expire in 30 days or less.
Cisco Unified Serviceability Alarm Definition Catalog
System/CertMonitorAlarmCatalog
Severity
Warning(4)
Routing List
Event Log
Sys Log
Parameters
Message(String)
Recommended Action
Regenerate the certificate that is about to expire by accessing the Cisco Unified Operating System and
go to Certificate Management. If the certificate is issued by a CA, generate a CSR, submit the CSR to
CA, obtain a fresh certificate from CA, and upload it to Cisco Unified CM.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
6-191
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Warning-Level Alarms
ConferenceNoMoreResourcesAvailable
Conference resource allocation failed for one or more of the following reasons: the required number of
conference resources were not available; for an IOS-based conference bridge, the number of participants
to be added to the conference bridge exceeded the maximum number of participants allowed per
conference; no lower precedence conference was available for preemption although MLPP preemption
was enabled; a lower-precedence conference bridge was not preempted.
History
Cisco Unified Communications
Release
Action
8.0(1)
Changed severity level from Error to Warning.
Facility/Sub-Facility
CCM_CALLMANAGER-CALLMANAGER
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/CallManager
Severity
Warning
Parameter(s)
Media Resource List Name(String)
Recommended Action
For IOS-based conference bridges, make sure that the maximum number of participants configured in a
conference bridge does not exceed the number of participants allowed per conference; please check the
IOS-based conference bridge user manual for limitations on the number of participants. Also, be sure to
educate end users about the maximum number of participants allowed. For IOS-based and
non-IOS-based, consider installing additional conference resources.
CtiDeviceOpenFailure
Application is unable to open the device.
History
Cisco Unified Communications
Release
Action
8.0(1)
Name changed from kCtiDeviceOpenFailure.
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/CtiManager
Severity
WARNING
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
6-192
OL-20105-01
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Warning-Level Alarms
Routing List
SDL
SDI
Sys Log
Event Log
Data Collector
Parameter(s)
Device Name(String)
ReasonCode(Enum)
Enum Definitions - Reason Code
Value
Definition
0x8CCC0013 (2362179603)
Device is already opened by another application; identify the
application that is controlling this device. You can determine
this information from RTMT (CallManager->CTI Manager
and CallManager->CTI Search)
0x8CCC00DA (2362179802)
Unable to communicate with database; verify the CPU utilization is in the safe range for (this can be monitored using RTMT
via CPU Pegging Alert)
0x8CCC009A (2362179738)
Device is unregistering; wait for the device to register. Due to
user initiated reset or restart of the device from Unified CM.
Device should automatically register wait for few moments for
the device to register
0x8CCC0018 (2362179608)
Device is not in the user control list; verify whether the device
is configured for control by this application. For the application to control the device it should be included in the user
control list. To check whether the device is in the user control
list, 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)
0x8CCC00F3 (2362179827)
IPAddress mode (IPv4 or IPv6 or both) specified by the application does not match with IP Addressing mode that is configured in Unified CM Administration; check the IP addressing
mode of the device in Cisco Unified CM Administration
(Device > Device Settings > Common Device Configuration)
Recommended Action
Check the reason code and take appropriate action to resolve the issue.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
6-193
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Warning-Level Alarms
CtiLineOpenFailure
Application is unable to open the line.
History
Cisco Unified Communications
Release
Action
8.0(1)
Name changed from kCtiLineOpenFailure.
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/CtiManager
Severity
WARNING
Routing List
SDL
SDI
Sys Log
Event Log
Data Collector
Parameter(s)
Device Name(String)
Directory Number(String)
Partition(String)
Reason(Enum)
Enum Definitions - Reason Code
Value
Definition
0
Unknown
0x8CCC0018 (2362179608) Device is not in the user control list; verify whether the device is configured for control by this application. For the application to control the
device it should be included in the user control list. To check whether
the device is in the user control list, 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)
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
6-194
OL-20105-01
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Warning-Level Alarms
Value
Definition
0x8CCC0005 (2362179589) Line is not found in the device; possible cause could be that the line that
previously existed on this device is not available. This could be due to
a extension mobility login or logout
0x8CCC00D3 (2362179795) Administrator has restricted the Line to be controllable by application.
If the intent of the Administrator is to allow control of this line, enable
the check box labelled Allow control of Device from CTI, in Unified
CM Administration under Call Routing > Directory Number and choose
the line that should be controlled by this application
Recommended Action
Review the reason code and take appropriate action to resolve the issue.
CtiIncompatibleProtocolVersion
Incompatible protocol version.
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 IP
addressing mode of the Application.
History
Cisco Unified Communications
Release
Action
8.0(1)
Name changed from kCtiIncompatibleProtocolVersion.
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/CtiManager
Severity
WARNING
Routing List
SDL
SDI
Sys Log
Event Log
Parameter(s)
Unified CM Version(String)
IPAddress(String)
IPv6Address(String)
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
6-195
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Warning-Level Alarms
Recommended Action
Verify that the correct version of the application is being used. If you are not sure 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).
CtiMaxConnectionReached
Maximum number of CTI connections has been reached, no new connection will be accepted unless an
existing connection is closed.
History
Cisco Unified Communications
Release
Action
8.0(1)
Name changed from kCtiMaxConnectionReached.
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/CtiManager
Severity
WARNING
Routing List
SDL
SDI
Sys Log
Event Log
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.
CtiProviderCloseHeartbeatTimeout
CTI heartbeat timeout occurred causing CTIManager to close the application connection.
History
Cisco Unified Communications
Release
Action
8.0(1)
Name changed from kCtiProviderCloseHeartbeatTimeout.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
6-196
OL-20105-01
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Warning-Level Alarms
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/CtiManager
Severity
WARNING
Routing List
SDL
SDI
Sys Log
Event Log
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.
CtiQbeFailureResponse
The requested operation from the application could not be performed because of a normal or abnormal
condition.
History
Cisco Unified Communications
Release
Action
8.0(1)
Name changed from kCtiQbeFailureResponse.
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/CtiManager
Severity
WARNING
Routing List
SDL
SDI
Sys Log
Event Log
Parameter(s)
Error message(String)
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
6-197
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Warning-Level Alarms
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.
DaTimeOut
The digit analysis component in Cisco Unified Communications Manager has timed out. This can occur
because Cisco Unified Communications Manager is busy and the resulting delay in processing request
and response messages caused the digit analysis component to time out.
History
Cisco Unified Communications
Release
Action
8.0(1)
Severity changed from Error to Warning.
Facility/Sub-Facility
CCM_CALLMANAGER-CALLMANAGER
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/CallManager
Severity
Warning
Recommended Action
In the Service Parameter Configuration window in Cisco Unified CM Administration, check the Cisco
CallManager service parameter, Digit Analysis Timer, to confirm that the default value is in use. Use
RTMT to monitor the system resources and correct any system issues that might be contributing to high
CPU utilization on Cisco Unified CM.
DevicePartiallyRegistered
Device partially registered. A device is partially registered with Cisco CallManager. Some, but not all,
of the lines configured on the device have successfully registered.
History
Cisco Unified Communications
Release
Action
8.0(1)
Following information is updated:
•
Enum Definitions for performance monitor object type
•
Enum Definitions for DeviceType
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
6-198
OL-20105-01
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Warning-Level Alarms
Facility/Sub-Facility
CCM_CALLMANAGER-CALLMANAGER
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/CallManager
Severity
Warning (4)
Parameters
Device name. [String] Device MAC address [Optional]. [String] Device IP address. [String]
Protocol. [String] Device description [Optional]. [String] User ID [Optional]. [String] Load ID.
[Optional] [String] Associated directory numbers. [String] Performance monitor object
type [Enum]Device type. [Optional] [Enum]
Enum Definitions for Performance Monitor Object type
Code
Reason
1
Cisco CallManager
2
Cisco Phones
3
Cisco Lines
4
Cisco H323
5
Cisco MGCP Gateway
6
Cisco MOH Device
7
Cisco Analog Access
8
Cisco MGCP FXS Device
9
Cisco MGCP FXO Device
10
Cisco MGCP T1CAS Device
11
Cisco MGCP PRI Device
Enum Definitions for DeviceType
Code
Reason
1
CISCO_30SP+
2
CISCO_12SP+
3
CISCO_12SP
4
CISCO_12S
5
CISCO_30VIP
6
CISCO_7910
7
CISCO_7960
8
CISCO_7940
9
CISCO_7935
10
CISCO_VGC_PHONE
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
6-199
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Warning-Level Alarms
11
CISCO_VGC_VIRTUAL_PHONE
12
CISCO_ATA_186
20
SCCP_PHONE
30
ANALOG_ACCESS
40
DIGITAL_ACCESS
42
DIGITAL_ACCESS+
43
DIGITAL_ACCESS_WS-X6608
47
ANALOG_ACCESS_WS-X6624
48
VGC_GATEWAY
50
CONFERENCE_BRIDGE
51
CONFERENCE_BRIDGE_HARDWARE
52
CONFERENCE_BRIDGE_HARDWARE_HDV2
53
CONFERENCE_BRIDGE_HARDWARE_WS-SVC-CMM
61
H323_PHONE
62
H323_GATEWAY
70
MUSIC_ON_HOLD
71
DEVICE_PILOT
72
CTI_PORT
73
CTI_ROUTE_POINT
80
VOICE_MAIL_PORT
83
SOFTWARE_MEDIA_TERMINATION_POINT_HDV2
84
CISCO_MEDIA_SERVER
85
CISCO_VIDEO_CONFERENCE_BRIDGE
90
ROUTE_LIST
100
LOAD_SIMULATOR
110
MEDIA_TERMINATION_POINT
111
MEDIA_TERMINATION_POINT_HARDWARE
112
MEDIA_TERMINATION_POINT_HDV2
113
MEDIA_TERMINATION_POINT_WS-SVC-CMM
115
CISCO_7941
119
CISCO_7971
120
MGCP_STATION
121
MGCP_TRUNK
122
GATEKEEPER
124
7914_14_BUTTON_LINE_EXPANSION_MODULE
125
TRUNK
126
TONE_ANNOUNCEMENT_PLAYER
131
SIP_TRUNK
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
6-200
OL-20105-01
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Warning-Level Alarms
132
SIP_GATEWAY
133
WSM_TRUNK
134
REMOTE_DESTINATION_PROFILE
227
7915_12_BUTTON_LINE_EXPANSION_MODULE
228
7915_24_BUTTON_LINE_EXPANSION_MODULE
229
7916_12_BUTTON_LINE_EXPANSION_MODULE
230
7916_24_BUTTON_LINE_EXPANSION_MODULE
232
CKEM_36_BUTTON_LINE_EXPANSION_MODULE
254
UNKNOWN_MGCP_GATEWAY
255
UNKNOWN
302
CISCO_7989
307
CISCO_7911
308
CISCO_7941G_GE
309
CISCO_7961G_GE
335
MOTOROLA_CN622
336
BASIC_3RD_PARTY_SIP_DEVICE
348
CISCO_7931
358
CISCO_UNIFIED_COMMUNICATOR
365
CISCO_7921
369
CISCO_7906
374
ADVANCED_3RD_PARTY_SIP_DEVICE
375
CISCO_TELEPRESENCE
404
CISCO_7962
412
CISCO_3951
431
CISCO_7937
434
CISCO_7942
435
CISCO_7945
436
CISCO_7965
437
CISCO_7975
446
CISCO_3911
468
CISCO_UNIFIED_MOBILE_COMMUNICATOR
478
CISCO_TELEPRESENCE_1000
479
CISCO_TELEPRESENCE_3000
480
CISCO_TELEPRESENCE_3200
481
CISCO_TELEPRESENCE_500
484
CISCO_7925
493
CISCO_9971
495
CISCO_6921
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
6-201
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Warning-Level Alarms
496
CISCO_6941
497
CISCO_6961
20000
CISCO_7905
30002
CISCO_7920
30006
CISCO_7970
30007
CISCO_7912
30008
CISCO_7902
30016
CISCO_IP_COMMUNICATOR
30018
CISCO_7961
30019
CISCO_7936
30027
ANALOG_PHONE
30028
ISDN_BRI_PHONE
30032
SCCP_GATEWAY_VIRTUAL_PHONE
30035
IP_STE
Recommended Action
In the Cisco Unified Reporting tool, run the Unified CM Multi-Line Devices report and check the
number of lines that are supposed to be configured on the device identified in this alarm. If the device
has registered an inconsistent number of lines compared the Multi-Lines report for this device, restart
the device so that it can reregister all lines. If this alarm persists, verify that the appropriate number of
lines has been configured on the device, and that the appropriate directory numbers have been
configured. If the device is a third-party SIP phone, verify that the directory numbers configured on the
phone match the directory numbers configured on the device in Unified CM Administration.
DeviceTransientConnection
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.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
6-202
OL-20105-01
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Warning-Level Alarms
History
Cisco Unified Communications
Release
Action
8.0(1)
•
Severity changed from Error to Warning.
•
Following information is updated:
– Enum Definitions for DeviceType
– Enum Definitions
– Enum Definitions for IPAddrAttributes
– Enum Definitions for IPV6AddrAttributes
7.1
IPv6 parameters added: IPV6Address[Optional][String],
IPAddrAttributes[Optional][Enum], and
IPV6AddrAttributes[Optional][Enum].
Facility/Sub-Facility
CCM_CALLMANAGER-CALLMANAGER
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/CallManager
Severity
Warning
Parameters
Device IP address [Optional].[String]
Device name [Optional].[String]
Device MAC address [Optional].[String]
Protocol.[String]
Device type. [Optional][Enum]
Reason Code [Optional].[Enum]
Connecting Port [UInt]
Registering SIP User. [Optional].[String]
IPV6Address [Optional].[String]
IPAddressAttributes [Optional].[Enum]
IPV6AddressAttributes [Optional].[Enum]
Enum Definitions for DeviceType
Code
Reason
10
CISCO_VGC_PHONE
11
CISCO_VGC_VIRTUAL_PHONE
30
ANALOG_ACCESS
40
DIGITAL_ACCESS
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
6-203
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Warning-Level Alarms
42
DIGITAL_ACCESS+
43
DIGITAL_ACCESS_WS-X6608
47
ANALOG_ACCESS_WS-X6624
48
VGC_GATEWAY
50
CONFERENCE_BRIDGE
51
CONFERENCE_BRIDGE_HARDWARE
52
CONFERENCE_BRIDGE_HARDWARE_HDV2
53
CONFERENCE_BRIDGE_HARDWARE_WS-SVC-CMM
62
H323_GATEWAY
70
MUSIC_ON_HOLD
71
DEVICE_PILOT
73
CTI_ROUTE_POINT
80
VOICE_MAIL_PORT
83
SOFTWARE_MEDIA_TERMINATION_POINT_HDV2
84
CISCO_MEDIA_SERVER
85
CISCO_VIDEO_CONFERENCE_BRIDGE
90
ROUTE_LIST
100
LOAD_SIMULATOR
110
MEDIA_TERMINATION_POINT
111
MEDIA_TERMINATION_POINT_HARDWARE
112
MEDIA_TERMINATION_POINT_HDV2
113
MEDIA_TERMINATION_POINT_WS-SVC-CMM
120
MGCP_STATION
121
MGCP_TRUNK
122
GATEKEEPER
124
7914_14_BUTTON_LINE_EXPANSION_MODULE
125
TRUNK
126
TONE_ANNOUNCEMENT_PLAYER
131
SIP_TRUNK
132
SIP_GATEWAY
133
WSM_TRUNK
134
REMOTE_DESTINATION_PROFILE
227
7915_12_BUTTON_LINE_EXPANSION_MODULE
228
7915_24_BUTTON_LINE_EXPANSION_MODULE
229
7916_12_BUTTON_LINE_EXPANSION_MODULE
230
7916_24_BUTTON_LINE_EXPANSION_MODULE
232
CKEM_36_BUTTON_LINE_EXPANSION_MODULE
254
UNKNOWN_MGCP_GATEWAY
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
6-204
OL-20105-01
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Warning-Level Alarms
255
UNKNOWN
30027
ANALOG_PHONE
30028
ISDN_BRI_PHONE
30032
SCCP_GATEWAY_VIRTUAL_PHONE
Enum Definitions
Code
Reason
1
Unknown—(SCCP only) The device failed to register for an unknown reason. If this persists,
collect SDL/SDI traces with "Enable SCCP Keep Alive Trace" enabled and contact TAC.
2
NoEntryInDatabase—(MGCP only) The device is not configured in the Unified CM
Administration database and auto-registration is either not supported for the device type or is
not enabled. To correct this problem, configure this device in Unified CM Administration.
3
DatabaseConfigurationError—The device is not configured in the Unified CM Administration
database and auto-registration is either not supported for the device type or is not enabled. To
correct this problem, configure this device in Unified CM Administration.
4
DeviceNameUnresolveable—For SIP third-party devices this means that Unified CM could not
determine the name of the device from the Authorization header in the REGISTER message.
The device did not provide an Authorization header after Unified CM challenged with a 401
Unauthorized message. Verify that the device is configured with digest credentials and is able
to respond to 401challenges with an Authorization header. If this is a Cisco IP phone, the
configuration may be out-of-sync. First, go to the Cisco Unified Reporting web page, generate
a Unified CM Database Status report, and verify "all servers have a good replication status". If
DB replications looks good, reset the phone. If that still doesn't fix the problem, restart the
TFTP and the Cisco CallManager services. For all other devices, this reason code means that
DNS lookup failed. Verify the DNS server configured via the OS Administration CLI is correct
and that the DNS name used by the device is configured in the DNS server.
6
ConnectivityError—The network connection between the device and Cisco Unified CM
dropped before the device was fully registered. Possible causes include device power outage,
network power outage, network configuration error, network delay, packet drops and packet
corruption. It is also possible to get this error if the Cisco Unified CM node is experiencing
high CPU usage. Verify the device is powered up and operating, verify network connectivity
between the device and Cisco Unified CM, and verify the CPU utilization is in the safe range
(this can be monitored using RTMT via CPU Pegging Alert).
7
InitializationError—An internal error occurred within Cisco Unified CM while processing the
device registration. It is recommended to restart the Cisco CallManager service. If this occurs
repeatedly, collect SDL/SDI detailed traces with "Enable SIP Keep Alive (REGISTER
Refresh) Trace" and "Enable SCCP Keep Alive Trace" under Cisco CallManager services
turned on and contact TAC.
10
AuthenticationError—The device failed either TLS or SIP digest security authentication. If the
device is a SIP phone and is enabled for digest authentication (on the System > Security Profile
> Phone Security Profile, check if "Enable Digest Authentication" checkbox is checked), verify
the "Digest Credentials" in the End User config page are configured. Also, check the phone
config page to see if the phone is associated with the specified end user in the Digest User drop
box. If the device is a third-party SIP device, verify the digest credentials configured on the
phone match the "Digest Credentials" configured in the End User page.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
6-205
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Warning-Level Alarms
11
InvalidX509NameInCertificate—Configured "X.509 Subject Name" doesn't match what's in
the certificate from the device. Check the Security profile of the indicated device and verify
the "Device Security Mode" is either "Authenticated" or "Encrypted". Verify the "X.509
Subject Name" field has the right content. It should match the Subject Name in the certificate
from the peer.
12
InvalidTLSCipher—Unsupported cipher algorithm used by the device; Cisco Unified CM only
supports AES_128_SHA cipher algorithm. Recommended action is for the device to regenerate
its certificate with the AES_128_SHA cipher algorithm.
14
MalformedRegisterMsg—(SIP only) A SIP REGISTER message could not be processed
because of an illegal format. Possible causes include a missing Call-ID header, a missing AoR
in the To header, and an expires value too small. Verify the REGISTER message does not
suffer from any of these ills.
15
ProtocolMismatch—The protocol of the device (SIP or SCCP) does not match the configured
protocol in Cisco Unified CM. Recommended actions: 1) Verify the device is configured with
the desired protocol; 2) Verify the firmware load ID on the Device Defaults page is correct and
actually exists on the TFTP server; 3) If there is a firmware load ID configured on the device
page, verify it is correct and exists on the TFTP server (On Cisco Unified OS Administration
page, Software Upgrades > TFTP File Management, look for the file name as specified by load
ID); 4) Restart the TFTP and Cisco CallManager services. Use the Cisco Unified OS
Administration TFTP File Management page to verify the configured firmware loads exist.
16
DeviceNotActive—The device has not been activated
17
AuthenticatedDeviceAlreadyExists—A device with the same name is already registered. If this
occurs repeatedly, collect SDL/SDI detailed traces with "Enable SIP Keep Alive (REGISTER
Refresh) Trace" and "Enable SCCP Keep Alive Trace" under Cisco CallManager services
turned on and contact TAC. There may be an attempt by unauthorized devices to register.
18
ObsoleteProtocolVersion—(SCCP only) A SCCP device registered with an obsolete protocol
version. Power cycle the phone. Verify that the TFTP service is activated. Verify that the TFTP
server is reachable from the device. If there is a firmware load ID configured on the Phone
Config page, verify that the firmware load ID exists on the TFTP server (On Cisco Unified OS
Administration page, Software Upgrades > TFTP File Management, look for the file name as
specified by load ID).
Enum Definitions for IPAddrAttributes
Code
Reason
0
Unknown—The device has not indicated what this IPv4 address is used for.
1
Administrative only—The device has indicated that this IPv4 address is used for
administrative communication (web interface) only.
2
Signal only—The device has indicated that this IPv4 address is used for control
signaling only.
3
Administrative and signal—The device has indicated that this IPv4 address is
used for administrative communication (web interface) and control signaling.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
6-206
OL-20105-01
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Warning-Level Alarms
Enum Definitions for IPV6AddrAttributes
Code
Reason
0
Unknown—The device has not indicated what this IPv6 address is used for.
1
Administrative only—The device has indicated that this IPv6 address is used for
administrative communication (web interface) only.
2
Signal only—The device has indicated that this IPv6 address is used for control
signaling only.
3
Administrative and signal—The device has indicated that this IPv6 address is
used for administrative communication (web interface) and control signaling.
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 for recommended actions. No
action is required if this event was issued as a result of a normal device rehome.
DeviceUnregistered
A device that has previously registered with Cisco CallManager has unregistered. In cases of normal
unregistration with reason code 'CallManagerReset', 'CallManagerRestart', or 'DeviceInitiatedReset', the
severity of this alarm is lowered to INFORMATIONAL. A device can unregister for many reasons, both
intentional, such as manually resetting the device after a configuration change, or unintentional, such as
loss of network connectivity. Other causes for this alarm could include a phone being registered to a
secondary node and then the primary node come back online, causing the phone to rehome to the primary
Unified CM node or lack of a KeepAlive being returned from the Unified CM node to which this device
was registered. Unregistration also occurs if Unified CM receives a duplicate registration request for this
same device.
History
Cisco Unified Communications
Release
8.0(1)
Action
•
Severity changed from Error to Warning.
•
Following information is updated:
– Enum Definitions for DeviceType
– Enum Definition
– Enum Definitions for IPAddrAttributes
– Enum Definitions for IPV6AddrAttributes
7.1
Parameters added: IPV6Address,IPAddrAttributes, and
IPV6AddrAttributes.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
6-207
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Warning-Level Alarms
Facility/Sub-Facility
CCM_CALLMANAGER-CALLMANAGER
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/CallManager
Severity
Warning
Parameters
Device name. [String]
Device MAC address [Optional]. [String]
Device IP address [Optional]. [String]
Protocol. [String]
Device type. [Optional] [Enum]
Device description [Optional]. [String]
Reason Code [Optional]. [Enum]
IPV6Address [Optional]. [String]
IPAddressAttributes [Optional]. [Enum]
IPV6AddressAttributes [Optional]. [Enum]
Enum Definitions for DeviceType
Code
Device Type
10
CISCO_VGC_PHONE
11
CISCO_VGC_VIRTUAL_PHONE
30
ANALOG_ACCESS
40
DIGITAL_ACCESS
42
DIGITAL_ACCESS+
43
DIGITAL_ACCESS_WS-X6608
47
ANALOG_ACCESS_WS-X6624
48
VGC_GATEWAY
50
CONFERENCE_BRIDGE
51
CONFERENCE_BRIDGE_HARDWARE
52
CONFERENCE_BRIDGE_HARDWARE_HDV2
53
CONFERENCE_BRIDGE_HARDWARE_WS-SVC-CMM
62
H323_GATEWAY
70
MUSIC_ON_HOLD
71
DEVICE_PILOT
73
CTI_ROUTE_POINT
80
VOICE_MAIL_PORT
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
6-208
OL-20105-01
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Warning-Level Alarms
83
SOFTWARE_MEDIA_TERMINATION_POINT_HDV2
84
CISCO_MEDIA_SERVER
85
CISCO_VIDEO_CONFERENCE_BRIDGE
90
ROUTE_LIST
100
LOAD_SIMULATOR
110
MEDIA_TERMINATION_POINT
111
MEDIA_TERMINATION_POINT_HARDWARE
112
MEDIA_TERMINATION_POINT_HDV2
113
MEDIA_TERMINATION_POINT_WS-SVC-CMM
120
MGCP_STATION
121
MGCP_TRUNK
122
GATEKEEPER
124
7914_14_BUTTON_LINE_EXPANSION_MODULE
125
TRUNK
126
TONE_ANNOUNCEMENT_PLAYER
131
SIP_TRUNK
132
SIP_GATEWAY
133
WSM_TRUNK
134
REMOTE_DESTINATION_PROFILE
227
7915_12_BUTTON_LINE_EXPANSION_MODULE
228
7915_24_BUTTON_LINE_EXPANSION_MODULE
229
7916_12_BUTTON_LINE_EXPANSION_MODULE
230
7916_24_BUTTON_LINE_EXPANSION_MODULE
232
CKEM_36_BUTTON_LINE_EXPANSION_MODULE
254
UNKNOWN_MGCP_GATEWAY
255
UNKNOWN
30027
ANALOG_PHONE
30028
ISDN_BRI_PHONE
30032
SCCP_GATEWAY_VIRTUAL_PHONE
Enum Definition
Code
Reason
1
Unknown - The device has unregistered for an unknown reason. If the device does not
re-register within 5 minutes, verify it is powered-up and verify network connectivity
between the device and Cisco Unified CM.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
6-209
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Warning-Level Alarms
6
ConnectivityError - Network communication between the device and Cisco Unified CM
has been interrupted. Possible causes include device power outage, network power
outage, network configuration error, network delay, packet drops and packet corruption.
It is also possible to get this error if the Cisco Unified CM node is experiencing high CPU
usage. Verify the device is powered up and operating, verify network connectivity
between the device and Cisco Unified CM, and verify the CPU utilization is in the safe
range (this can be monitored using RTMT via CPU Pegging Alert).
8
DeviceInitiatedReset - The device has initiated a reset, possibly due to a power cycle or
internal error. No action required; the device will re-register automatically.
9
CallManagerReset - A device reset was initiated from Cisco Unified CM Administration,
either due to an explicit command from an administrator, or due to internal errors
encountered. No action necessary, the device will re-register automatically.
10
DeviceUnregistered - The device has explicitly unregistered. Possible causes include a
change in the IP address or port of the device. No action is necessary, the device will
re-register automatically.
11
MalformedRegisterMsg - (SIP only) A SIP REGISTER message could not be processed
because of an illegal format. Possible causes include a missing Call-ID header, a missing
AoR in the To header, and an expires value too small. Verify the REGISTER message
does not suffer from any of these ills.
12
SCCPDeviceThrottling - (SCCP only) The indicated SCCP device exceeded the
maximum number of events allowed per-SCCP device. Events can be phone calls,
KeepAlive messages, or excessive SCCP or non-SCCP messages. The maximum number
of allowed events is controlled by the Cisco CallManager service parameter, Max Events
Allowed. When an individual device exceeds the number configured in that service
parameter, Unified CM closes the TCP connection to the device; automatic reregistration
generally follows. This action is an attempt to stop malicious attacks on Unified CM or
to ward off excessive CPU usage.
13
KeepAliveTimeout - A keepalive message was not received. Possible causes include
device power outage, network power outage, network configuration error, network delay,
packet drops and packet corruption. It is also possible to get this error if the Cisco Unified
CM node is experiencing high CPU usage. Verify the device is powered up and operating,
verify network connectivity between the device and Cisco Unified CM, and verify the
CPU utilization is in the safe range (this can be monitored using RTMT via CPU Pegging
Alert).
14
ConfigurationMismatch (SIP only) The configuration on the device does not match the
configuration in Cisco Unified CM. This can be caused by database replication errors or
other internal Cisco Unified CM communication errors. First go to the Cisco Unified
Reporting web page, generate a Unified CM Database Status report, and verify "all
servers have a good replication status". If this device continues to unregister with this
reason code, go to the CCMAdmin Device web page for the device and click Save. This
allows a change notify to be generated to the Unified CM and TFTP services and rebuild
a new config file. If the problem still persists, restart the TFTP service and Cisco Unified
CM service.
15
CallManagerRestart - A device restart was initiated from Cisco Unified CM, either due
to an explicit command from an administrator, or due to a configuration change such as
adding, deleting or changing a DN associated with the device. No action necessary, the
device will re-register automatically.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
6-210
OL-20105-01
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Warning-Level Alarms
16
DuplicateRegistration - Cisco Unified CM detected that the device attempted to register
to 2 nodes at the same time. Cisco Unified CM initiated a restart to the phone to force it
to re-home to a single node. No action necessary, the device will re-register
automatically.
17
CallManagerApplyConfig - An ApplyConfig command was invoked from Unified CM
Administration resulting in an unregistration. No action necessary, the device will
re-register automatically.
18
DeviceNoResponse - The device did not respond to a reset or restart notification, so it is
being forcefully reset. If the device does not re-register within 5 minutes, confirm it is
powered-up and confirm network connectivity between the device and Cisco Unified
CM.
Enum Definitions for IPAddrAttributes
Code
Reason
0
Unknown—The device has not indicated what this IPv4 address is used for.
1
Administrative only—The device has indicated that this IPv4 address is used for
administrative communication (web interface) only.
2
Signal only—The device has indicated that this IPv4 address is used for control
signaling only.
3
Administrative and signal—The device has indicated that this IPv4 address is
used for administrative communication (web interface) and control signaling.
Enum Definitions for IPV6AddrAttributes
Code
Reason
0
Unknown - The device has not indicated what this IPv6 address is used for
1
Administrative only - The device has indicated that this IPv6 address is used for
administrative communication (web interface) only.
2
Signal only - The device has indicated that this IPv6 address is used for control
signaling only.
3
Administrative and signal - The device has indicated that this IPv6 address is
used for administrative communication (web interface) and control signaling.
Recommended Action
Actions to take vary depending on the reason specified for the device unregistration. If the reason is
ConfigurationMismatch, go to the Device Configuration page in Cisco Unified CM Administration,
make a change to the Description field for this device, click Save, then reset the device. In the case of a
network connectivity or loss of KeepAlives problem, use network diagnostic tools and the Cisco Unified
CM Reporting tool to fix any reported network or Unified CM system errors. In the case of a device
rehoming to the primary Unified CM node, watch for a successful registration of the device on the
primary node. In the case of a duplicate registration request, it may be a non-malicious occurrence due
to timing of a device registering and unregistering; if duplicate registration requests continue or if the
same device has different IP addresses, confirm the IP address on the physical device itself by checking
the settings on the device (settings button). If unregistration of this device was expected, no action is
required. Also, refer to the reason code descriptions for recommended actions.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
6-211
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Warning-Level Alarms
DigitAnalysisTimeoutAwaitingResponse
Cisco Unified Communications Manager sent a routing request to the policy decision point but the
request timed out without a response.
Cisco Unified Communications Manager (Unified CM) was unable to complete the routing request
before timing out. This time out could occur due to low system resources, high CPU usage, or a high
volume of call activities on this Unified CM node. Unified CM applies the Call Treatment on Failure
that is configured for the External Call Control Profile associated with this call.
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/CallManager
Severity
WARNING
Routing List
SDL
SDI
Sys Log
Event Log
Parameter(s)
Translation Pattern Triggering Point(String)
Policy Decision Point(String)
Recommended Action
•
Check the External Call Control object in Real-Time Monitoring Tool (RTMT) to see whether the
ExternalCallControlEnabledCallAttempted counter is spiking. If so, this indicates an unusually high
number of calls at this time which could result in reduced system resources.
•
Check the QueueSignalsPresent2-Normal for persistent long high signal queue. If the long signal
queue exists, check whether the Code Yellow alarm has already issued and check the system CPU
and memory usage for this Unified CM node.
•
Follow the recommended actions for Code Yellow alarm if the Code Yellow alarm has fired.
For high CPU usage, use RTMT to determine which areas may be contributing to the high CPU usage.
If this alarm persists, collect system performance data (such as the percentage of Memory, Page and VM
usage, partition read and write bytes per second, the percentage of CPU usages of all the processes, and
the processor IOWait percentage) and contact Cisco Technical Assistance Center (TAC).
DRFNoBackupTaken
A valid backup of the current system was not found after an Upgrade, Migration, or Fresh Install.
Cisco Unified Serviceability Alarm Definition Catalog
System/DRF
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
6-212
OL-20105-01
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Warning-Level Alarms
Severity
WARNING
Routing List
Event Log
Sys Log
Parameter(s)
Reason(String)
Recommended Action
It is recommended to perform a Backup using the Disaster Recovery System.
EMCCFailedInRemoteCluster
There was an EMCC login failure at a remote Unified CM. EMCC login could fail due to the following
reasons:
•
User does not exist in any of the configured remote cluster.
•
User is not enabled for EMCC.
•
No free EMCC base device.
•
EMCC access was prevented by remote cluster.
•
Untrusted certificate received from the remote end while trying to establish a connection.
Reason Codes:
•
38—EMCC or PSTN is not activated in InterClusterServiceProfile page
•
31—User is not enabled for EMCC
•
39—Default and Backup TFTP Service is not configured
Cisco Unified Serviceability Alarm Definition Catalog
System/EMAlarmCatalog
Severity
Warning(4)
Routing List
Sys Log
Event Log
Alert Manager
Parameters
Device Name(String)
Login Date/Time(String)
Login UserID(String)
Reason(String)
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
6-213
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Warning-Level Alarms
Recommended Action
Perform the following steps:
Step 1
Ensure that the user is a valid EMCC user and that user home cluster is added as a EMCC remote cluster
(From Unified CM Administration window, go to System > EMCC > Remote Cluster > Add New).
Step 2
Contact remote site administrator to enable user for EMCC (From Unified CM Administration window,
go to User Management > End User > Select User > Enable Extension Mobility Cross Cluster
checkbox).
Step 3
Contact remote site administrator for adding or freeing EMCC Base Devices (From Unified CM
Administration window, go to Bulk Administration > EMCC > Insert/Update EMCC).
Step 4
Contact remote site administrator to validate the remote cluster setting for this cluster.
Step 5
Ensure that a bundle of all Tomcat certificates (PKCS12) got imported into the local tomcat-trust
keystore (From the OS Administration window, go to Security > Certificate Management.
ErrorParsingResponseFromPDP
Cisco Unified Communications Manager failed to parse one or multiple optional elements or attributes
in the call routing response from the policy decision point.
A routing response was received from the policy decision point (PDP) but Cisco Unified
Communications Manager (Unified CM) failed to parse the optional elements in the response. Optional
elements may include modified calling numbers or called numbers, call reject or call diversion reasons,
and so on. The cause may be a syntax error or missing attributes in the call routing response.
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/CallManager
Severity
WARNING
Routing List
SDL
SDI
Sys Log
Event Log
Parameter(s)
Policy Decision Point(String)
Called Party Number(String)
Calling Party Number(String)
Calling User Id(String)
Request XML Data(String)
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
6-214
OL-20105-01
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Warning-Level Alarms
Recommended Action
Check if call routing response from the policy decision point complies with the guidelines specified for
external call control in the Cisco Unified Communications Manager documentation. Check if any
optional elements included as the policy obligations in the call routing response are correctly entered
according to the external call control documentation, including any applicable API documentation.
FailedToFulfillDirectiveFromPDP
Cisco Unified Communications Manager cannot fulfill the call routing directive returned by the PDP.
The failure can occur because of the following conditions:
•
Call was cleared by a CTI application before Cisco Unified Communications Manager was able to
route it to the location defined by the PDP.
•
Call that was allowed by a policy server was redirected by the CTI application to a destination.
•
Annunciator ID was misconfigured in the PDP.
•
Unified CM attempted to invoke a media resource such as Annunciator but no resources were
available.
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/CallManager
Severity
Warning(4)
Routing List
SDL
SDI
Sys Log
Event Log
Parameters
Policy Decision Point(String)
Reason, Unified CM failed to fulfill the directive(String)
Called Party Number(String)
Calling Party Number(String)
Calling User Id(String)
Recommended Action
In many cases, the cause for a failure occurs because of the intervention by a CTI application which
scoops up the call before Unified CM is able to fulfill the routing directive in the PDP. Examine the CTI
application to ensure that the call is in alerting or connected state before the CTI begins to interact with
it.
If the failure is caused by a problem with the annunciator ID, ensure the ID has been accurately
configured in the PDP and that it exists in Unified CM Administration.
If the failure was caused by a lack of media resources, try increasing the Annunciator Call Count service
parameter in the Cisco IP Voice Media Streaming App service.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
6-215
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Warning-Level Alarms
H323Stopped
Cisco CallManager is not ready to handle calls for the indicated H323 device.
Cisco Unified Communications Manager (Unified CM) is not ready to handle calls for the indicated
H.323 device. This could be due to Unified CM being unable to resolve the gateway name to IP address.
For trunks, this alarm should only occur when a system administrator has made a configuration change
such as resetting the H.323 trunk. For H.323 clients, this alarm occurrence is normal on lower-priority
Unified CM nodes when a high-priority Unified CM node starts.
History
Cisco Unified Communications
Release
Action
8.0(1)
Following information updated:
•
Parameters
•
Enum Definitions for DeviceType
Facility/Sub-Facility
CCM_CALLMANAGER-CALLMANAGER
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/CallManager
Severity
Warning (4)
Parameters
Device Name. [String] IP Address [String] Device type. [Optional] [Enum]Device description
[Optional]. [String] Remote CallManager Server 1[Optional]. [String] Remote CallManager Server
2[Optional]. [String] Remote CallManager Server 3[Optional]. [String]
Enum Definitions for DeviceType
Code
Device Type
61
H323_PHONE
62
H323_GATEWAY
122
GATEKEEPER
125
TRUNK
Recommended Action
If the service was stopped intentionally, no action is required. Check the domain name system (DNS)
configuration for any errors in the gateway name or IP address and correct.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
6-216
OL-20105-01
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Warning-Level Alarms
InvalidSubscription
A message has been received from an IME server that contains a subscription identifier that is not
handled by this node
Each node that communicates with a IME server saves a subscription identifier associated with each IME
client instance. A IME server has sent a message with a subscription identifier that does not match any
of the previously sent subscription identifiers.
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/CallManager
Severity
WARNING
Recommended Action
This may be a race condition if the IME client instance has been recently added or deleted. If this error
continues, there may be a synchronization issue between this node and the IME server sending this
message.
Routing List
SDL
SDI
Sys Log
Event Log
Parameter(s)
Subscription Identifier(UInt)
IME Server(String)
InvalidQBEMessage
QBE PDU from application is invalid.
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/CtiManager
Severity
WARNING
Routing List
SDL
SDI
Sys Log
Event Log
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
6-217
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Warning-Level Alarms
Parameter(s)
CTI Connection type(String)
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).
kANNAudioFileMissing
Announcement file not found. 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.
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/IpVms
Severity
WARNING
Routing List
SDI
Event Log
Sys Log
Parameter(s)
Missing filename(String)
Recommended Action
Upload the custom announcement to the server or install the missing locale package.
kANNAudioUndefinedAnnID
Requested announcement not found. This may be caused by using an incorrect announcement identifier
for a custom announcement. Use the Cisco Unified CM Admin to view a list of custom announcement
identifiers and verify the correct one is being used.
History
Cisco Unified Communications
Release
8.0(1)
Action
•
Severity changed from Error to Warning.
•
Parameter list removed.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
6-218
OL-20105-01
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Warning-Level Alarms
Facility/Sub-Facility
CCM_MEDIA_STREAMING_APP-IPVMS
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/IpVms
Severity
Warning
Recommended Action
Add the announcement.
kANNAudioUndefinedLocale
Unknown ANN locale. 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.
History
Cisco Unified Communications
Release
8.0(1)
Action
•
Severity changed from Error to Warning.
•
Parameter list is updated.
Facility/Sub-Facility
CCM_MEDIA_STREAMING_APP-IPVMS
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/IpVms
Severity
Warning
Parameters
Locale Type [String]
Recommended Action
Install the locale package or check device settings for an incorrect locale value.
kANNDeviceStartingDefaults
The ANN device configuration was not found. 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.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
6-219
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Warning-Level Alarms
History
Cisco Unified Communications
Release
8.0(1)
Action
•
Severity changed from Informational to Warning.
•
Parameter list added.
Facility/Sub-Facility
CCM_MEDIA_STREAMING_APP-IPVMS
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/IpVms
Severity
Warning
Parameter(s)
Parameter Name [String]
Value Used [String]
Recommended Action
Review the service parameter settings and configure the ANN device settings properly using the Cisco
Unified CM Administration.
kCFBDeviceStartingDefaults
CFB device configuration not found. 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.
History
Cisco Unified Communications
Release
Action
3.x and 4.x
Added for Windows.
7.0(1)
Obsoleted.
8.0(1)
This alarm is available in 8.0(1).
•
Severity changed from Informational to Warning.
•
New parameters added:
– Parameter Name(String)
– Value Used(String)
Facility/Sub-Facility
CCM_MEDIA_STREAMING_APP-IPVMS
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
6-220
OL-20105-01
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Warning-Level Alarms
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/IpVms
Severity
Warning
Parameter(s)
Parameter Name(String)
Value Used(String)
Recommended Action
Review the service parameter settings and configure the CFB device settings properly using the Cisco
Unified CM Administration.
kChangeNotifyServiceCreationFailed
Database change notification subsystem not starting. 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.
History
Cisco Unified Communications
Release
Action
3.x and 4.x
Added for Windows.
7.0(1)
Obsoleted.
8.0(1)
This alarm is available in 8.0(1).
•
Severity changed from Error to Warning.
•
Following parameters added:
– OS Error Code(Int)
– OS Error Description(String)
Facility/Sub-Facility
CCM_MEDIA_STREAMING_APP-IPVMS
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/IpVms
Severity
Warning
Parameter(s)
OS Error Code(Int)
OS Error Description(String)
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
6-221
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Warning-Level Alarms
Recommended Action
Restart the Cisco IP Voice Media Streaming App service to get the DB notification reenabled.
kChangeNotifyServiceGetEventFailed
Invalid notification event returned by database change notification. 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.
History
Cisco Unified Communications
Release
Action
3.x and 4.x
Added for Windows.
7.0(1)
Obsoleted.
8.0(1)
This alarm is available in 8.0(1)
•
Severity changed from Error to Warning.
•
Following parameters added:
– OS Error Code(Int)
– OS Error Description(String)
Facility/Sub-Facility
CCM_MEDIA_STREAMING_APP-IPVMS
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/IpVms
Severity
Warning
Parameter(s)
OS Error Code(Int)
OS Error Description(String)
Recommended Action
Check the current status of the Cisco IP Voice Media Streaming App service and monitor for repeated
occurrences.
kChangeNotifyServiceRestartFailed
Database change notification restart failure. The change notification subsystem failed to restart.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
6-222
OL-20105-01
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Warning-Level Alarms
History
Cisco Unified Communications
Release
Action
3.x and 4.x
Added for Windows.
7.0(1)
Obsoleted.
8.0(1)
This alarm is available in 8.0(1)
•
Severity changed from Error to Warning.
•
Following parameters added:
– OS Error Code(Int)
– OS Error Description(String)
Facility/Sub-Facility
CCM_MEDIA_STREAMING_APP-IPVMS
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/IpVms
Severity
Warning
Parameter(s)
OS Error Code(Int)
OS Error Description(String)
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.
kDeviceDriverError
IP voice media streaming device driver error. The IP voice media streaming device driver returned an
error. This may indicate a significant media error or resource shortage.
History
Cisco Unified Communications
Release
Action
3.x and 4.x
Added for Windows.
7.0(1)
Obsoleted.
8.0(1)
This alarm is available in 8.0(1).
Severity changed from Error to Warning.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
6-223
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Warning-Level Alarms
Facility/Sub-Facility
CCM_MEDIA_STREAMING_APP-IPVMS
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/IpVms
Severity
Warning
Parameters
Error [String]
Recommended Action
Restarting the Cisco IP Voice Media Streaming App service or possibly restarting the server may resolve
the error condition.
kDeviceMgrCreateFailed
Device connection manager failed to start. The device controller was unable to start a connection to
control device registration with CallManager. This is possibly due to lack of memory.
History
Cisco Unified Communications
Release
Action
3.x and 4.x
Added for Windows.
7.0(1)
Obsoleted.
8.0(1)
This alarm is available in 8.0(1).
Severity changed from Error to Warning.
Facility/Sub-Facility
CCM_MEDIA_STREAMING_APP-IPVMS
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/IpVms
Severity
Warning
Parameters
Device Name [String] Server Name [String]
Recommended Action
Restart the Cisco IP Voice Media Streaming App service or restart the Cisco Unified CM server.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
6-224
OL-20105-01
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Warning-Level Alarms
kDeviceMgrOpenReceiveFailedOutOfStreams
Open receive failure. The open receive channel failed. This may indicate a mismatch of media resources
between Cisco Unified Call Manager and the Cisco IP Voice Media Streaming App service.
History
Cisco Unified Communications
Release
Action
3.x and 4.x
Added for Windows.
7.0(1)
Obsoleted.
8.0(1)
This alarm is available in 8.0(1). Severity changed from Error to
warning.
Facility/Sub-Facility
CCM_MEDIA_STREAMING_APP-IPVMS
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/IpVms
Severity
Warning
Parameters
Trace Name [String]
Recommended Action
Check the performance monitor counters for resource availability on Cisco Unified CM 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 Cisco Unified CM server.
kDeviceMgrRegisterKeepAliveResponseError
Cisco Unified Communications Manager not responding. The specified Cisco Unified Communications
Manager is not responding to the keepalive messages. The connection with Cisco Unified CM 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
Cisco Unified CM.
History
Cisco Unified Communications
Release
Action
3.x and 4.x
Added for Windows.
7.0(1)
Obsoleted.
8.0(1)
This alarm is available in 8.0(1). Severity changed from Error to
Warning.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
6-225
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Warning-Level Alarms
Facility/Sub-Facility
CCM_MEDIA_STREAMING_APP-IPVMS
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/IpVms
Severity
Warning
Parameters
Trace Name [String]
Recommended Action
Cisco Unified Communications Manager may have gone down or is unable to respond. Check status of
Cisco Unified CM. The media device should automatically reregister.
kDeviceMgrRegisterWithCallManagerError
Connection error with Cisco Unified Communications Manager. 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.
History
Cisco Unified Communications
Release
Action
8.0(1)
Severity changed from Error to Warning.
Facility/Sub-Facility
CCM_MEDIA_STREAMING_APP-IPVMS
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/IpVms
Severity
Warning
Parameters
Trace Name [String]
Recommended Action
No action is required; The media device will reregister.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
6-226
OL-20105-01
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Warning-Level Alarms
kDeviceMgrSocketNotifyEventCreateFailed
Creation socket event failure. 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.
History
Cisco Unified Communications
Release
Action
3.x and 4.x
Added for Windows.
7.0(1)
Obsoleted.
8.0(1)
This alarm is available in 8.0(1). Severity changed from Error to
Warning.
Facility/Sub-Facility
CCM_MEDIA_STREAMING_APP-IPVMS
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/IpVms
Severity
Warning
Parameters
Device Name [String] Trace Name [String] OS Error Description [String]
Recommended Action
Restart the Cisco IP Voice Media Streaming App service and monitor for reoccurrence or restart the
Cisco Unified CM server.
kDeviceMgrStartTransmissionOutOfStreams
Start transmission failure. An error was encountered while starting an RTP transmission audio stream.
This may indicate a mismatch of resources between Cisco Unified Communications Manager and Cisco
IP Voice Media Streaming App service.
History
Cisco Unified Communications
Release
Action
3.x and 4.x
Added for Windows.
7.0(1)
Obsoleted.
8.0(1)
This alarm is available in 8.0(1). Severity changed from Error to
Warning.
Facility/Sub-Facility
CCM_MEDIA_STREAMING_APP-IPVMS
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
6-227
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Warning-Level Alarms
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/IpVms
Severity
Warning
Parameters
Trace Name [String]
Recommended Action
Check the performance counters for the media resources on Cisco Unified CM 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.
kDeviceMgrThreadxFailed
Creation of thread failure. An error was reported when starting a process for the specified media device.
This may be due to a system resource shortage.
History
Cisco Unified Communications
Release
Action
3.x and 4.x
Added for Windows.
7.0(1)
Obsoleted.
8.0(1)
This alarm is available in 8.0(1).
•
Severity changed from Error to Warning.
•
Following parameters added:
– OS Error Code[Int]
– OS Error Description [String]
Facility/Sub-Facility
CCM_MEDIA_STREAMING_APP-IPVMS
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/IpVms
Severity
Warning
Parameters
Device Name [String] Trace Name [String] OS Error Code [Int] OS Error Description [String]
Recommended Action
Restart the Cisco IP Voice Media Streaming App service or restart the Cisco Unified CM server to
recover from this error.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
6-228
OL-20105-01
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Warning-Level Alarms
kFixedInputCodecStreamFailed
Fixed input codec stream initialization failure. Initialization of sound card codec source transcoding
process failed. The fixed audio source will not play possibly due to memory or resource shortage.
History
Cisco Unified Communications
Release
8.0(1)
Action
•
Severity changed from Error to Warning.
•
Following parameters removed:
– Audio Source ID [ULong]
– System error code [ULong]
Facility/Sub-Facility
CCM_MEDIA_STREAMING_APP-IPVMS
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/IpVms
Severity
Warning
Parameters
Error text [String] Codec Type [String]
Recommended Action
Reset MOH device, or restart Cisco IO Voice Media Streaming App service, or restart server.
kFixedInputCreateControlFailed
Fixed stream control create failure. 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.
History
Cisco Unified Communications
Release
Action
3.x and 4.x
Added for Windows.
7.0(1)
Obsoleted.
8.0(1)
This alarm is available in 8.0(1).
•
Severity changed from Error to Warning.
•
Audio Source ID [ULong] parameter is removed.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
6-229
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Warning-Level Alarms
Facility/Sub-Facility
CCM_MEDIA_STREAMING_APP-IPVMS
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/IpVms
Severity
Warning
Parameters
Codec Type [String]
Recommended Action
Reset MOH device, if failure continues restart the server. Monitor for errors in trace files and system log.
kFixedInputCreateSoundCardFailed
Fixed stream sound card interface create failure. 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.
History
Cisco Unified Communications
Release
8.0(1)
Action
•
Severity changed from Error to Warning.
•
Audio Source ID [ULong] parameter is removed.
Facility/Sub-Facility
CCM_MEDIA_STREAMING_APP-IPVMS
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/IpVms
Severity
Warning
Parameters
Codec Type [String]
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.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
6-230
OL-20105-01
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Warning-Level Alarms
kFixedInputInitSoundCardFailed
Fixed stream sound card interface initialization failure. Initialization of sound card failed. Fixed audio
source will not play possibly due to missing or unconfigured USB sound device.
History
Cisco Unified Communications
Release
8.0(1)
Action
•
Severity changed from Error to Warning.
•
Following parameters are removed:
– Audio Source ID [ULong]
– System error code [ULong]
Facility/Sub-Facility
CCM_MEDIA_STREAMING_APP-IPVMS
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/IpVms
Severity
Warning
Parameters
Error text [String] Device name [String]
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 additional information.
kFixedInputTranscoderFailed
Fixed input audio stream transcoder failure. 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.
History
Cisco Unified Communications
Release
8.0(1)
Action
•
Severity changed from Error to Warning.
•
Following parameters are removed:
– Audio Source ID [ULong]
– System error code [ULong]
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
6-231
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Warning-Level Alarms
Facility/Sub-Facility
CCM_MEDIA_STREAMING_APP-IPVMS
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/IpVms
Severity
Warning
Parameters
Error text [String]
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.
kGetFileNameFailed
Get audio source file name failure. The Music-on-Hold audio source is not assigned to an audio file.
History
Cisco Unified Communications
Release
Action
3.x and 4.x
Added for Windows.
7.0(1)
Obsoleted.
8.0(1)
This alarm is available in 8.0(1).
•
Severity changed from Error to Warning.
•
Audio Source ID [ULong] parameter is removed.
Facility/Sub-Facility
CCM_MEDIA_STREAMING_APP-IPVMS
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/IpVms
Severity
Warning
Parameters
Codec Type [String]
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.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
6-232
OL-20105-01
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Warning-Level Alarms
kIPVMSMgrEventCreationFailed
Creation of required signaling event failed. 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.
History
Cisco Unified Communications
Release
Action
3.x and 4.x
Added for Windows.
7.0(1)
Obsoleted.
8.0(1)
This alarm is available in 8.0(1). Severity changed from Error to
Warning.
Facility/Sub-Facility
CCM_MEDIA_STREAMING_APP-IPVMS
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/IpVms
Severity
Warning
Parameters
OS Error Description(String)
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.
kIPVMSMgrThreadxFailed
Creation of the IPVMSMgr thread failed. 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.
History
Cisco Unified Communications
Release
Action
3.x and 4.x
Added for Windows.
7.0(1)
Obsoleted.
8.0(1)
This alarm is available in 8.0(1). Severity changed from Error to
Warning.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
6-233
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Warning-Level Alarms
Facility/Sub-Facility
CCM_MEDIA_STREAMING_APP-IPVMS
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/IpVms
Severity
Warning
Parameters
OS Error Description(String)
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.
kIpVmsMgrThreadWaitFailed
Error while waiting for asynchronous notifications of events. 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).
History
Cisco Unified Communications
Release
Action
3.x and 4.x
Added for Windows.
7.0(1)
Obsoleted.
8.0(1)
This alarm is available in 8.0(1). Severity changed from Error to
Warning.
Facility/Sub-Facility
CCM_MEDIA_STREAMING_APP-IPVMS
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/IpVms
Severity
Warning
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.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
6-234
OL-20105-01
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Warning-Level Alarms
kMOHMgrCreateFailed
Error starting MOH Audio source subcomponent. 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).
History
Cisco Unified Communications
Release
Action
3.x and 4.x
Added for Windows.
7.0(1)
Obsoleted.
8.0(1)
This alarm is available in 8.0(1).
•
Severity changed from Error to Warning.
•
OS Error Description(String) parameter is added.
Facility/Sub-Facility
CCM_MEDIA_STREAMING_APP-IPVMS
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/IpVms
Severity
Warning
Parameter(s)
OS Error Description(String)
Recommended Action
Restart the Cisco IP Voice Media Streaming App service or restart the server.
kMOHMgrExitEventCreationFailed
Creation of MOH manager exit event failure. An error was encountered when allocating a signaling
event. This may be caused by a resource shortage.
History
Cisco Unified Communications
Release
Action
3.x and 4.x
Added for Windows.
7.0(1)
Obsoleted.
8.0(1)
This alarm is available in 8.0(1). Severity changed from Error to
Warning.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
6-235
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Warning-Level Alarms
Facility/Sub-Facility
CCM_MEDIA_STREAMING_APP-IPVMS
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/IpVms
Severity
Warning
Parameters
OS Error Description(String)
Recommended Action
Restart the Cisco IP Voice Media Streaming App service or restart the server.
kMOHMgrThreadxFailed
Starting of MOH audio manager failed. An error was encountered when starting the Music-on-Hold
audio manager subcomponent. Music-on-Hold audio services will not be avaliable.
History
Cisco Unified Communications
Release
Action
3.x and 4.x
Added for Windows.
7.0(1)
Obsoleted.
8.0(1)
This alarm is available in 8.0(1).
•
Severity changed from Error to Warning.
•
OS Error Description(String) parameter is added.
Facility/Sub-Facility
CCM_MEDIA_STREAMING_APP-IPVMS
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/IpVms
Severity
Warning
Parameters
OS Error Description(String)
Recommended Action
Restart the Cisco IP Voice Media Streaming App service.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
6-236
OL-20105-01
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Warning-Level Alarms
kMTPDeviceRecordNotFound
MTP device record not found. 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.
History
Cisco Unified Communications
Release
Action
3.x and 4.x
Added for Windows.
7.0(1)
Obsoleted.
8.0(1)
This alarm is available in 8.0(1). Severity changed from
Informational to Warning.
Facility/Sub-Facility
CCM_MEDIA_STREAMING_APP-IPVMS
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/IpVms
Severity
Warning
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.
kRequestedCFBStreamsFailed
CFB requested streams failure. The resources for the number of requested full-duplex streams was not
available.
History
Cisco Unified Communications
Release
Action
8.0(1)
Severity changed from Error to Warning.
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/IpVms
Severity
WARNING
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
6-237
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Warning-Level Alarms
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.
kRequestedMOHStreamsFailed
MOH requested streams failure. The resources for the number of requested streams was not available.
History
Cisco Unified Communications
Release
Action
8.0(1)
Severity changed from Error to Warning.
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/IpVms
Severity
WARNING
Recommended Action
Verify the number of calls configuration setting for Music-on-Hold device. Restart the server to reset
the resources.
kRequestedMTPStreamsFailed
MTP requested streams failure. The resources for the number of requested full-duplex Media
Termination Point streams was not available.
History
Cisco Unified Communications
Release
Action
8.0(1)
Severity changed from Error to Warning.
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/IpVms
Severity
WARNING
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.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
6-238
OL-20105-01
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Warning-Level Alarms
LogCollectionJobLimitExceeded
The number of Log Collection Jobs have exceeded the allowed limit. 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.
History
Cisco Unified Communications
Release
Action
8.0(1)
Severity changed from Informational to Warning.
Facility/Sub-Facility
CCM_TCT-LPMTCT
Cisco Unified Serviceability Alarm Definition Catalog
System/LpmTct
Severity
Warning
Parameters
JobType [String]
Recommended Action
Cancel one or more of the currently running queries and try again to configure the trace collection.
LogPartitionLowWaterMarkExceeded
The percentage of used disk space in the log partition has exceeded the configured low water mark.
History
Cisco Unified Communications
Release
Action
8.0(1)
Severity changed from Error to Warning.
Facility/Sub-Facility
CCM_TCT-LPMTCT
Cisco Unified Serviceability Alarm Definition Catalog
System/LpmTct
Severity
Warning
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
6-239
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Warning-Level Alarms
Parameters
UsedDiskSpace [String] MessageString [Optional]. [String]
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.
MaliciousCall
Malicious Call Identification feature is invoked in Cisco CallManager.
History
Cisco Unified Communications
Release
Action
8.0(1)
Severity changed from Informational to Warning.
Facility/Sub-Facility
CCM_CALLMANAGER-CALLMANAGER
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/CallManager
Severity
Warning
Parameters
Called Party Number [String] Called Device Name [String] Called Display Name [String] Calling Party
Number [String] Calling Device Name [String] Calling Display Name [String]
Recommended Action
No action is required.
MaxDevicesPerNodeExceeded
An application has opened more devices than the limit set in the CTIManager service parameter,
Maximum Devices Per Node.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
6-240
OL-20105-01
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Warning-Level Alarms
History
Cisco Unified Communications
Release
Action
8.0(1)
Name changed from kCtiMaxDevicesPerNodeExceeded.
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/CtiManager
Severity
WARNING
Routing List
SDL
SDI
Sys Log
Event Log
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.
MaxDevicesPerProviderExceeded
An application has opened more devices than the limit set in the CTIManager service parameter,
Maximum Devices Per Provider.
History
Cisco Unified Communications
Release
Action
8.0(1)
Name changed from kCtiMaxDevicesPerProviderExceeded.
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/CtiManager
Severity
WARNING
Routing List
SDL
SDI
Sys Log
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
6-241
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Warning-Level Alarms
Event Log
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.
MemAllocFailed
CMI tried to allocate memory and failed.
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.
History
Cisco Unified Communications
Release
Action
7.0(1)
Added to CallManager Catalog.
Cisco Unified Serviceability Alarm Definition Catalog
CMIAlarmCatalog/CMI
Severity
WARNING
Routing List
Event Log
SDI
Parameter(s)
Memory Allocation Failure(String)
Recommended Action
Use the Real-Time Monitoring Tool to check the 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).
MohNoMoreResourcesAvailable
No more MOH resources available.
This alarm occurs when allocation of Music On Hold fails for all the registered MOH servers belonging
to the Media Resource Group List and Default List. Each MOH server may fail for different reasons.
Following are some of the reasons that could cause an MOH server allocation to fail: All the resources
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
6-242
OL-20105-01
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Warning-Level Alarms
of MOH server are already in use; No matching codecs or capability mismatch between the held party
and MOH server; Not enough bandwidth between the held party and MOH source; No audio stream
available for the MOH server.
History
Cisco Unified Communications
Release
Action
8.0(1)
Severity changed from Error to Warning.
Facility/Sub-Facility
CCM_CALLMANAGER-CALLMANAGER
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/CallManager
Severity
Warning
Recommended Action
If all the resources of the MOH servers are already in use, check to be sure that all the MOH servers that
belong to the Media Resource Groups of the indicated Media Resource Group List and Default List are
configured and registered in all the applicable Unified CM nodes. To check the registration status go to
the Media Resources > Music On Hold Server menu and click the Find button. It will display all the
MOH servers with their status, device pool, and so on.
Check the status field to discover whether it is registered with Unified CM. Note that the display on the
status field is not a confirmation that the device is registered to Unified CM. It may happen in a Unified
CM cluster that the Publisher can only write to the Unified CM database and the Publisher goes down.
Because the Subscriber may not be able to write to the database, the devices may still display as
registered in Unified CM Administration after they are actually unregistered. However, if the Publisher
is down that should generate another alarm with higher priority than this alarm.
The MOH allocation can also fail due to codec mismatch or capability mismatch between the endpoint
and the MOH server. If there is a codec mismatch or capability mismatch (such as the endpoint using
IPv6 addressing but MOH server supporting only IPv4), an MTP or transcoder should be allocated. If
the MTP or transcoder is not allocated then either MediaResourceListExhausted (with Media Resource
Type as Media termination point or transcoder) or MtpNoMoreResourcesAvailable alarm will be
generated for the same Media Resource Group List and you should first concentrate on that alarm.
The MOH allocation may even fail after checking the region bandwidth between the regions to which
the held party belongs and the region to which the MOH server belongs. Increasing the region bandwidth
may be a solution to the problem, but that decision should be made after careful consideration of the
amount of bandwidth you're willing to allocate per call between the set of regions.
You'll need to weigh different factors such as the total amount of available bandwidth, the average
number of calls, the average number of calls using the MOH servers, approximate bandwidth use per
call, and so on, and accordingly calculate the region bandwidth. Another possible cause is that the
bandwidth needed for the call may not be available. This can occur if the MOH server and endpoint
belong to different locations and the bandwidth that is set between the locations is already in use by other
calls.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
6-243
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Warning-Level Alarms
Examine the bandwidth requirements in your deployment to determine whether bandwidth between the
locations can be increased. However, please note that increasing the bandwidth between these two
locations means that you may need to reduce the bandwidth between other locations.
Refer to the System Guide, SRNDs, and related Unified CM documentation for more details. Be aware
that reducing the bandwidth or removing the higher bandwidth codecs from configuration may result in
poor voice quality during call. Consider increasing the total amount of network bandwidth. Another
reason for the MOH allocation failure may be due to meeting the maximum number of unicast or
multicast streams supported by the MOH server.
If all available streams are already in use, none can be allocated. Finally, check the Music On Hold
Audio Source Configuration window in Cisco Unified CM Administration to confirm that at least one
audio source is configured. If an audio source is not configured, upload an audio file and then configure
the audio source in Cisco Unified CM Administration (refer to the Music On Hold configuration
documentation for specific details).
MtpNoMoreResourcesAvailable
Media termination point or transcoder allocation failed.
The alarm occurs when allocation of a media termination point (MTP) or transcoder fails for all the
registered MTPs or transcoders belonging to the Media Resource Group List and Default List. Each MTP
or transcoder may fail for different reasons. Following are some of the reasons that could cause an MTP
or transcoder allocation to fail: a capability mismatch between the device endpoint and MTP/transcoder,
codec mismatch between the endpoint and the MTP/transcoder; a lack of available bandwidth between
the endpoint and the MTP/transcoder; or because the MTP/transcoders resources are already in use.
A capability mismatch may be due to the MTP/transcoder not supporting one or more of the required
capabilities for the call such as Transfer Relay Point (which is needed for QoS or firewall traversal), RFC
2833 DTMF (which is necessary when one side of the call does not support RFC 2833 format for
transmitting DTMF digits and the other side must receive the DTMF digits in RFC2833 format, resulting
in conversion of the DTMF digits), RFC 2833 DTMF passthrough (in this case, the MTP or transcoder
does not need to convert the DTMF digits from one format to another format but it needs to receive
DTMF digits from one endpoint and transmit them to the other endpoint without performing any
modifications), passthrough (where no codec conversion will occur, meaning the media device will
receive media streams in any codec format and transmit them to the other side without performing any
codec conversion), IPv4 to IPv6 conversion (when one side of the call supports only IPv4 and the other
side of the call supports only IPv6 and so an MTP needs to be inserted to perform the necessary
conversion between IPv4 and IPv6 packets), or multimedia capability (if a call involving video and/or
data in addition to audio requires insertion of an MTP or transcoder then the MTP/transcoder which
supports multimedia will be inserted).
History
Cisco Unified Communications
Release
8.0(1)
Action
•
Severity changed from Error to Warning.
•
Media Resource List Name parameter added.
Facility/Sub-Facility
CCM_CALLMANAGER-CALLMANAGER
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
6-244
OL-20105-01
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Warning-Level Alarms
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/CallManager
Severity
Warning
Parameter(s)
Media Resource List Name(String)
Recommended Action
If the MTP or transcoder allocation is failing due to a capability mismatch, it's possible that the media
device does not support the capability (such as IPv4 to IPv6 conversion, passthrough) or the capability
might not be configured in the device. Please check the user guide and documentation of the media
device to make sure that device supports all the necessary capabilities. Also, caution should be taken
care if all the MTP or transcoders are configured with all the supported capabilities.
There are certain capabilities (such as RFC 2833 DTMF or RFC 2833 DTMF passthrough or
passthrough) which could be supported by most of the MTPs or transcoders and there may be certain
capabilities (such as IPv4 to IPv6 conversion and vice versa or Transfer Relay Point or multimedia
capability) which can be supported by only by a single MTP or transcoder depending on the devices that
you have. For example, you may have IP phones that support only IPv4 protocol and there may also be
IP phones that support only IPv6 protocol.
To make a call between IPv4-only and IPv6-only phones, you need to have an MTP configured to
perform the conversion of IPv4 to IPv6 and vice versa. However, suppose all the MTPs or transcoders
are configured with all the supported capabilities and only one MTP supports IPv4 to IPv6 conversion;
if this MTP is configured with all the supported capabilities (which all the other MTPs or transcoders in
the same MRGL or default MRGL also support) it may happen that this MTP can get allocated for
Transfer Relay Point or RFC 2833 DTMF or RFC 2833 DTMF passthrough or passthrough instead. As
a result, when the need arises for IPv4 to IPv6 conversion (which other MTPs or transcoders in the same
MRGL or default MRGL do not support), all the resources of MTP may be in use and the IPv4 to IPv6
conversion may fail. To avoid this kind of problem, setting the priority of the media resources may be a
good idea.
This can be done only in the Media Resource Group List and not in the Default List of the media
resources. In any Media Resource Group List all the Media Resource Groups have different priorities;
during allocation the first Media Resource Group is always checked for availability of the requested type
of the media devices. The first Media Resource Group in the Media Resource Group List will have the
highest priority, then the second one, and so on.
To check all the Media Resource Groups and their priority go the Media Resources and Media Resource
Group List of Cisco Unified CM Administration page and click the appropriate Media Resource Group
List and check the Selected Media Resource Groups; the priority decreases from top to bottom. So, the
MTP or transcoder that you want to be selected for the most basic functionalities should be positioned
in the higher priority Media Resource Groups whereas the ones with more rare functionality should be
positioned in the Media Resource Groups with lower priority. MTP/transcoder allocation may fail due
to codec mismatch between the endpoint and the MTP/transcoder.
A solution may be to configure the MTP/transcoder with all the supported codecs (as specified in the
user guide of the MTP/transcoder), but be aware that doing so might result in too much bandwidth being
allocated for calls. You'll need to weigh different factors such as the total amount of available
bandwidth, the average number of calls, approximate bandwidth use per call (not involving
MTP/transcoder), and so on, and accordingly calculate the maximum bandwidth that can be allocated
per call involving an MTP/transcoder and take that into consideration when configuring the supported
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
6-245
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Warning-Level Alarms
codecs in the MTPs and transcoders. A good idea is to configure the media devices with all the supported
codecs and set the region bandwidths to restrict too much bandwidth usage (refer to the Unified CM
documentation for details on region and location settings).
Also, there may be a codec mismatch between the endpoint and the MTP/transcoders after considering
the region bandwidth between the MTP/transcoder and the endpoint. Increasing the region bandwidth
may be a solution to the problem, but again, that decision should be made after careful consideration of
the amount of bandwidth you're willing to allocate per call between the set of regions. Another possible
cause that an MTP/transcoder did not get allocated is because there was not enough available bandwidth
for the call.
This can happen if the MTP/transcoder and endpoint belong to different locations and the bandwidth that
is set between the locations is already in use by other calls. Examine the bandwidth requirements in your
deployment to determine whether bandwidth between the locations can be increased.
However, please note that increasing the bandwidth between these two locations means that you may
need to reduce the bandwidth between other locations. Refer to the System Guide, SRNDs, and related
Unified CM documentation for more details. Be aware that reducing the bandwidth or removing the
higher bandwidth codecs from configuration may result in poor voice quality during call. Consider
increasing the total amount of network bandwidth available. Finally, if MTP or transcoder allocation
fails due to capability mismatch or all the resources being in use, consider installing additional MTP or
transcoder devices.
MTPDeviceRecoveryCreateFailed
MTP device recovery create failure. An error was encountered trying to restart the Media Termination
Point device. This may be due to a shortage of application memory.
History
Cisco Unified Communications
Release
8.0(1)
Action
Changed severity level from Error to Warning and added existing
Routing List elements and Parameters.
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/IpVms
Severity
Warning
Routing List
SDI
Event Log
Sys Log
Parameters
OS Error Description(String)
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
6-246
OL-20105-01
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Warning-Level Alarms
Recommended Action
Restart the IP Voice Media Streaming App service or restart the server.
NotEnoughChans
Call attempt was rejected because requested gateway channel(s) could not be allocated. Some of the
more common reasons for the lack of channel to place outgoing calls include: High call traffic volume
that has the B-channels in the device fully utilized; B-channels have gone out of service for the following
reasons: Taking the channel out of service intentionally to perform maintenance on either the near- or
far-end; MGCP gateway returns an error code 501 or 510 for a MGCP command sent from Cisco Unified
Communications Manager; MGCP gateway doesn't respond to an MGCP command sent by Unified CM
three times; a speed and duplex mismatch exists on the Ethernet port between Unified CM and the
MGCP gateway.
History
Cisco Unified Communications
Release
8.0(1)
Action
•
Severity changed from Error to Warning.
•
Device Name(String) is the only parameter
Facility/Sub-Facility
CCM_CALLMANAGER-CALLMANAGER
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/CallManager
Severity
Warning
Parameters
Device Name(String)
Recommended Action
Add more gateway resources; Check the Unified CM 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; Reset the MGCP gateway; Check the speed and duplex settings on the Ethernet port.
NoCallManagerFound
No Cisco Unified Communications Manager (Cisco Unified CM, formerly known as Cisco Unified
CallManager) node has been configured. A Cisco Unified Communications Manager Group exists but it
has no Cisco Unified CM node configured as its group member.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
6-247
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Warning-Level Alarms
History
Cisco Unified Communications
Release
Action
7.0(1)
Name changed from kNoCallManagerFound.
8.0(1)
Severity changed from Error to Warning.
Facility/Sub-Facility
CCM_TFTP-TFTP
Cisco Unified Serviceability Alarm Definition Catalog
System/TFTP
Severity
Warning
Parameters
Error [String]
Recommended Action
In Cisco Unified CM Administration (System > Cisco Unified CM Group), configure at least one Cisco
Unified CM node for the Cisco Unified CM Group referenced in this alarm. The Cisco Unified CM
Group is part of the device pool to which the specified phone belongs.
PublishFailed
Publish Failed.
Unified CM attempted to store a number into the IME distributed cache, but the attempt failed. This is
typically due to a transient problem in the IME distributed cache. The problem will self-repair under
normal conditions. However, you should be aware that, as a consequence of this failure, the E.164 DID
listed as part of the alarm will not be present in the IME distributed cache for a brief interval.
Consequently, this may delay the amount of time until which you will receive VoIP calls made to that
number - they may continue over the PSTN for some callers. It is useful to be aware of this, in case you
are trying to understand why a call is not being made over VoIP.
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/CallManager
Severity
WARNING
Recommended Action
If you notice single small numbers of these alarms in isolation, no action is required on your part.
However, a large number of them indicates a problem in the IME distributed cache, most likely due to
problems with Internet connectivity. Check your Internet connectivity.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
6-248
OL-20105-01
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Warning-Level Alarms
Routing List
SDL
SDI
Sys Log
Event Log
Parameter(s)
DID(String)
RejectedRoutes
Rejected route due to Untrusted status.
This alarm is generated when Unified CM learned a route from the IME server. However, due to the
configured Trusted or Untrusted list, the route was rejected.
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/CallManager
Severity
WARNING_ALARM
Recommended Action
This condition is not an error. However, it indicates to you that one of your users called a number which
was reachable over IME, however, due to your configured Trusted or Untrusted list, a IME call will not
be made. You might wish to consider adding the domain or prefix to your Trusted list or removing it
from the Untrusted list.
Routing List
SDL
SDI
Sys Log
Event Log
Parameter(s)
Domain name(String)
Phone number(String)
SparePartitionHighWaterMarkExceeded
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.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
6-249
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Warning-Level Alarms
Note
Spare Partition is not used for Intercompany Media Engine server. So this alert will not be triggered for
Intercompany Media Engine.
History
Cisco Unified Communications
Release
Action
7.0(1)
Error message added.
8.0(1)
Severity changed from Error to Warning.
Facility/Sub-Facility
CCM_TCT-LPMTCT
Cisco Unified Serviceability Alarm Definition Catalog
System/LpmTct
Severity
Warning
Parameters
UsedDiskSpace [String] MessageString [Optional]. [String]
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.
SIPStopped
Cisco CallManager is not ready to handle calls for the indicated SIP device. Possible reasons could be
internal database error, the SIP device is not activated on this node, the SIP device failed to register or
the SIP device was deleted from admin page.
History
Cisco Unified Communications
Release
8.0(1)
Action
Enum Definitions for InTransportType and OutTransportType are
updated.
Recommended Action changed.
7.0(1)
IPV6Address parameter added.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
6-250
OL-20105-01
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Warning-Level Alarms
Facility/Sub-Facility
CCM_CALLMANAGER-CALLMANAGER
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/CallManager
Severity
Warning (4)
Parameters
Device Name. [String] IP Address [String] Device type. [Optional] [Enum]Device description
[Optional]. [String] Incoming Port Number. [UInt] Outgoing Port Number. [UInt] Incoming Transport
Type [Enum]Outgoing Transport Type [Enum]IPV6Address [Optional]. [String]
Enum Definitions for DeviceType
131—SIP_TRUNK
Enum Definitions for InTransportType
Code
Definition
1
TCP
2
UDP
3
TLS
4
TCP/UDP
Enum Definitions for OutTransportType
Code
Definition
1
TCP
2
UDP
3
TLS
Recommended Action
This alarm doesn't necessarily mean an error. It could occur as a result of normal administrative changes.
If the alarm is unexpected, check whether the StationPortInitError alarm also fired. Check the Device
Pool assigned to the SIP device identified in this alarm to ensure that the Cisco Unified Communications
Manager Group of the Device Pool includes the Unified CM node that issued the alarm.
SIPLineRegistrationError
A SIP line attempted to register with CallManager and failed due to the error indicated in the Reason
Code parameter. The alarm could indicate a device misconfiguration, database error, or an
illegal/unknown device trying to attempt a connection.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
6-251
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Warning-Level Alarms
History
Cisco Unified Communications
Release
8.0(1)
Action
•
Severity changed from Error to Warning.
•
Enum Definitions for DeviceType are updated.
•
Enum Reasons table is updated.
Facility/Sub-Facility
CCM_CALLMANAGER-CALLMANAGER
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/CallManager
Severity
Warning
Parameters
Device IP address. [String] Device Port. [UInt] Device name [Optional]. [String] Device MAC address
[Optional]. [String] Device type. [Optional] [Enum]Reason Code [Optional]. [Enum]Connecting
Port [UInt] Configured DNs. [String] Registering SIP User. [String]
Enum Definitions for DeviceType
Code
Device Type
1
CISCO_30SP+
2
CISCO_12SP+
3
CISCO_12SP
4
CISCO_12S
5
CISCO_30VIP
6
CISCO_7910
7
CISCO_7960
8
CISCO_7940
9
CISCO_7935
12
CISCO_ATA_186
20
SCCP_PHONE
61
H323_PHONE
72
CTI_PORT
115
CISCO_7941
119
CISCO_7971
255
UNKNOWN
302
CISCO_7989
307
CISCO_7911
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
6-252
OL-20105-01
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Warning-Level Alarms
308
CISCO_7941G_GE
309
CISCO_7961G_GE
335
MOTOROLA_CN622
336
BASIC_3RD_PARTY_SIP_DEVICE
348
CISCO_7931
358
CISCO_UNIFIED_COMMUNICATOR
365
CISCO_7921
369
CISCO_7906
374
ADVANCED_3RD_PARTY_SIP_DEVICE
375
CISCO_TELEPRESENCE
404
CISCO_7962
412
CISCO_3951
431
CISCO_7937
434
CISCO_7942
435
CISCO_7945
436
CISCO_7965
437
CISCO_7975
446
CISCO_3911
468
CISCO_UNIFIED_MOBILE_COMMUNICATOR
478
CISCO_TELEPRESENCE_1000
479
CISCO_TELEPRESENCE_3000
480
CISCO_TELEPRESENCE_3200
481
CISCO_TELEPRESENCE_500
484
CISCO_7925
493
CISCO_9971
495
CISCO_6921
496
CISCO_6941
497
CISCO_6961
20000
CISCO_7905
30002
CISCO_7920
30006
CISCO_7970
30007
CISCO_7912
30008
CISCO_7902
30016
CISCO_IP_COMMUNICATOR
30018
CISCO_7961
30019
CISCO_7936
30035
IP_STE
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
6-253
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Warning-Level Alarms
Enum Reason
Code
Reason
2
MisconfiguredDirectoryNumber - There is a configuration mismatch between the directory
numbers configured on the phone and the directory numbers configured in the Cisco Unified
CM database. If this is a third-party phone, confirm that the phone configuration is correct and
matches the Cisco Unified CM configuration. If this is a Cisco IP phone, confirm database
replication has a "good status" in the Unified CM Database Status report. This can be found on
the Cisco Unified Reporting web page. If the database replication status is good, reset the
device. If the problem still persists, restart the TFTP service and the Cisco Unified CM service
from the Control Center - Feature Services web page.
3
MalformedRegisterMessage - Cisco Unified CM cannot process a REGISTER message
because of a problem with the format of the message. If the device is a third-party phone,
confirm that the endpoint is sending a properly formatted REGISTER message.
4
AuthenticationError - The digest userid or password sent from the phone does not match the
userid or password configured in Cisco Unified CM. Digest userid is the end-user associated
with the phone on the Phone Config page, Digest User drop down box. Password is configured
on the end user page, digest credentials box. If this is a third-party phone, ensure the phone
digest credentials match the digest credentials configured on the End User web page. If this is
a Cisco IP phone, confirm database replication has a "good status" in the Unified CM Database
Status report. This can be found on the Cisco Unified Reporting web page. If the database
replication status is good, reset the device. If the problem still persists, restart the TFTP service
and the Cisco Unified CM service from the Control Center - Feature Services web page.
6
MaxLinesExceeded - The phone is attempting to register more lines than are allowed. The
maximum lines per device is 1024. Reduce the number of lines configured on this device.
7
TransportProtocolMismatch - Incorrect transport protocol (UDP, TCP or TCL) on which the
REGISTER message was received. If the device is a third-party phone, ensure that the phone
is using a transport protocol that matches the Phone Security Profile assigned to the phone in
the CCMAdmin device page. If the device is a Cisco phone, confirm database replication has
a "good status" in the Unified CM Database Status report. This can be found on the Cisco
Unified Reporting web page. If the database replication status is good, reset the device. If the
problem still persists, restart the TFTP service and the Cisco Unified CM service from the
Control Center - Feature Services web page.
8
BulkRegistrationError - A unexpected bulk registration message was received. If this occurs
repeatedly, collect SDL/SDI detailed traces with "Enable SIP Keep Alive (REGISTER
Refresh) Trace" under Cisco CallManager services turned on and contact TAC.
Recommended Action
Verify that the directory number(s) on the device itself match the directory number(s) that are configured
for that device in Cisco Unified CM Administration. Also, confirm that database replication is working.
Refer to the reason code definitions for additional recommended actions.
StationEventAlert
A station device sent an alert to Cisco Unified Communications Manager, which acts as a conduit from
the device to generate this alarm.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
6-254
OL-20105-01
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Warning-Level Alarms
History
Cisco Unified Communications
Release
Action
8.0(1)
Severity changed from Error to Warning.
Facility/Sub-Facility
CCM_CALLMANAGER-CALLMANAGER
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/CallManager
Severity
Warning
Parameters
Protocol [String] TCP ProcessID [String] Device Text [String] Param1 [UInt] Param2 [UInt]
Recommended Action
Refer to the specific device type and information passed via this alarm to determine the appropriate
action.
SoftwareLicenseNotValid
There is no valid software license; the Cisco IP Voice Media Streaming App service requires a valid
software license to operate.
History
Cisco Unified Communications
Release
Action
8.0(1)
Severity changed from Error to Warning.
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/IpVms
Severity
Warning
Routing List
SDI
Event Log
Sys Log
Recommended Action
Install a valid software license and restart Cisco IP Voice Media Streaming App service.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
6-255
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Warning-Level Alarms
ThreadKillingError
An error occurred when CMI tried to stop the CMI service.
As a normal part of the process of stopping the CMI service, open threads are closed (killed). This alarm
indicates that a timeout has occurred which means that the shutdown process is taking longer than
expected, causing the operating system to return an error.
History
Cisco Unified Communications
Release
Action
8.0(1)
Name changed from kThreadKillingError.
Enum Definitions for MediaResourceType is updated.
Cisco Unified Serviceability Alarm Definition Catalog
CMIAlarmCatalog/CMI
Severity
WARNING
Routing List
Event Log
SDI
Parameter(s)
Error Information(String)
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).
UserInputFailure
EMCC login failure due to invalid user input due to invalid user credentials or the credentials have
expired. Reason Code: 2—Authentication Error.
Cisco Unified Serviceability Alarm Definition Catalog
System/EMAlarmCatalog
Severity
Warning(4)
Routing List
Sys Log
Event Log
Alert Manager
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
6-256
OL-20105-01
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Warning-Level Alarms
Parameters
Device Name(String)
Login Date/Time(String)
Login UserID(String)
Reason(String)
Recommended Action
Try again with valid credentials or try resetting the credentials.
UserUserPrecedenceAlarm
User-to-user IE was not successfully tunneled to destination; please refer to reason code for additional
details.
History
Cisco Unified Communications
Release
8.0(1)
Action
•
Severity changed from Error to Warning.
•
Enum definitions updated.
Facility/Sub-Facility
CCM_CALLMANAGER-CALLMANAGER
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/CallManager
Severity
Warning
Parameters
Device Name. [String] Reason Code [Enum]
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
6-257
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Warning-Level Alarms
Enum Definitions
Code
Definition
2
HopCountExceeded—The hop count field in passing User-to-User IE exceeded
the maximum value of 10. The reason could be the presence of routing loops
across the Unified CM trunk interfaces (PRI, intercluster trunk, and so on). The
recommended action is to check that no routing loops exist across the Unified CM
trunk interfaces (PRI, intercluster trunk, and so on) and gateway (H.323) devices
related to the indicated failed call. By examining trace files and CDR data in all
Unified CM nodes and route patterns in gateways (H.323) that are involved in
routing of the indicated failed call, you may be able to detect a translation pattern,
route list or other routing mechanism that is part of the loop. Update the routing
mechanism that resulted in the loop, and then if the looping route pattern was on
a Unified CM, reset the affected route list/pattern in an attempt to clear the route
loop; if that fails, reset the affected trunk/gateway or if the looping route pattern
was on an H.323 gateway, restart the gateway.
3
UserUserIEDropped—The passing UserUserIE is dropped. If the indicated device
is an H.323 intercluster trunk then the possible reason could be that the Passing
Precedence Level Through UUIE checkbox in the Trunk Configuration window
in Unified CM is not enabled; the recommended action is to verify that the Passing
Precedence Level Through UUIE checkbox has been enabled. If the indicated
device is an MGCP gateway with Device Protocol set to Digital Access PRI, the
possible reason could be that in the incoming UUIE message, either the IEID is
not set to USER_USER_IE (126) or the User specific protocol ID value is not set
to PRI_4ESS_UUIE_DEFAULT_PROT_DISC (0x00); the recommended action
is to verify that the far-end side of the configured PRI trunk interface supports PRI
4ESS UUIE-based MLPP and sends the UUIE message with IEID value set to
USER_USER_IE (126) and the User specific protocol ID value is set to
PRI_4ESS_UUIE_DEFAULT_PROT_DISC (0x00).
Recommended Action
For HopCountExceeded alarm, the recommended action is to check that no routing loops exist across
the Unified CM trunk interfaces (PRI, intercluster trunk, and so on) and gateway (H.323) devices related
to the indicated failed call. By examining trace files and CDR data in all Unified CM nodes and route
patterns in gateways (H.323) that are involved in routing of the indicated failed call, you may be able to
detect a translation pattern, route list or other routing mechanism that is part of the loop.
Update the routing mechanism that resulted in the loop, and then if the looping route pattern was on a
Unified CM, reset the affected route list/pattern in an attempt to clear the route loop; if that fails, reset
the affected trunk/gateway or if the looping route pattern was on a H.323 gateway, restart the gateway.
For call failure reason UserUserIEDropped, if the indicated device is an H.323 intercluster trunk then
the recommended action is to verify that the Passing Precedence Level Through UUIE checkbox has
been enabled on the Trunk Configuration window. If the indicated device is an MGCP gateway with
Device Protocol set to Digital Access PRI and Passing Precedence Level Through UUIE is enabled on
the gateway, then verify that the far-end side of the configured PRI trunk interface supports PRI 4ESS
UUIE-based MLPP and sends the UUIE message with IEID value set to USER_USER_IE (126) and the
User specific protocol ID value set to PRI_4ESS_UUIE_DEFAULT_PROT_DISC (0x00).
UnableToSetorResetMWI
An error occurred when setting the message waiting indication (MWI) lamp
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
6-258
OL-20105-01
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Warning-Level Alarms
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/CtiManager
Severity
WARNING
Routing List
SDL
SDI
Sys Log
Event Log
Parameter(s)
Directory Number(String)
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.
MediaResourceListExhausted
The requested device type is not found in the media resource list or default list or the configured devices
are not registered.
The requested device is not configured in the Media Resource Group List or Default List, or it's possible
that one or more of the devices that are configured in the Media Resource Group List or Default List are
not registered to Cisco Unified Communications Manager.
History
Cisco Unified Communications
Release
Action
8.0(1)
Enum Definitions for MediaResourceType is updated.
Facility/Sub-Facility
CCM_CALLMANAGER-CALLMANAGER
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/CallManager
Severity
Warning (4)
Parameters
Media Resource Type [Enum]Media Resource List Name [String]
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
6-259
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Warning-Level Alarms
Enum Definitions for MediaResourceType
Code
Definition
1
MediaTerminationPoint
2
Transcoder
3
ConferenceBridge
9
RSVP Agent
Recommended Action
First, go to Cisco Unified CM Administration to check the configuration of the devices that are part of
the Media Resource Groups in the Media Resource Group List that was specified in the alarm (Media
Resource Group List Configuration window and Media Resource Group Configuration window in
Unified CM Administration).
Check whether the requested type of device is configured in any of the Media Resource Groups in that
particular Media Resource Group List in Cisco Unified CM Administration; for RSVP Agent, check
whether any media termination point or transcoder is configured in any of the Media Resource Groups
in that particular Media Resource Group List. Next, go to the Media Resources menu in Cisco Unified
CM Administration to see all the devices of the requested type and then check all the Media Resource
Groups (irrespective of whether they belong to the Media Resource Group List for which the alarm is
generated) to see whether the devices belong to at least one Media Resource Group.
If there exists some media resources of the requested type which do not belong to any Media Resource
Groups, then these devices will belong to the default list. If the requested type of devices are not
configured in any of the Media Resource Groups of the Media Resource Group List for which the alarm
is generated or the Default List, add the requested type of device to a Media Resource Group in the
specified Media Resource Group List or add it to the Default List.
To add a media resource to the Default List remove the Media Device from all the Media Resource
Groups. In general, when a new media device is initially added to Unified CM it will automatically be
added to the Default List. This Default List can be used by any device or trunk. But when the media
device is added to any particular Media Resource Group it will not be available to the Default List. It
can only be used by devices and trunks that are configured with the Media Resource Group List which
have that particular Media Resource Group.
Note that a particular Media Resource Group can be added to multiple Media Resource Group Lists. If
the requested device is properly configured in Cisco Unified CM Administration, check whether the
device is registered to Unified CM. To do that go to the Media Resources menu of the requested type of
device (such as Annunciator or Conference Bridge or Media Termination Point or Music On Hold Server
or Transcoder) and click the Find button. It will display all the devices of that type with their status,
device pool, etc. Check the status field to see whether it is registered with the Cisco Unified
CallManager. Note that the display on the status field is not a confirmation that the device is registered
to Unified CM. It may happen in a Unified CM cluster that the Publisher can only write to the Unified
CM database and suppose the Publisher goes down. Because the Subscriber may not be able to write to
the database the devices may still display as registered in Unified CM Administration after they are
unregistered. However, if the Publisher is down that should generate another alarm with higher priority
than this alarm. If the device is not registered, click on the name of that particular device and check the
type of the device.
Device types including Cisco Conference Bridge Software, Cisco Media Termination Point Software, or
that specify a server name that is the same name as a Unified CM node of the cluster indicate that the
requested device is a software device and is part of the Cisco IP Voice Media Streaming application.
Check to be sure that the IP Voice Media Streaming App service is enabled on that Unified CM node
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
6-260
OL-20105-01
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Warning-Level Alarms
(Cisco Unified Serviceability > Tools > Service Activation) and if it is not enabled, activate the Cisco
IP Voice Media Streaming App service. Devices should try to register. You can also check the status of
the service to be sure it is showing as Started (Tools > Control Center > Feature Services). If the device
type is a type other than Cisco Conference Bridge Software, Cisco Media Termination Point Software,
or a server name that is the same name as a Unified CM node, that indicates that the device is an external
media resource to Unified CM.
Check the configuration (such as Conference Bridge type, MAC address, and conference bridge name
in the case of a conference bridge; Media Termination Point name in the case of a Media Termination
Point; Transcoder type, MAC address, and Transcoder name in the case of a Transcoder) of the device
in Cisco Unified CM Administration and compare it with the configuration of the actual device. To
check the configuration of the actual device you may need to refer to the user manual of the media
device.
The user manual should provide all the details such as connecting to the media device to check the
configuration, commands needed to view and update the configuration, and so on. If configuration in
Unified CM and on the actual devices are different, make the necessary changes so that the
configurations match. If the configuration matches and the device is still not registered, restart the
external media device or the service associated with the external media device. If the external media
device continues to fail to register with Unified CM, check the network connectivity between Unified
CM and the media device.
RouteListExhausted
An available route could not be found in the indicated route list. This alarm is generated when all
members' status is unavailable or busy or when the member is down (out of service), not registered, or
busy.
Facility/Sub-Facility
CCM_CALLMANAGER-CALLMANAGER
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/CallManager
Severity
Warning (4)
Parameters
Route List Name [String]
Recommended Action
Consider adding additional routes in the indicated route list. For shared line when some phones are not
ringing, check the busy trigger and maximum call settings of shared line phones; check whether there
are some outstanding calls on that DN.
When one shared line phone answers an incoming call, the other shared line phone cannot see that
remote-in-use call; check the privacy setting of the phone that answers the call.
Try to make a call directly to the member, bypassing the route list, to verify that there is not a device or
connectivity issue. If you cannot identify the cause through these steps, gather the CCM (SDI) trace and
contact the Cisco Technical Assistance Center; TAC may be able to locate a cause code which may
provide additional explanation for this alarm.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
6-261
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Warning-Level Alarms
CDRHWMExceeded
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. E-mail alert will be sent to the admin.
History
Cisco Unified Communications
Release
Action
8.0(1)
Changed Data Collector Routing List element to Alert Manager.
Facility/Sub-Facility
CDRREP
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/CDR Rep
Severity
Warning (4)
Routing List
Event Log
Sys Log
Alert Manager
Parameters
DiskUsageInMB [String]
Recommended Action
The preservation duration may be too long. Reduce it at serviceability->tools->CDRM Configuration.
Or raise maximum allocated disk space and/or HWM for CDR files.
QRTRequest
User submitted problem report using Quality Report Tool. User has experienced a problem with Phone
and has submitted problem report.
History
Cisco Unified Communications
Release
Action
8.0(1)
Changed Data Collector Routing List element to Alert Manager.
Facility/Sub-Facility
CCM_CBB-CALLBACK
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
6-262
OL-20105-01
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Warning-Level Alarms
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/CEF
Severity
Warning (4)
Routing List
SDI
Sys Log
Event Log
Alert Manager
SNMP Traps
Parameters
Category(String)
Reason Code(String)
Report Timestamp(String)
Device name.(String)
Device IP address.(String)
Directory number(String)
Recommended Action
Investigate the cause for problem report.
DeviceImageDownloadFailure
Cisco IP Phone failed to download its image.
History
Cisco Unified Communications
Release
Action
7.1
Added DeviceImageDownloadFailure to the Phone Catalog.
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/Phone
Severity
Warning (4)
Parameters
DeviceName(String)
IPAddress(String)
Active(String)
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
6-263
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Warning-Level Alarms
Inactive(String)
FailedLoadId(String)
Method(Enum)
FailureReason(Enum)
Server(String)
Enum Definitions for Method
Code
Definition
1
TFTP
2
HTTP
3
PPID
Enum Definitions for FailureReason
Code
Definition
1
TFTP server returned specific error text
2
File Not Found
3
Internal Phone Error
4
TftpClient could not write out the results
5
Encryption error
6
File not encrypted
7
Encryption key mismatch
8
Decryption failed
9
No Tftp server set
10
Illegal tftp operation
11
File already exists
12
No such user
13
Exceeded max waiting time for status
14
Data block received from Tftp was too short
15
Data block received from Tftp was too long
16
Network is down
17
DNS Name for this server could not be resolved
18
No DNS Server
19
TFTP Timeout
Recommended Action
Verify the following:
•
Image Download Server IP address or hostname is correct. If using a hostname, verify the Domain
Name Server (DNS) is accessible from the phone and can resolve the hostname.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
6-264
OL-20105-01
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Warning-Level Alarms
•
TFTP service is activated and running on the Image Download Server. Verify the Image Download
Server is accessible from the phone.
•
Device configured.
EMAppStopped
EM Application started.Application is shutting down gracefully because of an unloaded from Tomcat.
Cisco Unified Serviceability Alarm Definition Catalog
System/EMAlarmCatalog
Severity
NOTICE
Routing List
Sys Log
Event Log
Parameter(s)
Servlet Name(String)
Recommended Action
No action required.
IPMAStopped
IPMA Application stopped and unloaded from Tomcat.
Facility/Sub-Facility
CCM_JAVA_APPS-TOMCATAPPLICATIONS
Cisco Unified Serviceability Alarm Definition Catalog
System/Java Applications
Severity
Warning (4)
Parameters
Servlet Name [String] Reason [String]
Recommended Action
Check if Tomcat service is up.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
6-265
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Warning-Level Alarms
IPMAManagerLogout
IPMA Manager Logged out.
Facility/Sub-Facility
CCM_JAVA_APPS-TOMCATAPPLICATIONS
Cisco Unified Serviceability Alarm Definition Catalog
System/Java Applications
Severity
Warning (4)
Parameters
Servlet Name [String] Reason [String]
Recommended Action
To re-login the user, click update in the CCMAdmin IPMA Service configuration page for this user.
BDIStopped
BDI Application stopped. Application was unloaded from Tomcat.
Facility/Sub-Facility
CCM_JAVA_APPS-TOMCATAPPLICATIONS
Cisco Unified Serviceability Alarm Definition Catalog
System/Java Applications
Severity
Warning (4)
Recommended Action
Check if Tomcat service is up.
DirSyncNoSchedulesFound
No schedules found in DB for directory synchronization. No automatic LDAP directory synchronization
possible.
Facility/Sub-Facility
CCM_JAVA_APPS-TOMCATAPPLICATIONS
Cisco Unified Serviceability Alarm Definition Catalog
System/Java Applications
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
6-266
OL-20105-01
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Warning-Level Alarms
Severity
Warning (4)
Parameters
ScheduleTableName [String]
Recommended Action
Check the DirSync configuration
DirSyncScheduledTaskTimeoutOccurred
Timeout occurred for directory synchronization task.
Facility/Sub-Facility
CCM_JAVA_APPS-TOMCATAPPLICATIONS
Cisco Unified Serviceability Alarm Definition Catalog
System/Java Applications
Severity
Warning (4)
Parameters
SchedulerID [String] TaskID [String]
Recommended Action
Check the DirSync configuration.
DRFComponentDeRegistered
DRF successfully de-registered the requested component.
History
Cisco Unified Communications
Release
Action
8.0(1)
Name changed from CiscoDRFComponentDeRegistered.
Routing List elements added.
Facility/Sub-Facility
CCM_DRF_LOCAL & CCM_DRF_MASTER/DRF
Cisco Unified Serviceability Alarm Definition Catalog
System/DRF
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
6-267
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Warning-Level Alarms
Severity
Warning (4)
Routing List
Event Log
Sys Log
Parameters
Reason(String)
Recommended Action
Ensure that the component that was de-registered is not needed for further backup/restore operation.
DRFDeRegistrationFailure
DRF de-registration request for a component failed.
History
Cisco Unified Communications
Release
Action
8.0(1)
Name changed from CiscoDRFDeRegistrationFailure.
Routing List elements added.
Facility/Sub-Facility
CCM_DRF_LOCAL & CCM_DRF_MASTER/DRF
Cisco Unified Serviceability Alarm Definition Catalog
System/DRF
Severity
Warning (4)
Routing List
Event Log
Sys Log
Parameters
Reason(String)
Recommended Action
Check the DRF logs and contact support if needed.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
6-268
OL-20105-01
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Warning-Level Alarms
DRFDeRegisteredServer
DRF automatically de-registered all the components for a server. This server might have got
disconnected from CCM cluster.
History
Cisco Unified Communications
Release
Action
8.0(1)
Name changed from CiscoDRFDeRegisteredServer.
Routing List elements added.
Facility/Sub-Facility
CCM_DRF_LOCAL & CCM_DRF_MASTER/DRF
Cisco Unified Serviceability Alarm Definition Catalog
System/DRF
Severity
Warning (4)
Routing List
Event Log
Sys Log
Parameters
Reason(String)
Recommended Action
None
DRFSchedulerDisabled
DRF Scheduler is disabled because no configured features available for backup.
History
Cisco Unified Communications
Release
Action
8.0(1)
Name changed from CiscoDRFSchedulerDisabled.
Routing List elements added.
Facility/Sub-Facility
CCM_DRF_LOCAL & CCM_DRF_MASTER/DRF
Cisco Unified Serviceability Alarm Definition Catalog
System/DRF
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
6-269
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Warning-Level Alarms
Severity
Warning (4)
Routing List
Event Log
Sys Log
Parameters
Reason(String)
Recommended Action
Ensure at least one feature is configured for the scheduled backup to run.
TotalProcessesAndThreadsExceededThresholdStart
The current total number of processes and threads has exceeded the maximum number of tasks
configured for Cisco RIS Data Collector service parameter. This situation could indicate some process
is leaking or some process has thread leaking.
Facility/Sub-Facility
CCM_CALLMANAGER-CALLMANAGER
Cisco Unified Serviceability Alarm Definition Catalog
System/System Access
Severity
Warning (4)
Parameters
NumberOfProcesses [String] NumberOfThreads [String] Reason [String]
ProcessWithMostInstances [String] ProcessWithMostThreads [String]
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 (Cisco 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.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
6-270
OL-20105-01
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Warning-Level Alarms
To determine if this is the cause of the alarm - after you have checked all the other errors described here
- use RTMT to check the System object for performance counters Total Threads and Total Processes to
confirm that the values in those counters do not exceed the value configured in the Cisco RIS Data
Collector service parameter, Maximum Number of Processes and Threads. If the counters do not show
a value that is higher than what is configured in the service parameter, restart Cisco RIS Data Collector
service. If the alarm persists after restarting the service, go to Cisco Unified Serviceability and collect
trace logs (Trace > Configuration) for Cisco Syslog, Cisco RIS Data Collector, Cisco AMC Service, and
Cisco RIS Perfmon Logs and contact Cisco Technical Assistance Center (TAC) for detailed assistance.
ServingFileWarning
There was an error during processing of file request. 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.
History
Cisco Unified Communications
Release
Action
7.0(1)
Name changed from kServingFileWarning.
Facility/Sub-Facility
CCM_TFTP-TFTP
Cisco Unified Serviceability Alarm Definition Catalog
System/TFTP
Severity
Warning (4)
Parameters
ErrorNumber [Int] FileName [String] IPAddress_Port [String] Mode [String] OpCode [Int]
Reason [String]
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 (Cisco Unified CM). Either add the phone to Cisco 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).
TestAlarmWarning
Testing warning alarm.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
6-271
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Warning-Level Alarms
Facility/Sub-Facility
CCM_CALLMANAGER-CALLMANAGER
Cisco Unified Serviceability Alarm Definition Catalog
System/Test
Severity
Warning (4)
Recommended Action
None
authLdapInactive
Authentication failed because the user exists in the database and the system specifies LDAP
authentication. A directory sync got performed in the immediate past (1 day).
History
Cisco Unified Communications
Release
Action
7.0(1)
Error message added.
8.0(1)
Revised the description and added text to Recommended Action.
Cisco Unified Serviceability Alarm Definition Catalog
System/IMS
Severity
Warning (4)
Parameters
Authentication failure due to LDAP inactive(String)
Recommended Action
This user has yet to be removed from the database or the alarm will clear itself within 24 hours.
authAdminLock
User is locked out by administrator.
History
Cisco Unified Communications
Release
Action
7.0(1)
Error message added.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
6-272
OL-20105-01
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Warning-Level Alarms
Cisco Unified Serviceability Alarm Definition Catalog
System/IMS
Severity
Warning (4)
Parameters
lock(String)
Recommended Action
Administrator can unlock this user.
authHackLock
User attempted too many incorrect authentications. The maximum number of attempts gets set by the
administrator.
History
Cisco Unified Communications
Release
Action
7.0(1)
Error message added.
8.0(1)
Added more descriptive text and corrected the parameter.
Cisco Unified Serviceability Alarm Definition Catalog
System/IMS
Severity
Warning (4)
Parameters
UserID(String)
Recommended Action
Wait for administrator specified time to retry, or have administrator unlock the credential.
authInactiveLock
The user has been inactive for a specified time and the credential is locked.
History
Cisco Unified Communications
Release
Action
7.0(1)
Error message added.
8.0(1)
Changed parameter text.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
6-273
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Warning-Level Alarms
Cisco Unified Serviceability Alarm Definition Catalog
System/IMS
Severity
Warning (4)
Parameters
UserID(String)
Recommended Action
Reset credential.
BeginThrottlingCallListBLFSubscriptions
Cisco Unified Communications Manager has initiated throttling of CallList BLF Subscriptions as a
preventive measure to avoid overloading the system. This alarm is raised when the total number of active
BLF subscriptions exceeds the configured limit set by the Presence Subscription Throttling Threshold
service parameter.
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/CallManager
Severity
Warning (4)
Parameters
Active External Presence Subscriptions [UInt] CallList BLF Subscriptions Throttling Threshold [UInt]
CallList BLF Subscriptions Resume Threshold [UInt] Total Begin Throttling CallList BLF
Subscriptions [UInt]
Recommended Action
Determine if CPU and memory resources are available to meet the higher demand for CallList BLF
Subscriptions. If so, increase the CallListBLFSubscriptionsThrottlingThreshold and correspondingly
the CallListBLFSubscriptionsResumeThreshold. If not, increase system resources to meet the demand.
ServiceStartupFailed
Service startup failure.
Cisco Unified Serviceability Alarm Definition Catalog
System/Generic
Severity
Warning (4)
Parameters
None
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
6-274
OL-20105-01
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Warning-Level Alarms
Recommended Action
Restart the service.
authFail
Failed to authenticate this user.
History
Cisco Unified Communications
Release
Action
7.0(1)
Error message added.
8.0(1)
Changed severity level from Notice to Warning.
Cisco Unified Serviceability Alarm Definition Catalog
System/IMS
Severity
Warning (4)
Parameters
Authentication failure(String)
Recommended Action
Determine correct credentials and retry.
kANNAudioCreateDirFailed
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.
History
Cisco Unified Communications
Release
8.0(1)
Action
Added more Recommended Action text. Updated parameters and
changed severity level from Error to Warning.
Facility/Sub-Facility
CCM_MEDIA_STREAMING_APP-IPVMS
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/IpVms
Severity
Warning (4)
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
6-275
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Warning-Level Alarms
Parameters
OS Error Text(String)
Path Name(String)
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.
MOHDeviceRecoveryCreateFailed
An error got triggered restarting the Music On Hold (MOH) device. It may have been caused by a
shortage of memory resources.
History
Cisco Unified Communications
Release
8.0(1)
Action
Changed severity level from Error to Warning and added existing
Routing List elements.
Facility/Sub-Facility
CCM_MEDIA_STREAMING_APP-IPVMS
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/IpVms
Severity
Warning (4)
Routing List
SDI
Event Log
Sys Log
Parameters
ErrorText(String)
Error(ULong0
Recommended Action
Check the status of the MOH device. If it is not registered and available, restart the Cisco IP voice Media
Streaming App service or restart the server.
kMOHDeviceRecordNotFound
MOH device was not found for the server. This device gets added automatically when a server gets
added to the configuration.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
6-276
OL-20105-01
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Warning-Level Alarms
History
Cisco Unified Communications
Release
Action
3.x and 4.x
Added for Windows.
8.0(1)
Updated the descriptive text and Recommended Action text. Added
Caution statement. Changed severity level from Informational to
Warning.
Facility/Sub-Facility
CCM_MEDIA_STREAMING_APP-IPVMS
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/IpVms
Severity
Warning (4)
Recommended Action
If MOH functionality is required, you will have to remove and re-add the device to database.
Caution
Adding and removing the device may impact other configuration settings, for example, Cisco Unified
Communications Manager groups and media resource groups.
kDeviceMgrExitEventCreationFailed
Creation of device manager exit event failure. 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.
History
Cisco Unified Communications
Release
Action
3.x and 4.x
Added for Windows.
8.0(1)
Added Routing List elements. Changed severity level from Error to
Warning.
Facility/Sub-Facility
CCM_MEDIA_STREAMING_APP-IPVMS
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/IpVms
Severity
Warning (4)
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
6-277
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Warning-Level Alarms
Routing List
SDI
Event Log
Sys Log
Parameters
Device Name [String]
Trace Name [String]
OS Error Text [String]
Recommended Action
This error may be due to a memory resource shortage. Restart the Cisco IP Voice Media Streaming App
service or restart the Cisco Unified CM server.
kMOHBadMulticastIP
An invalid multicast IP address (out of range) was found.
History
Cisco Unified Communications
Release
Action
3.x and 4.x
Added for Windows.
8.0(1)
Added Routing List elements and changed severity level to Warning
from Error.
Following parameters are removed:
•
Audio Source ID [ULong]
•
Call/Conference ID [ULong]
•
Multicast IP Port [ULong]
Facility/Sub-Facility
CCM_MEDIA_STREAMING_APP-IPVMS
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/IpVms
Severity
Warning (4)
Routing List
SDI
Event Log
Sys Log
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
6-278
OL-20105-01
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Warning-Level Alarms
Parameters
Codec Type [String]
Multicast IP Address [String]
Recommended Action
Correct the setting on the Music-on-Hold device configuration for multicast address.
kDeviceMgrSocketDrvNotifyEvtCreateFailed
This alarm get generated when creating a signaling event for communication with the media streaming
kernel driver. It can be caused by memory or system resource shortages/
History
Cisco Unified Communications
Release
Action
3.x and 4.x
Added for Windows.
8.0(1)
Added Routing List elements. Changed severity level to Warning
from Error.
Facility/Sub-Facility
CCM_MEDIA_STREAMING_APP-IPVMS
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/IpVms
Severity
Warning (4)
Routing List
SDI
Event Log
Sys Log
Parameters
Device Name [String]
Trace Name [String]
OS Error Description [String]
Recommended Action
Restart the Cisco IP Voice Media Streaming App service or restart the Cisco Unified Communications
Manager server.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
6-279
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Notice-Level Alarms
WDStopped
WebDialer application stopped and was unloaded from Tomcat.
History
Cisco Unified Communications
Release
Action
8.0(1)
Severity changed from Alert to Warning.
Facility/Sub-Facility
CCM_JAVA_APPS_TOMCATAPPLICATIONS
Cisco Unified Serviceability Alarm Definition Catalog
System/Java Applications
Severity
Warning
Parameters
Servlet Name [String] Reason [String]
Recommended Action
Check if Tomcat service is up.
Notice-Level Alarms
The notice-level alarm is 5 and no action is needed unless the information is unexpected. Notifications
about interesting system-level conditions which are not error conditions. Informational in nature but
having a more important need-to-know status. Examples are:
•
System-wide notifications
•
Process is shutting down gracefully on request
•
Clearing of previously raised conditions
•
A device or subsystem un-registering or shutting down for expected and normal reason (for
individual phone related expected and normal unregistering or shutting down, informational level
should be used)
•
Password change notification and upgrade notification
BChannelISV
B-channel is in service.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
6-280
OL-20105-01
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Notice-Level Alarms
History
Cisco Unified Communications
Release
Action
8.0(1)
Changed severity level from Informational to Notice.
Facility/Sub-Facility
CCM_CALLMANAGER-CALLMANAGER
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/CallManager
Severity
Notice
Parameters
Channel Id. [UInt] Unique channel ID [String] Device name. [String]
Recommended Action
None
CallManagerOnline
Cisco CallManager service has completed initialization is online.
Facility/Sub-Facility
CCM_CALLMANAGER-CALLMANAGER
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/CallManager
Severity
Notice (5)
Parameters
CCM Version [String]
Recommended Action
None
CertValidityOver30Days
Alarm indicates that the certificate expiry is approaching but the expiry date is more than 30 days.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
6-281
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Notice-Level Alarms
Cisco Unified Serviceability Alarm Definition Catalog
System/CertMonitorAlarmCatalog
Severity
Notice(5)
Routing List
Event Log
Sys Log
Parameters
Message(String)
Recommended Action
Regenerate the certificate that is about to expire by accessing the Cisco Unified Operating System and
go to Certificate Management. If the certificate is issued by a CA, generate a CSR, submit the CSR to
CA, obtain a fresh certificate from CA, and upload it to Cisco Unified CM.
CodeYellowExit
CodeYellowExit. Unified CM has ceased throttling calls and has exited the Code Yellow state.
History
Cisco Unified Communications
Release
Action
8.0(1)
Severity changed from Error to Notice.
Facility/Sub-Facility
CCM_CALLMANAGER-CALLMANAGER
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/CallManager
Severity
Notice
Parameters
Expected Average Delay [UInt] Entry Latency [UInt] Exit Latency [UInt] Sample Size [UInt] Time
Spent in Code Yellow [UInt] Number of Calls Rejected Due to Call Throttling [UInt] Total Code Yellow
Exit [UInt]
Recommended Action
None.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
6-282
OL-20105-01
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Notice-Level Alarms
DbInsertValidatedDIDFailure
The Insertion of a IME provided e164DID has failed. A failure occurred attempting to insert a Cisco
Unified Active Link learned DID
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/CallManager
Severity
NOTICE
Routing List
SDL
SDI
Sys Log
Event Log
SNMP Traps
Data Collector
Parameter(s)
e164 DID(String)
Granting Domain(String)
Recommended Action
Verify the DID and the granting domain. Check other associated alarms. Verify the database integrity.
DChannelISV
Indicated D-channel has gone in service.
History
Cisco Unified Communications
Release
Action
8.0(1)
Severity changed from Informational to Notice.
Facility/Sub-Facility
CCM_CALLMANAGER-CALLMANAGER
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/CallManager
Severity
Notice
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
6-283
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Notice-Level Alarms
Parameters
Channel Id. [UInt] Unique channel Id [String] Device Name. [String] Device IP address [String]
Recommended Action
None
EndPointRegistered
This alarm occurs when a device is successfully registered with Cisco Unified Communications
Manager.
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/CallManager
Severity
NOTICE
Routing List
SDL
SDI
Sys Log
Data Collector
SNMP Traps
Alternate Syslog
Parameter(s)
Device name(String)
Device MAC address(String)
Device IP address(String)
Protocol(String)
Device description(String)
User ID(String)
Load ID(String)
Associated directory numbers(String)
Performance monitor object type(Enum)
Device type(Enum)
Configured Gatekeeper Name(String)
Technology Prefix Name(String)
Zone Information(String)
Alternate Gatekeeper List(String)
Active Gatekeeper(String)
Call Signal Address(String)
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
6-284
OL-20105-01
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Notice-Level Alarms
RAS Address(String)
IPV6Address(String)
IPAddressAttributes(Enum)
IPV6AddressAttributes(Enum)
ActiveLoadId(String)
InactiveLoadId(String)
Enum Definitions -Performance monitor object type
Value
Definition
2
Cisco Phone
Enum Definitions -Device type
Value
Definition
1
CISCO_30SP+
2
CISCO_12SP+
3
CISCO_12SP
4
CISCO_12S
5
CISCO_30VIP
6
CISCO_7910
7
CISCO_7960
8
CISCO_7940
9
CISCO_7935
12
CISCO_ATA_186
20
SCCP_PHONE
61
H323_PHONE
72
CTI_PORT
115
CISCO_7941
119
CISCO_7971
255
UNKNOWN
302
CISCO_7989
307
CISCO_7911
308
CISCO_7941G_GE
309
CISCO_7961G_GE
335
MOTOROLA_CN622
336
BASIC_3RD_PARTY_SIP_DEVICE
348
CISCO_7931
358
CISCO_UNIFIED_COMMUNICATOR
365
CISCO_7921
369
CISCO_7906
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
6-285
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Notice-Level Alarms
Value
Definition
374
ADVANCED_3RD_PARTY_SIP_DEVICE
375
CISCO_TELEPRESENCE
404
CISCO_7962
412
CISCO_3951
431
CISCO_7937
434
CISCO_7942
435
CISCO_7945
436
CISCO_7965
437
CISCO_7975
446
CISCO_3911
468
CISCO_UNIFIED_MOBILE_COMMUNICATOR
478
CISCO_TELEPRESENCE_1000
479
CISCO_TELEPRESENCE_3000
480
CISCO_TELEPRESENCE_3200
481
CISCO_TELEPRESENCE_500
484
CISCO_7925
493
CISCO_9971
495
CISCO_6921
496
CISCO_6941
497
CISCO_6961
20000
CISCO_7905
30002
CISCO_7920
30006
CISCO_7970
30007
CISCO_7912
30008
CISCO_7902
30016
CISCO_IP_COMMUNICATOR
30018
CISCO_7961
30019
CISCO_7936
30035
IP_STE
Enum Definitions -IPAddressAttributes
Value
Definition
0
Unknown - The device has not indicated what this IPv4 address is used
for
1
Administrative only - The device has indicated that this IPv4 address is
used for administrative communication (web interface) only
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
6-286
OL-20105-01
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Notice-Level Alarms
Value
Definition
2
Signal only - The device has indicated that this IPv4 address is used for
control signaling only
3
Administrative and signal - The device has indicated that this IPv4
address is used for administrative communication (web interface) and
control signaling
Enum Definitions -IPV6AddressAttributes
Value
Definition
0
Unknown - The device has not indicated what this IPv6 address is used
for
1
Administrative only - The device has indicated that this IPv6 address is
used for administrative communication (web interface) only
2
Signal only - The device has indicated that this IPv6 address is used for
control signaling only
3
Administrative and signal - The device has indicated that this IPv6
address is used for administrative communication (web interface) and
control signaling
Recommended Action
No action is required.
H323Started
Cisco CallManager is ready to handle calls for the indicated H323 device. Cisco Unified
Communications Manager is ready to communicate with the indicated H.323 device. Note that this alarm
describes the readiness of Unified CM to communicate with the indicated device, but does not provide
information about the state of the H.323 device (whether it is ready to communicate as well).
History
Cisco Unified Communications
Release
8.0(1)
Action
•
Severity changed from Informational to Notice.
•
Following information updated:
– Parameters
– Enum Definitions for DeviceType
Facility/Sub-Facility
CCM_CALLMANAGER-CALLMANAGER
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/CallManager
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
6-287
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Notice-Level Alarms
Severity
Notice
Parameters
Device Name. [String] IP Address [String] Device type. [Optional] [Enum]Device description
[Optional]. [String] The Server 1 IP Address/Host Name as configured in the Trunk Configuration
window [String] Remote CallManager Server 2[Optional]. [String] Remote CallManager Server
3[Optional]. [String]
Enum Definitions for DeviceType
Code
Device Type
61
H323_PHONE
62
H323_GATEWAY
122
GATEKEEPER
125
TRUNK
Recommended Action
None
ICTCallThrottlingEnd
Cisco CallManager starts handling calls for the indicated H323 device. Cisco CallManager has ceased
throttling calls on the indicated H.323 device.
History
Cisco Unified Communications
Release
Action
8.0(1)
Severity changed from Error to Notice.
Facility/Sub-Facility
CCM_CALLMANAGER-CALLMANAGER
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/CallManager
Severity
Notice
Parameters
Device Name. [String] IP Address [String] Device type. [Optional] [Enum]Device description
[Optional]. [String]
Enum Definitions for DeviceType
•
125—TRUNK
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
6-288
OL-20105-01
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Notice-Level Alarms
Recommended Action
None.
kDeviceMgrMoreThan50SocketEvents
More than 50 events returned from TCP link. The specified Cisco Unified Communications Manager
TCP link has returned a large number of TCP events. This indicates an unexpected flood of events.
History
Cisco Unified Communications
Release
Action
3.x and 4.x
Added for Windows.
7.0(1)
Obsoleted.
8.0(1)
This alarm is available in 8.0(1). Severity changed from
Informational to Notice.
Facility/Sub-Facility
CCM_MEDIA_STREAMING_APP-IPVMS
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/IpVms
Severity
Notice
Parameters
Trace Name [String]
Recommended Action
No action is required. Monitor for reoccurrence. This could be an indication of a security issue.
MGCPGatewayGainedComm
The MGCP gateway has established communication with Cisco Unified Communications Manager.
History
Cisco Unified Communications
Release
Action
8.0(1)
Severity changed from Informational to Notice.
Facility/Sub-Facility
CCM_CALLMANAGER-CALLMANAGER
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
6-289
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Notice-Level Alarms
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/CallManager
Severity
Notice
Parameters
Device Name [String]
Recommended Action
Informational purposes only; no action is required.
MaxCallDurationTimeout
An active call was cleared because the amount of time specified in the Maximum Call Duration Timer
service parameter had elapsed. If the allowed call duration is too short, you can increase the value. If
you do not want a limit on the duration of an active call, you can disable the limit. If the duration is
correct but you did not expect a call to ever exceed that duration, check the trace information around the
time that this alarm occurred to try to determine if a gateway port had failed to release a call.
History
Cisco Unified Communications
Release
8.0(1)
Action
•
Severity changed from Informational to Notice.
•
Following parameters added:
– Originating Device name(String)
– Destination Device name(String)
– Call start time(UInt)
– Call stop time(UInt)
– Calling Party Number(String)
– Called Party Number(String)
Facility/Sub-Facility
CCM_CALLMANAGER-CALLMANAGER
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/CallManager
Severity
Notice
Parameters
Maximum Call Duration (minutes) [UInt]
Originating Device name(String)
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
6-290
OL-20105-01
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Notice-Level Alarms
Destination Device name(String)
Call start time(UInt)
Call stop time(UInt)
Calling Party Number(String)
Called Party Number(String)
Recommended Action
If the duration of the call is too short, increase the value in the Cisco CallManager service parameter or
disable the maximum duration by setting the Maximum Call Duration Timer parameter to zero. If you
suspect a hung gateway port, check the trace files around the time that this alarm occurred to search for
the gateway that was involved in the call, then check the status of that gateway to determine if all ports
are functioning normally.
SDLLinkISV
SDL link to remote application is restored. This alarm indicates that the local Cisco CallManager has
gained communication with the remote Cisco CallManager.
Note
The remote Cisco CallManager should also indicate SDLLinkISV with a different LinkID.
History
Cisco Unified Communications
Release
Action
8.0(1)
Severity changed from Informational to Notice.
Facility/Sub-Facility
CCM_CALLMANAGER-CALLMANAGER
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/CallManager
Severity
Notice
Parameters
Remote IP address of remote application [String] Unique Link ID. [String] Local node ID [UInt] Local
Application ID. [Enum]RemoteNodeID [UInt] Remote application ID. [Enum]
Enum Definitions for LocalApplicationId and RemoteApplicationID
Code
Reason
100
CallManager
200
CTI Manager
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
6-291
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Notice-Level Alarms
Recommended Action
None
SIPStarted
Cisco CallManager is ready to handle calls for the indicated SIP device. This alarm does not indicate the
current state of the SIP device, only that Cisco CallManager is prepared to handle calls to/from the SIP
device.
History
Cisco Unified Communications
Release
8.0(1)
7.1
Action
•
Severity changed from Informational to Notice.
•
Enum Definitions for InTransportType and OutTransportType
are updated.
IPV6Address parameter added.
Facility/Sub-Facility
CCM_CALLMANAGER-CALLMANAGER
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/CallManager
Severity
Notice
Parameters
Device Name. [String]
IP Address [Optional]. [String]
Device type. [Optional] [Enum]
Device description [Optional]. [String]
Incoming Port Number. [UInt]
Outgoing Port Number. [UInt]
Incoming Transport Type [Enum]
Outgoing Transport Type [Enum]
IPV6Address [Optional]. [String]
Enum Definitions for DeviceType
•
131—SIP_TRUNK
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
6-292
OL-20105-01
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Notice-Level Alarms
Enum Definitions for InTransportType
Code
Definition
1
TCP
2
UDP
3
TLS
4
TCP/UDP
Enum Definitions for OutTransportType
Code
Definition
1
TCP
2
UDP
3
TLS
Recommended Action
None
SMDICmdError
CMI receives an invalid incoming SMDI message.
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 does not have one of the
acceptable formats as described.
History
Cisco Unified Communications
Release
Action
8.0(1)
Name changed from kSMDICmdError.
Cisco Unified Serviceability Alarm Definition Catalog
CMIAlarmCatalog/CMI
Severity
NOTICE
Routing List
Event Log
SDI
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
6-293
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Notice-Level Alarms
Parameter(s)
Invalid SMDI command(String)
Recommended Action
Contact the vendor of the third-party voice messaging system and discover why it is sending SMDI
message with an invalid format.
SMDIMessageError
SMDI message contains invalid DN.
History
Cisco Unified Communications
Release
Action
8.0(1)
Name changed from kSMDIMessageError.
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.
Cisco Unified Serviceability Alarm Definition Catalog
CMIAlarmCatalog/CMI
Severity
NOTICE
Routing List
Event Log
SDI
Parameter(s)
Invalid SMDI command(String)
Recommended Action
Verify that the Cisco Messaging Interface service parameter Validate DNs is set to false.
TestAlarmNotice
Testing notice alarm.
Facility/Sub-Facility
CCM_CALLMANAGER-CALLMANAGER
Cisco Unified Serviceability Alarm Definition Catalog
System/Test
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
6-294
OL-20105-01
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Notice-Level Alarms
Severity
Notice (5)
Recommended Action
None
TotalProcessesAndThreadsExceededThresholdEnd
The current total number of processes and threads is less than the maximum number of tasks configured
in the Cisco RIS Data Collector service parameter, Maximum Number of Processes and Threads.
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.
History
Cisco Unified Communications
Release
Action
8.0(1)
Severity changed from Informational to Notice.
Facility/Sub-Facility
CCM_CALLMANAGER-CALLMANAGER
Cisco Unified Serviceability Alarm Definition Catalog
System/System Access
Severity
Notice
Parameters
NumberOfProcesses [String] NumberOfThreads [String] Reason [String]
Recommended Action
This alarm is for information purposes only; no action is required.
authExpired
Authentication failure due to expired soft lock. User credentials have expired.
History
Cisco Unified Communications
Release
Action
7.0(1)
Error message added.
8.0(1)
Added Routing List element and updated the parameter list.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
6-295
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Notice-Level Alarms
Cisco Unified Serviceability Alarm Definition Catalog
System/IMS
Severity
Notice (5)
Routing List
Event Log
Parameters
Authentication failure due to expired soft lock.(String)
Recommended Action
Administrator may reset the credential.
authMustChange
Authentication failed because it is marked that it must be changed by the user.“User must change” is set
on this credential. The user must change the credential.
History
Cisco Unified Communications
Release
Action
7.0(1)
Error message added.
8.0(1)
Added more description and Routing List element. Corrected the
parameter.
Cisco Unified Serviceability Alarm Definition Catalog
System/IMS
Severity
Notice (5)
Routing List
Event Log
Parameters
UserID[String]
Recommended Action
User or Administrator may reset credential.
credReadFailure
Error occurred attempting to read a credential in the database. This could be a network or database issue.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
6-296
OL-20105-01
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Informational-Level Alarms
History
Cisco Unified Communications
Release
Action
7.0(1)
Error message added.
8.0(1)
Changed severity level to Notice from Informational.Corrected
parameter and added Routing List element.
Cisco Unified Serviceability Alarm Definition Catalog
System/IMS
Severity
Notice (5)
Routing List
Event
Parameters
Credential read failure for(String)
Recommended Action
Ensure credential (user name) exists. Could be a database problem.
Informational-Level Alarms
The informational-level of alarm is 6 and no action is needed. Informational messages provide historical
data such as internal flows of the application or per-request information. Informational messages are
used for troubleshooting by users who are familiar with the basic flows of the application. An example
would be a normal (expected) event occurred that the customer may want to be notified about.
AdministrativeEvent
Failed to write into the primary file path. Audit Event is generated by this application.
Cisco Unified Serviceability Alarm Catalog
AuditLog
Severity
INFORMATIONAL
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.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
6-297
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Informational-Level Alarms
CiscoHardwareLicenseInvalid
Installation on invalid or obsolete hardware. Cannot upload license files.
Cisco Unified Serviceability Alarm Definition Catalog
System/Java Applications
Severity
INFORMATIONAL
Routing List
Sys Log
Event Log
SNMP Traps
Parameter(s)
Reason(String)
Recommended Action
Obtain correct hardware and re-install.
CiscoLicenseFileInvalid
License File is invalid.
Cisco Unified Serviceability Alarm Definition Catalog
System/Java Applications
Severity
INFORMATIONAL
Routing List
Sys Log
Event Log
SNMP Traps
Parameter(s)
Reason(String)
Recommended Action
Rehost the License files.
CMIServiceStatus
CMI service is running and working properly.Cisco Unified Serviceability Alarm Definition Catalog.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
6-298
OL-20105-01
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Informational-Level Alarms
History
Cisco Unified Communications
Release
Action
8.0(1)
Name changed from kCMIServiceStatus.
Cisco Unified Serviceability Alarm Definition Catalog
CMIAlarmCatalog/CMI
Severity
INFORMATIONAL
Routing List
Event Log
SDI
Parameter(s)
Service Priority(String)
Recommended Action
Informational purpose only; no action is required.
ConnectionToPDPInService
A connection was successfully established between Cisco Unified Communications Manager (Unified
CM) and the policy decision point (PDP).
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/CallManager
Severity
Informational(6)
Routing List
SDL
SDI
Sys Log
Event Log
Parameters
Policy Decision Point(String)
Recommended Action
None
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
6-299
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Informational-Level Alarms
CriticalEvent
Failed to write into the primary file path. Audit Event is generated by this application.
Cisco Unified Serviceability Alarm Catalog
AuditLog
Severity
INFORMATIONAL
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.
CtiDeviceClosed
Application closed a device.
History
Cisco Unified Communications
Release
Action
8.0(1)
Name changed from kCtiDeviceClosed.
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/CtiManager
Severity
INFORMATIONAL
Routing List
SDL
SDI
Sys Log
Event Log
Data Collector
Parameter(s)
Device Name(String)
RTP Address(String)
Reason code.(Enum)
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
6-300
OL-20105-01
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Informational-Level Alarms
Enum Definitions - Reason Code
Value
Definition
0
Unknown
1
CallManager service is not available to process request; verify that the CallManager service is active. Check the Cisco Unified Serviceability Control
Center section in Cisco Unified CM Administration (Tools > Control Center
- Feature Services)
2
Device has unregistered with Cisco Unified Communications Manager
3
Device failed to rehome to Cisco Unified Communications Manager; verify
that the device is registered
4
Device is removed from the Unified CM database
5
Application controlling the device has closed the connection
6
Route Point already registered by another application
7
CTI Port already registered by another application
8
CTI Port/Route Point already registered with dynamic port media termination
9
Enabling softkey failed for device; verify that the device is registered
10
Multiple applications have registered the device with media capability that
do not match
11
This device is already controlled by another application
12
Protocol used by the device is not supported
13
Device is restricted for control by any application
14
Unable to communicate with database to retrieve device information
15
Device is resetting
16
Unable to register the device as specified media type is not supported
17
Unsupported device configuration
18
Device is being reset
19
IPAddress mode does not match what is configured in Unified CM
Recommended Action
This alarm is for informational purposes only; no action is required.
CtiDeviceInService
Device is back in service.
History
Cisco Unified Communications
Release
Action
8.0(1)
Name changed from kCtiDeviceInService.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
6-301
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Informational-Level Alarms
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/CtiManager
Severity
INFORMATIONAL
Routing List
SDL
SDI
Sys Log
Event Log
Parameter(s)
Device Name(String)
Recommended Action
This alarm is for informational purposes only; no action is required.
CtiDeviceOpened
Application opened a device.
History
Cisco Unified Communications
Release
Action
8.0(1)
Name changed from kCtiDeviceOpened.
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/CtiManager
Severity
INFORMATIONAL
Routing List
SDL
SDI
Sys Log
Event Log
Data Collector
Parameter(s)
Device Name(String)
RTP Address(String)
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
6-302
OL-20105-01
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Informational-Level Alarms
Recommended Action
This alarm is for informational purposes only; no action is required.
CtiLineOpened
Application opened the line.
History
Cisco Unified Communications
Release
Action
8.0(1)
Name changed from kCtiLineOpened.
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/CtiManager
Severity
INFORMATIONAL
Routing List
SDL
SDI
Sys Log
Event Log
Data Collector
Parameter(s)
Directory Number(String)
Partition(String)
Device Name(String)
Recommended Action
This alarm is for informational purposes only; no action is required.
CtiLineOutOfService
Line is out of service.
History
Cisco Unified Communications
Release
Action
8.0(1)
Name changed from kCtiLineOutOfService.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
6-303
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Informational-Level Alarms
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/CtiManager
Severity
INFORMATIONAL
Routing List
SDL
SDI
Sys Log
Event Log
Parameter(s)
Directory Number(String)
Device Name(String)
Recommended Action
This alarm is for informational purposes only; no action is required.
CtiProviderClosed
CTI application closed the provider. The IP address is shown in either IPv4 or IPv6 format depending
on the IP addressing mode of the application.
History
Cisco Unified Communications
Release
Action
8.0(1)
Name changed from kCtiProviderClosed.
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/CtiManager
Severity
INFORMATIONAL
Routing List
SDL
SDI
Sys Log
Event Log
Data Collector
Parameter(s)
Login User Id(String)
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
6-304
OL-20105-01
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Informational-Level Alarms
IPAddress(String)
IPV6Address(String)
Reason code(Enum)
Enum Definitions - Reason Code
Value
Definition
0
Unknown
1
Heart beat from application missed. Possible causes include network
connectivity issues or Unified CM node experiencing high CPU usage.
Make sure that the network connectivity between Unified CM and the
application by pinging the application server host from Cisco Unified
OS Administration and take steps to establish connectivity if it has been
lost. Also check for and fix any network issues or high CPU usage on
the application server
2
Unexpected shutdown; possibly cause is application disconnected the
TCP connection. Also check for and fix any network issues or high CPU
usage on the application server
3
Application requested provider close
4
Provider open failure; application could not be initialized
5
User deleted. User associated with the application is deleted from the
Unified CM Administration
6
SuperProvider permission associated with the application is removed.
Verify the user group configuration for the user in Unified CM Admin
under (User Management > End User/Application User), select the user
and review the associated permissions information
7
Duplicate certificate used by application. Verify the CAPF profile configuration for the user in Unified CM Admin under (User Management
> End User CAPF Profile/Application User CAPF Profile), select the
CAPF profile of the user and review the associated information
8
CAPF information unavailable. Verify the CAPF profile configuration
for the user in Unified CM Admin under (User Management > End User
CAPF Profile/Application User CAPF Profile), select the CAPF profile
of the user and review the associated information
9
Certificate compromised. Verify the CAPF profile configuration for the
user in Unified CM Admin under (User Management > End User CAPF
Profile/Application User CAPF Profile), select the CAPF profile of the
user and review the associated information
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
6-305
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Informational-Level Alarms
3
Application requested provider close
4
Provider open failure; application could not be initialized
5
User deleted. User associated with the application is deleted from the
Unified CM Administration
6
SuperProvider permission associated with the application is removed.
Verify the user group configuration for the user in Unified CM Admin
under (User Management > End User/Application User), select the user
and review the associated permissions information
7
Duplicate certificate used by application. Verify the CAPF profile configuration for the user in Unified CM Admin under (User Management
> End User CAPF Profile/Application User CAPF Profile), select the
CAPF profile of the user and review the associated information
8
CAPF information unavailable. Verify the CAPF profile configuration
for the user in Unified CM Admin under (User Management > End User
CAPF Profile/Application User CAPF Profile), select the CAPF profile
of the user and review the associated information
9
Certificate compromised. Verify the CAPF profile configuration for the
user in Unified CM Admin under (User Management > End User CAPF
Profile/Application User CAPF Profile), select the CAPF profile of the
user and review the associated information
Recommended Action
This alarm is for informational purposes only; no action is required.
CtiProviderOpened
CTI Application opened the provider successfully. The IP address is shown in either IPv4 or IPv6 format
depending on the IP addressing mode of the Application.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
6-306
OL-20105-01
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Informational-Level Alarms
History
Cisco Unified Communications
Release
Action
8.0(1)
Name changed from kCtiProviderOpened.
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/CtiManager
Severity
INFORMATIONAL
Routing List
SDL
SDI
Sys Log
Event Log
Data Collector
Parameter(s)
Login User Id(String)
Version Number(String)
IPAddress(String)
IPV6Address(String)
Recommended Action
This alarm is for informational purposes only; no action is required.
DatabaseDefaultsRead
Database default information was read successfully.
History
Cisco Unified Communications
Release
Action
8.0(1)
Severity changed from Notice to Informational.
Facility/Sub-Facility
CCM_CALLMANAGER-CALLMANAGER
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/CallManager
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
6-307
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Informational-Level Alarms
Severity
Informational
Parameters
None
Recommended Action
None
CtiDeviceOutofService
Device is out of service.
History
Cisco Unified Communications
Release
Action
8.0(1)
Name changed from kCtiDeviceOutofService.
Severity changed from Notice to Informational.
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/CtiManager
Severity
INFORMATIONAL
Routing List
SDL
SDI
Sys Log
Event Log
Parameter(s)
Device Name(String)
Recommended Action
This alarm is for informational purposes only; no action is required.
CtiLineClosed
Application closed the line.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
6-308
OL-20105-01
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Informational-Level Alarms
History
Cisco Unified Communications
Release
Action
8.0(1)
Name changed from kCtiLineClosed.
Severity changed from Notice to Informational.
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/CtiManager
Severity
INFORMATIONAL
Routing List
SDL
SDI
Sys Log
Event Log
Data Collector
Parameter(s)
Directory Number(String)
Partition(String)
Device Name(String)
Reason code.(Enum)
Enum Definitions - Reason Code
Value
Definition
0
Unknown
1
CallManager failure
2
Device has unregistered with Cisco Unified Communications Manager;
wait for the device to register
3
CTI failed to rehome the line; verify that the device is registered
4
Undefined line, possible cause could be that line is no more active on
that device due to extension mobility login or logout
5
Device removed
6
Provider controlling the device is closed
7
Protocol used by the device is not supported
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
6-309
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Informational-Level Alarms
Value
Definition
8
Application cannot control this line as CTI Allow Control is not
enabled. Administrator has restricted the Line to be controllable by application. If the intent of the Administrator is to allow control of this
line, enable the check box labelled Allow control of Device from CTI,
in Unified CM Administration under Call Routing > Directory Number
and choose the line that should be controlled by this application
9
Unable to register the device; application specified media type is not
supported
10
Device is being reset; verify that the device is registered before opening
the line
11
Unsupported device configuration
Recommended Action
This alarm is for informational purposes only; no action is required.
CtiLineInService
Line is back in service
History
Cisco Unified Communications
Release
Action
8.0(1)
Name changed from kCtiLineInService.
Severity changed from Notice to Informational.
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/CtiManager
Severity
INFORMATIONAL
Routing List
SDL
SDI
Sys Log
Event Log
Recommended Action
This alarm is for informational purposes only; no action is required.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
6-310
OL-20105-01
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Informational-Level Alarms
DefaultDurationInCacheModified
Default value of a Certificate duration in cache is modified in the Service Parameter page. This usually
means that the Default Certificate duration in cache value is modified in the Service Parameter page.
Cisco Unified Serviceability Alarm Catalog
System/TVS
Severity
INFORMATIONAL
Routing List
SDI
Event Log
Data Collector
Sys Log
Recommended Action
None.
DeviceApplyConfigInitiated
Device Apply Config initiated.
This alarm occurs when a system administrator presses the Apply Config button in Cisco Unified
Communications Manager (Unified CM). The Apply Config button initiates a conditional restart on
devices that support conditional restart. This button triggers the system to determine if any relevant
configuration has changed for the device. If the configuration changes can be applied dynamically, they
are made without service interruption. If a change requires that the device reregister with Unified CM,
reregistration occurs automatically. If a change requires a restart, the device will be automatically
restarted. If the load ID for a device changes, the device will initiate a background download of the new
firmware. The new firmware can then be applied immediately or at a later time. For phones and devices
that do not support conditional restart, clicking Apply Config causes these devices to restart.
Severity
Informational
Parameter(s)
Device name(String)
Product type(String)
Device type(Enum)
Enum Definitions for Device type
•
493—CISCO_9971
Recommended Action
None
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
6-311
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Informational-Level Alarms
DRFBackupCompleted
DRF backup completed successfully.
Cisco Unified Serviceability Alarm Definition Catalog
System/DRF
Severity
INFORMATIONAL
Routing List
Event Log
Sys Log
Parameter(s)
Reason(String)
Recommended Action
Ensure that the backup operation is completed successfully.
DRFRestoreCompleted
DRF restore completed successfully.
Cisco Unified Serviceability Alarm Definition Catalog
System/DRF
Severity
INFORMATIONAL
Routing List
Event Log
Sys Log
Parameter(s)
Reason(String)
Recommended Action
Ensure that the restore operation is completed successfully.
EndPointResetInitiated
This alarm occurs when a device is reset via the Reset button in Cisco Unified CM Administration. Reset
causes the device to shut down and come back in service. A device can be reset only when it is registered
with Cisco Unified Communications Manager.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
6-312
OL-20105-01
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Informational-Level Alarms
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/CallManager
Severity
INFORMATIONAL
Routing List
SDL
SDI
Sys Log
Alternate Syslog
Parameter(s)
Device name(String)
Product type(String)
Device type(Enum)
Enum Definitions -Device type
Value
Definition
1
CISCO_30SP+
2
CISCO_12SP+
3
CISCO_12SP
4
CISCO_12S
5
CISCO_30VIP
6
CISCO_7910
7
CISCO_7960
8
CISCO_7940
9
CISCO_7935
12
CISCO_ATA_186
20
SCCP_PHONE
61
H323_PHONE
72
CTI_PORT
115
CISCO_7941
119
CISCO_7971
255
UNKNOWN
302
CISCO_7989
307
CISCO_7911
308
CISCO_7941G_GE
309
CISCO_7961G_GE
335
MOTOROLA_CN622
336
BASIC_3RD_PARTY_SIP_DEVICE
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
6-313
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Informational-Level Alarms
Value
Definition
348
CISCO_7931
358
CISCO_UNIFIED_COMMUNICATOR
365
CISCO_7921
369
CISCO_7906
374
ADVANCED_3RD_PARTY_SIP_DEVICE
375
CISCO_TELEPRESENCE
404
CISCO_7962
412
CISCO_3951
431
CISCO_7937
434
CISCO_7942
435
CISCO_7945
436
CISCO_7965
437
CISCO_7975
446
CISCO_3911
468
CISCO_UNIFIED_MOBILE_COMMUNICATOR
478
CISCO_TELEPRESENCE_1000
479
CISCO_TELEPRESENCE_3000
480
CISCO_TELEPRESENCE_3200
481
CISCO_TELEPRESENCE_500
484
CISCO_7925
493
CISCO_9971
495
CISCO_6921
496
CISCO_6941
497
CISCO_6961
20000
CISCO_7905
30002
CISCO_7920
30006
CISCO_7970
30007
CISCO_7912
30008
CISCO_7902
30016
CISCO_IP_COMMUNICATOR
30018
CISCO_7961
30019
CISCO_7936
30035 I
P_STE
Recommended Action
Informational purposes only; no action is required.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
6-314
OL-20105-01
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Informational-Level Alarms
EndPointRestartInitiated
Device restart initiated or Apply Config initiated on the specified device.
This alarm occurs when a device is restarted via the Restart button in Cisco Unified CM Administration
window or when a system administrator presses the Apply Config button for a device that does not
support conditional restart. Restart causes the device to unregister, receive an updated configuration file,
and re-register with Cisco Unified Communications Manager (Unified CM) without shutting down. A
device can be restarted only when it is registered with Unified CM.
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/CallManager
Severity
INFORMATIONAL
Routing List
SDL
SDI
Sys Log
Alternate Syslog
Parameter(s)
Device name(String)
Product type(String)
Device type(Enum)
Enum Definitions -Device type
Value
Definition
1
CISCO_30SP+
2
CISCO_12SP+
3
CISCO_12SP
4
CISCO_12S
5
CISCO_30VIP
6
CISCO_7910
7
CISCO_7960
8
CISCO_7940
9
CISCO_7935
12
CISCO_ATA_186
20
SCCP_PHONE
61
H323_PHONE
72
CTI_PORT
115
CISCO_7941
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
6-315
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Informational-Level Alarms
119
CISCO_7971
255
UNKNOWN
302
CISCO_7989
307
CISCO_7911
308
CISCO_7941G_GE
309
CISCO_7961G_GE
335
MOTOROLA_CN622
336
BASIC_3RD_PARTY_SIP_DEVICE
348
CISCO_7931
358
CISCO_UNIFIED_COMMUNICATOR
365
CISCO_7921
369
CISCO_7906
374
ADVANCED_3RD_PARTY_SIP_DEVICE
375
CISCO_TELEPRESENCE
404
CISCO_7962
412
CISCO_3951
431
CISCO_7937
434
CISCO_7942
435
CISCO_7945
436
CISCO_7965
437
CISCO_7975
446
CISCO_3911
468
CISCO_UNIFIED_MOBILE_COMMUNICATOR
478
CISCO_TELEPRESENCE_1000
479
CISCO_TELEPRESENCE_3000
480
CISCO_TELEPRESENCE_3200
481
CISCO_TELEPRESENCE_500
484
CISCO_7925
493
CISCO_9971
495
CISCO_6921
496
CISCO_6941
497
CISCO_6961
20000
CISCO_7905
30002
CISCO_7920
30006
CISCO_7970
30007
CISCO_7912
30008
CISCO_7902
30016
CISCO_IP_COMMUNICATOR
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
6-316
OL-20105-01
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Informational-Level Alarms
30018
CISCO_7961
30019
CISCO_7936
30035
IP_STE
Recommended Action
Informational purposes only; no action is required.
EndThrottlingCallListBLFSubscriptions
CallManager has resumed accepting CallList BLF Subscriptions subsequent to prior throttling.
History
Cisco Unified Communications
Release
Action
8.0(1)
Severity changed from Warning to Informational.
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/CallManager
Severity
Informational
Parameters
EndThrottlingCallListBLFSubscriptionsActive External Presence Subscriptions [UInt] CallList BLF
Subscriptions Throttling Threshold [UInt] CallList BLF Subscriptions Resume Threshold [UInt] Time
Duration Of Throttling CallList BLF Subscriptions [UInt] Number of CallList BLF Subscriptions
Rejected Due To Throttling [UInt] Total End Throttling CallList BLF Subscriptions [UInt]
Recommended Action
Determine if CPU and memory resources are available to meet the higher demand for CallList BLF
Subscriptions. If so, increase the CallListBLFSubscriptionsThrottlingThreshold and correspondingly
the CallListBLFSubscriptionsResumeThreshold. If not, increase system resources to meet the demand.
DeviceRegistered
A device successfully registered with Cisco CallManager.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
6-317
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Informational-Level Alarms
History
Cisco Unified Communications
Release
Action
8.0(1)
Following information is updated:
7.1
•
Enum Definitions for Performance Monitor ObjType
•
Enum Definitions for Device type
Parameters added for IPv6: IPV6Address[Optional].[String],
IPAddressAttributes[Optional].[Enum], IPV6AddressAttributes
[Optional].[Enum], and ActiveLoadId [Optional].[String].
Facility/Sub-Facility
CCM_CALLMANAGER-CALLMANAGER
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/CallManager
Severity
Informational (6)
Parameters
Device name.[String]
Device MAC address [Optional].[String]
Device IP address [Optional].[String]
Protocol.[String]
Device description [Optional].[String]
User ID [Optional].[String]
Load ID. [Optional][String]
Associated directory numbers.[Optional].[String]
Performance monitor object type[Enum]
Device type. [Optional][Enum]
Configured GateKeeper Name [Optional].[String]
Technology Prefix Name [Optional].[String]
Zone Information [Optional].[String]
Alternate Gatekeeper List [Optional].[String]
Active Gatekeeper [Optional].[String]
Call Signal Address [Optional].[String]
RAS Address [Optional].[String]
IPV6Address[Optional].[String]
IPAddressAttributes[Optional].[Enum]
IPV6AddressAttributes [Optional].[Enum]
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
6-318
OL-20105-01
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Informational-Level Alarms
ActiveLoadId [Optional].[String]
InactiveLoadId [Optional].[String]
Enum Definitions for Performance Monitor ObjType
Code
Reason
1
Cisco CallManager
3
Cisco Lines
4
Cisco H.323
5
Cisco MGCP Gateway
6
Cisco MOH Device
7
Cisco Analog Access
8
Cisco MGCP FXS Device
9
Cisco MGCP FXO Device
10
Cisco MGCP T1CAS Device
11
Cisco MGCP PRI Device
30
Cisco Mobility Manager
Enum Definitions for DeviceType
Code
Reason
10
CISCO_VGC_PHONE
11
CISCO_VGC_VIRTUAL_PHONE
30
ANALOG_ACCESS
40
DIGITAL_ACCESS
42
DIGITAL_ACCESS+
43
DIGITAL_ACCESS_WS-X6608
47
ANALOG_ACCESS_WS-X6624
48
VGC_GATEWAY
50
CONFERENCE_BRIDGE
51
CONFERENCE_BRIDGE_HARDWARE
52
CONFERENCE_BRIDGE_HARDWARE_HDV2
53
CONFERENCE_BRIDGE_HARDWARE_WS-SVC-CMM
62
H323_GATEWAY
70
MUSIC_ON_HOLD
71
DEVICE_PILOT
73
CTI_ROUTE_POINT
80
VOICE_MAIL_PORT
83
SOFTWARE_MEDIA_TERMINATION_POINT_HDV2
84
CISCO_MEDIA_SERVER
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
6-319
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Informational-Level Alarms
85
CISCO_VIDEO_CONFERENCE_BRIDGE
90
ROUTE_LIST
100
LOAD_SIMULATOR
110
MEDIA_TERMINATION_POINT
111
MEDIA_TERMINATION_POINT_HARDWARE
112
MEDIA_TERMINATION_POINT_HDV2
113
MEDIA_TERMINATION_POINT_WS-SVC-CMM
120
MGCP_STATION
121
MGCP_TRUNK
122
GATEKEEPER
124
7914_14_BUTTON_LINE_EXPANSION_MODULE
125
TRUNK
126
TONE_ANNOUNCEMENT_PLAYER
131
SIP_TRUNK
132
SIP_GATEWAY
133
WSM_TRUNK
134
REMOTE_DESTINATION_PROFILE
227
7915_12_BUTTON_LINE_EXPANSION_MODULE
228
7915_24_BUTTON_LINE_EXPANSION_MODULE
229
7916_12_BUTTON_LINE_EXPANSION_MODULE
230
7916_24_BUTTON_LINE_EXPANSION_MODULE
232
CKEM_36_BUTTON_LINE_EXPANSION_MODULE
254
UNKNOWN_MGCP_GATEWAY
255
UNKNOWN
30027
ANALOG_PHONE
30028
ISDN_BRI_PHONE
30032
SCCP_GATEWAY_VIRTUAL_PHONE
Enum Definitions for IPAddrAttributes
Code
Reason
0
Unknown—The device has not indicated what this IPv4 address is used for.
1
Administrative only—The device has indicated that this IPv4 address is used for
administrative communication (web interface) only.
2
Signal only—The device has indicated that this IPv4 address is used for control
signaling only.
3
Administrative and signal—The device has indicated that this IPv4 address is
used for administrative communication (web interface) and control signaling.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
6-320
OL-20105-01
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Informational-Level Alarms
Enum Definitions for IPV6AddrAttributes
Code
Reason
0
Unknown—The device has not indicated what this IPv6 address is used for.
1
Administrative only—The device has indicated that this IPv6 address is used for
administrative communication (web interface) only.
2
Signal only—The device has indicated that this IPv6 address is used for control
signaling only.
3
Administrative and signal—The device has indicated that this IPv6 address is
used for administrative communication (web interface) and control signaling.
Recommended Action
None
DeviceDnInformation
List of directory numbers associated with the device.
Facility/Sub-Facility
CCM_CALLMANAGER-CALLMANAGER
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/CallManager
Severity
Informational (6)
Parameters
Device Name [String] Device type. [Optional] [Enum]Station Desc [String] Station Dn [String]
Enum Definitions for DeviceType
Code
Device Type
1
CISCO_30SP+
2
CISCO_12SP+
3
CISCO_12SP
4
CISCO_12S
5
CISCO_30VIP
6
CISCO_7910
7
CISCO_7960
8
CISCO_7940
9
CISCO_7935
10
CISCO_VGC_PHONE
11
CISCO_VGC_VIRTUAL_PHONE
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
6-321
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Informational-Level Alarms
Code
Device Type
12
CISCO_ATA_186
20
SCCP_PHONE
21
STATION_PHONE_APPLICATION
30
ANALOG_ACCESS
40
DIGITAL_ACCESS
41
DIGITAL_ACCESS_T1
42
DIGITAL_ACCESS+
43
DIGITAL_ACCESS_WS-X6608
47
ANALOG_ACCESS_WS-X6624
48
VGC_GATEWAY
50
CONFERENCE_BRIDGE
51
CONFERENCE_BRIDGE_HARDWARE
52
CONFERENCE_BRIDGE_HARDWARE_HDV2
53
CONFERENCE_BRIDGE_HARDWARE_WS-SVC-CMM
61
H323_PHONE
62
H323_GATEWAY
70
MUSIC_ON_HOLD
71
DEVICE_PILOT
72
CTI_PORT
73
CTI_ROUTE_POINT
80
VOICE_MAIL_PORT
83
SOFTWARE_MEDIA_TERMINATION_POINT_HDV2
84
CISCO_MEDIA_SERVER
85
CISCO_VIDEO_CONFERENCE_BRIDGE
90
ROUTE_LIST
100
LOAD_SIMULATOR
110
MEDIA_TERMINATION_POINT
111
MEDIA_TERMINATION_POINT_HARDWARE
112
MEDIA_TERMINATION_POINT_HDV2
113
MEDIA_TERMINATION_POINT_WS-SVC-CMM
115
CISCO_7941
119
CISCO_7971
120
MGCP_STATION
121
MGCP_TRUNK
122
GATEKEEPER
124
7914_14_BUTTON_LINE_EXPANSION_MODULE
125
TRUNK
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
6-322
OL-20105-01
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Informational-Level Alarms
Code
Device Type
126
TONE_ANNOUNCEMENT_PLAYER
131
SIP_TRUNK
132
SIP_GATEWAY
133
WSM_TRUNK
134
REMOTE_DESTINATION_PROFILE
254
UNKNOWN_MGCP_GATEWAY
255
UNKNOWN
302
CISCO_7989
307
CISCO_7911
308
CISCO_7941G_GE
309
CISCO_7961G_GE
335
MOTOROLA_CN622
336
BASIC_3RD_PARTY_SIP_DEVICE
358
CISCO_UNIFIED_COMMUNICATOR
365
CISCO_7921
369
CISCO_7906
374
ADVANCED_3RD_PARTY_SIP_DEVICE
375
CISCO_TELEPRESENCE
404
CISCO_7962
412
CISCO_3951
431
CISCO_7937
434
CISCO_7942
435
CISCO_7945
436
CISCO_7965
437
CISCO_7975
20000
CISCO_7905
30002
CISCO_7920
30006
CISCO_7970
30007
CISCO_7912
30008
CISCO_7902
30016
CISCO_IP_COMMUNICATOR
30018
CISCO_7961
30019
CISCO_7936
30027
ANALOG_PHONE
30028
ISDN_BRI_PHONE
30032
SCCP_GATEWAY_VIRTUAL_PHONE
30035
IP_STE
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
6-323
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Informational-Level Alarms
Recommended Action
None
EMCCUserLoggedIn
EMCC login was successful.
Cisco Unified Serviceability Alarm Definition Catalog
System/EMAlarmCatalog
Severity
Informational(6)
Routing List
Sys Log
Event Log
Parameters
Device Name(String)
Login Date/Time(String)
Login UserID(String)
Recommended Action
None
EMCCUserLoggedOut
EMCC logout was successful.
Cisco Unified Serviceability Alarm Definition Catalog
System/EMAlarmCatalog
Severity
Informational(6)
Routing List
Sys Log
Event Log
Parameters
Device Name(String)
Login Date/Time(String)
UserID(String)
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
6-324
OL-20105-01
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Informational-Level Alarms
Recommended Action
None
ITLFileRegenerated
New ITL File has been generated. This usually means that a new certificate related to ITLFile has been
modified.
Cisco Unified Serviceability Alarm Catalog
System/TVS
Severity
INFORMATIONAL
Routing List
SDI
Event Log
Data Collector
Sys Log
Recommended Action
None.
kDeviceMgrLockoutWithCallManager
Cisco Unified Communications Manager in lockout.The specified Cisco Unified Communications
Manager has failed to respond to control messages. The TCP control connection to Cisco Unified CM is
being suspended. This will cause a switch to another Cisco Unified CM 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 Cisco Unified CM server.
History
Cisco Unified Communications
Release
Action
3.x and 4.x
Added for Windows.
7.0(1)
Obsoleted.
8.0(1)
This alarm is available in 8.0(1).
Severity changed from Error to Informational.
Facility/Sub-Facility
CCM_MEDIA_STREAMING_APP-IPVMS
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/IpVms
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
6-325
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Informational-Level Alarms
Severity
Informational
Parameters
Trace Name [String]
Recommended Action
Check the status of the Cisco Unified Communications Manager service. You may have to restart the
Cisco Unified CM service or the Cisco Unified CM server.
kDeviceMgrThreadWaitFailed
Wait call failure in device manager thread. An error was reported during a system request to wait on an
event, the media device will be restarted.
History
Cisco Unified Communications
Release
Action
3.x and 4.x
Added for Windows.
7.0(1)
Obsoleted.
8.0(1)
This alarm is available in 8.0(1).
•
Severity changed from Error to Informational.
•
Following parameters added:
– OS Error Code [Int]
– OS Error Description [String]
Facility/Sub-Facility
CCM_MEDIA_STREAMING_APP-IPVMS
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/IpVms
Severity
Informational
Parameters
Trace Name [String]
OS Error Code [Int]
OS Error Description [String]
Recommended Action
None
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
6-326
OL-20105-01
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Informational-Level Alarms
kMOHMgrThreadWaitFailed
Wait call failure in MOH manager thread. An error was encountered in Music-on-Hold audio manager
subcomponent while waiting for asynchronous event signaling. The MOH device will be restarted.
History
Cisco Unified Communications
Release
Action
3.x and 4.x
Added for Windows.
7.0(1)
Obsoleted.
8.0(1)
This alarm is available in 8.0(1).
•
Severity changed from Error to Informational.
•
OS Error Description(String) parameter is added.
Facility/Sub-Facility
CCM_MEDIA_STREAMING_APP-IPVMS
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/IpVms
Severity
Informational
Parameter(s)
OS Error Description(String)
Recommended Action
No action is required.
kMOHRewindStreamControlNull
Attempted to rewind an inactive MOH audio source. An attempt was made to rewind or restart the
Music-on-Hold audio source that is inactive. This has been ignored.
History
Cisco Unified Communications
Release
Action
3.x and 4.x
Added for Windows.
7.0(1)
Obsoleted.
8.0(1)
This alarm is available in 8.0(1).
•
Severity changed from Error to Informational.
•
Audio Source ID [ULong] parameter is removed.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
6-327
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Informational-Level Alarms
Facility/Sub-Facility
CCM_MEDIA_STREAMING_APP-IPVMS
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/IpVms
Severity
Informational
Parameters
Codec Type [String]
Recommended Action
None
kMOHRewindStreamMediaPositionObjectNull
Error rewinding MOH audio source that is not playing. An attempt was made to rewind or restart a
Music-on-Hold wav file that was not being played. This has been ignored.
History
Cisco Unified Communications
Release
Action
3.x and 4.x
Added for Windows.
7.0(1)
Obsoleted.
8.0(1)
This alarm is available in 8.0(1).
•
Severity changed from Error to Informational.
•
Audio Source ID [ULong] parameter is removed.
Facility/Sub-Facility
CCM_MEDIA_STREAMING_APP-IPVMS
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/IpVms
Severity
Informational
Parameters
Codec Type [String]
Recommended Action
None
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
6-328
OL-20105-01
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Informational-Level Alarms
PublicationRunCompleted
Completion of publication of published DID patterns.
This alarm is generated when Unified CM completes a publication of the DID patterns into the IME
network.
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/CallManager
Severity
INFORMATIONAL
Recommended Action
This alarm is provided for historic and informational purposes. It can be used to give you feedback that
the system is working and is correctly publishing numbers into the IME network. It can also be used for
troubleshooting. If some of the publishes fail for some reason, the alarm will contain a list of those
numbers which were not published. If your users are receiving calls, and they are not over IP but you
think they ought to be, you can check the history of these alarms to see if the number failed to be
published into the network.
Routing List
SDL
SDI
Sys Log
Event Log
Parameter(s)
Start time(String)
End time(String)
DID count(UInt)
Failed DID count(UInt)
Failed DIDs(String)
RedirectCallRequestFailed
CTIManager is unable to redirect a call
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/CtiManager
Severity
INFORMATIONAL
Routing List
SDL
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
6-329
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Informational-Level Alarms
SDI
Sys Log
Event Log
Parameter(s)
Directory Number(String)
Partition(String)
Recommended Action
This alarm is for informational purposes only; no action is required.
RollBackToPre8.0Disabled
Roll Back to Pre 8.0 has been disabled in the Enterprise Parameter page. This usually means that the
RollBack to Pre 8.0 feature is modified in the Enterprise Parameter page.
Cisco Unified Serviceability Alarm Catalog
System/TVS
Severity
INFORMATIONAL
Routing List
SDI
Event Log
Data Collector
Sys Log
Recommended Action
None.
RollBackToPre8.0Enabled
Roll Back to Pre 8.0 has been enabled in the Enterprise Parameter page.
Cisco Unified Serviceability Alarm Catalog
System/TVS
Severity
INFORMATIONAL
Routing List
SDI
Event Log
Data Collector
Sys Log
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
6-330
OL-20105-01
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Informational-Level Alarms
Recommended Action
None.
RouteRemoved
Route removed automatically.
This alarm is generated when UC Manager removes a route from its routing tables because the route is
stale and has expired, or because the far end has indicated the number is no longer reachable at that
domain.
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/CallManager
Severity
INFORMATIONAL
Routing List
SDL
SDI
Sys Log
Event Log
Parameter(s)
E.164 number(String)
Domain name(String)
Route learned time(String)
Reason Code(Enum)
Enum Definitions -Reason Code
Value Definition
1
Expired
2
Unreachable
Recommended Action
This alarm is provided for historic and informational purposes. It helps you understand why certain
numbers are in your routing tables, and why others are not. This historical information is useful to help
determine why a call to a particular number is not going over IP, when you expect it to.
SAFPublishRevoke
A CLI command revoked the publish action for the specified service or subservice ID.
A system administrator issued a CLI command on the SAF Forwarder router to revoke the publish action
for the service or subservice ID specified in this alarm.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
6-331
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Informational-Level Alarms
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/CallManager
Severity
INFORMATIONAL
Routing List
SDL
SDI
Sys Log
Event Log
Parameter(s)
Client Handle(String)
Service ID(UInt)
Sub Service ID(UInt)
InstanceID1(UInt)
InstancID2(UInt)
InstanceID3(UInt)
InstanceID4(UInt)
Recommended Action
Informational purposes only; no action is required.
SAFUnknownService
Unified CM does not recognize the service ID in a publish revoke or withdraw message.
Unified CM received a Publish Revoke message or Withdraw message from the SAF Forwarder but the
service ID in the message is not recognized by Unified CM. Unified CM may not recognize the service
ID if the service ID was mistyped in the publish revoke CLI command, or if the service was previously
withdrawn.
Cisco Unified Serviceability Alarm Catalog
CallManager/CallManager
Severity
Informational(6)
Routing List
SDL
SDI
Sys Log
Event Log
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
6-332
OL-20105-01
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Informational-Level Alarms
Parameters
Client Handle(String)
Service ID(UInt)
Sub Service ID(UInt)
InstanceID1(UInt)
InstancID2(UInt)
InstanceID3(UInt)
InstanceID4(UInt)
Recommended Action
None
SecurityEvent
Failed to write into the primary file path. Audit Event is generated by this application.
Cisco Unified Serviceability Alarm Catalog
AuditLog
Severity
INFORMATIONAL
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.
SoftwareLicenseValid
A valid software license has been detected by the IP Voice Media Streaming App service.
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/IpVms
Severity
INFORMATIONAL
Routing List
SDI
Event Log
Recommended Action
No action required. This informational message indicates alarm SoftwareLicenseNotValid is cleared.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
6-333
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Informational-Level Alarms
StationConnectionError
Station device is closing its connection with Cisco Unified Communications Manager because of the
reason that is stated in this alarm.
History
Cisco Unified Communications
Release
8.0(1)
Action
•
Reason Code[Enum] parameter added.
•
Enum Definitions for Reason Code table added.
Facility/Sub-Facility
CCM_CALLMANAGER-CALLMANAGER
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/CallManager
Severity
Informational
Parameters
Device Name [String]
Reason Code[Enum]
Enum Definitions -Reason Code
Code
Reason
0
deviceInitiatedReset—The device has initiated a reset, possibly due to a power cycle or
internal error. No action required; the device will re-register automatically.
1
sccpDeviceThrottling—(SCCP only) The indicated SCCP device exceeded the maximum
number of events allowed per-SCCP device. Events can be phone calls, KeepAlive messages,
or excessive SCCP or non-SCCP messages. The maximum number of allowed events is
controlled by the Cisco CallManager service parameter, Max Events Allowed. When an
individual device exceeds the number configured in that service parameter, Unified CM closes
the TCP connection to the device; automatic reregistration generally follows. This action is an
attempt to stop malicious attacks on Unified CM or to ward off excessive CPU usage. No
action necessary, the device will re-register automatically.
2
keepAliveTimeout—Unified CM did not receive a KeepAlive message from the device.
Possible causes include device power outage, network power outage, network configuration
error, network delay, packet drops and packet corruption. It is also possible to get this error if
the Unified CM node is experiencing high CPU usage. Verify the device is powered up and
operating, verify network connectivity between the device and Unified CM, and verify the
CPU utilization is in the safe range (this can be monitored using RTMT via CPU Pegging
Alert). No action necessary, the device will re-register automatically.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
6-334
OL-20105-01
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Informational-Level Alarms
3
dbChangeNotify—An ApplyConfig command was invoked from Unified CM Administration
resulting in an unregistration. No action necessary, the device will re-register automatically.
4
deviceRegistrationSuperceded—An initial device registration request was received but
authentication had not yet completed before a new registration request was received. The first
registration request was discarded and re-registration should proceed normally. No action is
required, the device will re-register automatically.
Recommended Action
None
StationAlarm
A station device sent an alarm to Cisco Unified Communications Manager, which acts as a conduit from
the device to generate this alarm.
Facility/Sub-Facility
CCM_CALLMANAGER-CALLMANAGER
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/CallManager
Severity
Informational (6)
Parameters
Protocol [String] TCP ProcessID [String] Device Text [String] Param1 [UInt] Param2 [UInt]
Recommended Action
Refer to the specific device type and information passed via this alarm to determine the appropriate
action.
TVSCertificateRegenerated
TVS Server certificate has been regenerated. This usually means that the TVS certificate has been
regenerated. TVS server will automatically be restarted
Cisco Unified Serviceability Alarm Catalog
System/TVS
Severity
INFORMATIONAL
Routing List
SDI
Event Log
Data Collector
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
6-335
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Informational-Level Alarms
Sys Log
Recommended Action
None.
DeviceResetInitiated
Device reset initiated on the specified device.
This alarm occurs when a device is reset via the Reset button in Cisco Unified CM Administration. Reset
may cause the device to shut down and come back in service. A device can be reset only when it is
registered with Cisco Unified Communications Manager.
History
Cisco Unified Communications
Release
Action
8.0(1)
•
Enum Definitions for DeviceType are updated.
•
Parameters added: Product type [String]
Facility/Sub-Facility
CCM_CALLMANAGER-CALLMANAGER
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/CallManager
Severity
Informational (6)
Parameters
Device name [Optional]. [String] Device type. [Optional] [Enum] Product type [String]
Enum Definitions for DeviceType
Code
Device Type
10
CISCO_VGC_PHONE
11
CISCO_VGC_VIRTUAL_PHONE
30
ANALOG_ACCESS
40
DIGITAL_ACCESS
42
DIGITAL_ACCESS+
43
DIGITAL_ACCESS_WS-X6608
47
ANALOG_ACCESS_WS-X6624
48
VGC_GATEWAY
50
CONFERENCE_BRIDGE
51
CONFERENCE_BRIDGE_HARDWARE
52
CONFERENCE_BRIDGE_HARDWARE_HDV2
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
6-336
OL-20105-01
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Informational-Level Alarms
53
CONFERENCE_BRIDGE_HARDWARE_WS-SVC-CMM
62
H323_GATEWAY
70
MUSIC_ON_HOLD
71
DEVICE_PILOT
73
CTI_ROUTE_POINT
80
VOICE_MAIL_PORT
83
SOFTWARE_MEDIA_TERMINATION_POINT_HDV2
84
CISCO_MEDIA_SERVER
85
CISCO_VIDEO_CONFERENCE_BRIDGE
90
ROUTE_LIST
100
LOAD_SIMULATOR
110
MEDIA_TERMINATION_POINT
111
MEDIA_TERMINATION_POINT_HARDWARE
112
MEDIA_TERMINATION_POINT_HDV2
113
MEDIA_TERMINATION_POINT_WS-SVC-CMM
120
MGCP_STATION
121
MGCP_TRUNK
122
GATEKEEPER
124
7914_14_BUTTON_LINE_EXPANSION_MODULE
125
TRUNK
126
TONE_ANNOUNCEMENT_PLAYER
131
SIP_TRUNK
132
SIP_GATEWAY
133
WSM_TRUNK
134
REMOTE_DESTINATION_PROFILE
227
7915_12_BUTTON_LINE_EXPANSION_MODULE
228
7915_24_BUTTON_LINE_EXPANSION_MODULE
229
7916_12_BUTTON_LINE_EXPANSION_MODULE
230
7916_24_BUTTON_LINE_EXPANSION_MODULE
232
CKEM_36_BUTTON_LINE_EXPANSION_MODULE
254
UNKNOWN_MGCP_GATEWAY
255
UNKNOWN
30027
ANALOG_PHONE
30028
ISDN_BRI_PHONE
30032
SCCP_GATEWAY_VIRTUAL_PHONE
Recommended Action
None
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
6-337
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Informational-Level Alarms
DeviceRestartInitiated
Device restart initiated or Apply Config initiated on the specified device.
This alarm occurs when a device is restarted via the Restart button in Cisco Unified CM Administration
window or when a system administrator presses the Apply Config button for a device that does not
support conditional restart. Restart causes the device to unregister, receive updated configuration, and
re-register with Cisco Unified Communications Manager (Unified CM) without shutting down. A device
can be restarted only when it is registered with Unified CM.
History
Cisco Unified Communications
Release
Action
8.0(1)
•
Enum Definitions for DeviceType are updated.
•
Parameters added: Product type [String]
Facility/Sub-Facility
CCM_CALLMANAGER-CALLMANAGER
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/CallManager
Severity
Informational (6)
Parameters
Device name [Optional]. [String] Device type. [Optional] [Enum] Product type [String]
Enum Definitions for DeviceType
Code
Device Type
10
CISCO_VGC_PHONE
11
CISCO_VGC_VIRTUAL_PHONE
30
ANALOG_ACCESS
40
DIGITAL_ACCESS
42
DIGITAL_ACCESS+
43
DIGITAL_ACCESS_WS-X6608
47
ANALOG_ACCESS_WS-X6624
48
VGC_GATEWAY
50
CONFERENCE_BRIDGE
51
CONFERENCE_BRIDGE_HARDWARE
52
CONFERENCE_BRIDGE_HARDWARE_HDV2
53
CONFERENCE_BRIDGE_HARDWARE_WS-SVC-CMM
62
H323_GATEWAY
70
MUSIC_ON_HOLD
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
6-338
OL-20105-01
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Informational-Level Alarms
71
DEVICE_PILOT
73
CTI_ROUTE_POINT
80
VOICE_MAIL_PORT
83
SOFTWARE_MEDIA_TERMINATION_POINT_HDV2
84
CISCO_MEDIA_SERVER
85
CISCO_VIDEO_CONFERENCE_BRIDGE
90
ROUTE_LIST
100
LOAD_SIMULATOR
110
MEDIA_TERMINATION_POINT
111
MEDIA_TERMINATION_POINT_HARDWARE
112
MEDIA_TERMINATION_POINT_HDV2
113
MEDIA_TERMINATION_POINT_WS-SVC-CMM
120
MGCP_STATION
121
MGCP_TRUNK
122
GATEKEEPER
124
7914_14_BUTTON_LINE_EXPANSION_MODULE
125
TRUNK
126
TONE_ANNOUNCEMENT_PLAYER
131
SIP_TRUNK
132
SIP_GATEWAY
133
WSM_TRUNK
134
REMOTE_DESTINATION_PROFILE
227
7915_12_BUTTON_LINE_EXPANSION_MODULE
228
7915_24_BUTTON_LINE_EXPANSION_MODULE
229
7916_12_BUTTON_LINE_EXPANSION_MODULE
230
7916_24_BUTTON_LINE_EXPANSION_MODULE
232
CKEM_36_BUTTON_LINE_EXPANSION_MODULE
254
UNKNOWN_MGCP_GATEWAY
255
UNKNOWN
30027
ANALOG_PHONE
30028
ISDN_BRI_PHONE
30032
SCCP_GATEWAY_VIRTUAL_PHONE
Recommended Action
None
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
6-339
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Informational-Level Alarms
MaxHoldDurationTimeout
A held call was cleared because the amount of time specified in the Maximum Hold Duration Timer
service parameter had elapsed. If the allowed call-on-hold duration is too short, you can increase the
value. If you do not want a limit on the duration of a held call, you can disable the limit.
History
Cisco Unified Communications
Release
Action
8.0(1)
Following parameters added:
•
Originating Device Name(String)
•
Destination Device Name(String)
•
Hold start time(UInt)
•
Hold stop time(UInt)
•
Calling Party Number(String)
•
Called Party Number(String)
Facility/Sub-Facility
CCM_CALLMANAGER-CALLMANAGER
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/CallManager
Severity
Informational (6)
Parameters
Maximum Hold Duration (minutes) [Int]
Originating Device Name(String)
Destination Device Name(String)
Hold start time(UInt)
Hold stop time(UInt)
Calling Party Number(String)
Called Party Number(String)
Recommended Action
If the duration of the hold time is too short, increase the value in the Cisco CallManager service
parameter or disable the maximum duration by setting the Maximum Hold Duration Timer parameter to
zero.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
6-340
OL-20105-01
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Informational-Level Alarms
PktCapServiceStarted
Packet capture service started. Packet capture feature has been enabled on the Cisco Unified
Communications Manager server. A Cisco CallManager service parameter, Packet Capture Enable, must
be set to True for packet capture to occur.
Facility/Sub-Facility
CCM_CALLMANAGER-CALLMANAGER
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/CallManager
Severity
Informational (6)
Recommended Action
None
PktCapServiceStopped
Packet capture service stopped. The packet capture feature has been disabled on the Cisco Unified
Communications Manager server.
Facility/Sub-Facility
CCM_CALLMANAGER-CALLMANAGER
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/CallManager
Severity
Informational (6)
Recommended Action
None
PktCapOnDeviceStarted
Packet capture started on the device. Indicated packet capture has been enabled on the device.
Facility/Sub-Facility
CCM_CALLMANAGER-CALLMANAGER
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/CallManager
Severity
Informational (6)
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
6-341
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Informational-Level Alarms
Parameters
Device Name [String] Packet Capture Mode [String] Packet Capture Duration [String]
Recommended Action
None
PktCapOnDeviceStopped
Packet capture stopped on the device. Indicated packet capture has been disabled on the device.
Facility/Sub-Facility
CCM_CALLMANAGER-CALLMANAGER
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/CallManager
Severity
Informational (6)
Parameters
Device Name [String] Packet Capture Mode [String] Packet Capture Duration [String]
Recommended Action
None
CMInitializationStateTime
Indicates the amount of time required to complete initialization for the specified state.
Facility/Sub-Facility
CCM_CALLMANAGER-CALLMANAGER
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/CallManager
Severity
Informational (6)
Parameters
Initialization State [String] Initialization Time [String] Initialization Time in Milliseconds [UInt]
Recommended Action
None
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
6-342
OL-20105-01
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Informational-Level Alarms
CMTotalInitializationStateTime
Indicates the amount of time required to complete the specified total system initialization state.
Facility/Sub-Facility
CCM_CALLMANAGER-CALLMANAGER
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/CallManager
Severity
Informational (6)
Parameters
Total Initialization Time [String] Total Initialization Time in Milliseconds [UInt]
Recommended Action
None
kANNICMPErrorNotification
ANN stream ICMP port unreachable error. 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.
History
Cisco Unified Communications
Release
Action
8.0.1
Parameter list updated.
Facility/Sub-Facility
CCM_MEDIA_STREAMING_APP-IPVMS
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/IpVms
Severity
Informational (6)
Parameters
Destination IP Address [String]
Recommended Action
No action is required. This may occur at times when connections are being stopped or redirected.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
6-343
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Informational-Level Alarms
kCFBICMPErrorNotification
CFB stream ICMP error. 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.
History
Cisco Unified Communications
Release
Action
3.x and 4.x
Added for Windows.
7.0(1)
Obsoleted.
8.0(1)
This alarm is available in 8.0(1).
Following parameters removed:
Call ID [ULong] Party ID [ULong] IP Port [ULong]
Facility/Sub-Facility
CCM_MEDIA_STREAMING_APP-IPVMS
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/IpVms
Severity
Informational (6)
Parameters
Destination IP Address [String]
Recommended Action
No action is required. This may occur at times when connections are being stopped or redirected.
kReadCfgIpTosMediaResourceToCmNotFound
IP TOS MediaResource to Cm value not found. 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).
History
Cisco Unified Communications
Release
Action
3.x and 4.x
Added for Windows.
7.0(1)
Obsoleted.
8.0(1)
This alarm is available in 8.0(1).
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
6-344
OL-20105-01
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Informational-Level Alarms
Facility/Sub-Facility
CCM_MEDIA_STREAMING_APP-IPVMS
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/IpVms
Severity
Informational (6)
Recommended Action
Set the Ip Type-of-Service Media Resource To Call Manager service parameter for the Cisco IP Voice
Media Streaming App service.
kDeviceMgrRegisterWithCallManager
Register with Cisco Unified Communications Manager. The software media device registered with the
specified Cisco Unified Communications Manager.
History
Cisco Unified Communications
Release
Action
3.x and 4.x
Added for Windows.
7.0(1)
Obsoleted.
8.0(1)
This alarm is available in 8.0(1).
Facility/Sub-Facility
CCM_MEDIA_STREAMING_APP-IPVMS
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/IpVms
Severity
Informational (6)
Parameters
Trace Name [String]
Recommended Action
None
kDeviceMgrUnregisterWithCallManager
Unregister with Cisco Unified Communications Manager. A media device has unregistered with the
specified Cisco Unified Communications Manager.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
6-345
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Informational-Level Alarms
History
Cisco Unified Communications
Release
Action
3.x and 4.x
Added for Windows.
7.0(1)
Obsoleted.
8.0(1)
This alarm is available in 8.0(1).
Facility/Sub-Facility
CCM_MEDIA_STREAMING_APP-IPVMS
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/IpVms
Severity
Informational (6)
Parameters
Trace Name [String]
Recommended Action
No action is required. The media device will automatically reregister.
kIPVMSStarting
The Cisco IP Voice Media Streaming App service is starting.
History
Cisco Unified Communications
Release
Action
3.x and 4.x
Added for Windows.
7.0(1)
Obsoleted.
8.0(1)
This alarm is available in 8.0(1).
ProcessID [ULong] parameter is removed.
Facility/Sub-Facility
CCM_MEDIA_STREAMING_APP-IPVMS
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/IpVms
Severity
Informational (6)
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
6-346
OL-20105-01
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Informational-Level Alarms
Parameters
Version [String] IPAddress [String] Hostname [String] ServiceName [String]
Recommended Action
No action is required.
kIPVMSStopping
The Cisco IP voice media streaming application is shutting down.
History
Cisco Unified Communications
Release
Action
3.x and 4.x
Added for Windows.
7.0(1)
Obsoleted.
8.0(1)
This alarm is available in 8.0(1).
ProcessID [ULong] parameter is removed.
Facility/Sub-Facility
CCM_MEDIA_STREAMING_APP-IPVMS
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/IpVms
Severity
Informational (6)
Parameters
Version [String] IPAddress [String] Hostname [String] ServiceName [String]
Recommended Action
No action is required.
kMOHICMPErrorNotification
MOH stream ICMP error. 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.
History
Cisco Unified Communications
Release
Action
3.x and 4.x
Added for Windows.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
6-347
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Informational-Level Alarms
History
Cisco Unified Communications
Release
Action
7.0(1)
Obsoleted.
8.0(1)
This alarm is available in 8.0(1).
Following parameters are removed:
Call ID [ULong] Party ID [ULong] IP Port [ULong]
Facility/Sub-Facility
CCM_MEDIA_STREAMING_APP-IPVMS
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/IpVms
Severity
Informational (6)
Parameters
Destination IP Address [String]
Recommended Action
No action is required.
kMOHMgrIsAudioSourceInUseThisIsNULL
Synchronization error detected in MOH audio manager. A synchronization error was detected.
Condition has been resolved automatically.
History
Cisco Unified Communications
Release
Action
3.x and 4.x
Added for Windows.
7.0(1)
Obsoleted.
8.0(1)
This alarm is available in 8.0(1).
Facility/Sub-Facility
CCM_MEDIA_STREAMING_APP-IPVMS
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/IpVms
Severity
Informational (6)
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
6-348
OL-20105-01
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Informational-Level Alarms
Recommended Action
No action is required.
kMTPDeviceStartingDefaults
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.
History
Cisco Unified Communications
Release
Action
3.x and 4.x
Added for Windows.
7.0(1)
Obsoleted.
8.0(1)
This alarm is available in 8.0(1).
MTP Run Flag(String) parameter is added.
Facility/Sub-Facility
CCM_MEDIA_STREAMING_APP-IPVMS
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/IpVms
Severity
Informational (6)
Parameter(s)
MTP Run Flag(String)
Recommended Action
Configure the service parameter settings for the MTP device.
kReadCfgMOHEnabledCodecsNotFound
MOH enabled codecs not found. The Music-on-Hold service parameter for codec selection could not be
read from database. Defaulting to G.711 mu-law codec.
Facility/Sub-Facility
CCM_MEDIA_STREAMING_APP-IPVMS
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/IpVms
Severity
Informational (6)
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
6-349
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Informational-Level Alarms
Recommended Action
Set the Music-on-Hold service parameter for Cisco IP Voice Media Streaming App service.
LoadShareDeActivateTimeout
There was timeout during wait for DeActivateLoadShare acknowledgement.
Facility/Sub-Facility
CCM_TCD-TCD
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/TCD SRV
Severity
Informational (6)
Recommended Action
None
UserLoginSuccess
User successfully logged in.
Facility/Sub-Facility
CCM_TCD-TCD
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/TCD SRV
Severity
Informational (6)
Parameters
UserID [String]
Recommended Action
None
UserAlreadyLoggedIn
User is already logged in.
Facility/Sub-Facility
CCM_TCD-TCD
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
6-350
OL-20105-01
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Informational-Level Alarms
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/TCD SRV
Severity
Informational (6)
Parameters
UserID [String]
Recommended Action
None
UserLoggedOut
User logged out.
Facility/Sub-Facility
CCM_TCD-TCD
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/TCD SRV
Severity
Informational (6)
Parameters
UserID [String]
Recommended Action
None
AgentOnline
Agent online
Facility/Sub-Facility
CCM_TCD-TCD
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/TCD SRV
Severity
Informational (6)
Recommended Action
None
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
6-351
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Informational-Level Alarms
AgentOffline
Agent offline
Facility/Sub-Facility
CCM_TCD-TCD
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/TCD SRV
Severity
Informational (6)
Recommended Action
None
DeviceImageDownloadStart
Cisco IP Phone has started downloading its image.
History
Cisco Unified Communications
Release
7.1
Action
Added DeviceImageDownloadStart to the Phone Catalog in the
CallManager alarm definitions.
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/Phone
Severity
Informational (6)
Parameters
DeviceName(String)
IPAddress(String)
Active(String)
RequestedLoadId(String
Recommended Action
No action is required.
DeviceImageDownloadSuccess
Cisco IP Phone has successfully downloaded its image.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
6-352
OL-20105-01
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Informational-Level Alarms
History
Cisco Unified Communications
Release
7.1
Action
Added DeviceImageDownloadSuccess to the Phone Catalog in
the CallManager alarm definitions.
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/Phone
Severity
Informational (6)
Parameters
DeviceName(String)
IPAddress(String)
Method(Enum)
Active(String)
Inactive(String)
Server(String)
Recommended Action
No action is required.
DeviceApplyConfigResult
Cisco IP Phone has applied its configuration.
History
Cisco Unified Communications
Release
7.1
Action
Added DeviceApplyConfigResult to the Phone Catalog in the
CallManager alarm definitions.
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/Phone
Severity
Informational (6)
Parameters
DeviceName(String)
IPAddress(String)
UnifiedCM_Result(String)
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
6-353
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Informational-Level Alarms
Phone_Result(String)
Reason(String)
Recommended Action
No action is required.
IDSEngineInformation
No error has occurred but some routine event completed in IDS database engine. This alarm is
informational. No error has occurred but some routine event completed in IDS database engine.
Facility/Sub-Facility
CCM_DB_LAYER-DB
Cisco Unified Serviceability Alarm Definition Catalog
System/DB
Severity
Informational (6)
Parameters
Event Class ID [String] Event class message [String] Event Specific Message [String]
Recommended Action
None
IDSReplicationInformation
Information about IDS replication.
History
Cisco Unified Communications
Release
Action
8.0(1)
Added Recommended Action comments.
Facility/Sub-Facility
DB
Cisco Unified Serviceability Alarm Definition Catalog
System/DB
Severity
Informational (6)
Parameters
Event Class ID [String]
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
6-354
OL-20105-01
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Informational-Level Alarms
Event class message [String]
Event Specific Message [String]
Recommended Action
Information only. No action is required.
ServiceStarted
Service has started.
History
Cisco Unified Communications Manager
Release
Action
7.1
Added IPv6Address[Optional][String] parameter.
Facility/Sub-Facility
CCM_CBB-GENERIC
Cisco Unified Serviceability Alarm Definition Catalog
System/Generic
Severity
Informational (6)
Parameters
IP Address of hosting node(String)
IPV6Address[Optional](String)
Host name of hosting node(String)
Service Name(String)
Version Information(String)
Recommended Action
None
EMAppStarted
EM Application started successfully.
Cisco Unified Serviceability Alarm Definition Catalog
System/EMAlarmCatalog
Severity
INFORMATIONAL
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
6-355
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Informational-Level Alarms
Routing List
Sys Log
Event Log
Parameter(s)
Servlet Name(String)
Recommended Action
No action required.
IPMAStarted
IPMA Application started successfully.
Facility/Sub-Facility
CCM_JAVA_APPS-TOMCATAPPLICATIONS
Cisco Unified Serviceability Alarm Definition Catalog
System/Java Applications
Severity
Informational (6)
Parameters
Servlet Name [String] Reason [String]
Recommended Action
None
IPMAInformation
IPMA Information.
Facility/Sub-Facility
CCM_JAVA_APPS-TOMCATAPPLICATIONS
Cisco Unified Serviceability Alarm Definition Catalog
System/Java Applications
Severity
Informational (6)
Parameters
Servlet Name [String] Reason [String]
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
6-356
OL-20105-01
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Informational-Level Alarms
Recommended Action
None
BDIStarted
Application started successfully.
Facility/Sub-Facility
CCM_JAVA_APPS-TOMCATAPPLICATIONS
Cisco Unified Serviceability Alarm Definition Catalog
System/Java Applications
Severity
Informational (6)
Recommended Action
None
WDStarted
WebDialer Application started successfully.
Facility/Sub-Facility
CCM_JAVA_APPS-TOMCATAPPLICATIONS
Cisco Unified Serviceability Alarm Definition Catalog
System/Java Applications
Severity
Informational (6)
Parameters
Servlet Name [String] Reason [String]
Recommended Action
None
WDInformation
WebDialer informational alarm.
Facility/Sub-Facility
CCM_JAVA_APPS-TOMCATAPPLICATIONS
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
6-357
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Informational-Level Alarms
Cisco Unified Serviceability Alarm Definition Catalog
System/Java Applications
Severity
Informational (6)
Parameters
Servlet Name [String] Reason [String]
Recommended Action
None
CiscoDirSyncStarted
Cisco DirSync Application started. Application started successfully.
Facility/Sub-Facility
CCM_JAVA_APPS-TOMCATAPPLICATIONS
Cisco Unified Serviceability Alarm Definition Catalog
System/Java Applications
Severity
Informational (6)
Recommended Action
None
CiscoDirSyncProcessStarted
LDAPSync process started to sync user data on configured agreement ID.
Facility/Sub-Facility
CCM_JAVA_APPS-TOMCATAPPLICATIONS
Cisco Unified Serviceability Alarm Definition Catalog
System/Java Applications
Severity
Informational (6)
Parameters
AgreementId [String]
Recommended Action
None
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
6-358
OL-20105-01
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Informational-Level Alarms
CiscoDirSyncProcessCompleted
LDAPSync process completed on particular sync agreement.
Facility/Sub-Facility
CCM_JAVA_APPS-TOMCATAPPLICATIONS
Cisco Unified Serviceability Alarm Definition Catalog
System/Java Applications
Severity
Informational (6)
Parameters
AgreementId [String]
Recommended Action
None
CiscoDirSyncProcessStoppedManually
LDAPSync process stopped manually on particular sync agreement.
Facility/Sub-Facility
CCM_JAVA_APPS-TOMCATAPPLICATIONS
Cisco Unified Serviceability Alarm Definition Catalog
System/Java Applications
Severity
Informational (6)
Parameters
AgreementId [String]
Recommended Action
None
CiscoDirSyncProcessStoppedAuto
LDAPSync process stopped automatically on particular sync agreement. It will restart automatically.
Facility/Sub-Facility
CCM_JAVA_APPS-TOMCATAPPLICATIONS
Cisco Unified Serviceability Alarm Definition Catalog
System/Java Applications
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
6-359
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Informational-Level Alarms
Severity
Informational (6)
Parameters
AgreementId [String]
Recommended Action
None
DirSyncScheduledTaskOver
Directory synchronization operation started.
Facility/Sub-Facility
CCM_JAVA_APPS-TOMCATAPPLICATIONS
Cisco Unified Serviceability Alarm Definition Catalog
System/Java Applications
Severity
Informational (6)
Parameters
SchedulerID [String] TaskID [String]
Recommended Action
None
DirSyncSchedulerEngineStopped
DirSync scheduler engine stopped.
Facility/Sub-Facility
CCM_JAVA_APPS-TOMCATAPPLICATIONS
Cisco Unified Serviceability Alarm Definition Catalog
System/Java Applications
Severity
Informational (6)
Parameters
DirSyncSchedulerVersion [String]
Recommended Action
None
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
6-360
OL-20105-01
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Informational-Level Alarms
DirSyncNewScheduleInserted
New schedule inserted in the DirSync Scheduler.
Facility/Sub-Facility
CCM_JAVA_APPS/JAVAAPPLICATIONS
Cisco Unified Serviceability Alarm Definition Catalog
System/Java Applications
Severity
Informational (6)
Parameters
EngineScheduleID [String]
Recommended Action
None
DRFLA2MAFailure
DRF Local Agent to Master Agent connection has some problems.
History
Cisco Unified Communications Manager
Release
Action
8.0(1)
New name changed from CiscoDRFLA2MAFailure.
Facility/Sub-Facility
CCM_JAVA_APPS/JAVAAPPLICATIONS
Cisco Unified Serviceability Alarm Definition Catalog
System/DRF
Severity
Informational (6)
Parameters
Reason [String]
Recommended Action
Check if the Master Agent is up and the port is authorized.
DRFMA2LAFailure
Master Agent was unable to send a backup/restore request to the local agent.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
6-361
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Informational-Level Alarms
History
Cisco Unified Communications Manager
Release
Action
8.0(1)
New name changed from CiscoDRFMA2LAFailure.
Descriptive text and Recommended action changed.
Facility/Sub-Facility
CCM_JAVA_APPS/JAVAAPPLICATIONS
Cisco Unified Serviceability Alarm Definition Catalog
System/DRF
Severity
Informational (6)
Parameters
Reason [String]
Recommended Action
Restart the corresponding local agents and the master agent.
CiscoDRFComponentRegistered
DRF Successfully Registered the requested component.
History
Cisco Unified Communications Manager
Release
Action
8.0(1)
Name changed from CiscoDRFComponentRegistered.
Facility/Sub-Facility
CCM_DRF_LOCAL & CCM_DRF_MASTER/DRF
Cisco Unified Serviceability Alarm Definition Catalog
System/DRF
Severity
Informational (6)
Parameters
Reason(String)
Recommended Action
Ensure that the registered component is needed for backup/restore operation.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
6-362
OL-20105-01
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Informational-Level Alarms
DRFSchedulerUpdated
DRF Scheduled backup configurations is updated automatically due to feature de-registration.
History
Cisco Unified Communications Manager
Release
Action
8.0(1)
Name changed from CiscoDRFSchedulerUpdated.
Facility/Sub-Facility
CCM_DRF_LOCAL & CCM_DRF_MASTER/DRF
Cisco Unified Serviceability Alarm Definition Catalog
System/DRF
Severity
Informational (6)
Parameters
Reason(String)
Recommended Action
Ensure that the new configurations is appropriate one for the backup/restore operation.
CiscoDhcpdRestarted
DHCP Daemon restarted successfully.
Facility/Sub-Facility
CCM_JAVA_APPS-TOMCATAPPLICATIONS
Cisco Unified Serviceability Alarm Definition Catalog
System/Java Applications
Severity
Informational (6)
Parameters
Reason [String]
Recommended Action
None
DirSyncScheduleInsertFailed
DirSync schedule insertion failed.
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
6-363
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Informational-Level Alarms
Facility/Sub-Facility
CCM_JAVA_APPS-TOMCATAPPLICATIONS
Cisco Unified Serviceability Alarm Definition Catalog
System/Java Applications
Severity
Informational (6)
Parameters
ScheduleID [String]
Recommended Action
Check the DirSync configuration and logs
DirSyncSchedulerEngineStarted
DirSync scheduler engine started.
Facility/Sub-Facility
CCM_JAVA_APPS-TOMCATAPPLICATIONS
Cisco Unified Serviceability Alarm Definition Catalog
System/Java Applications
Severity
Informational (6)
Parameters
DirSyncSchedulerVersion [String]
Recommended Action
None
AuthenticationSucceeded
Login Authentication succeeded.
Facility/Sub-Facility
CCM_TOMCAT_APPS-LOGIN
Cisco Unified Serviceability Alarm Definition Catalog
System/Login
Severity
Informational (6)
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
6-364
OL-20105-01
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Informational-Level Alarms
Parameters
Login IP Address/Hostname [String] Login Date/Time [String] Login UserID [String] Login
Interface [String]
Recommended Action
If this event is expected, no action is required; otherwise, notify the administrator.
LogFileSearchStringFound
The search string has been found in the log file. Trace and Log Central has found the search string that
the user has configured.
Facility/Sub-Facility
CCM_TCT-LPMTCT
Cisco Unified Serviceability Alarm Definition Catalog
System/LpmTct
Severity
Informational (6)
Parameters
SearchString [String]
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.
BuildStat
Device configuration files are being built. This alarm provides information about the BUILD ALL
operation to build all types of configuration files.
Facility/Sub-Facility
CCM_TFTP-TFTP
Cisco Unified Serviceability Alarm Definition Catalog
System/TFTP
Severity
Informational (6)
Parameters
DeviceCount [Int] DeviceTime [Int] UnitCount [Int] UnitTime [Int] SoftkeyCount [Int]
SoftkeyTime [Int] DialruleCount [Int] DialruleTime [Int] TotalTime [Int] BuildStatus [String]
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
6-365
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Informational-Level Alarms
Recommended Action
This alarm is for information purposes only; no action is required.
TestAlarmInformational
Testing informational alarm.
Facility/Sub-Facility
CCM_CALLMANAGER-CALLMANAGER
Cisco Unified Serviceability Alarm Definition Catalog
System/Test
Severity
Informational (6)
Recommended Action
None
TestAlarmAppliance
Testing alarm for Appliance OS based server only.
Facility/Sub-Facility
CCM_CALLMANAGER-CALLMANAGER
Cisco Unified Serviceability Alarm Definition Catalog
System/Test
Severity
Informational (6)
Recommended Action
None
ServiceActivated
This service is now activated.
Facility/Sub-Facility
CCM_SERVICEMANAGER-GENERIC
Cisco Unified Serviceability Alarm Definition Catalog
System/Service Manager
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
6-366
OL-20105-01
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Informational-Level Alarms
Severity
Informational (6)
Parameters
Service Name(String)
Recommended Action
None
ServiceDeactivated
The service is now deactivated.
Facility/Sub-Facility
CCM_SERVICEMANAGER-GENERIC
Cisco Unified Serviceability Alarm Definition Catalog
System/Service Manager
Severity
Informational (6)
Parameters
Service Name(String)
Recommended Action
None
authSuccess
Successfully authenticated this user.
History
Cisco Unified Communications
Release
Action
7.0(1)
Error message added.
Cisco Unified Serviceability Alarm Definition Catalog
System/IMS
Severity
Informational (6)
Parameters
Authentication successful(String)
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
6-367
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Informational-Level Alarms
Recommended Action
None
credUpdateFailure
The credential update failed most likely because the credential did not pass the security requirements
(too short or credential used before, for example).
History
Cisco Unified Communications
Release
Action
7.0(1)
Error message added.
8.0(1)
Added more descriptive text.
Cisco Unified Serviceability Alarm Definition Catalog
System/IMS
Severity
Informational (6)
Parameters
Credential Update Failure for(String)
Recommended Action
Determine issue (check length requirements, etc.) for this credential and retry.
credUpdateSuccess
Credential was successfully updated.
History
Cisco Unified Communications
Release
Action
7.0(1)
Error message added.
Cisco Unified Serviceability Alarm Definition Catalog
System/IMS
Severity
Informational (6)
Parameters
Credential Update success for(String)
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
6-368
OL-20105-01
Chapter 6
Cisco Unified Serviceability Alarms and CiscoLog Messages
Informational-Level Alarms
Recommended Action
None
credFullUpdateSuccess
Credential was successfully updated.
History
Cisco Unified Communications
Release
Action
7.0(1)
Error message added.
Cisco Unified Serviceability Alarm Definition Catalog
System/IMS
Severity
Informational (6)
Parameters
(String)
Recommended Action
None
credFullUpdateFailure
An error was encountered during update of credential fields.
History
Cisco Unified Communications
Release
Action
7.0(1)
Error message added.
Cisco Unified Serviceability Alarm Definition Catalog
System/IMS
Severity
Informational (6)
Paramete