Table of Contents
Advertisement
Configuring and Managing Embedded Event Manager Policies
EEM handlers require the ability to run CLI commands. A command is available to the Tcl shell to allow
execution of CLI commands from within Tcl scripts.
Application-specific Embedded Event Management
Any Cisco IOS XR Software application can define and publish application-defined events. Application-defined
events are identified by a name that includes both the component name and event name, to allow application
developers to assign their own event identifiers. Application-defined events can be raised by a Cisco IOS XR
Software component even when there are no subscribers. In this case, the EEM dismisses the event, which
allows subscribers to receive application-defined events as needed.
An EEM script that subscribes to receive system events is processed in the following order:
1 This CLI configuration command is entered: event manager policy scriptfilename username username.
2 The EEM scans the EEM script looking for an eem event event_type keyword and subscribes the EEM
script to be scheduled for the specified event.
3 The Event Detector detects an event and contacts the EEM.
4 The EEM schedules event processing, causing the EEM script to be run.
5 The EEM script routine returns.
Event Detection and Recovery
Events are detected by routines called event detectors. Event detectors are separate programs that provide an
interface between other Cisco IOS XR Software components and the EEM. They process information that
can be used to publish events, if necessary.
These event detectors are supported:
An EEM event is defined as a notification that something significant has happened within the system. Two
categories of events exist:
• System EEM events
• Application-defined events
System EEM events are built into the EEM and are grouped based on the fault detector that raises them. They
are identified by a symbolic identifier defined within the API.
Some EEM system events are monitored by the EEM whether or not an application has requested monitoring.
These are called built-in EEM events. Other EEM events are monitored only if an application has requested
EEM event monitoring. EEM event monitoring is requested through an EEM application API or the EEM
scripting interface.
Some event detectors can be distributed to other hardware cards within the same secure domain router (SDR)
or within the administration plane to provide support for distributed components running on those cards.
General Flow of EEM Event Detection and Recovery
EEM is a flexible, policy-driven framework that supports in-box monitoring of different components of the
system with the help of software agents known as event detectors. The relationship is between the EEM server,
Cisco ASR 9000 Series Aggregation Services Router System Monitoring Configuration Guide, Release 4.2.x
Application-specific Embedded Event Management
49
Advertisement
Table of Contents
