Action Statements; Vsh Script Policies; Environment Variables - Cisco AP776A - Nexus Converged Network Switch 5020 Configuration Manual

Cisco mds 9000 family cli configuration guide - release 4.x (ol-18084-01, february 2009)
Hide thumbs Also See for AP776A - Nexus Converged Network Switch 5020:
Table of Contents

Advertisement

About EEM
S e n d d o c u m e n t a t i o n c o m m e n t s t o m d s f e e d b a c k - d o c @ c i s c o . c o m

Action Statements

Action statements describe the action 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:
Verify that your action statements within your user policy or overriding policy do not negate each other
Note
or adversely affect the associated system policy.

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
polices. After you write your script policy, copy it to the device and activate it. To configure a policy in
a script, see the

Environment Variables

You can define environment variables for EEM that are available for all policies. Environment variables
are useful for configuring common values that you can use in multiple policies. For example, you can
create an environment variable for the IP address of an external e-mail server.
You can use an environment variable in action statements by using the parameter substitution format.
Example 54-1
"EEM action."
Example 54-1 Action Statement
switch (config-eem-policy)# action 1.0 forceshut module 1 reset-reason "EEM action"
If you define an environment variable for the shutdown reason, called default-reason, you can replace
that reset reason with the environment variable, as shown in
Cisco MDS 9000 Family CLI Configuration Guide
54-4
Execute any CLI commands.
Update a counter.
Log an exception.
Force the shut down of any module.
Reload the device.
Shut down specified modules because the power is over budget.
Generate a syslog message.
Generate a Call Home event.
Generate an SNMP notification.
Use the default action for the system policy.
"Defining a Policy Using a VSH Script" section on page
shows a sample action statement to force a module 1 shutdown, with a reset reason of
Chapter 54
Configuring the Embedded Event Manager
54-10.
Example
54-2.
OL-18084-01, Cisco MDS NX-OS Release 4.x

Hide quick links:

Advertisement

Table of Contents
loading

Table of Contents