Cisco Explorer 1540 Specifications Page 64

  • Download
  • Add to my manuals
  • Print
  • Page
    / 924
  • Table of contents
  • TROUBLESHOOTING
  • BOOKMARKS
  • Rated. / 5. Based on customer reviews
Page view 63
2-26
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
Chapter 2 New and Changed Information
Cisco Unified Communications Manager, Release 8.0(1)
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).
Note 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.
Page view 63
1 ... 63 64 65 ... 924

Comments to this Manuals

No comments