
196
Action
You can create a series of order-dependent actions to take in response to the event specified in the
monitor policy.
The following are available actions:
•
Executing a command.
•
Sending a log.
•
Enabling an active/standby switchover.
•
Executing a reboot without saving the running configuration.
User role
For EAA to execute an action in a monitor policy, you must assign the policy the user role that has
access to the action-specific commands and resources. If EAA lacks access to an action-specific
command or resource, EAA does not perform the action and all the subsequent actions.
For example, a monitor policy has four actions numbered from 1 to 4. The policy has user roles that
are required for performing actions 1, 3, and 4, but it does not have the user role required for
performing action 2. When the policy is triggered, EAA executes only action 1.
For more information about user roles, see RBAC in
Fundamentals Configuration Guide
.
Runtime
Policy runtime limits the amount of time that the monitor policy can run from the time it is triggered.
This setting prevents system resources from being occupied by incorrectly defined policies.
EAA environment variables
EAA environment variables decouple the configuration of action arguments from the monitor policy
so you can modify a policy easily.
An EAA environment variable is defined as a <
variable_name
variable
_
value
> pair and can be used
in different policies. When you define an action, you can enter a variable name with a leading dollar
sign (
$variable_name
) instead of entering a value for an argument. EAA will replace the variable
name with the variable value when it performs the action.
To change the value for an action argument, modify the value specified in the variable pair instead of
editing each affected monitor policy.
EAA environment variables include system-defined variables and user-defined variables.
System-defined variables
System-defined variables are provided by default, and they cannot be created, deleted, or modified
by users. System-defined variable names start with an underscore (_) sign, and variable values are
set automatically by the system depending on the event setting in the policy that references the
variables.
System-defined variables include the following types:
•
Public
variable
—Available for any events.
•
Event-specific
variable
—Available only for a type of event.
shows all system-defined variables.
Table 20 System-defined EAA environment variables by event type
Variable name
Description
Any event:
_event_id Event
ID.