Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Attention: The Cisco Support Community site will be in read only mode on Dec14, 2017 from 12:01am PST to 11:30am for standard maintenance. Sorry for the inconvenience.

New Member

EEM applet for "no shutdown" of the external interface

Hi,

I needed 2 applets for failover;

1)one to down the interface when it finds the DNS interface down.

2) 2nd to Up the interface when it finds the DNS interface up.

Now, The "down applet" works fine, but "Up applet" doesn't.

Can you please check what mistake am i making? Also, If I keep one IP SLA for both EEM applets (for up and down).Will that be ok?

ip sla 443

tcp-connect 10.10.1.1 443 control disable

frequency 60

ip sla schedule 443 life forever start-time now

track 443 rtr 443 reachability

delay down 60 up 60

event manager applet server_up_example

event track 443 state up

action 01.0 syslog msg "TCP service is available"

action 02.0 cli command "enable"

action 03.0 cli command "config t"

action 03.0 cli command "interface gig0/0"

action 04.0 cli command "no shut"

action 05.0 syslog msg

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

OUTPUT (somthing like this. It doesn;t Up the interface. while for down it works fine)

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

Round Trip Time (RTT) for Index 1

Type of operation: icmp-echo

Latest RTT: 1 ms

Latest operation start time: 10:02:15.190 UTC Thu Aug 20 2009

Latest operation return code: OK

Number of successes: 0

Number of failures: 4

Operation time to live: Forever

2 REPLIES
New Member

Re: EEM applet for "no shutdown" of the external interface

I found the problem. I was making it down using cli command for testing purposes. When i tried with physical wire plug in and out, it start working fine.

Cisco Employee

Re: EEM applet for "no shutdown" of the external interface

The actual state of the IP SLA collector isn't as important as the state of the tracked object. Even if you shutdown an interface manually, if the collector cannot reach 10.10.1.1, then it will go down, and 60 seconds later, so should the tracked object.

Typically, when I'm testing this kind of thing, I use a black hold route. For example:

ip route 10.10.1.1 255.255.255.255 null0

This way, I don't lose other connectivity, and I can still check whether or not the IP SLA collector, EOT, and EEM functions are working.

And, yes, one collector, and one tracked object is fine for what you want to do.

207
Views
0
Helpful
2
Replies
CreatePlease to create content