Cisco Cisco IOS Software Release 12.2(25)S
Embedded Event Manager 2.0
Prerequisites for Embedded Event Manager 2.0
2
Cisco IOS Release 12.2(25)S
Prerequisites for Embedded Event Manager 2.0
•
If the action cns-event command is used, access to a CNS Event gateway must be configured.
•
If the action force-switchover command is used, a secondary processor must be configured on the
device.
device.
•
If the action snmp-trap command is used, the snmp-server enable traps event-manager
command must be enabled to permit Simple Network Management Protocol (SNMP) traps to be sent
from the Cisco IOS device to the SNMP server. Other relevant snmp-server commands must also
be configured; for details see
command must be enabled to permit Simple Network Management Protocol (SNMP) traps to be sent
from the Cisco IOS device to the SNMP server. Other relevant snmp-server commands must also
be configured; for details see
command page.
Restrictions for Embedded Event Manager 2.0
Only Cisco-defined policies can be used with Cisco IOS Release 12.2(25)S.
Information About Embedded Event Manager 2.0
To configure Embedded Event Manager 2.0, you should understand the following concepts:
•
•
•
•
Embedded Event Manager 2.0
Event tracking and management has traditionally been performed by devices external to the networking
device. Embedded Event Manager (EEM) has been designed to offer event management capability
directly in Cisco IOS based devices. The on-device, proactive event management capabilities of EEM
are useful because not all event management can be done off router because some problems compromise
communication between the router and the external network management device. Capturing the state of
the router during such situations can be invaluable in taking immediate recovery actions and gathering
information to perform root-cause analysis. Network availability is also improved if automatic recovery
actions are performed without the need to fully reboot the routing device.
device. Embedded Event Manager (EEM) has been designed to offer event management capability
directly in Cisco IOS based devices. The on-device, proactive event management capabilities of EEM
are useful because not all event management can be done off router because some problems compromise
communication between the router and the external network management device. Capturing the state of
the router during such situations can be invaluable in taking immediate recovery actions and gathering
information to perform root-cause analysis. Network availability is also improved if automatic recovery
actions are performed without the need to fully reboot the routing device.
EEM 2.0 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.
of the system with the help of software agents known as event detectors.
between the EEM server, the event publishers (event detectors), and the event subscribers (policies).
Basically, 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 when an event of
interest occurs. The EEM policies that are configured using the Cisco IOS command-line interface (CLI)
then implement recovery on the basis of the current state of the system and the actions specified in the
policy for the given event.
Basically, 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 when an event of
interest occurs. The EEM policies that are configured using the Cisco IOS command-line interface (CLI)
then implement recovery on the basis of the current state of the system and the actions specified in the
policy for the given event.