Embedded Event Manager Policy Creation - Cisco Catalyst 2960 series Configuration Manual
Consolidated platform configuration guide, ios release 15.2(4)e
Hide thumbs
Also See for Catalyst 2960 series:
- Software configuration manual (980 pages) ,
- Command reference manual (800 pages) ,
- Configuration manual (120 pages)
Table of Contents
Advertisement
Information About Embedded Event Manager
Environment Variable
_tm_fsys_usage_cron
_tm_fsys_usage_debug
_tm_fsys_usage_ freebytes
_tm_fsys_usage_percent
Embedded Event Manager Policy Creation
EEM is a policy driven process in which the EEM policy engine receives notifications when faults and other
events occur in the Cisco software system. Embedded Event Manager policies implement recovery based on
the current state of the system and the actions specified in the policy for a given event. Recovery actions are
triggered when the policy is run.
Although there are some EEM CLI configuration and show commands, EEM is implemented through the
creation of policies. An EEM policy is an entity that defines an event and the actions to be taken when that
event occurs. There are two types of EEM policies: an applet or a script. An applet is a simple form of policy
that is defined within the CLI configuration. A script is a form of policy that is written in Tcl.
The creation of an EEM policy involves:
• Selecting the event for which the policy is run.
• Defining the event detector options associated with logging and responding to the event.
• Defining the environment variables, if required.
• Choosing the actions to be performed when the event occurs.
There are two ways to create an EEM policy. The first method is to write applets using CLI commands, and
the second method is to write Tcl scripts. Cisco provides enhancements to Tcl in the form of Tcl command
extensions that facilitate the development of EEM policies. Scripts are defined off the networking device
Consolidated Platform Configuration Guide, Cisco IOS Release 15.2(4)E (Catalyst 2960-X Switches)
1678
Description
(Optional) A CRON specification
that is used in the event_register
keyword extension. If unspecified,
the _tm_fsys_usage.tcl policy is
triggered once per minute.
(Optional) When this variable is
set to a value of 1, disk usage
information is displayed for all
entries in the system.
(Optional) Free byte threshold for
systems or specific prefixes. If free
space falls below a given value, a
warning is displayed.
(Optional) Disk usage percentage
thresholds for systems or specific
prefixes. If disk usage percentage
exceeds a given percentage, a
warning is displayed. If
unspecified, the default disk usage
percentage is 80 percent for all
systems.
Example
0-59/1 0-23/1 * * 0-7
1
disk2:98000000
nvram:25 disk2:5
Hide quick links:
Advertisement
Table of Contents
Troubleshooting
