Cisco Cisco IOS Software Release 12.2(25)S
Embedded Event Manager 2.0
Information About Embedded Event Manager 2.0
5
Cisco IOS Release 12.2(25)S
Embedded Event Manager Actions
The CLI-based corrective actions that are taken when event detectors report events enable a powerful
on-device event management mechanism. EEM 2.0 supports the following actions:
on-device event management mechanism. EEM 2.0 supports the following actions:
•
Modifying a named counter.
•
Publishing an application-specific event.
•
Generating an SNMP trap.
•
Generating prioritized syslog messages.
•
Generating a CNS event for upstream processing by Cisco CNS devices.
•
Reloading the Cisco IOS software.
•
Switching to a secondary processor in a fully redundant hardware configuration.
Embedded Event Manager Environment Variables
Tool Command Language (Tcl) permits global variables—called environment variables—to be defined
for use within an EEM policy. There are three different types of environment variables associated with
Embedded Event Manager. User-defined environment variables are defined by you if you create an
environment variable in a policy that you have written. Cisco-defined environment variables are either
created for a specific policy (sample policy) or considered to be Cisco system-defined (see
for use within an EEM policy. There are three different types of environment variables associated with
Embedded Event Manager. User-defined environment variables are defined by you if you create an
environment variable in a policy that you have written. Cisco-defined environment variables are either
created for a specific policy (sample policy) or considered to be Cisco system-defined (see
) and
may apply to one specific event detector or to all event detectors. Environment variables that are
user-defined or defined by Cisco in a sample policy are set using the event manager environment
command. Variables that are used in the EEM policy must be defined before you register the policy. A
policy contains a section called “Environment Must Define” that can be defined to check that any
required environment variables are defined before the policy runs. Cisco system-defined environment
variables are set by the system when the policy starts to execute.
user-defined or defined by Cisco in a sample policy are set using the event manager environment
command. Variables that are used in the EEM policy must be defined before you register the policy. A
policy contains a section called “Environment Must Define” that can be defined to check that any
required environment variables are defined before the policy runs. Cisco system-defined environment
variables are set by the system when the policy starts to execute.
Note
Cisco-defined environment variables begin with an underscore character (_). We strongly recommend
that customers avoid the same naming convention to prevent naming conflicts.
that customers avoid the same naming convention to prevent naming conflicts.
describes the Cisco system-defined environment variables.
Table 1
Cisco System-Defined Environment Variables
Environment Variable
Description
All Events
_event_pub_time
Time at which the event type was published.
_event_type_string
Event type that triggered the event.
Application-Specific Event Detector
_application_data1
Character text, the value of an environment variable, or a
combination of the two to be passed to an application-specific
event when the event is published.
combination of the two to be passed to an application-specific
event when the event is published.
_application_data2
Character text, the value of an environment variable, or a
combination of the two to be passed to an application-specific
event when the event is published.
combination of the two to be passed to an application-specific
event when the event is published.