The Embedded Event Manager (EEM) feature is constantly evolving. EEM 1.0 was first introduced in 12.3(4)T, but did not offer much in the way of power. Now, with EEM 3.x and 4.0 in recent versions of IOS, policies can interact with the CLI, send messages between devices, process complex show command output, intercept SNMP messages, manipulate files, and much more.
In order to know what features of EEM your device has, you must first know what version it supports. If you are not running one of the main IOS version trains, this information may not be obvious. In fact, it may not be that easy to determine the version of EEM. Prior to EEM 2.4, there was no command to determine the version of EEM. One has to be a bit clever.
As of EEM 2.4, a new command, show event manager version was introduced which shows the version of EEM as well as all of the associated Event Detectors.
If the device does not support the show event manager version command, you do not have EEM 2.4. To find out if your device supports at least EEM 1.0, check for the presence of the show event manager ? command. That is, if you run show event manager, then type a '?', you should see command syntax. If so, then your device supports EEM 1.0 at the very least.
EEM 2.0 was only ported to the 12.2(26)S (and only existed in the 12.2S train). As of 12.2(30)S and higher, those platforms support at least version 2.1.
In order to determine if your device supports EEM 2.1, you should check to make sure it supports the show event manager environment command.
If this command is supported, then the device supports EEM 2.1 at the very least.
The primary feature added to EEM 2.2 was Enhanced Object Tracking (EOT) support. However, even for devices which would otherwise support EEM 2.2, they may not support EOT. For example, Catalyst 6500s running 12.2(33)SXH code support EEM 2.3, but do not support EOT/EEM integration. Catalyst 3K switches (e.g. 3560, 3750, etc.) as of 12.2(40)SE support EEM 2.4, but do not support EOT/EEM integration. However, for other devices, verify that the event track command is supported when configuring an EEM applet.
If the track Event Detector is available, then you know for a fact that the device supports EEM 2.2 at the very least.
The primary user-facing feature of EEM 2.3 was the support for running interactive (e.g. clear counters, crypto key zeroize rsa, etc.). Therefore, to determine if a device supports EEM 2.3, check to make sure the pattern keyword is supported for the CLI action in applet configuration mode.
These techniques work for all IOS and IOS-XE devices.
Hi All, Is it supported for a fabric edge to also operate as a fabric internal border? We have a router that needs to connect to our network and based on its location the easiest place to connect it will be fabric edge. The router has a couple of net...
Hello,The http server web interface header is missing information that would be nice to have.The switch was like this during first log in.I did update the IOS/Web UI to Release 15.2.7E3 but same results.Here's a screenshot.
Hello, I own a domain name, let's call it mydomain.us, and I have a few hosts that are multihomed and have a public IP as well as a private IP, and I am trying to see if I can do the following on a Cisco 2951 router. If I want to use the same ho...
Hi Guys, I am unable to add new node to Cisco CTC. By following the standard node addition process (adding a node from File menu) I am unable to add new node to current CTC view. Any advise and suggestions are welcome BR,
I am trying to understand what the throughput capacity is for a vedge 100b GigabitEthernet port. Assuming I had a 1GB Internet connection terminated on a vedge 100B port, what is the maximum throughput rate I could achieve? I have not found an...