Embedded event manager: Difference between revisions

Revision as of 15:21, 23 August 2009

Revision as of 02:59, 18 October 2009

Line 1:

''(Cisco EEM stands for Embedded Event Manager)''

== Cisco EEM (Embedded Event Manager) ==

Cisco EEM is a feature included in Cisco's IOS operating system (and some other Cisco OSes such as IOS-XR, IOS-XE, and NX-OS) 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 (called Event Detectors) to watch for specific types of situations or thresholds, or run a set of actions periodically.

Line 8:

[[File:embedded event manager overview.png|{{deletable image-caption|1=Wednesday, 5 August 2009}}|{{deletable image-caption|1=Friday, 21 August 2009}}]]

== Cisco Embedded Management Family ==

EEM is a member of a family of embedded management technologies in Cisco IOS including SNMP, NetFlow, IP SLA, WSMA (Web Services Management Agent), Syslog, ESM (Embedded Syslog Manager), ERM (Embedded Resource Manager), EMM (Embedded Menu Manager), 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, and the latest version is 3.0 which was introduced in IOS 12.4(22)T. 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.

Line 43 ⟶ 41:

* None (launch the event manually)

=== EEM Policies ===

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.

Line 53 ⟶ 51:

# IOS.sh - newer versions of IOS support IOS.sh (IOS shell) macros similar to Linux bash shell

=== EEM Version Comparison ===

{| class="wikitable"

|-

Line 94 ⟶ 91:

|-

| Watchdog, Counter, Interface Counter, Timer, Application-Specific EDs

|

| X

| X

Line 166 ⟶ 163:

|}

== 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.

Line 184 ⟶ 181:

8. <tt>action 1.3 cli command "show standby | append flash:hsrp_state_change.txt"</tt> ''<span style="color:blue;">&lt;-- write some debugging output to flash</span>''

9. <tt>action 1.4 cli command "show standby brief | flash:append hsrp_state_change.txt"</tt> ''<span style="color:blue;">&lt;-- more debugging output</span>''

10. <tt>action 1.5 mail server "$_email_server" to "$_email_to" from "$_email_from" subject "HSRP_STATE_CHANGE Alert from $_info_routername: $_syslog_msg" body "$_cli_result"</tt> ''<span style="color:blue;">&lt;-- send an email with the result of the last CLI command in the body of the message</span>''

== Related Links ==

* [http://www.cisco.com/en/US/prod/collateral/iosswrel/ps6537/ps6555/ps6815/datasheet_c78-492444.html EEM Data Sheet]

* [[Cisco]]

* [http://www.cisco.com/go/eem Go EEM]

Line 197 ⟶ 194:

* [http://www.cisco.com/go/smartcallhome Go Smart Call Home]

== Network Management Software and Tools Support ==

Software solutions utilizing EEM include, but not limited to:

Line 203 ⟶ 200:

* [[CiscoWorks#LMS_Applications|CiscoWorks LMS]]

== References ==

<references/>