Cisco Catalyst 2960 Series, Configuration Manual

Page: 1881 / 2288

Use this command to manually run an EEM policy. In this example, the policy named libtest.tcl is run to test the Tcl
support in EEM. The example output shows that the test for Tcl support in EEM was successful.
Example:
Device(config)#
event manager run libtest.tcl
The following output is displayed:
01:24:37: %HA_EM-6-LOG: libtest.tcl: In procedure test1
01:24:37: %HA_EM-6-LOG: libtest.tcl: In procedure test2
01:24:37: %HA_EM-6-LOG: libtest.tcl: In procedure test3
Creating an EEM User Tcl Package Index
Perform this task to create a Tcl package index file that contains a directory of all the Tcl packages and version
information contained in a library of Tcl package files. Tcl packages are supported, depending on your release,
using the Tcl
package keyword.
Tcl packages are located in either the EEM system library directory or the EEM user library directory. When
a
package require Tcl command is executed, the user library directory is searched first for a pkgIndex.tcl
file. If the pkgIndex.tcl file is not found in the user directory, the system library directory is searched. In this
task, a Tcl package directory--the pkgIndex.tcl file--is created in the appropriate library directory using the
pkg_mkIndex command to contain information about all of the Tcl packages contained in the directory along
with version information. If the index is not created, the Tcl packages will not be found when an EEM policy
is run that contains a
package require Tcl command.
Using the Tcl package support in EEM, users can gain access to packages such as XML_RPC for Tcl. When
the Tcl package index is created, a Tcl script can easily make an XML-RPC call to an external entity.
Packages implemented in C programming code are not supported in EEM. Note
Consolidated Platform Configuration Guide, Cisco IOS Release 15.2(4)E (Catalyst 2960-X Switches)
1799
How to Write Embedded Event Manager Policies Using Tcl