Table of Contents
Advertisement
Event Detection and Recovery
the core event publishers (event detectors), and the event subscribers (policies). Event publishers screen events
and publish them when there is a match on an event specification that is provided by the event subscriber.
Event detectors notify the EEM server when an event of interest occurs.
When an event or fault is detected, Embedded Event Manager determines from the event publishers—an
example would be the OIR events publisher —if a registration for the encountered fault or event has occurred.
EEM matches the event registration information with the event data itself. A policy registers for the detected
event with the Tcl command extension event_register_xxx. The event information Tcl command extension
event_reqinfo is used in the policy to query the Embedded Event Manager for information about the detected
event.
System Manager Event Detector
The System Manager Event Detector has four roles:
• Records process reliability metric data.
• Screens for processes that have EEM event monitoring requests outstanding.
• Publishes events for those processes that match the screening criteria.
• Asks the System Manager to perform its default action for those events that do not match the screening
criteria.
The System Manager Event Detector interfaces with the System Manager to receive process startup and
termination notifications. The interfacing is made through a private API available to the System Manager. To
minimize overhead, a portion of the API resides within the System Manager process space. When a process
terminates, the System Manager invokes a helper process (if specified in the process.startup file) before calling
the Event Detector API.
Processes can be identified by component ID, System Manager assigned job ID, or load module pathname
plus process instance ID. POSIX wildcard filename pattern support using *, ?, or [...] is provided for load
module pathnames. Process instance ID is an integer assigned to a process to differentiate it from other
processes with the same pathname. The first instance of a process is assigned an instance ID value of 1, the
second 2, and so on.
The System Manager Event Detector handles EEM event monitoring requests for the EEM events shown in
this table.
Table 6: System Manager Event Detector Event Monitoring Requests
Embedded Event Manager Event
Normal process termination EEM event—built in
Abnormal process termination EEM event—built in
Process startup EEM event—built in
Cisco ASR 9000 Series Aggregation Services Router System Monitoring Configuration Guide, Release 4.2.x
50
Configuring and Managing Embedded Event Manager Policies
Description
Occurs when a process matching the screening criteria
terminates.
Occurs when a process matching the screening criteria
terminates abnormally.
Occurs when a process matching the screening criteria
starts.
Advertisement
Table of Contents
