EEM using IPSLA HTTP not getting the results I expect.

[jotapia32]

Hello,

I have created the configuration below, monitoring HTTP to detect Internet connectivity issue to shutdown the loopback interface when down.  The IPSLA is working but the EEM actions are not being executed.  Could you help me identify what I'm doing wrong.  We are doing this on a Cisco ISR4331 Router IOS-XE.

track 1 ip sla 1

ip sla 1
 http get http://www.google.com source-ip 40.129.90.65 name-server 66.155.216.122
 timeout 5000
ip sla schedule 1 life forever start-time now

event manager session cli username "USERNAME" privilege 15
event manager applet Internet_OK
 event track 1 state up
 action 1.0 cli command "enable"
 action 2.0 cli command "config t"
 action 3.0 cli command "interface loopback 0"
 action 4.0 cli command "no shutdown"
 action 5.0 cli command "end"
event manager applet Internet_Not_OK
 event track 1 state down
 action 1.0 cli command "enable"
 action 2.0 cli command "config t"
 action 3.0 cli command "interface loopback 0"
 action 4.0 cli command "shutdown"
 action 5.0 cli command "end"
!

[Joe Clarke · Accepted solution]

Is the tracked object transitioning state?  Enable "debug event manager action cli", reproduce the track state change and post the log output.

[jotapia32]

Hello Joe,

Thank you for the reply.  The configuration is working.  I was able to force the transitioning to have it tested.  I had the loopback interface shutdown and thought that once the IPSLA started the Even Manager Applet would take action, my mistake. 

[CATHLEEN CAVANAGH]

Hi jotapia

I think I'm having the same problem.  Can you confirm that your assume was that applet Internet_OK would enable the port, and that was the flaw?  Once you manually enabled the interface as the initial configuration, did the applets get triggered appropriately during the track state changes?

Thanks for your input!

Cathleen

[Boo]

Teach shows, "track 1 ip sla 1" instead of  "track 1 ip sea 1 reachability".
Can that be the cause of the problem Joe Clarke?

 jotapia32 , as Joe suggested debug is a good way to go. Along with that if you show track, it will show the events that are being tracked.