Maintenance Manual

6-3
Cisco ICM Enterprise Edition Administrator Guide Release 6.0(0)
Chapter 6 Event Management
Overview
As show in Figure 6-1, event logging in the ICM system involves central and
remote system components. The Event Management System (EMS) enables ICM
components and the processes that run on them to report events back to the
Central Controller. The Central Controller then forwards the events to the Logger
for storage in the central database. Events are also forwarded to the HDS database
on the Distributor AW. Some of these EMS events may also be forwarded to your
ICM support provider’s Listener process by the Distributed Diagnostic and
Services Network (DDSN).
The DDSN and Listener are described in Chapter 7, “Support Facilities.”
ICM software classifies events based on their severity. Table 6-1 lists the severity
levels for ICM events.
Trace events are stored in log files, but not in the ICM database.
Table 6-1 Event Severity
Severity Description
Error Indicates a significant problem such as a loss of data,
incorrect configuration data, or a loss of function. For
example, an error would be logged if a Peripheral Gateway
were to become disconnected.
Warning Indicates a potential problem in the ICM system. For
example, a warning event might be logged if a user
attempted to add a duplicate record to the configuration.
Although an event such as this does not cause a loss of
function, it is something that you should note.
Informational Documents a successful operation for a major process or
application in the system. For example, an informational
event might indicate that the peripheral data service was
activated on a specific Peripheral Gateway in the system.
Trace Used for internal testing and diagnostics only.