IP SLA - and Event manager applet

[ChristianT1]

Good afternoon, folks, looking for some assistance on my configurations for our SBC ISR 4451 router. I am trying to conduct a failover of services to other outlying devices by inserting manual disabling of interfaces within that SBC, as described below. It functions as written, but how do I create an applet to sense when that outlying interface is restored, and "no shut" those interfaces to restore the link, WITHOUT having to console in and manually do it. Thank you!

ip sla 1
icmp-echo 10.X.X.4 source-ip 10.X.X.3
frequency 10
ip sla schedule 1 life forever start-time now

ip sla 2
icmp-echo 11.X.X.20 source-ip 11.X.X.21
frequency 10
ip sla schedule 2 life forever start-time now

ip sla 3
icmp-echo 11.X.X.24 source-ip 11.X.X.25
frequency 10
ip sla schedule 3 life forever start-time now

track 1 interface GigabitEthernet0/0/0 ip routing

track 2 interface GigabitEthernet0/0/2 ip routing

track 3 interface GigabitEthernet0/0/3 ip routing

event manager applet tdmSWDOWN
event track 1 state down
action 1 cli command "enable"
action 2 cli command "config t"
action 3 cli command "int g0/0/2"
action 4 cli command "shut"
action 5 cli command "int g0/0/3"
action 6 cli command "shut"
action 7 cli command "end"
event manager applet tdmSWMUP
event track 1 state up
action 1 cli command "enable"
action 2 cli command "config t"
action 3 cli command "int g0/0/2"
action 4 cli command "no shut"
action 5 cli command "int g0/0/3"
action 6 cli command "no shut"
action 7 cli command "end"

event manager applet SBC1dn
event track 2 state down
action 1 cli command "enable"
action 2 cli command "config t"
action 3 cli command "int g0/0/0"
action 4 cli command "shut"
action 5 cli command "end"
event manager applet SBC1up
event track 2 state up
action 1 cli command "enable"
action 2 cli command "config t"
action 3 cli command "int g0/0/0"
action 4 cli command "no shut"
action 5 cli command "end"

event manager applet SBC2dn
event track 3 state down
action 1 cli command "enable"
action 2 cli command "config t"
action 3 cli command "int g0/0/0"
action 4 cli command "shut"
action 5 cli command "end"
event manager applet SBC2up
event track 3 state up
action 1 cli command "enable"
action 2 cli command "config t"
action 3 cli command "int g0/0/0"
action 4 cli command "no shut"
action 5 cli command "end"

[David Ruess]

Are you asking about checking an interface on another device and whether or not its up? If that's the case you can create an IP SLA to track that and write another set of EEM commands to perform a set of commands from that status.

-David

[ChristianT1]

Thanks David,

If I only have those three interfaces, and they are all "shut" because I have configured them to when that "other" device is down, can I have another EEM command that could "sense" when the "other" comes back up, and "no shut" those closed interfaces?  Hope that is clearer??

[David Ruess]

If you have the 3 interfaces that connect to the other device shutdown you have cut off communication. Effectively you cant determine when that "other device" comes up because the local device has no way of getting that information.

-David

[ChristianT1]

Thank you, David,

is there another option to disable an interface without it being too restrictive...perhaps a "soft close" or "sleep" command?  Not trying to be funny, but I do understand what you are saying.    

[David Ruess · Accepted solution]

I understand what you are trying to achieve but at least one of the interfaces needs to be "no shut/open" in order to check communications on the remote device. Once it verifies connectivity your EEM scrips can enable the other interfaces. That or you can just write a script on a server/PC that can check the connectivity and enable the interfaces that way. Kind of like an OOBM scenario.

Hope that helps

-David

[ChristianT1]

Thank you David for your response and patience.

regards,

christian