Table 172: Cisco IOS EEM Namespace Groupings
Category of Tcl Command ExtensionNamespace
EEM event registration::cisco::eem
EEM event information
EEM event publish
EEM action
EEM utility
EEM context library
EEM system information
CLI library
SMTP library::cisco::lib
Make sure that you import the appropriate namespaces or use the qualified command names when using the
above commands.
Note
Step 6
Program the must defines section to check for each environment variable that is used in this policy.
This is an optional step. Must defines are a section of the policy that tests whether any EEM environment variables that
are required by the policy are defined before the recovery actions are taken. The must defines section is not required if
the policy does not use any EEM environment variables. EEM environment variables for EEM scripts are Tcl global
variables that are defined external to the policy before the policy is run. To define an EEM environment variable, use
the Embedded Event Manager configuration command event manager environment CLI command. By convention all
Cisco EEM environment variables begin with “ _ ” (an underscore). In order to avoid future conflict, customers are urged
not to define new variables that start with “ _ ”.
You can display the Embedded Event Manager environment variables set on your system by using the show
event manager environment privileged EXEC command.
Note
For example, Embedded Event Manager environment variables defined by the sample policies include e-mail variables.
The sample policies that send e-mail must have the variables shown in the table below set in order to function properly.
The table below describes the e-mail-specific environment variables used in the sample EEM policies.
Consolidated Platform Configuration Guide, Cisco IOS Release 15.2(4)E (Catalyst 2960-X Switches)
1792
How to Write Embedded Event Manager Policies Using Tcl
To Next Page
Loading...
Need help?
General
