Consolidated Platform Configuration Guide, Cisco Ios Release 15.2(4)E (Catalyst 2960-X Switches - Cisco Catalyst 2960 series Configuration Manual

• ap_perf_test_base_cpu.tcl--Is run to measure the the CPU performance of EEM policies.
• no_perf_test_init.tcl--Is run to measure the CPU performance of EEM policies.
• sl_intf_down.tcl--Is run when a configurable syslog message is logged. It executes up to two configurable
CLI commands and e-mails the results.
• tm_cli_cmd.tcl--Is run using a configurable CRON entry. It executes a configurable CLI command and
e-mails the results.
• tm_crash_reporter.tcl--Is run 5 seconds after it is registered and 5 seconds after the device boots up.
When triggered, the script attempts to find the reload reason. If the reload reason was due to a crash, the
policy searches for the related crashinfo file and sends this information to a URL location specified by
the user in the environment variable _crash_reporter_url.
• tm_fsys_usage.tcl--This policy runs using a configurable CRON entry and monitors disk space usage.
A syslog message is displayed if disk space usage crosses configurable thresholds.
Event Manager Environment Variables for the Sample Policies
Event manager environment variables are Tcl global variables that are defined external to the EEM policy
before the policy is registered and run. The sample policies require three of the e-mail environment variables
to be set ; only _email_cc is optional. Other required and optional variable settings are outlined in the following
tables.
The table below describes the EEM environment variables that must be set before the ap_perf_test_base_cpu.tcl
sample policy is run.
Table 174: Environment Variables Used in the ap_perf_test_base_cpu.tcl Policy
Environment Variable
_perf_iterations
_perf_cmd1
_perf_cmd2
_perf_cmd3

Consolidated Platform Configuration Guide, Cisco IOS Release 15.2(4)E (Catalyst 2960-X Switches)

Configuration Examples for Writing Embedded Event Manager Policies Using Tcl
Description
The number of iterations over
which to run the measurement.
The first non interactive CLI
command that is executed as part
of the measurement test. This
variable is optional and need not
be specified.
The second non interactive CLI
command that is as part of the
measurement test. To use
_perf_cmd2, _perf_cmd1 must be
defined. This variable is optional
and need not be specified.
The third non interactive CLI
command that is as part of the
measurement test. To use
_perf_cmd3, _perf_cmd1 must be
defined. This variable is optional
and need not be specified.
Example
100
enable
show version
show interface counters protocol
status
1803