• SNMP Notification—The SNMP notification event detector provides the ability to intercept SNMP trap
and inform messages coming into the device. An SNMP notification event is generated when an incoming
SNMP trap or inform message matches specified values or crosses specified thresholds.
• RPC—The remote procedure call (RPC) event detector provides the ability to invoke EEM policies from
outside the device over an encrypted connection using Secure Shell (SSH). The RPC event detector uses
Simple Object Access Protocol (SOAP) data encoding for exchanging XML-based messages. This event
detector can be used to run EEM policies and then receive output in a SOAP XML-formatted reply.
EEM 2.4 added enhancements to the following event detectors:
• Interface counter rate-based trigger—This feature adds the ability for an interface event to be triggered
based on a rate of change over a period of time. A rate can be specified both for the entry value and the
exit value. This feature copies the rate-based functionality that currently exists for the SNMP event
detector.
• SNMP delta value—The difference between the monitored Object Identifier (OID) value at the beginning
of the monitored period and the actual OID value when the event is published will be provided in the
event reqinfo data for both the SNMP event detector and the Interface Counter event detector.
EEM 2.4 introduced the following actions:
• Multiple event support—The ability to run multiple events was introduced. and show event manager
commands were enhanced to show multiple events.
• Support for parameters—The parameter argument has been added to the event manager run command.
A maximum of 15 parameters can be used.
•
Display of Job IDs and completion status--Some of the show event manager commands were enhanced
to display Job IDs and completion status.
• Bytecode support—Tcl 8 defines a specialized bytecode language (BCL) and includes a just-in-time
compiler that translates Tcl scripts to BCL. Byte sequence is executed by a “virtual machine,”
Tcl_ExecuteByteCode(), or TEBC for short, as often as needed. Currently EEM accepts file extensions,
such as *.tcl for user policies and *.tm for system policies. Tcl standard extension for bytecode scripts
are *.tbc. Now EEM will accept *.tbc as valid EEM policies.
• Registration substitution enhancement—Supports replacing multiple parameters in the event registration
statement lines with a single environment variable.
•
Tcl package support
Embedded Event Manager 3.0
EEM 3.0 introduced the following new event detectors:
•
Custom CLI--The custom CLI event detector publishes an event to add and enhance existing CLI
command syntax.
•
Routing--The Routing event detector publishes an event when route entries change in the Routing
Information Base (RIB).
•
NetFlow-- The NetFlow event detector publishes an event when a NetFlow event is triggered.
•
IP SLA--The IP SLA event detector publishes an event when an IP SLA reaction is triggered.
Consolidated Platform Configuration Guide, Cisco IOS Release 15.2(4)E (Catalyst 2960-X Switches)
1664
Information About Embedded Event Manager
To Next Page
Loading...
Need help?
General
