Event Statements - Cisco AP776A - Nexus Converged Network Switch 5020 Configuration Manual

Chapter 54 Configuring the Embedded Event Manager
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
Your override policy should always include an event statement. An override policy without an event
Note
statement overrides all possible events in the system policy.

Event Statements

An event is any device activity for which some action, such as a workaround or a notification, should be
taken. In many cases, these events are related to faults in the device such as when an interface or a fan
malfunctions.
EEM defines event filters so only critical events or multiple occurrences of an event within a specified
time period trigger an associated action.
Figure 54-2
Figure 54-2 EEM Overview
User-defined Policy
(Defined in CLI in
an applet or script.)
Event statements specify the event that triggers a policy to run. You can configure only one event
statement per policy.
EEM schedules and runs policies on the basis of event statements. EEM examines the event and action
commands and runs them as defined.
OL-18084-01, Cisco MDS NX-OS Release 4.x
shows events that are handled by EEM.
Validates and records user-defined
policy information.
Directs event notifications.
Dir ects policy actions.
Logs e vents.
Events
System_switchover
File_system_events
HAP_reset
OIR
fanabsent
fanbad
tempsensor
module_failure
Event Manager
Dynamically registers the following:
– event names
event descriptions
–
event actions
–
event parameters
–
Filters events and matches with policies
Event Log
Cisco MDS 9000 Family CLI Configuration Guide
About EEM
54-3