Cisco Catalyst 2960 Series, Руководство по настройке

Страница: 1891 / 2288

Running the no_perf_test_init.tcl Sample Policy
This sample policy measures the the cpu performance of EEM policies. The policy helps to find the average
execution time of each EEM policy and uses the CLI library to execute the configuration commands specified
in the EEM environment variables _perf_cmd1 and, optionally, _perf_cmd2 and _perf_cmd3.
The following sample configuration demonstrates how to use this policy. Starting in user EXEC mode, enter
the
enable command at the device prompt. The device enters privileged EXEC mode, where you can enter
the show event manager policy registered command to verify that no policies are currently registered. The
next command is the show event manager policy available command to display which policies are available
to be installed. After you enter the configure terminal command to reach global configuration mode, you
can register the no_perf_test_init.tcl policy with EEM using the event manager policy command. Exit from
global configuration mode and enter the
show event manager policy registered
command again to verify
that the policy has been registered.
Analyze the results using the syslog messages from each iteration. The total number of iteration is specified
by the variable _perf_iterations. Take the time difference and divide it by the total number of iterations to get
the average execution time of each EEM policy.
enable
show event manager policy registered
show event manager policy available
configure terminal
event manager policy no_perf_test_init.tcl
end
show event manager policy registered
show event manager environment
Running the sl_intf_down.tcl Sample Policy
This sample policy demonstrates the ability to modify the configuration when a syslog message with a specific
pattern is logged. The policy gathers detailed information about the event and uses the CLI library to execute
the configuration commands specified in the EEM environment variables _config_cmd1 and, optionally,
_config_cmd2. An e-mail message is sent with the results of the CLI command.
The following sample configuration demonstrates how to use this policy. Starting in user EXEC mode, enter
the
enable
command at the device prompt. The device enters privileged EXEC mode, where you can enter
the show event manager policy registered command to verify that no policies are currently registered. The
next command is the show event manager policy available command to display which policies are available
to be installed. After you enter the configure terminal command to reach global configuration mode, you
can register the sl_intf_down.tcl policy with EEM using the event manager policy command. Exit from
global configuration mode and enter the show event manager policy registered command again to verify
that the policy has been registered.
The policy runs when an interface goes down. Enter the show event manager environment command to
display the current environment variable values. Unplug the cable (or configure a shutdown) for the interface
specified in the _syslog_pattern EEM environment variable. The interface goes down, prompting the syslog
daemon to log a syslog message about the interface being down, and the syslog event detector is called.
The syslog event detector reviews the outstanding event specifications and finds a match for interface status
change. The EEM server is notified, and the server runs the policy that is registered to handle this
event--sl_intf_down.tcl.
enable
show event manager policy registered
show event manager policy available
configure terminal
event manager policy sl_intf_down.tcl
end
Consolidated Platform Configuration Guide, Cisco IOS Release 15.2(4)E (Catalyst 2960-X Switches)
1809
Configuration Examples for Writing Embedded Event Manager Policies Using Tcl