Your software release may not support all the features documented in this module. For the latest caveats and feature information, see Bug Search Tool and the release notes for your platform and software release. To find information about the features documented in this module, and to see a list of the releases in which each feature is supported, see the feature information table at the end of this module.

Use Cisco Feature Navigator to find information about platform support and Cisco software image support. To access Cisco Feature Navigator, go to http:/​/​www.cisco.com/​go/​cfn. An account on Cisco.com is not required.

Embedded Event Manager (EEM) policies support Python scripts. You can register Python scripts as EEM policies, and execute the registered Python scripts when a corresponding event occurs. The EEM Python script has the same event specification syntax as the EEM TCL policy.

Configured EEM policies run within the Guest Shell. Guest Shell is a virtualized Linux-based environment, designed to run custom Linux applications, including Python for automated control and management of Cisco devices. The Guest Shell container provides a Python interpreter.

The EEM Python package can be imported to Python scripts for running EEM-specific extensions.

Note	The EEM Python package is available only within the EEM Python script (The package can be registered with EEM, and has the EEM event specification in the first line of the script.) and not in the standard Python script (which is run using the Python script name).

The Python package includes the following application programming interfaces (APIs):

• Action APIs—Perform EEM actions and have default parameters.

• CLI-execution APIs—Run IOS commands, and return the output. The following are the list of CLI-execution APIs:

  • eem_cli_open()

  • eem_cli_exec()

  • eem_cli_read()

  • eem_cli_read_line()

  • eem_cli_run()

  • eem_cli_run_interactive()

  • eem_cli_read_pattern()

  • eem_cli_write()

  • eem_cli_close()

• Environment variables-accessing APIs—Get the list of built-in or user-defined variables. The following are the environment variables-accessing APIs:

  • eem_event_reqinfo ()-Returns the built-in variables list.

  • eem_user_variables()-Returns the current value of an argument.

The Python package (is available only within the EEM script, and not available for the standard Python script) supports the following EEM actions:

• Syslog message printing

• Send SNMP traps

• Reload the box

• Switchover to the standby device

• Run a policy

• Track Object read

• Track Object Set

• Cisco Networking Services event generation

The EEM Python package exposes the interfaces for executing EEM actions. You can use the Python script to call these actions, and they are forwarded from the Python package via Cisco Plug N Play (PnP) to the action handler.

An EEM policy can have the following types of variables:

• Event-specific built-in variables—A set of predefinied variables that are populated with details about the event that triggered the policy. The eem_event_reqinfo () API returns the builtin variables list. These variables can be stored in the local machine and used as local variables. Changes to local variables do not reflect in builtin variables.

• User-defined variables—Variables that can be defined and used in policies. The value of these variables can be referred in the Python script. While executing the script, ensure that the latest value of the variable is available. The eem_user_variables() API returns the current value of the argument that is provided in the API.

The following CLI library commands are available within EEM for the Python script to work:

• eem_cli_close()—Closes the EXEC process and releases the VTY and the specified channel handler connected to the command.

• eem_cli_exec—Writes the command to the specified channel handler to execute the command. Then reads the output of the command from the channel and returns the output.

• eem_cli_open—Allocates a VTY, creates an EXEC CLI session, and connects the VTY to a channel handler. Returns an array including the channel handler.

• eem_cli_read()—Reads the command output from the specified CLI channel handler until the pattern of the device prompt occurs in the contents read. Returns all the contents read up to the match.

• eem_cli_read_line()—Reads one line of the command output from the specified CLI channel handler. Returns the line read.

• eem_cli_read_pattern()—Reads the command output from the specified CLI channel handler until the pattern that is to be matched occurs in the contents read. Returns all the contents read up to the match.

• eem_cli_run()—Iterates over the items in the clist and assumes that each one is a command to be executed in the enable mode. On success, returns the output of all executed commands and on failure, returns error.

• eem_cli_run_interactive()—Provides a sublist to the clist which has three items. On success, returns the output of all executed commands and on failure, returns the error. Also uses arrays when possible as a way of making things easier to read later by keeping expect and reply separated.

• eem_cli_write()—Writes the command that is to be executed to the specified CLI channel handler. The CLI channel handler executes the command.

For the Python script to work, you must enable the Guest Shell. For more information, see the Guest Shell chapter.