EEM not start despite the fact that response of the track is down

[josedunet]

Hello all,

I am trying to configure an EEM which shutdown and interface when the track is down but i remark that the action of EEM not start despite that every seem good. Here is the config :

ip sla 5

icmp-echo 8.8.8.8

timeout 20000

threshold 15000

frequency 25

ip sla schedule 5 life forever start-time now

track 1 ip sla 5

event manager applet SET-DOWN-INTERFACE

event track 1 state down

action 1.0 cli command "enable"

action 1.1 cli command "conf t"

action 1.2 cli command "int fastethernet 0/0"

action 1.3 cli command "shutdown"

action 1.4 cli command "end"

action 1.5 cli command "exit"

- --------------------

SHow command :

#sh ip sla statisti

IPSLA operation id: 5

Type of operation: icmp-echo

        Latest RTT: NoConnection/Busy/Timeout

Latest operation start time: *14:07:36.962 UTC Thu Nov 17 2011

Latest operation return code: Timeout

Number of successes: 0

Number of failures: 6

Operation time to live: Forever

#sh track brief

Track   Object                           Parameter        Value      Last Change

1            ip sla      5                    state            Down       01:09:39

Despite the fact that everything is down, EEM does not execute. Who can help me ?

Thanks in advance.

[Joe Clarke]

Enable "debug event manager action cli" then bounce the tracked object to get the policy to run again.  What debugging output do you see?

[josedunet]

Hi Clarke,

The debug event manager action cli send nothing.

I do also debug event manager all. I just have this periodly :

001294: *Nov 18 08:58:00.002 UTC: fh_fd_timer_process_async

001295: *Nov 18 08:58:00.002 UTC: cron_tick: num_matches 0

It's seem that it was unable to receive the result of the track to trigger actions.

I do :

debug event manager detector cli

debug event manager detector  track

debug event manager detector ipsla

But nothing.

[Joe Clarke · Accepted solution]

Is the tracked object changing state?  That is, are you able to get the object to transition to up then down again?  That needs to happen for the applet to execute.  From your IP SLA show command output, it does not appear the collector is ever succeeding.

[smitesh kharecha]

Hi,

Is your track configured for reachability or state ??

Regards,

Smitesh

[josedunet]

Hi Joseph,

Yes it's becausethe tracked object doesn't changing. I do the test with tracked changing and it's okay.

Thanks all.

[josedunet]

Hi  Smitesh,

How can I configure the eem to checked state of two track before performing an action.

the State of the two track must be down or UP for example that it execute action

If i take my config above :

ip sla 5

icmp-echo 8.8.8.8

timeout 20000

threshold 15000

frequency 25

ip sla schedule 5 life forever start-time now

ip sla 5

icmp-echo 8.8.8.8

timeout 20000

threshold 15000

frequency 25

ip sla schedule 5 life forever start-time now

ip sla 10

icmp-echo 4.4.4.4

timeout 20000

threshold 15000

frequency 25

ip sla schedule 5 life forever start-time now

track 1 ip sla 5

track 2 ip sla 10

How configure the event manager to doconfigure an interface only when the state of this two track is down or UP

event manager applet SET-DOWN-INTERFACE

?????

Best Regards

[Joe Clarke]

You can do one of two things.  You can either create a boolean tracked object or use multiple event detectors.  For example, to use a boolean tracked object, do:

track 3 list boolean and

object 1

object 2

Then you can track object 3 with your EEM policy.