EEM Action Statements
Action statements describe the action that is triggered by a policy. Each policy can have multiple action
statements. If no action is associated with a policy, EEM still observes events but takes no actions.
EEM supports the following actions in action statements:
•
Execute any CLI commands.
•
Update a counter.
•
Log an exception.
•
Reload the device.
•
Generate a syslog message.
•
Generate an SNMP notification.
•
Use the default action for the system policy.
If you want to allow the triggered event to process any default actions, you must configure the EEM 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 does not allow the CLI command to
execute.
Verify that your action statements within your user policy or overriding policy do not negate each other
or adversely affect the associated system policy.
Note
VSH Script Policies
You can also write policies in a VSH script, using a text editor. These policies have an event statement and
action statement(s) just as other policies, and these policies can either augment or override system policies.
After you write your VSH script policy, copy it to the device and activate it. To configure a policy in a VSH
script, see Defining a Policy Using a VSH Script, on page 245.
EEM Event Correlation
First, you use the tag keyword to create and differentiate multiple events in the EEM policy. Then, using a
set of Boolean operators (and, or, andnot), with the count and time, you can define a combination of these
events to trigger a custom action.
For information about configuring EEM event correlation, see Defining a User Policy Using the CLI, on
page 241.
Note
Cisco Nexus 5600 Series NX-OS System Management Configuration Guide, Release 7.x
238 OL-31641-01
Configuring EEM
EEM Action Statements
To Next Page
Loading...
