/mcpAlarms This release of Unified Communications Manager introduces a CAR alarm catalog (CARAlarmCatalog.xml) for the CAR Scheduler. The following table displays the alarms/alerts in this catalog. To configure these alarms, go to Cisco Unified Serviceability > Alarm > Configuration > CDR Services. Table 11: CAR Alarm Catalog Description Severity Name A critical CAR scheduled job failed. An alert gets raised when critical CDR Scheduler jobs and tasks fail (for example, DailyCdrLoad, PopulateSchedules, etc.). ERROR_ALARM CARSchedulerJobFailed A CAR scheduled job failed. An alarm gets sent for all other noncritical CAR Scheduler jobs and tasks (for example, daily, weekly, and monthly reports, QoSNotification, ChargeLimitNotification, etc.). ERROR_ALARM CARSchedulerJobError Bad CDR or CMR flat file was found during CDR Load to the CAR database. The CDR Loader can detect bad or corrupted CDR and/or CMR flat files and log the specified error. Information on the failure cause (specified reason for the bad record) and the failure summary (tracks number of bad records in comparison to the total records in the file) gets provided. ERROR_ALARM BadCDRFileFound 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. DEBUG_ALARM CARIDSEngineDebug No error has occurred but some routine event has completed in CAR IDS database engine. INFORMATION_ALARM CARIDSEngineInformation This alarm does not compromise data or prevent the use of the system but requires monitoring by the CAR DB adminstrator. CRITICAL_ALARM CARIDSEngineCritical Combined alarm for emergency and error situations. This alarm indicates that something unexpected occurred that can compromise data, or access to data, or cause CAR IDS to fail. ERROR_ALARM CARIDSEngineFailure Call Reporting and Billing Administration Guide for Cisco Unified Communications Manager, Release 15 and SUs 42 CDR Analysis and Reporting Alarms