Multiple EEM Aborted Reason

[yanuar-saputro]

 Hi all,

I have 2 IP SLA and track and each track have EEM when they are DOWN and UP. Sometimes both IP SLA down together and multiple times. This caused the EEM in aborted. How can we know why it is aborted ?

No. Job Id Proc Status Time of Event Event Type Name
1 50 Actv success Thu Oct29 15:26:03 2026 track applet: SLA_DOWN_1

2 51 Actv success Thu Oct29 15:30:09 2026 track applet: SLA_UP_1

3 52 Actv success Thu Oct29 15:34:25 2026 track applet: SLA_DOWN_1

4 53 Actv success Thu Oct29 15:34:25 2026 track applet: SLA_DOWN_2

5 54 Actv success Thu Oct29 15:38:31 2026 track applet: SLA_UP_1

6 55 Actv success Thu Oct29 15:38:31 2026 track applet: SLA_UP_2

7 56 Actv success Thu Oct29 15:55:52 2026 track applet: SLA_DOWN_1

8 57 Actv abort Thu Oct29 15:56:03 2026 track applet: SLA_DOWN_2

9 58 Actv abort Thu Oct29 15:59:38 2026 track applet: SLA_UP_2

10 59 Actv abort Thu Oct29 15:59:48 2026 track applet: SLA_UP_1

My EEM :
event manager applet SLA_UP_2
event track 3 state up
action 1 syslog msg "IPSLA 3 is UP"
action 10 cli command "enable"
action 11 cli command "conf t"
action 12 cli command "route-map OUT2 permit 10"
action 13 cli command "no set as-path prepend 123 123"
action 14 cli command "exit"
action 15 cli command "route-map SET-LP-250 permit 10"
action 16 cli command "set local-preference 250"
action 17 cli command "end"
action 18 cli command "clear ip bgp x.x.x.89 out"
action 19 cli command "clear ip bgp x.x.x.89 in"
action 20 wait 2
action 21 cli command "clear ip bgp x.x.x.13 out"
action 22 cli command "clear ip bgp x.x.x.13 in"
event manager applet SLA_DOWN_2
event track 3 state down
action 1 syslog msg "IPSLA 3 is Down"
action 10 cli command "enable"
action 11 cli command "conf t"
action 12 cli command "route-map OUT2 permit 10"
action 13 cli command "set as-path prepend 123 123"
action 14 cli command "exit"
action 15 cli command "route-map SET-LP-250 permit 10"
action 16 cli command "set local-preference 90"
action 17 cli command "end"
action 18 cli command "clear ip bgp x.x.x.89 out"
action 19 cli command "clear ip bgp x.x.x.89 in"
action 20 wait 2
action 21 cli command "clear ip bgp x.x.x.13 out"
action 22 cli command "clear ip bgp x.x.x.13 in"
event manager applet SLA_UP_1
event track 2 state up
action 1 syslog msg "IPSLA 2 is UP"
action 10 cli command "enable"
action 11 cli command "conf t"
action 12 cli command "route-map OUT1 permit 10"
action 13 cli command "no set as-path prepend 123 123"
action 14 cli command "exit"
action 15 cli command "route-map SET-LP-150 permit 10"
action 16 cli command "set local-preference 150"
action 17 cli command "end"
action 18 cli command "clear ip bgp x.x.x.81 out"
action 19 cli command "clear ip bgp x.x.x.81 in"
action 20 wait 2
action 21 cli command "clear ip bgp x.x.x.13 out"
action 22 cli command "clear ip bgp x.x.x.13 in"
event manager applet SLA_DOWN_2
event track 2 state down
action 1 syslog msg "IPSLA 2 is Down "
action 10 cli command "enable"
action 11 cli command "conf t"
action 12 cli command "route-map OUT1 permit 10"
action 13 cli command "set as-path prepend 123 123"
action 14 cli command "exit"
action 15 cli command "route-map SET-LP-150 permit 10"
action 16 cli command "set local-preference 90"
action 17 cli command "end"
action 18 cli command "clear ip bgp x.x.x.81 out"
action 19 cli command "clear ip bgp x.x.x.81 in"
action 20 wait 2
action 21 cli command "clear ip bgp x.x.x.13 out"
action 22 cli command "clear ip bgp x.x.x.13 in"

[David Ruess]

Hello,

An EEM script can abort for several reasons such as:

-Runs too long (20 seconds max unless configured otherise)

-Incorrect syntax

-Needs confirmation after a certain command.

Have you copied all these commands into the router without the EEM script and made sure it does not error on any of the CLI commands?

-David

[yanuar-saputro]

Yes i have copy them all. But for "clear ip bgp" it takes long i think and make CPU higher cause of full route..
is this maybe the cause ?

[M02@rt37]

Hello @yanuar-saputro 

In addition to Mr Ruess answer, since both IP SLA tracks can trigger simultanously, test whether the commands from both EEM applets can execute successfully when run concurrently. A CLI command working manually does not necessarily rule out an EEM concurrency issue.

What I mean is that two eem applet can execute at almost exactly the same time when both ip sla tracks change state together...

So, instead of having four independent applets, you could consider using one centralized eem policy to evaluate both track states and make routing changes. This should avoid multiple applets independently trying to modify the same config.

[David Ruess]

Possibly. The EEM must run within 20 seconds. If the processes doesn't complete in that time it may abort. YOu can try adding the command:

event manager applet SLA_DOWN_2 maxrun 60

60 is the number of seconds the applet can take to run.

-David