- Embedded Event Manager Overview
- Writing Embedded Event Manager Policies Using the Cisco IOS CLI
- Writing Embedded Event Manager Policies Using Tcl
- EEM Action Tcl Command Extension
- EEM CLI Library Tcl Command Extensions
- EEM CLI Library XML-PI Tcl Support
- EEM Context Library Tcl Command Extensions
- EEM Event Registration Tcl Command Extensions
- EEM Event Tcl Command Extensions
- EEM Library Debug Tcl Command Extensions
- EEM Multiple Event Support Tcl Command Extensions
- EEM SMTP Library Tcl Command Extensions
- EEM System Information Tcl Command Extensions
- EEM Utility Tcl Command Extensions
EEM Multiple Event Support Tcl Command Extensions
The following conventions are used for the syntax documented on the Tcl command extension pages:
[type ?]
- A question mark ? represents a variable to be entered.
- Choices between arguments are represented by pipes, for example:
priority low|normal|high
Note |
For all EEM Tcl command extensions, if there is an error, the returned Tcl result string contains the error information. |
Note |
Arguments for which no numeric range is specified take an integer from -2147483648 to 2147483647, inclusive. |
attribute
Specifies a complex event.
Syntax
attribute tag ? [occurs ?]
Arguments
tag |
Specifies a tag using the event-tag argument that can be used with the attribute command to associate an event. |
occurs |
(Optional) Specifies the number of occurrences before an EEM event is triggered. If not specified, an EEM event is triggered on the first occurrence. The range is from 1 to 4294967295. |
Result String
None
Set _cerrno
No
correlate
Builds a single complex event and allows boolean logic to relate events and tracked objects.
Syntax
correlate event ? track ? [andnot | and | or] event ? track ?
Arguments
event |
Specifies the event that can be used with the trigger command to support multiple event statements within an script. If the event associated with the event-tag argument occurs for the number of times specified by the trigger command, the result is true. If not, the result is false. |
track |
Specifies the event object number for tracking. The range is from 1 to 500. If the tracked object is set, the result of the evaluation is true. If the tracked object is not set or is undefined, the result of the evaluation is false. This result is regardless of the state of the object. |
andnot |
(Optional) Specifies that if event 1 occurs the action is executed, and if event 2 and event 3 occur together the action is not executed. |
and |
(Optional) Specifies that if event 1 occurs the action is executed, and if event 2 and event 3 occur together the action is executed. |
or |
(Optional) Specifies that if event 1 occurs the action is executed, or else if event 2 and event 3 occur together the action is executed. |
Result String
None
Set _cerrno
No
trigger
Specifies the multiple event configuration ability of Embedded Event Manager (EEM) events. A multiple event is one that can involve one or more event occurrences, one or more tracked object states, and a time period for the event to occur. The events are raised based on the specified parameters.
Syntax
trigger [occurs ?] [period ?] [period-start ?] [delay ?]
Arguments
occurs |
(Optional) Specifies the number of times the total correlation occurs before an EEM event is raised. When a number is not specified, an EEM event is raised on the first occurrence. The range is from 1 to 4294967295. |
period |
(Optional) Time interval in seconds and optional milliseconds, during which the one or more occurrences must take place. This is specified in the format ssssssssss[.mmm], where ssssssssss must be an integer number representing seconds between 0 and 4294967295, inclusive and mmm represents milliseconds and must be an integer number between 0 to 999. |
period-start |
(Optional) Specifies the start of an event correlation window. If not specified, event monitoring is enabled after the first CRON period occurs. |
delay |
(Optional) Specifies the number of seconds and optional milliseconds after which an event will be raised if all the conditions are true (specified in the format ssssssssss[.mmm], where ssssssssss must be an integer number representing seconds between 0 and 4294967295, inclusive and mmm represents milliseconds and must be an integer number between 0 to 999). |
Result String
None
Set _cerrno
No