Cisco ASR 9000 Serie

PurposeCommand or Action
• An optional prefix—Mandatory.—indicating, if present, that this is a system
policy that should be registered automatically at boot time if it is not already
registered. For example: Mandatory.sl_text.tcl.
•
A filename body part containing a two-character abbreviation (see Table
4: Two-Character Abbreviation Specification, on page 47) for the first
event specified, an underscore character part, and a descriptive field part
further identifying the policy.
•
A filename suffix part defined as .tcl.
For more details, see theCisco File Naming Convention for Embedded Event
Manager, on page 47.
Copy the file to the flash file system on the router—typically disk0:.
configure
Step 11
Specifies a directory to use for storing user library files or user-defined EEM
policies.
event manager directory user
{library path | policy path}
Example:
RP/0/RSP0/CPU0:router(config)#
Step 12
event manager directory user
library disk0:/user_library
Registers the EEM policy to be run when the specified event defined within the
policy occurs.
event manager policy policy-name
username username [persist-time
[seconds | infinite] | type [system |
user]]
Step 13
Example:
RP/0/RSP0/CPU0:router(config)#
event manager policy test.tcl
username user_a type user
commit
Step 14
—
Cause the policy to execute, and
observe the policy.
Step 15
—
Use debugging techniques if the policy
does not execute correctly.
Step 16
Creating an EEM User Tcl Library Index
Perform this task to create an index file that contains a directory of all the procedures contained in a library
of Tcl files. This task allows you to test library support in EEM Tcl. In this task, a library directory is created
to contain the Tcl library files, the files are copied into the directory, and an index tclIndex) is created that
Cisco ASR 9000 Series Aggregation Services Router System Monitoring Configuration Guide, Release 4.2.x
74
Configuring and Managing Embedded Event Manager Policies
How to Write Embedded Event Manager Policies Using Tcl