What does “event none” in an EEM applet mean
A member of the cisco-nsp mailing list asked an interesting question a while ago: he tried to test his EEM applet with the event manager run command and got the “Embedded Event Manager policy not registered with event none Event Detector” message.
An EEM applet (until EEM 3.02.4) can be triggered only by a single condition. If you want to trigger the applet from the command line (with the "event man run" command), it cannot be triggered by anything else. Such an applet must have "event none" pseudo-trigger.
The event none is used to indicate that "no trigger" is actually what you want to do (as opposed to "I forgot to specify the trigger").
This article is part of You've asked for it series.
I wrote down my applet:
event manager applet Fiber_Down
event track 1 state down
action 1 cli command "enable"
action 2 cli command "configure terminal"
action 3 cli command "int gi0/1"
action 4 cli command "ip address 192.168.1.102 255.255.255.0"
action 5 cli command "exit"
action 6 syslog priority critical msg "Cisco becomes gateway"
Also I configured the track object:
show track 1
Track 1
IP SLA 1 state
State is Up
1 change, last change 00:11:16
Delay up 5 secs, down 3 secs
Latest operation return code: OK
Latest RTT (millisecs) 1
Tracked by:
EEM applet Fiber_Up
EEM applet Fiber_Down
What else should l do to "start" the EEM applet? Or is it already ACTIVE?
Every applet is triggered by a tracking object, no need to "start it" or make it active.