Embedded event manager


Cisco Embedded Event Manager is a feature included in Cisco's IOS operating system that allow programmability and automation capabilities inside the device. EEM allows the behavior of a Cisco device to adapt to specific user requirements by allowing scripting, thresholding, proactive actions, data collection and event management inside the Cisco device itself. Using EEM, problems can be identified and resolved automatically in advance by setting event triggers to watch for specific types of situations or thresholds, or run a set of actions periodically.
When a situation is detected by EEM, it uses policies to invoke actions based on the type of event and the configured policy. EEM currently supports three different types of programming actions.

Cisco Embedded Management Family

EEM is a member of a family of embedded management technologies in Cisco IOS including SNMP, NetFlow, IP SLA, Web Services Management Agent, Syslog, ESM, ERM, EMM, Tcl and Service Diagnostics.

About EEM

With EEM, users can capture complex network events and run sophisticated programs on Cisco devices. The version of EEM on most Cisco devices is version 2.1, or version is 3.0 which was introduced in IOS 12.4T. The latest version is version 4.0, which was released November 2011, targeting IOS releases 12.2SR, 12.2SB, 12.4, and 12.4T, 15.0M, 12.2SG, 12.2SE, Cisco IOS XE, and future versions. EEM consists of three areas; Event Detectors, Policies and Programming languages.

Event Detectors

The brains of EEM are event detectors. These event detectors are built-in capabilities to watch for specific situations or conditions. Newer versions of EEM have more event detectors than older ones.
Typical of EEM Event Detectors:
Policies determine what is run when an event is detected. Policies save users from having to enumerate an action for every possible event.

Programming Capabilities

EEM supports three methods of programmability and scripting.
  1. Applets - these allow CLI to be run when a certain set of conditions occurs
  2. Tcl - when more complex programs need to be built, EEM supports Tcl development
  3. IOS.sh - newer versions of IOS support IOS.sh macros similar to Linux bash shell

    EEM Version Comparison

Example EEM Commands

There are four steps to setting up an EEM system. In this example, we will get an email of the status of the system when the HSRP state changes. This examples defines an applet action rather than Tcl.
  1. <-- define the environment variable
  2. <-- define the address to which email will be sent
  3. <-- define the address from which the email will be sent
  4. <-- set up the policy
  5. <-- define the trigger
  6. <-- obtain the current device hostname and place it in the $_info_routername variable
  7. <-- actions such as writing to flash, making config changes, etc. require enable privilege
  8. <-- write some debugging output to flash
  9. <-- more debugging output
  10. <-- send an email with the result of the last CLI command in the body of the message

    Network Management Software and Tools Support

Software solutions utilizing EEM include, but not limited to: