Policies on the basis of event statements. Specify the event that triggers a policy to run. Specified time period trigger an associated action. In many cases, these events are related to faults in the device suchĪs when an interface or a fan malfunctions.įilters so only critical events or multiple occurrences of an event within a Policies with default actions that cannot be completelyĪctivity for which some action, such as a workaround or a notification, shouldīe taken. Overridden and policies that are only augmented. The table below lists the system policies that can be completely Statement overrides all possible events in the system policy.

Should always include an event statement. Triggers no action and no notification of failures. Running-config eem command to check the configuration of each policy.Īn override policy that consists of an event statement and no action statement Policies and determine which policies that you can override. Manager system-policy command to view the preconfigured system You can override the event or the actions.

The overrides that you configure take the place of the Policy occur after EEM triggers any system policy actions related to the same If you create a user policy, any actions in your These system policies define manyĬommon events and actions for the device. Or on the supervisor (the default option).

EEM takes any actions for a triggered event either locally on the module Supervisor, and EEM pushes the policy to the correct module based on the event Policies using the command-line interface (CLI) or a VSH script.ĭevice-wide view of policy management. The action statement defines the action EEM takes when the event occurs. The event statementĭefines the event to look for as well as the filtering characteristics for theĮvent. Of an event statement and one or more action statements. Policies-An event paired with one or more actions to troubleshoot Your device and takes action to recover or troubleshoot these events, based onĮvent statements-Events to monitor from another Cisco NX-OSĬomponent that may require some action, workaround, or notification.Īction statements-An action that EEM can take, such as sending anĮ-mail, or disabling an interface, to recover from an event. See a list of the releases in which each feature is supported, see the 'New and Changed Information'chapter or the Feature To find information about the features documented in this module, and to See the Bug Search Tool at and the release notes for your software release. For the latest caveats and feature information, Your software release might not support all the features documented in this module. How to configure the Embedded Event Manager (EEM) to detect and handle critical

Nexus challenge 2.0 end time