in my example i am using a real world example of a problem that really annoyed me.
I have a ATA (for phone connectivity) connected to interface FastEthernet0 of my ISR881W.
I got sick of getting phantom/anonymous calls at weird hours of the morning, so i setup a simple Embedded Event Manager (EEM) script to shut down FastEthernet 0 at 1am.
Also set up another script to enable the interface at 7am.
I really don't want phone calls between the hours of 1am to 7am .
The IOS documentation mentioned the need to create a couple of extra vty interfaces for both of my CLI scripts, I just added, because I was lazy; line vty 5 15. Not sure why cisco couldn't allow for the CLI commands without creating extra vty interfaces"
But suffice to say, I am only using a very limited subset of EEM commands. Lots of tremendous functionality with many examples at cisco.com
If i try to manually run the script, i get an errior as shown below, not very descriptive .
Raleigh#event manager run applet ATAon EEM policy applet not registered with event none Event Detector
But at 1am fastEthernet 0 DOES shutdown. So my only way to test the functionality was to manually alter the time in the script and watch the LED corresponding to FastEthernet 0 or the console interface messages.
Hope this example is useful, it made my household a little quieter at the wee early hours and ties me to a 881W with this pseudo triggering functionality