Default Settings For Eem; Configuring Eem; Defining An Environment Variable - Cisco Nexus 7000 Series Configuration Manual
Hide thumbs
Also See for Nexus 7000 Series:
- Command reference manual (1018 pages) ,
- Reference manual (746 pages) ,
- Configuration manual (536 pages)
Table of Contents
Advertisement
Configuring the Embedded Event Manager
• Action statements within your user policy or overriding policy should not negate each other or adversely
• If you want to allow a triggered event to process any default actions, you must configure the EEM policy
• An override policy that consists of an event statement and no action statement triggers no action and no
• An override policy without an event statement overrides all possible events in the system policy.
• The following rules apply to regular command expressions: all keywords must be expanded, and only
• EEM event correlation is supported only on the supervisor module.
• EEM event correlation is not supported across different modules within a single policy.
• EEM event correlation supports up to four event statements in a single policy. The event types can be
• When more than one event statement is included in an EEM policy, each event statement must have a
• EEM event correlation does not override the system default policies.
• Default action execution is not supported for policies that are configured with tagged events.
• You can invoke EEM from Python. For more information about Python, see the Cisco Nexus 7000 Series
Default Settings for EEM
This table lists the default settings for EEM parameters.
Parameters
System policies
Configuring EEM
You can create policies that contain actions to take based on system policies. To display information about
the system policies, use the show event manager system-policy command.
Defining an Environment Variable
You can define a variable to serve as a parameter in an EEM policy.
affect the associated system policy.
to allow the default action. For example, if you match a CLI command in a match statement, you must
add the event-default action statement to the EEM policy or EEM will not allow the CLI command to
execute.
notification of failures.
the * symbol can be used for argument replacement.
the same or different, but only these event types are supported: cli, counter, module, module-failure, oir,
snmp, and syslog.
tag keyword with a unique tag argument.
NX-OS Programmability Guide.
Default
Active
Cisco Nexus 7000 Series NX-OS System Management Configuration Guide
Default Settings for EEM
245
Advertisement
Table of Contents
